AI-Enabled Project Management Control Tower

Automated alert engine

Source-linked notifications · escalation rules · preview & audit evidence
SIMULATION · NO EMAILS SENTRAG: checking
Demonstration scope: rule-based evaluation of the identical fictional registers used by Deliverables 2 and 3. A notification shown here is a preview, not an actual Teams or email message. Approval age uses the record's updatedAt as a labelled proxy because the dataset has no formal approvalRequestedAt. Any RAG transition is hypothetical until a previous approved snapshot is connected.

Notification queue

Click an alert to review message text, underlying evidence, and escalation rationale.

0 records
Notification / evidenceOwner / recipientsPriorityEscalationSimulation state

Selected message preview

Recipient, subject, action and source record

Select a row to inspect the full message.

Recent simulation events

Generated on this browser only

Governance boundaries

An alert never substitutes for formal approval. Acknowledging a notice does not resolve a risk, approve a requirement, or suppress mandatory escalations. Real delivery requires approved recipient mappings, durable storage, working-day/holiday calendars, and authorized Teams/email connectors.

Eight notification automation rules

Business rules and escalations are configurable proposals for assessment, not policy already approved.

Governed registers→Scheduled / change trigger→Validate + calculate→Deduplicate→Owner or escalation route→Audit + close
RuleTriggerRecipients / channelAction / escalation

Simulation audit log

Immutable in production. This local example log can be reset.

State transitions are logged when a user clicks Simulate dispatch or Acknowledge. Running the rules previews current conditions and does not send anything. Replaying the same alert key does not create duplicate dispatch events in this browser.

Data exchange and deployment controls

Reusable with the Deliverable 2 dashboard JSON export and Deliverable 3 agent.

Production workflow design

Power Automate scheduled cloud flow (weekday 08:00 Asia/Dubai) and SharePoint/Dataverse item-change events → read governed lists with least-privilege service identity → validate required dates, status and ownership → evaluate rules → write a notification outbox item with an idempotency key → send via approved Teams/email connector → record delivery attempt and retry status → escalate through a separate timer-driven flow → close/suppress only when source state or approved exception warrants it.

Safety and implementation boundaries

The demo runs entirely client-side; no real connector, recipients' emails, push notifications, scheduling service, authentication or server-side audit store. Import only fictional or non-sensitive data. Production must support RBAC, error and dead-letter queues, exception monitoring, local holidays, quiet hours, retention policy and change-controlled escalation thresholds.