What Is CAM? Common Area Maintenance Charges, Explained for Indian Properties

Definition at a glance

Question	Working answer
What is it?	CAM means common area maintenance charges: the allocation of eligible shared-property operating costs among occupants or owners according to the governing agreement and applicable rules. CAM may cover security, cleaning, utilities, maintenance and shared services, but scope and allocation bases vary. Transparent billing requires an approved budget, consistent area data, documented apportionment, actual-versus-budget reconciliation and auditable supporting invoices.
Who should own it internally?	Assign the operational or compliance owner responsible for the underlying process and evidence.
What should the system hold?	Authoritative master data, dated source requirements, workflow status, approvals, exceptions and retrievable evidence.
What is the main mistake?	Treating a general definition as a substitute for the current rule, standard, contract or operating context.

Use the definition as an orientation point. Verify current primary sources before making a regulated, financial, safety or certification decision.

Operational control map

Use this map when translating the guide into system configuration or procedure. Replace every placeholder and add jurisdiction-specific rows before approval.

Control area	Minimum requirement	Owner	Evidence
Scope and applicability	Confirm entity, jurisdiction, activity and effective date.	[ASSIGN]	[EVIDENCE LINK]
Authoritative requirement	Link the current source from JOPD, DLD.	[ASSIGN]	[EVIDENCE LINK]
Master data	Define fields, identifiers and ownership.	[ASSIGN]	[EVIDENCE LINK]
Workflow control	Record submission, approval, rejection and correction states.	[ASSIGN]	[EVIDENCE LINK]
Evidence	Retain source documents, acknowledgements and versions.	[ASSIGN]	[EVIDENCE LINK]
Exception handling	Assign escalation, target and acceptance authority.	[ASSIGN]	[EVIDENCE LINK]
Periodic review	Set an owner and regulatory review date.	[ASSIGN]	[EVIDENCE LINK]

Treat this as a maintained record. Store source publication, internal approval and next review dates, and preserve prior versions whenever a rule or workflow changes.

FM begins before there is a facility to manage

Traditional mobilisation starts a few months before practical completion: recruit supervisors, tender cleaning and maintenance, load assets into a system and prepare opening day. That model is too late for a Saudi giga-project.

By then, equipment selections are fixed, access panels are built, warranty terms are signed, asset tags are inconsistent and commissioning records sit across contractors. The FM provider inherits operating cost and service risk it had no chance to influence.

Saudi giga-projects also combine scale with novelty. PIF describes its giga-project portfolio across future cities, tourism, entertainment, culture and integrated communities. A destination may open in phases while construction continues nearby. Digital systems, public realm, utilities, hospitality, transport and residential assets can share dependencies but have different operators.

Mobilisation is therefore an operational-readiness programme embedded in design, construction, commissioning and phased occupation.

Define the demand organisation before the FM model

ISO 41014 frames FM strategy around alignment with the demand organisation's objectives, needs and constraints. That is especially important when the final operating company, tenant mix or governance model is still forming.

Document the intended outcomes:

• guest, resident, employee and visitor experience;
• safety, security and business continuity;
• asset life and reliability;
• environmental and resource commitments;
• cultural, heritage or conservation needs;
• revenue-critical operating hours;
• accessibility and inclusion;
• local-content and workforce objectives;
• digital-service expectations;
• cost and lifecycle constraints.

Then define who owns each outcome. A project development team cannot remain the permanent decision authority after opening. Map developer, asset owner, operator, FM integrator, utility entity, district management, tenants and public agencies.

Unresolved governance is a mobilisation risk. Put it in the readiness register rather than assuming somebody will decide later.

Create an FM basis of design

The FM basis of design translates operating outcomes into requirements that design teams can use. It should address:

• service zones and operating boundaries;
• maintenance access and safe isolation;
• replacement routes for major equipment;
• cleaning access, façade systems and waste flow;
• stores, workshops, loading and staff facilities;
• metering and submetering;
• asset tagging and data standards;
• BMS, IoT, security and system integration;
• resilience, redundancy and recovery priorities;
• spare-parts strategy;
• environmental conditions and corrosion exposure;
• documentation, training and commissioning evidence;
• maintainability and lifecycle-cost review gates.

A pump can meet engineering performance and still be unmaintainable because lifting access is absent. A façade can be visually complete but require an impractical cleaning method. FM review must happen while those conditions can still change.

Track every review comment to disposition: accepted, incorporated, rejected with rationale, or pending decision. Meeting attendance is not evidence of influence.

Build the asset information model from the beginning

The asset register should not be assembled by extracting equipment names from PDF manuals at handover. Define the information requirement before procurement.

Use a hierarchy:

portfolio → destination or district → site → building or infrastructure system → floor/zone → space → system → maintainable asset → component

For each maintainable asset, require as applicable:

• unique project and operational identifier;
• type, description and classification;
• location and system relationship;
• manufacturer, model and serial;
• capacity and criticality;
• design, installation and commissioning dates;
• warranty supplier, start, end and conditions;
• preventive-maintenance requirement;
• statutory or certification requirement;
• spare-parts and consumables;
• drawing, manual, test and certificate links;
• BMS or sensor point reference;
• parent-child and redundancy relationship;
• ownership and maintaining party;
• acceptance and data-validation status.

Control allowed values and units. “AHU-01”, “Air Handler 1” and a contractor equipment code should not become three assets.

Keep data status separate from physical status. An installed asset may have incomplete data; a fully populated record may describe equipment not yet commissioned.

Set phased data drops

One final handover submission is too late. Require staged information:

1. design: planned systems, spaces, maintainable-asset types and performance;
2. procurement: selected manufacturer, model, supplier and warranty terms;
3. installation: actual location, serial, tag and installation evidence;
4. commissioning: test, setting, result, defect and witness;
5. handover: accepted manuals, certificates, spares, training and baseline condition;
6. post-occupancy: seasonal commissioning, optimisation and outstanding closure.

Validate each drop automatically where possible and sample physically. Required-field completeness does not prove that the serial number matches the installed unit.

Use data-quality rules for uniqueness, valid location, classification, unit, document link, parent system and commissioning status. Reject records through a controlled issue workflow.

Commissioning is evidence of performance, not a folder

The FM team needs to know how systems perform individually and together under realistic load. Link commissioning to operational acceptance.

Evidence can include:

• approved design intent and sequence;
• factory and site tests;
• pre-functional checks;
• balancing and setting records;
• integrated systems testing;
• cause-and-effect verification;
• life-safety and emergency tests;
• failover and recovery;
• meter and sensor validation;
• seasonal or deferred tests;
• defects, concessions and outstanding actions;
• witness and acceptance authority.

Do not mark an asset available merely because a test sheet exists. Check test scope, result, configuration and unresolved defects. Preserve the commissioned settings as a baseline for later diagnosis.

Integrated testing is essential. Power, controls, fire alarm, lifts, access, smoke management and emergency response can work individually while their interface fails.

Define the handover unit

Giga-projects do not hand over once. A hotel may open while adjacent public realm is under construction; utilities may serve completed and incomplete plots; a district command centre may receive data from assets owned by several entities.

Define a handover unit that is operationally coherent: building, zone, system, utility segment or service area. Each unit needs boundaries, dependencies and acceptance authority.

Readiness gates should cover:

Gate	Evidence
Safe and compliant	required approvals, life-safety tests, access and emergency controls
Physically complete	scope, defects, protection and clean condition
Functionally proven	commissioning and integrated tests
Maintainable	safe access, isolation, tools, spares and instructions
Information complete	validated asset, space and document records
Operable	trained staff, vendors, permits, helpdesk and escalation
Commercially clear	ownership, warranties, utilities, contracts and responsibilities
Interface controlled	construction boundary, shared systems and dependency plans

Conditional acceptance must list restriction, interim control, owner, due date and expiry. “Accepted with comments” is not a control.

Mobilise the organisation in waves

Work backwards from opening, but recruit key roles early enough to influence delivery.

Strategic mobilisation team

FM director, mobilisation manager, asset-information lead, commissioning/technical lead, HSE, digital systems, commercial and service-design roles.

Operational leadership

Site and discipline managers, helpdesk, permit and control-room leadership, quality and training.

Front-line and specialist workforce

Technicians, operators, cleaning, landscaping, waste, security interfaces and specialist vendors.

Build a resource model by asset quantity, operating window, criticality, planned workload, expected reactive demand, geography and response time. Benchmark ratios are a sense check, not the calculation.

Map competency by task: isolation, high voltage, confined space, water hygiene, fire systems, BMS, vertical transport, specialist façades and emergency roles. Record assessment, not attendance alone.

Plan access, accommodation, transport, uniforms, tools, devices, licences and visas with realistic lead times. A headcount on the organisation chart is not a deployed capability.

Procure service partners around outcomes and interfaces

Package strategy matters. One integrated FM contract can simplify accountability but concentrate dependency. Multiple specialist packages retain expertise but create coordination risk.

For every package define:

• assets, spaces and services in scope;
• operating outcomes and service levels;
• mobilisation deliverables;
• staffing and competence where prescribed;
• planned and reactive workflow;
• data ownership and system use;
• spares, consumables and tools;
• subcontracting rules;
• interface with warranties and construction contractors;
• performance evidence and payment;
• transition, step-in and exit.

Tender against verified scope versions. If asset quantities are provisional, define remeasurement and price adjustment. Otherwise bidders load contingency or disputes begin at opening.

Require vendors to participate in commissioning, training and snag closure where their future service depends on the system.

Warranty transition is a workflow

Construction defect, warranty claim, FM reactive failure and operator damage can look identical at first report. Create a triage process with evidence, response ownership and clock.

For every warranty:

• identify covered asset and supplier;
• record start trigger, end date and conditions;
• link maintenance obligations that preserve coverage;
• define response and escalation;
• retain commissioning baseline and service history;
• track claim, attendance, repair, parts and closure;
• distinguish rejected claim and reason;
• alert before expiry and conduct condition review.

Do not let warranty ownership delay safety restoration. Use emergency response and preserve commercial recovery separately.

Spares must exist before the first failure

Develop spares from criticality, lead time, failure mode, redundancy and supplier support—not only contractor recommendations.

Classify:

• commissioning and startup spares;
• insurance or capital spares;
• operating consumables;
• repairable rotable spares;
• vendor-held stock;
• common cross-asset parts;
• obsolete or single-source risk.

Verify quantity, identity, condition, storage requirement, shelf life, preservation and ownership at handover. Load them into inventory with bin, reorder policy and linked assets.

A part listed in a handover spreadsheet but sitting unlabelled in a contractor container is not operational stock.

Establish the service desk before occupancy

Design request channels, categories, priorities, SLAs, assignment, escalation, communication and closure. Integrate alarms and automated events carefully; do not create thousands of duplicate tickets from noisy BMS points.

Priority should reflect consequence and affected service, not caller seniority. Define examples for life safety, critical operations, guest impact, comfort and routine request.

Test scenarios:

• power or water interruption;
• trapped passenger or lift outage;
• fire-system impairment;
• guest-room fault;
• public-realm hazard;
• utility leak across package boundaries;
• construction damage in an occupied zone;
• digital-system outage;
• repeated defect under warranty.

Measure acknowledgement, attendance, safe restoration, permanent resolution and communication separately.

Load preventive maintenance with risk logic

Do not import every manufacturer task at maximum frequency without review. Build maintenance from statutory requirements, warranty, failure modes, asset criticality, environment, duty and operating strategy.

Each job plan needs asset scope, competency, safety precautions, isolation, steps, readings, tolerances, parts, tools, evidence and follow-up trigger.

Use calendar, runtime, condition or event-based scheduling as appropriate. Coastal, desert, high-temperature and high-occupancy environments may require specific inspection and filtration strategies.

Before opening, simulate the first year of planned workload. Identify peaks, access conflicts and impossible resource demand. Smooth work where technically valid.

Control the construction-to-operations interface

Occupied zones beside active construction require joint permits, access, logistics, isolation and emergency arrangements.

Maintain a live interface register:

• temporary utilities and planned cutovers;
• shared roads, loading and emergency routes;
• dust, noise, vibration and water risk;
• contractor access to occupied assets;
• system ownership during testing;
• changes affecting accepted assets;
• protection and reinstatement;
• incident notification;
• daily configuration and handback.

The project team must not change an accepted system without operational change control. FM must not modify a commissioned asset in a way that invalidates project testing without coordination.

Digital systems need an operating architecture

A giga-project can include BIM, common data environment, CAFM/IWMS, BMS, digital twin, GIS, utility platforms, security and customer apps. Integration without governance creates duplicated assets and conflicting status.

Define system of record for:

• asset identity and hierarchy;
• spatial geometry;
• maintenance history;
• live telemetry;
• documents and revisions;
• incidents and requests;
• contracts and warranties;
• utility and sustainability data.

Define identifiers, interfaces, refresh, ownership, cybersecurity, retention and offline continuity. Test failure modes: what can operations still do if the network, identity provider or integration layer fails?

Operational readiness exercises

Run progressive exercises:

1. desktop process walk-through;
2. system and ticket simulation;
3. technical scenario at one asset;
4. multi-team integrated exercise;
5. occupied-day rehearsal with service volumes;
6. emergency and business-continuity test.

Evaluate decision, communication, physical action, system record and recovery. Track findings to verified closure. A successful demonstration arranged by the installer is not the same as an unannounced operational response by the deployed team.

The readiness dashboard

Report by handover unit:

• physical and systems completion;
• commissioning passed, failed and deferred;
• asset-data quality and physical validation;
• critical documents and approvals;
• high-risk defects;
• workforce recruited, deployed and assessed;
• contracts mobilised;
• tools, spares and consumables available;
• PM plans loaded and forecast;
• warranties validated;
• exercises passed and actions open;
• shared-interface risks;
• decision and accountable owner.

Avoid averaging readiness. Ninety-eight percent complete can hide the missing two percent that prevents safe opening.

The first 100 days after opening

Use enhanced control:

• daily defect and service review;
• rapid asset-data correction;
• warranty triage;
• BMS alarm rationalisation;
• maintenance-frequency adjustment with evidence;
• consumable and spare usage;
• staffing demand versus model;
• guest or occupant feedback;
• energy and water baseline;
• seasonal commissioning plan;
• contractor demobilisation and knowledge transfer.

Freeze learning into masters and job plans. Do not let temporary opening workarounds become undocumented permanent operations.

Set a formal point for transferring mobilisation governance into business-as-usual FM governance. Confirm accepted scope, residual risks, open defects, budget, contract ownership and reporting cadence. Without that transition, mobilisation teams demobilise while unresolved project decisions lose their accountable owner.

FAQ

When should FM mobilisation begin on a giga-project? During strategy and design, before maintainability, data and lifecycle decisions are fixed. Operational staffing ramps later, but FM influence starts early.

Is construction completion enough for FM acceptance? No. FM needs proven function, maintainability, information, trained capability, spares, contracts and controlled interfaces.

Should the CAFM wait until final asset data? No. Load controlled data drops progressively, validate them and preserve status. Waiting creates an impossible handover backlog.

Who owns defects after handover? Responsibility depends on contract and cause. Use one triage workflow while preserving construction, warranty, FM and operator accountability.

How should phased openings be managed? Define operationally coherent handover units, dependencies, conditional acceptance and construction interfaces for each phase.

Where a system helps

A connected FM platform can receive staged asset data, control readiness gates, link commissioning to assets, mobilise planned maintenance, track warranties and spares, and provide one workflow across construction defects and live service. It gives owners evidence that a destination is operable—not merely built.

Explore FaciOS for facility management.

Related reading: The FM KPIs That Predict a Failed Contract Renewal (KB-440) and What Is a CMMS? (KB-129).

Sources

• Public Investment Fund, Giga-Projects
• ISO 41014:2020, Development of a facility management strategy
• ISO 41001:2018, Facility management systems