# Project Description

## Distributed Intelligent Poultry Farm Environmental Control System (DIPFECS)

## 1\. Purpose of the System

The purpose of the **Distributed Intelligent Poultry Farm Environmental Control System (DIPFECS)** is to provide **continuous monitoring, real-time control, and data-driven optimization** of indoor poultry farm environments using a **hierarchical IoT architecture**, **edge computing**, and **cloud-based analytics and machine learning (ML)**.

The system is designed to **maximize animal welfare, production efficiency, energy efficiency, and operational reliability**, while ensuring **scalability across multiple farms and geographical locations**.

## 2\. System Scope

The system covers **indoor poultry houses** (broiler, layer, breeder, pullet) and includes:

*   Environmental sensing
    
*   Data acquisition and validation
    
*   Local real-time control
    
*   Actuator management
    
*   Alarm handling
    
*   Data logging and analytics
    
*   Cross-farm optimization via cloud services
    

The system explicitly **excludes** open-house farms and manual-only operations.

## 3\. System Architecture Overview

The system follows a **three-tier hierarchical architecture**:

1.  **Sub-Hub Layer (Sensor Layer)**
    
2.  **Main Hub Layer (Edge Control Layer)**
    
3.  **Central Server Layer (Cloud Intelligence Layer)**
    

Each tier has a **well-defined functional responsibility** and operates independently in case of upstream or downstream communication failures.

## 4\. System Decomposition

### 4.1 Sub-Hub Subsystem (SHS)

**Abbreviation:** SH  
**Typical Hardware:** ESP32 or equivalent MCU

#### 4.1.1 Functional Description

The Sub-Hub Subsystem (SHS) is responsible exclusively for **local data acquisition, basic preprocessing, and mini-calibration** of connected sensors.

SHS units are deployed in **high density** within each poultry house to provide **spatial granularity** of environmental data.

#### 4.1.2 Sensor Interfaces

Each Sub-Hub may interface with one or more of the following sensor types:

<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><thead class="op-uc-table--head"><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Parameter</p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Abbreviation</p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Unit</p></th></tr></thead><tbody><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Air Temperature</p></td><td class="op-uc-table--cell"><p class="op-uc-p">T</p></td><td class="op-uc-table--cell"><p class="op-uc-p">°C</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Relative Humidity</p></td><td class="op-uc-table--cell"><p class="op-uc-p">RH</p></td><td class="op-uc-table--cell"><p class="op-uc-p">%</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Ammonia</p></td><td class="op-uc-table--cell"><p class="op-uc-p">NH₃</p></td><td class="op-uc-table--cell"><p class="op-uc-p">ppm</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Carbon Dioxide</p></td><td class="op-uc-table--cell"><p class="op-uc-p">CO₂</p></td><td class="op-uc-table--cell"><p class="op-uc-p">ppm</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Carbon Monoxide</p></td><td class="op-uc-table--cell"><p class="op-uc-p">CO</p></td><td class="op-uc-table--cell"><p class="op-uc-p">ppm</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Oxygen (optional)</p></td><td class="op-uc-table--cell"><p class="op-uc-p">O₂</p></td><td class="op-uc-table--cell"><p class="op-uc-p">%</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Light Intensity</p></td><td class="op-uc-table--cell"><p class="op-uc-p">LUX</p></td><td class="op-uc-table--cell"><p class="op-uc-p">lux</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Air Velocity (optional)</p></td><td class="op-uc-table--cell"><p class="op-uc-p">AV</p></td><td class="op-uc-table--cell"><p class="op-uc-p">m/s</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Static Pressure (optional)</p></td><td class="op-uc-table--cell"><p class="op-uc-p">SP</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Pa</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Dust Particulate (optional)</p></td><td class="op-uc-table--cell"><p class="op-uc-p">PM₂.₅ / PM₁₀</p></td><td class="op-uc-table--cell"><p class="op-uc-p">µg/m³</p></td></tr></tbody></table></figure>

#### 4.1.3 Local Processing

The Sub-Hub shall perform:

*   Sensor sampling
    
*   Noise filtering
    
*   Offset correction
    
*   Basic plausibility checks
    
*   Timestamping
    

The Sub-Hub **shall not** perform any control decisions.

#### 4.1.4 Communication

*   Wireless uplink to Main Hub
    
*   Supported protocols (configurable):
    
    *   Wi-Fi
        
    *   Zigbee
        
    *   LoRa / LoRaWAN
        
    *   Proprietary RF
        

### 4.2 Main Hub Subsystem (MHS)

**Abbreviation:** MH  
**Location:** One per poultry house / room

#### 4.2.1 Functional Description

The Main Hub Subsystem is the **primary real-time control unit** of the poultry house.

It aggregates sensor data from all Sub-Hubs, executes **control algorithms**, and drives physical actuators through a **wired control interface**.

#### 4.2.2 Data Aggregation

The Main Hub shall:

*   Receive data from all connected Sub-Hubs
    
*   Perform spatial averaging and zoning
    
*   Detect anomalies and sensor faults
    
*   Maintain a local historical buffer
    

#### 4.2.3 Control Functions

The Main Hub shall execute:

*   Closed-loop environmental control
    
*   Rule-based logic
    
*   PID / proportional control
    
*   Fuzzy logic (optional)
    
*   ML-assisted parameter adaptation (optional)
    

#### 4.2.4 Actuator Interfaces

The Main Hub shall control the following actuators via a Control Board (CB):

<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><thead class="op-uc-table--head"><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Actuator</p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Abbreviation</p></th></tr></thead><tbody><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Ventilation Fans</p></td><td class="op-uc-table--cell"><p class="op-uc-p">FAN</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Air Inlets / Curtains</p></td><td class="op-uc-table--cell"><p class="op-uc-p">INL</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Heaters (Radiant / Forced)</p></td><td class="op-uc-table--cell"><p class="op-uc-p">HTR</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Cooling Pads / Foggers</p></td><td class="op-uc-table--cell"><p class="op-uc-p">CLG</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Lighting Systems</p></td><td class="op-uc-table--cell"><p class="op-uc-p">LGT</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Feeding Systems</p></td><td class="op-uc-table--cell"><p class="op-uc-p">FDR</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Drinking Systems</p></td><td class="op-uc-table--cell"><p class="op-uc-p">WTR</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Alarm Devices</p></td><td class="op-uc-table--cell"><p class="op-uc-p">ALM</p></td></tr></tbody></table></figure>

Control signals may include:

*   Relay (ON/OFF)
    
*   0–10 V
    
*   PWM
    
*   Modbus RTU/TCP
    
*   CAN Bus
    

#### 4.2.5 Local Autonomy

The Main Hub shall maintain **full operational capability** during:

*   Internet loss
    
*   Cloud service unavailability
    
*   Partial Sub-Hub failures
    

### 4.3 Central Server Subsystem (CSS)

**Abbreviation:** CS  
**Deployment:** Cloud or Hybrid

#### 4.3.1 Functional Description

The Central Server Subsystem provides **cross-farm data aggregation, analytics, and intelligence**.

It is responsible for **learning from all farms collectively** and improving control strategies continuously.

#### 4.3.2 Data Management

The Central Server shall:

*   Store time-series data
    
*   Maintain farm profiles
    
*   Support long-term historical analysis
    
*   Enable benchmarking across farms
    

#### 4.3.3 Machine Learning &amp; Analytics

The Central Server shall:

*   Train ML models using aggregated farm data
    
*   Identify optimal environmental setpoints
    
*   Detect patterns related to performance, health, and energy
    
*   Generate optimized control parameters
    

#### 4.3.4 Feedback Loop

The Central Server shall:

*   Send updated control parameters or models to Main Hubs
    
*   Support OTA firmware and configuration updates
    
*   Allow gradual rollout and rollback of updates
    

## 5\. Communication Architecture

<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><thead class="op-uc-table--head"><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Link</p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Direction</p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Protocol</p></th></tr></thead><tbody><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Sensors → Sub-Hub</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Wired</p></td><td class="op-uc-table--cell"><p class="op-uc-p">I²C, SPI, UART, Analog</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Sub-Hub → Main Hub</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Wireless</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Wi-Fi / Zigbee / LoRa</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Main Hub → Control Board</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Wired</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Modbus, Relay, CAN</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Main Hub ↔ Central Server</p></td><td class="op-uc-table--cell"><p class="op-uc-p">IP-based</p></td><td class="op-uc-table--cell"><p class="op-uc-p">MQTT / HTTPS / TLS</p></td></tr></tbody></table></figure>

All external communications shall be **encrypted**.

## 6\. Alarm and Safety Management

The system shall support:

*   Threshold-based alarms
    
*   Rate-of-change alarms
    
*   Sensor failure alarms
    
*   Communication failure alarms
    
*   Power failure alarms
    

Alarms shall be:

*   Local (audible/visual)
    
*   Remote (SMS, email, app notification)
    

## 7\. Scalability and Deployment

The system shall support:

*   Multiple Sub-Hubs per house
    
*   Multiple houses per farm
    
*   Multiple farms per server
    
*   Global multi-tenant operation
    

## 8\. Compliance and Industry Alignment

The system design aligns with:

*   Modern poultry automation practices (Big Dutchman, Fancom, SKOV, Hotraco)
    
*   Animal welfare standards
    
*   Environmental monitoring best practices
    
*   Industrial IoT architectures (Edge + Cloud)
    

## 9\. System Key Characteristics (Summary)

<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><thead class="op-uc-table--head"><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Attribute</p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Value</p></th></tr></thead><tbody><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Architecture</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Distributed, Hierarchical</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Control</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Local real-time + Cloud optimization</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Intelligence</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Edge + Central ML</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Reliability</p></td><td class="op-uc-table--cell"><p class="op-uc-p">High (local autonomy)</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Scalability</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Very High</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Vendor Lock-in</p></td><td class="op-uc-table--cell"><p class="op-uc-p">None</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Sensor Density</p></td><td class="op-uc-table--cell"><p class="op-uc-p">High</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Update Mechanism</p></td><td class="op-uc-table--cell"><p class="op-uc-p">OTA</p></td></tr></tbody></table></figure>

## 10\. Project Vision Statement

**DIPFECS is designed to become a scalable, intelligent, and adaptive poultry farm control platform that continuously improves environmental control strategies by combining dense sensing, robust local automation, and global data intelligence.**