Case Study: Taoyuan International Airport — CCTV & Perimeter Security Equipment Maintenance System (EMMS/FSM)

Project Code: union
Category: Equipment Maintenance Management System (EMMS) / Field Service Management (FSM)
Status: Active Development
Client: Taoyuan International Airport (Tao Yuan Guo Ji Ji Chang)
Industry: Critical Infrastructure / Aviation Security

1. Project Name

Airport EMMS/FSM — An integrated Equipment Maintenance Management and Field Service Management system for Taoyuan International Airport's CCTV and electronic perimeter security infrastructure, covering thousands of devices across multiple terminals and cargo zones.

2. Core Technology Stack

Custom Apps Built (Existing):
cores · frontend (field worker mobile UI) · hr · project_management · service · user_profiles · vendor · credentials

Custom Apps Planned:
assets (device registry) · work_orders (PM/CM/alarm test) · fsm (scheduling & workforce) · audit (compliance sign-off & immutable logs)

3. The Challenge (The Problem)

Critical infrastructure at a major international airport demands a level of equipment governance that generic CMMS (Computerised Maintenance Management Systems) cannot provide:

1. Scale and heterogeneity: Thousands of devices — IP cameras, controllers, network switches, electronic fence sensors — distributed across T1, T2, cargo facilities, and car parks, each with its own maintenance lifecycle, fault code library, and SOP.
2. Compliance and non-repudiation: The airport authority requires every maintenance action to be documented with an immutable audit trail — GPS-stamped site arrival, photographic proof, technician electronic signature — with tamper-evident Hash verification. Paper-based and informal systems cannot satisfy this requirement.
3. 24/7 fault response SLA: Corrective maintenance (CM) work orders triggered by fault alarms must reach a field technician within 15 minutes and be actioned before contractual SLA breach — a timeline incompatible with manual dispatch workflows.
4. Workforce compliance: Shift scheduling must enforce contractual minimum staffing levels and prevent conflicts with approved leave — a constraint generic HR tools cannot model against real-time work order demand.

4. The Solution (The Implementation)

Feature 1: Work Order Dispatch Centre with SLA Countdown

The custom Dispatch Centre provides a real-time Kanban board (Unassigned → In Progress → Awaiting Review → Completed) where supervisors see all open work orders colour-coded by urgency. CM fault work orders display a live SLA countdown timer; those approaching breach automatically escalate with push notifications. An automated vendor/technician recommendation engine filters by: skill match → service zone → current shift availability → rating — and surfaces the top 3 candidates, enabling a supervisor to complete a dispatch in under 2 minutes rather than the previous 5–8 minute manual process.

Feature 2: Mobile Field Operation Interface (GPS + Force-Photo + e-Signature)

The frontend app is a mobile-first RWD interface optimised for on-site use by maintenance technicians wearing gloves in variable-light environments (minimum 52px touch targets, 18px minimum font, high contrast). Every work order execution requires: GPS arrival check-in (coordinate validated against device location), step-by-step photographic evidence (mandatory per step, cannot be skipped), and a handwritten electronic signature on completion. All data is stored with cryptographic Hash values — making every completed work order tamper-evident. The interface supports offline operation: all inputs are stored locally and auto-synced when connectivity is restored.

Feature 3: Immutable Audit Chain with Hash Verification

The audit app computes a SHA-256 Hash over the complete work order record (all fields + photo references + GPS coordinates + timestamps) at the moment of technician submission. This Hash is stored in an immutable field. Any subsequent addition to the record (e.g., supervisor annotation) creates a new record version with a new Hash, preserving the full history. The airport authority can trigger a one-click Hash Verification on any work order at any time — if the current data Hash matches the stored Hash, the record is certified unmodified.

Feature 4: Preventive Maintenance Scheduler

The fsm app manages annual PM scheduling: a supervisor defines a device type, maintenance interval, and auto-generation lead time (e.g., "generate work order 7 days before due"). The system generates all future PM work orders automatically and displays them on a calendar view. Overdue PM work orders trigger escalation notifications — ensuring the contractual PM execution rate ≥ 95% is measurable and enforceable.

5. Business Impact (The Result)

• SLA compliance is measurable and automated: Previously, SLA breach tracking required manual log cross-referencing after the fact. The system now surfaces SLA risk in real time, enabling preventive action rather than post-breach reporting.
• Eliminated paper-based audit trail: Every maintenance action now generates a permanent, tamper-evident digital record — satisfying the airport authority's compliance requirements for critical infrastructure documentation and eliminating the storage and retrieval overhead of paper work orders.
• Reduced dispatch time from ~7 minutes to ~2 minutes through the automated recommendation engine and pre-filtered technician availability display.
• Offline-capable field interface eliminates the common failure mode of "technician in signal-dead equipment room, cannot complete digital form" — a scenario that previously forced returns to paper backup processes.
• [Needs Manual Input]: Total number of devices managed, number of technicians, historical SLA breach rate before vs. after deployment.

6. AI / Innovation Factor

• Claude AI-Produced UX Specification: All custom page flows — Work Order Dispatch, Mobile Field Operation, Asset Registry, PM Schedule Calendar, and Compliance Audit Sign-Off — have comprehensive pre-implementation UX Spec documents (user research, journey maps, use cases, interaction specifications, acceptance criteria) produced with Claude AI assistance. These artefacts prevented requirement ambiguity before development began.
• Cryptographic Audit Integrity: The SHA-256 Hash chain for work order records goes beyond standard database audit logs by providing a mathematically verifiable proof of record integrity — a capability typically found only in enterprise blockchain or legal document systems.
• IoT Platform Integration (Planned): Planned ThingsBoard integration will enable real-time device telemetry → automated CM work order generation pipeline, removing human intermediaries from the fault detection → dispatch chain entirely.
• [Needs Manual Input]: Specific AI/ML components planned for anomaly detection or predictive maintenance scheduling.

Document generated: 2026-05-03 | Maintained by Tom Lai / You Er Ta Mu She Ji