7.1 Supporting Infrastructure Overview

The smart campus environmental monitoring system depends on a range of supporting infrastructure systems that must be planned and provisioned as part of the overall deployment. These supporting systems span six categories: power and protection, network infrastructure, mounting and enclosure, calibration and maintenance tools, alarm and output systems, and data integration interfaces. Failure to adequately plan any of these supporting categories is a common cause of project delays and post-deployment reliability issues.

The integrated supporting equipment diagram below illustrates the complete ecosystem of supporting systems and their relationship to the central monitoring platform. Each category contains multiple components that must be specified, procured, installed, and commissioned as part of the overall system delivery. The diagram serves as a planning checklist to ensure that no supporting system is overlooked during project scoping.

Integrated supporting equipment diagram for smart campus environmental monitoring

Figure 7.1: Integrated Supporting Equipment Diagram — All Supporting Systems in a Single View

7.2 Power and Protection Requirements

Reliable power supply is the foundation of continuous monitoring. Power interruptions cause data gaps that may be unacceptable for compliance monitoring applications. The power design must address the primary power source, backup power duration, surge protection, and power quality requirements for each monitoring station. Solar-assisted systems require careful battery sizing to ensure adequate backup during extended low-irradiance periods.

ComponentSpecificationPurposeSizing Guidance
AC mains supply220V AC, dedicated circuit, 10A MCBPrimary power for fixed stationsOne circuit per cabinet; no shared circuits with other loads
24VDC power supplyDIN rail, 24V/5A minimum, CE/ULSensor and gateway powerSize for 150% of connected load; derating for temperature
UPS battery backupOnline or line-interactive; 4–8h backupContinuity during power outageCalculate load × backup hours; add 20% margin
Solar panel + controller20–100W panel; MPPT controller; 12V/24VRemote station primary or backup powerSize for worst-case irradiance month; 3-day battery reserve
Surge protection (AC)Type 2 SPD, 20kA, DIN railLightning surge protection on AC inputCoordinate with upstream MCB; replace after major strike
Surge protection (RS485)RS485 SPD, 3kA minimum, DIN railLightning protection on sensor cablesInstall at both ends of long cable runs
Earth rod and bondingCopper-clad steel rod, ≥2.4m; <10Ω resistanceSafety grounding and SPD discharge pathMeasure resistance after installation; add rods if needed

7.3 Network Infrastructure Requirements

The network infrastructure supporting the monitoring system must provide reliable, secure connectivity from field sensors to the cloud platform. Network planning must consider the coverage requirements of each sensor type, the bandwidth requirements of the data streams, the latency requirements of alarm paths, and the redundancy requirements of the overall system. The network design must be documented and reviewed by the IT security team before deployment.

Infrastructure ComponentSpecificationCoverage / CapacityKey Requirement
4G LTE router/gatewayIndustrial grade, dual SIM, -20 to +60°CPark-wide cellular coverageDual SIM for carrier redundancy; VPN support
LoRa gateway8-channel, outdoor IP65, 4G backhaul300–1000m radius per gatewayAntenna height ≥5m; avoid metal obstructions
Fiber switchIndustrial managed, DIN rail, SFP portsBuilding or zone backboneVLAN support; SNMP monitoring; redundant power
Wi-Fi access pointWi-Fi 5 or 6, outdoor IP67, PoE powered50–100m radius per APWPA3 security; separate SSID for sensors
NB-IoT moduleCat-NB1/NB2, low power, DIN rail or embeddedNational coverage via carrierPSM/eDRX for battery life; carrier SLA required
Network managementSNMP/NetFlow monitoring; centralized NMSAll network devicesAlert on link down; bandwidth utilization monitoring

7.4 Third-Party System Integration

The environmental monitoring platform must integrate with multiple third-party systems to deliver its full value. Integration with the Building Management System (BMS) enables correlation of environmental data with HVAC operation and energy consumption. Integration with the EHS management system enables automatic population of compliance reports and incident records. Integration with the property management system enables tenant notification and service request generation.

All integrations must use documented, versioned APIs with authentication and rate limiting. Integration points must be tested during commissioning and monitored in production to detect failures. A data dictionary must be maintained to document the field mapping between the monitoring platform and each integrated system, ensuring that data is correctly interpreted by all consumers.

Integration TargetProtocol / APIData ExchangedIntegration PriorityKey Requirement
Building Management System (BMS)BACnet/IP, Modbus TCP, REST APIEnvironmental readings, alarm states, HVAC setpointsHighBi-directional; real-time; data dictionary alignment
EHS Management SystemREST API, SFTP (report files)Compliance data, alarm events, calibration recordsHighAudit trail; data integrity; regulatory format
Property Management SystemREST API, webhookAlarm notifications, tenant reports, work ordersMediumTenant data isolation; RBAC; notification routing
SCADA / DCSOPC-UA, Modbus TCPReal-time sensor values, alarm statesMediumLatency <5s; data quality flags passed through
Regulatory reporting portalXML/CSV upload, REST APICompliance data in regulatory formatHighFormat compliance; digital signature; submission log
Energy management systemREST API, Modbus TCPEnergy meter readings, demand dataMediumTime synchronization; meter accuracy verification
GIS / mapping platformREST API, WMS/WFSSensor locations, zone boundaries, plume mapsLowCoordinate system alignment; real-time update

7.5 Alarm and Output Integration

Alarm integration ensures that environmental excursions trigger appropriate responses from the relevant stakeholders. The alarm routing matrix defines which alarms are sent to which recipients through which channels, based on the alarm severity, the affected zone, and the time of day. Multi-channel alarm delivery — combining platform notifications, SMS, email, and local beacon — ensures that critical alarms reach the responsible party even when one channel is unavailable.

Alarm SeverityResponse Time TargetNotification ChannelsEscalation PathDocumentation
Critical (safety)<60 secondsLocal beacon + siren + SMS + platform pushEHS officer → Site manager → Emergency servicesAuto-generated incident record
High (compliance)<5 minutesPlatform push + SMS + emailEHS officer → Compliance managerAlarm log + evidence package
Medium (operational)<30 minutesPlatform push + emailO&M team → Facility managerWork order generation
Low (informational)Next business dayDaily digest emailO&M teamTrend report
Sensor health<4 hoursPlatform push + emailO&M teamMaintenance ticket