Facility Intelligence Prototype solution benchmark / page 2
Solution hypothesis / prototype benchmark

From paper and WhatsApp to facility intelligence.

If NMC's operating data still begins on paper forms, chats, photos, and manual reports, the strongest first prototype is a capture layer first. The dashboard only becomes useful after messy signals become clean work orders, SLA records, asset evidence, cost fields, and ERP-ready data.

The prototype starts where NMC already has credibility: property, facility, outsourcing, vendor coordination, project management, and operational reporting, then makes every signal structured enough to manage.

Signal capture Work orders ERP sync Efficiency layer

Prototype thesis

NMC can benchmark against global property and facility platforms, while starting smaller: a dashboard that proves operational efficiency and gives management a clear view across properties.

Start viewWhatsApp, paper, photo, and report intake converted into structured records.
Primary proofEvery issue has site, asset, SLA, owner, evidence, and next action.
System roleCapture layer that feeds the facility dashboard, ERP, and BI with cleaner data.
AI roleClassify messy messages and draft summaries after human approval.
01 / Competitor benchmark

What mature property platforms already prove.

The prototype borrows product patterns from global operators, not their full enterprise complexity.

Prism

Building ops

Work orders, preventive maintenance, inspections, vendor contracts, tenant experience, and API-first infrastructure.

Source
Corrigo

Facilities scale

Work orders, assets, vendors, automation, business intelligence, and portfolio-level facilities management.

Source
Yardi

ERP backbone

Connected property management, accounting, leasing, and real estate operating data.

Source
MRI

Finance + FM

Leasing, property management, facilities, finance operations, tenant portals, and mobile workflows.

Source
Maximo

Assets

Asset lifecycle, facilities maintenance, inspections, predictive maintenance, IoT, analytics, and reliability.

Source
AppFolio

Modern UX

Portals, maintenance requests, work orders, accounting/reporting, APIs, and AI-powered smart maintenance.

Source
02 / ISS quality-control benchmark

ISS proves the standard: quality is governed, not only staffed.

Use ISS as the proof that facility services can become a quality-control system. Then position NMC around local, bank-grade field proof rather than global scale.

Reference benchmark

ISS wins through self-delivery, consistent frameworks, and technology-backed service control.

Public ISS materials emphasize integrated facility services, direct control through self-delivery, consistent service quality, risk reduction, and technology platforms that support operational, financial, and sustainability performance.

Do not copy ISS head-on

  • ISS has global operating scale and long maturity; NMC should not claim the same footprint.
  • Generic integrated-FM claims will sound smaller if they only imitate global players.
  • A dashboard without field proof will not prove quality control for cleaning or maintenance.

Where NMC can win

  • Build the Indonesian bank-network version: local facility operations with proof per worker, zone, asset, and vendor.
  • Convert paper, WhatsApp, GPS, QR scans, photos, and supervisor checks into trusted operating data.
  • Win by being faster to pilot, closer to CIMB/NMC reality, and more transparent at field-task level.
ISS standardSelf-delivery controls service quality

ISS says direct service delivery helps retain quality control and consistent standards.

NMC wedgeField proof controls local execution

NMC can show every cleaner, technician, zone, asset, checklist, and supervisor approval as auditable data.

Meeting lineISS proves the category; NMC localizes the proof

The pitch is not size versus size. It is global benchmark versus bank-grade local execution visibility.

03 / Personalized playbook

Personalization is how NMC can win building by building.

The same governance system should create different playbooks and work orders for a tower, branch cluster, retail asset, or training facility. That is where local operating memory beats generic templates.

CIMB Tower Ops playbook

High-visibility building: executive lobby, lifts, meeting rooms, HVAC comfort, and report discipline matter most.

playbook v1.4
building profile

The building profile changes the checklist, SLA, proof requirements, QC sampling, and work order language.

generated work order

Lobby readiness inspection

Inspect executive lobby before banking hours. Require QR zone scan, floor/photo proof, toilet and lift-lobby checklist, and supervisor approval before closure.

04 / Low-hanging fruit

WhatsApp car rental can become the first loyalty data engine.

Facility governance is the deeper moat. But the fastest commercial proof can be a simple non-facility flow: WhatsApp request, car rental service order, fulfillment, invoice readiness, and customer loyalty signal.

WhatsApp request

The request is simple enough to pilot quickly, but valuable enough to create customer/account memory.

See operating dashboard

Service order to loyalty profile

Click the flow to show how one WhatsApp request becomes an order, fulfillment record, invoice-ready item, and loyalty signal.

structured order
loyalty effect
CIMB transport profile updated

The completed service becomes account memory: preferred route, vehicle class, cost center, satisfaction, and repeat usage.

05 / Main prototype screen

NMC Operations Command Center: capture first, facility core next.

This screen is the meeting demo: click messy field signals first, create a structured work order, then switch between Facility Management Core and Non-Facility Services to show how NMC moves from paper reports into active operating decisions.

NMC Operations Command Centerinteractive prototype

Capture messy signals first

WhatsApp messages, paper forms, and site photos become structured facility records before they enter the dashboard.

Click a field signal, then create a work order
ERP sync 91%

Field signal inbox

Prototype the first operational habit: capture the signal from WhatsApp, paper, photo, or call log before asking management to trust a dashboard.

Structured facility record

The messy WhatsApp complaint becomes a work-order candidate with site, asset, SLA, owner, evidence, and confidence fields.

AI can suggest classification, but the property team approves before the record enters operations.

How the dashboard gets data

Click each stage to show the data lineage from original field evidence into dashboard metrics, ERP readiness, and report intelligence.

lineage visible
source proof
Raw WhatsApp message retained

Original message, sender, timestamp, and attachment remain attached to the generated work object.

system effect
Dashboard fields are fed by approved work objects

The dashboard updates only after the signal has been validated and converted into an operational object.

Field governance for cleaning and building maintenance

The dashboard gets trusted data when low-level work is measured step by step: worker identity, location proof, zone or asset scan, photo evidence, checklist completion, QC score, and supervisor approval.

cleaning route
Cleaner appShift A
Toilet Zone 3 cleaning round
QC score: cleaning proof

Location and QR prove presence. Checklist and photo prove completion. Supervisor approval proves quality.

84
Portfolio focus

Default management view: compare property health, cost trend, SLA risk, and ERP status across the operating portfolio.

Property
Health
Tickets
SLA risk
Cost trend
ERP
CIMB Tower Ops
92
21
2
-8%
Synced
Branch Cluster West
74
84
11
+12%
Pending
Retail Asset A
61
43
7
+19%
Blocked
Training Facility
88
12
0
-3%
Synced
Parking Portfolio
78
56
6
+5%
Synced
Recommended action
Investigate repeat AC failures

Open Retail Asset A, review vendor response, check warranty status, and prepare a root-cause memo for the property manager.

Open propertyAssign ownerPrepare report
06 / Property detail

Click one property, see the operating truth.

This screen proves depth: work orders, assets, vendors, tenants, preventive maintenance, finance, ESG, and reports.

Retail Asset A

High-risk property view / simulated data

61 health
43open tickets
7SLA risks
+19%cost trend
BlockedERP status

Health score combines SLA, ticket age, asset criticality, vendor performance, cost variance, ERP exceptions, and tenant signal.

The property page is the daily control room.It gives NMC a practical bridge from facility services into measurable managed operations.
07 / Efficiency layer

The money is in leakage detection.

The prototype should show how NMC can find inefficiency per property, not only digitize forms.

SLA leakage

Aging tickets

Flag work orders older than threshold by property, asset, vendor, and tenant impact.

Vendor leakage

Late response patterns

Compare vendor response time, repeat jobs, first-time fix rate, invoice lag, and complaint recurrence.

Asset leakage

Warranty and PM gaps

Detect assets under warranty, overdue preventive maintenance, and repeated failures before cost escalates.

Finance leakage

ERP posting exceptions

Surface work completed but not posted, wrong cost center, invoice mismatch, and missing approval trail.

Energy leakage

Usage anomalies

Show unusual energy patterns by building, area, time window, and related maintenance events.

Report leakage

Manual reporting drag

Turn tickets, SLAs, costs, photos, and notes into client-ready monthly reports with evidence attached.

08 / ERP and system connection

Do not replace ERP. Feed it cleaner operating data.

The prototype should position NMC Property Intelligence as an operations layer that connects to finance, asset, procurement, vendor, and BI systems.

Property Ops OS

Work ordersRequests, assignments, SLA, proof, closure.
AssetsEquipment, warranty, PM schedule, criticality.
VendorsResponse, contract, compliance, invoice readiness.
TenantsRequests, announcements, satisfaction signal.

Integration layer

ERP connectorCost center, AP, GL, invoice status, approvals.
Data quality rulesRequired fields, duplicate detection, exception queue.
Audit trailWho changed what, when, with supporting evidence.
BI exportPortfolio reporting, trend analysis, client packs.

Business outcomes

Lower leakageFewer missed SLAs, invoice mismatches, repeat repairs.
Better client proofService reports with quantified performance.
Higher margin workManaged digital operations, not only manpower.
AI readinessRisk detection and summaries after structured traces exist.
09 / Role views

Four role views make the prototype believable.

A real property operations platform is multi-role. The first prototype can show one main dashboard and four smaller role previews.

Executive

Portfolio health, client performance, margin leakage, SLA trend, vendor score, and report readiness.

Property manager

Daily tickets, escalations, tenant complaints, vendor assignment, evidence, and approval queue.

Technician / vendor

Mobile job list, checklist, photo proof, parts used, completion note, and response time.

Client / tenant

Request status, announcements, service report, SLA transparency, and contact channel.

Executive view

Best first demo: portfolio risk, margin leakage, ERP exceptions, and client-ready monthly report status.

10 / Source map

Benchmark references.

This prototype is a discussion artifact. Screens use simulated data and should be replaced with NMC operating truth after validation.