Türkçe 
English 
Notification Management is the orchestration layer within the BMS that ensures alerts and events generated are delivered at the right time, through the right channel, and to the right person. The goal is to capture the threshold that will motivate operations teams to take action, reduce noise, ensure delivery, and establish a communication flow that is consistent with organizational policies. For details and scope, see Notification Management.
Notification Management: Purpose and Scope
The role of the notification layer
Events generated in the Monitoring and Alert Management layers are delegated to Notification Management with channel selection, target audience, priority, scheduling, and escalation policies. This ensures critical events are delivered without delay, major events in shift workflows, and minor events in aggregate summaries.
Channels and communication strategy
Multi-channel
Email, SMS, mobile push notifications, voice calls, WhatsApp/Teams/Slack, web notifications, and webhooks.
Smart Sorting
First mobile push → then SMS → then voice call; stop the chain if an answer is received.
Maintenance & Quiet Hours
Maintenance windows muted; critical events only during nighttime hours.
Localization
Multilingual templates, unit conversion (°C/°F, kW/kBTU/h), time zone differences.
Templates, context, and action-orientedness.
Notifications are standardized using a template library: subject, body, summary, link, and CTA fields. Contextual elements (equipment name, location, latest trend, relevant work order link) indicate the operator's " next step ". Rich content (graphics, mini-tables) is used when necessary.
Targeting and role-based guidance.
Notification targets are defined by role (energy, facility, HSE, security), location (building/block/floor/zone), specialization (HVAC, electrical, IAQ), and shift information. With RBAC, only authorized personnel have access to alert details. Integration with on-call calendars and shift schedules provides 24/7 coverage.
Noise control and speed limiting.
- Debounce: Skip temporary bounces; report if it's permanent for X seconds.
- Consolidation: Reducing events stemming from the same root cause into a single statement.
- Rate limit: Set an upper limit on the number of notifications per minute/half hour.
- Priority matrix: Critical → immediate; major → short chain; minor → daily summary.
Reliable distribution and guaranteed delivery.
Provider backup (multi-carrier SMS, multi-email gateway), retry and failover flows ensure delivery. End-to-end visibility is provided with delivery receipt, open/open, and click metrics.
Subscription management and GDPR compliance.
Users can specify topic- based subscriptions (Energy, IAQ, Security), frequency (instant/hourly/daily), and channel preferences (email/SMS/mobile). Policies regarding explicit consent, minimization, masking, and deletion are applied in accordance with KVKK/GDPR.
Accountability and traceability
Each notification is tracked with event ID, rule version, target list, channel, submission time, delivery status, ACK time, and closing note. Audit trail provides a set of evidence for internal and external audits.
Centra Approach and Implementation Roadmap
Modular components
Notification Orchestra
Rule mapping, channel selection, priority matrix, quiet hours, maintenance modes, dynamic target lists.
Template & Language Management
Multilingual templates, localization and unit conversions; versioning and approval workflows.
Shipping Layer
SMTP/SMS gateway, push services, voice call integrations; retry/failover policies.
Observability
Delivery/open/open metrics, error rate, speed limit, warning hygiene signs.
Security & Compliance
RBAC, MFA, TLS, daily signing, GDPR compliance checks, data lifecycle management.
Integrations
CMMS/FM work order, Teams/Slack, WhatsApp Business, webhook and REST/GraphQL API.
KPI and SLO set
- Delivery Rate: Email ≥99%, SMS ≥98%, push ≥97%.
- First Aid: Median response time in critical events <15 min.
- False-positive: ≤5%, repeated reporting ≤10%.
- Performance: Median production→delivery delay <30 sec.
- Compliance: Auditable coverage >95%, consent record integrity 100%.
Use cases
Energy & Demand Response
When peak demand approaches, the chain is: push→SMS→call; simultaneously, a CMMS job is sent to the energy manager.
IAQ & Comfort
CO2 above 900 ppm and occupancy=1: zone manager receives a pushback; if it doesn't improve in 15 minutes, escalation occurs .
Security Scenarios
Correlation between smoke and pressure drop: voice call to the security team, SMS to the building manager.
Maintenance & Reliability
Compressor cycle count anomaly: push notification to technical team + work order link, parts stock alert.
Implementation roadmap
Stage Explanation Outputs
1) Discovery & Design Stakeholder analysis, channel inventory, priority matrix, quiet hours, and consent policies are determined. Target architecture, notification templates, security, and SLO plan.
2) Pilot In the selected building/zone, critical and major flows are activated, and delivery metrics are measured. Baselines, noise analysis, tuning list, training.
3) Scaling Multi-building deployment, template standardization, provider backup, and automation playbooks. Institutional library, documentation, training materials.
4) Continuous Improvement Monthly alarm/notification hygiene, rate targets, new channels and integrations. SLA/SLO reports, earnings report, release notes.
FAQ (short)
- Will it work with the existing BMS? Yes; it integrates with open protocols and APIs.
- Channels? Email, SMS, mobile push, voice call, Teams/Slack, webhook.
- Noise control? Debounce, merge, rate limit, quiet hours.
- Compliance? KVKK/GDPR consent and minimization; auditable traces.
- Failover? Multiple provider and automated retry strategies.
In short, Notification Management guarantees the “ last meter ” of information in the BMS: the right content meets the right channel and the right person. Operational excellence, energy efficiency, and sustainability goals are measurably supported through intelligent targeting, templating, noise control, and delivery reliability.
