Specs

Spec selection by segment — Rehab through Diamond — with the policy clause attached to every choice.

What it is

the org's segment library — Rehab, Gold-3, Gold-2, Gold-1, Platinum, Diamond — drives the spec selection for every material in a project. Each spec carries its segment basis as data. A Diamond-grade vitrified tile on a Gold-1 project is flagged, not silently absorbed. The spec library is machine-readable; downstream BOQ and tendering pull from it without re-interpretation.

Inputs

Triggers

·Project segment confirmed (Rehab / Gold-3 / Gold-2 / Gold-1 / Platinum / Diamond)
·New material or finish category requirement from design
·Spec library version update
·Deviation request from consultant or DCO

Data reads

·Project segment from project record
·Spec library — 1,316 BOQ items, 41 tech specs, 8 LOAM
·Segment-spec mapping table
·Past-project spec deviations for cost-impact reference

Artefacts consumed

·Spec requirement from design (e.g. living room tile, lobby finish, sanitary ware)
·Vendor catalogues for spec validation
·approved alternative spec list

Tools & Techniques

Methods

·Segment-driven spec selection — segment determines spec automatically
·Each spec carries its segment basis and policy clause as data
·Deviation workflow — Diamond spec on Gold project flagged with cost delta
·Tech spec attached to BOQ item — same spec, same project, same material
·LOAM (List of Approved Materials) lookup per spec

Policies

·segment policy defining what fits which positioning
·Spec library version policy
·Deviation approval policy with cost-impact thresholds
·LOAM policy — what materials are approved per spec

Decision rules

·Spec selection auto-driven by segment; manual override requires deviation approval
·Spec downgrade (Diamond → Platinum on Diamond project) requires Design Head plus MD
·Spec upgrade (Gold → Platinum) requires DCO cost-impact analysis first
·LOAM compliance mandatory; non-LOAM material requires Standards team approval

Outputs

Artefacts produced

·Project-specific spec package (~1,316 line items typical)
·Tech spec attachments per BOQ item
·Deviation register with cost-impact data
·Segment basis citation for every spec

Data writes

·Project spec record locked to drawing version
·Deviation history fed to spec library for trend analysis

Downstream triggers

·Spec package issuance triggers BOQ alignment in M10
·Spec drives tender pack assembly in M14
·Approved deviations feed budget update in M11

Stakeholders

DesignSpec selection per discipline
DCOSpec consolidation, deviation tracking
MarketingSegment positioning input
Standards teamLibrary maintenance and segment definitions
Design HeadDeviation approval

The flow

01Project segment selected — Rehab / Gold-3 / Gold-2 / Gold-1 / Platinum / Diamond
02Material spec library lookup by segment
03Each spec carries its policy clause and version
04Deviation approval where required
05Spec package issued to CPT for BOQ alignment and tendering

State change

Before

Spec library exists on paper; lookups inconsistent; deviations unaudited.

After

Spec selection is machine-readable; segment compliance enforced; deviations traceable.

Real-world example

Worli is Platinum. Living room vitrified tile spec auto-selected: 800×1600 polished, double-charge, water absorption ≤0.08%. The Diamond-grade option (1200×2400 full-body) is available but flagged with cost delta if proposed. Specs issued with 1,316 line items, all citing segment basis.

Artefacts

·Spec library (machine-readable)
·Project-specific spec package
·Deviation register
·Segment basis citations

Pain today

Wrong spec picked, deviation uncaught, cost overrun discovered at BOQ stage. Same spec evaluated repeatedly across projects with no library memory.

Integrations

No external system integrations — module operates on internal records.