COMPLETED HIGH-RISE PROJECT · JVC, DUBAI
A building with basement, upper-ground, four podiums, nineteen floors and roof cannot be treated as one repeated stack.
We carried out the recorded marble and stone project package for a B+G+UG+4P+19F+R building in JVC with TAK Construction LLC. The configuration itself explains the delivery challenge: basement and upper-ground conditions differ from podium interfaces, while nineteen upper floors depend on disciplined repetition. We approached the project as a sequence of building zones tied to one finish standard instead of assuming one detail could simply be copied from the bottom to the roof.
WHAT WE DELIVERED
What we did on this project
We delivered the recorded marble and stone scope on a building whose lower levels and upper stack demanded different execution logic.
Basement and upper-ground zones create access, service and level conditions that are different from podium and typical floors. We therefore treat every transition as a control point rather than assuming a detail approved on one level belongs everywhere.
Once the nineteen-floor stack begins, repetition becomes useful only after the benchmark is stable. The aim is to stop a small local deviation from becoming a nineteen-floor systemic problem.
THE REAL DELIVERY CHALLENGE
Different zones can require different access, measurement and sequencing even when the final finish is expected to read as one project.
Challenge
Different zones can require different access, measurement and sequencing even when the final finish is expected to read as one project.
Our response
We treat basement, upper-ground, podium and typical-floor conditions as separate work fronts while keeping joint, edge and finish expectations tied to one project-wide standard.
What the project demonstrates
The project adds transition control, podium-to-tower coordination and long repeat-floor discipline to our high-rise experience.
PROJECT DELIVERY CONTROLS
These controls are tailored to the recorded project context and are not presented as a reconstructed historical BOQ.
Separate basement, upper-ground, podium, typical-floor and roof-adjacent conditions before releasing repetitive work.
Confirm levels, joints and edge logic at every point where the building condition changes.
Establish one approved repeat reference before the nineteen-floor sequence scales.
Stage stone according to floor release and lifting access rather than sending material upward too early.
Compare completed floors against the benchmark and resolve drift before the next group repeats it.
Close finished zones progressively so later trades do not damage completed stone.
HOW WE APPROACHED THE WORK
The original historical method statement is not available; this sequence reflects the practical control logic appropriate to the verified project record.
Identify where the execution condition changes materially.
Confirm critical levels and interfaces before carrying the detail forward.
Establish the typical-floor benchmark.
Use the benchmark as control while still verifying the real floor.
Resolve outstanding details before the next zone inherits them.
PROJECT VISUALS
These URLs intentionally use existing generic site images so the page works now. Replace them later without changing the database structure.
WHAT THIS PROJECT ADDS TO OUR EXPERIENCE
Experience that carries into the next project
The strongest proof from this project is the ability to keep one stone quality language connected through several very different building conditions.
EXPERIENCE WE CARRY FORWARD
These points explain why this completed project matters as experience, rather than simply listing it as another completed job.
Treating changes in building condition as formal checkpoints.
Keeping nineteen floors tied to one visual and dimensional benchmark.
Coordinating installation, material movement and protection with real floor readiness.
Preventing unresolved issues from accumulating through a long tower programme.
PLANNING A SIMILAR PROJECT?
Send the floor matrix, transition details, stone schedule and programme. We can identify what can repeat and what must be independently verified before release.