Commuter Facility Equipment Monitoring

A monitoring replacement with an operational purpose

CFEMS relates to Singapore Land Transport Authority sites managed by Surbana Jurong. The project replaces a legacy system for monitoring lifts, escalators, and mechanical equipment. Its purpose is continuous equipment visibility, anomaly reporting to the responsible departments, and maintenance scheduling in a shared application.

My role covered requirement analysis, team leadership, system design, implementation, and cloud delivery. High availability was part of the stated engineering scope.

Separate telemetry, application, and operational responsibilities

Telemetry integration · EMQX

EMQX is part of the documented equipment-data stack. Telemetry integration connects incoming equipment information with the monitoring application.

Application services · C#/.NET, DDD, CQRS

The backend uses microservices, with DDD and CQRS included in the project stack. The functional scope spans equipment monitoring, anomaly reporting, and maintenance workflows.

Persistence and live views · SQL Server, SignalR, Angular

SQL Server supports the application data layer. SignalR provides real-time notifications to the Angular application, connecting backend events with the operational view.

Enterprise integration · Azure Integration Services

I built published APIs with API Management, messaging and event integrations with Service Bus and Event Grid, and processing/workflows with Azure Functions and Logic Apps.

Delivery and visibility · Azure DevOps, Kubernetes, Prometheus, Grafana

I designed and deployed containerized microservices on Azure using Docker and Kubernetes, set up CI/CD, and worked with the project's monitoring stack.

From an equipment update to operational action

1. Monitor equipment conditionIncoming equipment information contributes to continuous monitoring and status visibility.
2. Make the status available to usersThe backend and real-time notification layer support an up-to-date operational interface.
3. Report an anomaly to the responsible teamAnomaly reporting connects the monitoring function with the department or personnel who need to respond.
4. Manage maintenance workMaintenance schedules are managed alongside equipment monitoring in the application.

This is the functional operating flow. The exact anomaly rules, field protocols, and notification delivery channels belong to the implementation details of the deployed system.

Engineering leadership and production delivery

• Led the team through requirements, architecture, design, and development.
• Connected telemetry, application services, live updates, and enterprise integration responsibilities.
• Designed and deployed the microservices environment with Docker and Kubernetes on Azure.
• Established Azure DevOps delivery pipelines and applied OWASP secure development practices.

The delivery joined a live monitoring application with maintenance management and anomaly reporting. That combination is the capability to highlight: connecting an equipment signal to a usable operational workflow, while owning the engineering and release path.