INTRODUCTION TO STRUCUTRAL DESIGN RCC PRESENTATIONjay sinha
STRUCUTRAL DESIGN RCC PRESENTATION
INCLUDES DESIGN OF SLAB, BEAM, COLUMN, FOUNDATION
STADD.PRO INTRODUCTION
AND AUTOCAD INTERFACE
LOAD CALCULATION AND FORMULA
INTRODUCTION TO STRUCUTRAL DESIGN RCC PRESENTATIONjay sinha
STRUCUTRAL DESIGN RCC PRESENTATION
INCLUDES DESIGN OF SLAB, BEAM, COLUMN, FOUNDATION
STADD.PRO INTRODUCTION
AND AUTOCAD INTERFACE
LOAD CALCULATION AND FORMULA
This slide is a presentation during 15th International Surveyors' Congress on 28 Jun 2013 @ Hotel Istana, KL. Its demonstrates the role of BS in GBI. It doesn't mean exclusively done by BS, but just highlighting the relevant competency.
Civil Works Site Construction Guidelines for Haris & Co Civil Team.pdfusamazahoor159
Thrilled to unveil the culmination of my efforts: a comprehensive set of CME guidelines meticulously tailored for on-site telecom projects. These guidelines reflect not only my expertise but also my commitment to simplifying complexities and optimizing processes in the telecom sector. Dive into the details and let's elevate our practices together!
Enhanced Enterprise Intelligence with your personal AI Data Copilot.pdfGetInData
Recently we have observed the rise of open-source Large Language Models (LLMs) that are community-driven or developed by the AI market leaders, such as Meta (Llama3), Databricks (DBRX) and Snowflake (Arctic). On the other hand, there is a growth in interest in specialized, carefully fine-tuned yet relatively small models that can efficiently assist programmers in day-to-day tasks. Finally, Retrieval-Augmented Generation (RAG) architectures have gained a lot of traction as the preferred approach for LLMs context and prompt augmentation for building conversational SQL data copilots, code copilots and chatbots.
In this presentation, we will show how we built upon these three concepts a robust Data Copilot that can help to democratize access to company data assets and boost performance of everyone working with data platforms.
Why do we need yet another (open-source ) Copilot?
How can we build one?
Architecture and evaluation
More Related Content
Similar to Setting BI for ultimate performance for Site
This slide is a presentation during 15th International Surveyors' Congress on 28 Jun 2013 @ Hotel Istana, KL. Its demonstrates the role of BS in GBI. It doesn't mean exclusively done by BS, but just highlighting the relevant competency.
Civil Works Site Construction Guidelines for Haris & Co Civil Team.pdfusamazahoor159
Thrilled to unveil the culmination of my efforts: a comprehensive set of CME guidelines meticulously tailored for on-site telecom projects. These guidelines reflect not only my expertise but also my commitment to simplifying complexities and optimizing processes in the telecom sector. Dive into the details and let's elevate our practices together!
Enhanced Enterprise Intelligence with your personal AI Data Copilot.pdfGetInData
Recently we have observed the rise of open-source Large Language Models (LLMs) that are community-driven or developed by the AI market leaders, such as Meta (Llama3), Databricks (DBRX) and Snowflake (Arctic). On the other hand, there is a growth in interest in specialized, carefully fine-tuned yet relatively small models that can efficiently assist programmers in day-to-day tasks. Finally, Retrieval-Augmented Generation (RAG) architectures have gained a lot of traction as the preferred approach for LLMs context and prompt augmentation for building conversational SQL data copilots, code copilots and chatbots.
In this presentation, we will show how we built upon these three concepts a robust Data Copilot that can help to democratize access to company data assets and boost performance of everyone working with data platforms.
Why do we need yet another (open-source ) Copilot?
How can we build one?
Architecture and evaluation
Unleashing the Power of Data_ Choosing a Trusted Analytics Platform.pdfEnterprise Wired
In this guide, we'll explore the key considerations and features to look for when choosing a Trusted analytics platform that meets your organization's needs and delivers actionable intelligence you can trust.
Levelwise PageRank with Loop-Based Dead End Handling Strategy : SHORT REPORT ...Subhajit Sahu
Abstract — Levelwise PageRank is an alternative method of PageRank computation which decomposes the input graph into a directed acyclic block-graph of strongly connected components, and processes them in topological order, one level at a time. This enables calculation for ranks in a distributed fashion without per-iteration communication, unlike the standard method where all vertices are processed in each iteration. It however comes with a precondition of the absence of dead ends in the input graph. Here, the native non-distributed performance of Levelwise PageRank was compared against Monolithic PageRank on a CPU as well as a GPU. To ensure a fair comparison, Monolithic PageRank was also performed on a graph where vertices were split by components. Results indicate that Levelwise PageRank is about as fast as Monolithic PageRank on the CPU, but quite a bit slower on the GPU. Slowdown on the GPU is likely caused by a large submission of small workloads, and expected to be non-issue when the computation is performed on massive graphs.
Adjusting primitives for graph : SHORT REPORT / NOTESSubhajit Sahu
Graph algorithms, like PageRank Compressed Sparse Row (CSR) is an adjacency-list based graph representation that is
Multiply with different modes (map)
1. Performance of sequential execution based vs OpenMP based vector multiply.
2. Comparing various launch configs for CUDA based vector multiply.
Sum with different storage types (reduce)
1. Performance of vector element sum using float vs bfloat16 as the storage type.
Sum with different modes (reduce)
1. Performance of sequential execution based vs OpenMP based vector element sum.
2. Performance of memcpy vs in-place based CUDA based vector element sum.
3. Comparing various launch configs for CUDA based vector element sum (memcpy).
4. Comparing various launch configs for CUDA based vector element sum (in-place).
Sum with in-place strategies of CUDA mode (reduce)
1. Comparing various launch configs for CUDA based vector element sum (in-place).
06-04-2024 - NYC Tech Week - Discussion on Vector Databases, Unstructured Data and AI
Round table discussion of vector databases, unstructured data, ai, big data, real-time, robots and Milvus.
A lively discussion with NJ Gen AI Meetup Lead, Prasad and Procure.FYI's Co-Found
06-04-2024 - NYC Tech Week - Discussion on Vector Databases, Unstructured Data and AI
Discussion on Vector Databases, Unstructured Data and AI
https://www.meetup.com/unstructured-data-meetup-new-york/
This meetup is for people working in unstructured data. Speakers will come present about related topics such as vector databases, LLMs, and managing data at scale. The intended audience of this group includes roles like machine learning engineers, data scientists, data engineers, software engineers, and PMs.This meetup was formerly Milvus Meetup, and is sponsored by Zilliz maintainers of Milvus.
Adjusting OpenMP PageRank : SHORT REPORT / NOTESSubhajit Sahu
For massive graphs that fit in RAM, but not in GPU memory, it is possible to take
advantage of a shared memory system with multiple CPUs, each with multiple cores, to
accelerate pagerank computation. If the NUMA architecture of the system is properly taken
into account with good vertex partitioning, the speedup can be significant. To take steps in
this direction, experiments are conducted to implement pagerank in OpenMP using two
different approaches, uniform and hybrid. The uniform approach runs all primitives required
for pagerank in OpenMP mode (with multiple threads). On the other hand, the hybrid
approach runs certain primitives in sequential mode (i.e., sumAt, multiply).
STATATHON: Unleashing the Power of Statistics in a 48-Hour Knowledge Extravag...sameer shah
"Join us for STATATHON, a dynamic 2-day event dedicated to exploring statistical knowledge and its real-world applications. From theory to practice, participants engage in intensive learning sessions, workshops, and challenges, fostering a deeper understanding of statistical methodologies and their significance in various fields."
2. Performance Index is created to establish a uniform measure of performance for all projects as some schedules were
conservative and some were aggressive in their plans.
Timelines for
Parameter Unit Average PI 1 PI 2 PI 3 PI 4 PI 5
Typical Slab Cycle – Avg Days 18 12 10 8 7 6
Start to Terrace (G+23) Months 20 13.5 12 10.5 9 8
Terrace to OC application Months 20 10.5 10 9.5 9 8
Start to OC application Months 40 24 22 20 18 16
Degree of Difficulty
1) Best Performance of GPL Start to OC application – 21.5 months at Hillside would lead to PI 2.5
Benefits of PI Index
1. Has become common yardstick to gauge performance among Ops teams
2. It helps identify gaps in progress (eg superlative performance in RCC but lower in finishing)
3. Healthy competition among Ops teams as they are rated on common rules
4. Acts as a North star for teams to surpass existing benchmarks
5. High motivation levels among project teams to achieve Superlative Performance
Need for Performance Index for Operations
3. Contents
• Substructure
• Superstructure – Aluminum and Conventional formwork
• Superstructure – Tunnel, Pre cast and Hybrid formwork
• Finishing
• Finishing and Parking structure
• Terrace to OC
• Handover
• Annexure
• OC efficiency factor
• Excavation
• Vendor on board milestones
• Fastest achievements in GPL
4. Excavation and Substructure timelines
SL.
NO.
HEAD ACTIVITY UNIT
PI timelines REMARKS
PI 1 PI 2 PI 3 PI 4 PI 5
1
PILING &
EXCAVATION
Shore piles (300 mm dia ) (avg 15 m depth) NOS/DAY 9 12 15 18 20
Soil (project avg) cum/day 880 1000 1125 1250 1365
Soft rock (project avg) (which can be
excavated with bucket)
cum/day 770 870 970 1070 1170
Hard rock with breaker (project avg) cum/day 550 620 690 760 830
Excavation for buildings with no basement days 36 31 26 21 15
2 FOUNDATION
Regular raft / footing days 36 31 26 21 15
Complicated raft (pit parking) days 60 53 46 39 30
3
FOUNDATION
TO PLINTH
Foundation to plinth days 30 26 22 18 15
Durations are for avg of 3 to 4.5 m
depth. For 6 m depth consider
1.25 times the duration
4
BASEMENT /
PODIUM RCC
SLABS
Basement slab cycle (up to 4.5 M) days 35 30 25 20 15
For 6 m height consider 1.25 times
the duration
Podium slab cycle(up to 4.5 M) days 35 30 25 20 14
For 6 m height consider 1.25 times
the duration
5. Superstructure timelines
SL.
NO.
ACTIVITY UNIT
REVISED PI 14 Jun 22 REMARKS
PI 1 PI 2 PI 3 PI 4 PI 5
5
ALUMINIUM
FORMWORK
TECHNOLOGY
1st slab (in case of combo of aluform +
conventional) or (100% conventional)
days 30 27 24 21 19
2nd slab (in case of combo of aluform +
conventional) (in case of combo of aluform +
conventional) or (100% conventional
days 21 20 19 18 15
NEW ALUFORM MATERIAL - 1st setup of aluminum
formwork
days 30 25 21 17 12
REFURBISHED ALUFORM MATERIAL - 1st setup of
aluminum formwork
days 51 43 36 29 20
2nd slab after 1st set up (100% mivan) days 21 18 15 12 9
Typical Slab
Cycle - (Level 3
to terrace)
except service
floor, refuge
floor , change
of shuttering
Tower up to 18 floor height days 13 11 9 8 7
Consider 1 day extra for towers with RCC
elevation features (like grooves) as
observed in RKS
Tower (19 to 30 floor height) days 12 10 8 7 6
Tower (31 to 40 floor height) days 14 12 10 8 7
for towers above Level 30, consider the
duration on level basis. E.g. PI 3 : consider
from Level 3 to Level 18 as 9 days.
From Level 19 to Level 30 - 8 days.
From level 31 to 40 - 10 days ,
level 41 to 50 - 12 days.
Level 51 to L65 (except terrace) - 16 days
Tower (41 to 50 floor height) days 15.5 14 12 10 8
Tower (51 to 65 floor height) days 19.5 18 16 14 12.5
6
CONVENTIONAL/
FLOOR CHANGE
CONVENTIONAL FLOOR including any service floor,
refuge floor , change of shuttering, terrace etc
days 18 15 12 9 6
6. Superstructure timelines
SL.
NO.
HEAD ACTIVITY UNIT
REVISED PI 14 Jun 22 REMARKS
PI 1 PI 2 PI 3 PI 4 PI 5
7
JUMPFORM +
ALUFORM (51 to 65
floors height)
Set up of jump form + min. 4 floors jumping of core days 95 86 77 68 60 for towers above Level 30, consider
the duration on floor basis. E.g. PI 3
: consider from Level 3 to Level 18
as 8.5 days.
From Level 19 to Level 30 - 7.5
days.
From level 31 to 40 - 9.5 days ,
level 41 to 50 - 10.5 days. Level 51
to L65 (except terrace) - 13 days
(Terrace to be treated as
conventional)
Typical slab cycle (Level 3 to 18 floor ) days 10.5 9.5 8.5 7.5 7
Typical slab cycle (Level 19 to 30 floor ) days 9.5 8.5 7.5 6.5 6
Typical slab cycle (Level 31 to 40 floor ) days 11.5 10.5 9.5 8.5 7
Typical slab cycle (Level 41 to 50 floor ) days 13 11.5 10.5 9.5 8
Typical slab cycle (Level 51 to 65 floor excluding terrace ) days 17 15 13 11 9.5
8
TUNNEL FORMWORK
TECH
Set up for first 3 floors of tunnel form days 63 60 57 55 54
Typical floor up to terrace
Tunnel (Full set) days 5.5 4.5 3.5 2.5 2
Tunnel (Half set) days 11 9.5 8 6.5 5
Secondary RCC works (Staircase, upstands, façade walls etc)
gap (no
of floors )
7 6 5 4 3
9 PRECAST All floors days 8 7.5 7 6 5
10
HYBRID PRECAST
(VERTICALS CAST IN
SITU ALUFORM, SLAB
PRECAST)
for 18-30 floor tower ( 6000 to 7000 sqft floor plate)
1st set up Days 33 29 25 21 18
2nd slab days 21 19 17 15 14
Typical floor days 11 9.5 8 6.5 5
Terrace or any change in design floor days 11 9.5 8.5 7.5 6
7. Finishing timelines
SL.N
O.
HEAD ACTIVITY UNIT
REVISED PI 14 Jun 22 REMARKS
PI 1 PI 2 PI 3 PI 4 PI 5
11
TYPICAL FLOORS
FINISHING SLAB
CYCLE (applicable up
to tile flooring)
Block work & handrail days 10 9 8 7 6
Waterproofing days 14 13 12 11 10
MEP Works days 7 6 5 5 3
Plaster days 14 13 12 11 10
IPS Flooring days 10 9 8 7 6
Stone flooring days 7 6 5 4 3
Flat/ Toilet Tile flooring days 10 9 8 7 6
counters days 10 9 8 7 6
Tile cladding and skirting days 10 9 8 7 6
Temp Door fixinfg & skirting repair days 6 5 4 5 2
TOTAL DURATION days 98 88 78 71 58
12
INTERMEDIATE
FINISHING ACTIVITIES
(GAP FROM RCC
CASTING SLAB )
Blockwork & railing completion
no of
floors
7 6 5 4 3
Internal Plaster completion
no of
floors
8 7 6 5 4
Flat / Toilet Flooring/ Dado completion till temporary door
fixing
no of
floors
10 9 8 7 6
13 WINDOW FIXING Window fixing (Gap from Flat flooring)
no of
floors
8 6 4 3 2
Exceptional case with
external plaster to be
discussed
14
LIFT COMPLETION
FROM TERRACE
Lift completion (lift NOC) (lag from terrace completion to lift
installation)
days 160 135 120 105 90
8. Finishing and parking structure timelines
SL.N
O
HEAD ACTIVITY UNIT
REVISED PI 14 Jun 22 REMARKS
PI 1 PI 2 PI 3 PI 4 PI 5
15
FINISHING ACTIVITIES
COMPLETION TIMELINE
(From Terrace
completion)
Blockwork & railing completion
lag
(days)
80 60 40 30 20
Internal Plaster completion
lag
(days)
120 90 70 55 40
Flat / Toilet Flooring/ Dado completion
lag
(days)
170 155 135 120 100
Window fixing
lag
(days)
200 185 165 150 130
External Paint
lag
(days)
285 255 225 200 175
Common area flooring completion
lag
(days)
230 210 190 170 150
16
NTA works/ Podium/
MLCP tower completion
100 % RCC work completion slab area.
Inclusion of NTA/ Podium progress
along with tower works. It will have
weightage of 25 % for a given projects.
Rest all towers shall be distributed
within 75 %
NTA
Area
within
three
months of
last tower
RCC
completion
within one
month of
last tower
RCC
completion
Along with
last tower
RCC
completion
Before one
month of
last tower
RCC
completion
Before three
months of
last tower
RCC
completion
1. All measurement to be
done with Terrace
completion of last tower
of first phase. .
2. NTA to be done to the
extent of OC requirement
3. Tower height less than
13 floors to be discussed
separately.
9. Terrace to OC application timelines
O.C.
READINESS
FROM
COMPLETION
OF TERRACE
(MONTHS)
No of floors UNIT
PI 1 PI 2 PI 3 PI 4 PI 5
Bare
shell
Typical
High
end
Bare
shell
Typical
High
end
Bare
shell
Typical
High
end
Bare
shell
Typical
High
end
Bare
shell
Typical
High
end
up to 8 floors months 7.5 8.5 10.5 6.5 7.5 9.5 5.5 6.5 8.5 4.5 5.5 7.5 3.0 4.5 6.5
9 to 18 floors months 8.5 9.5 11.5 7.5 8.5 10.5 6.5 7.5 9.5 5.5 6.5 8.5 4.0 5.5 7.5
19-30 floors months 9.5 10.5 12.5 8.5 9.5 11.5 7.5 8.5 10.5 6.5 7.5 9.5 5.0 6.5 8.5
30-50 floors months 10.5 11.5 13.5 9.5 10.5 12.5 8.5 9.5 11.5 7.5 8.5 10.5 6.0 7.5 9.5
more than 50 floors months 11.5 12.5 14.5 10.5 11.5 13.5 9.5 10.5 12.5 8.5 9.5 11.5 7.0 8.5 10.5
10. Handover
Handover PI PI1 PI2 PI3 PI4 PI5
Start from OC receipt ( 1st Flat ) 7 months 6 months 5 months 4 months 3 months
Finish from OC Receipt 13 months 11 months 9 months 7.5 months 6 months
Notes
The above cases is where OC receipt is within 3 months of application. Otherwise above duration shall be
measured from OC application + 3 months
In case OC is stuck after application, handover to CQRA team shall be considered
12. OC led projects - Efficiency factor
Overall efficiency factor to be applied once if OC is received basis major work completion. This is being done to ensure faster work turnaround to handover post
OC receipt. Enumeration done below for a sample:
Activity UOM Target Actual achieved Completion % Weightage Final Factor
A B C = B/A D E = C*D
Flat flooring ( Except wooden flooring) No. of flats 1000 900 90% 25% 23%
Common area finishes (flooring, cladding, false ceiling) Floor 22 11 50% 15% 8%
Window fixing No. of windows 5000 3500 70% 15% 11%
Lift Nos. 3 3 100% 20% 20%
External paint 1st coat Sqm 13941 10000 72% 25% 18%
Net factor 78%
Net PI calculation
= OC PI X Net factor ( E)
= 3 0.8
Net PI = 2.4
Notes :
Grey cells to be filled as per actual progress
In case some activity are not required as per OC rule for the given geography; same will be exempted from calculation
13. Excavation timelines Enumeration
STRATA
volume as per geotech
report (cum)
swell (voids) total volume (cum) output (cum/day) Days
SOIL 18000 1.3 23400 880 27
WEATHERED ROCK 23000 1.35 31050 770 40
HARD ROCK 30000 1.4 42000 550 76
TOTAL 71000 96450 143
PILING LAG in case shore piling is to be done. In case shore piling is not required then this lag to be 0 45
TOTAL DAYS 188
P.I. REMARKS
BASE
DURATION
(WORKING
DAYS)
MONSOON
DAYS
LOSS DUE TO
MONSOON
(monsoon
days x
efficiency loss)
LOSS DUE TO
BASEMENT
DEPTH
FACTOR
DURATION OF
EXCAVATION +
SHORE PILING
FOR BI
WORKING
PILING
DURATION
EXCAVATION
LAG POST
PILING
PILES/DAY NO OF PILES
A B
D=B *
MONSOON
FACTOR
E=A * B A+D+E
1 BASE 188 120 36 9 234 120 113 7
842
2 10% REDUCTION 210 105 105 8
3 20% REDUCTION 187 94 93 9
4 30% REDUCTION 164 77 87 11
5 40% REDUCTION 140 70 70 12
14. Excavation timelines Enumeration (efficiency factors)
MONSOON FACTOR : EFFICIENCY LOSS DUE TO MONSOON
LOCATION SEASON EFFICIENCY LOSS DUE TO MONSOON
MUMBAI MONSOON 30%
PUNE MONSOON 25%
NCR / BANGALORE MONSOON 20%
BASEMENT DEPTH FACTOR (INCLUDES PARKING PITS)
1 BASEMENT 0%
Depth of 3.5 m
2 BASEMENT 5%
3 BASEMENT 10%
4 BASEMENT 15%
Note: in case basement depth is more than 4.2 m then an additional 2% to be considered
15. Vendor onboarding milestones
PACKAGE
3B+G+14 (Foundation + 3 basement
slabs+15 superstructure slabs)
G+23 (Foundation + 25 slabs) B+P+27 (Foundation + 29 slabs)
Piling 15 Days before start of construction 15 Days before start of construction
Excavation 15 Days before start of construction 15 Days before start of construction 15 Days before start of construction
Shell and Core
(Including electrical embedment/WP of foundation)
15 days before start of PCC 2 Week after excavation start 03 week after start of excavation
Aluform Basement 2 completion 15 Days Before start of construction At completion of excavation
Railing Level 5 Level 5 Level 4
Plumbing Including CP Sanitry Level 5 Level 5 Level 4
Fire Fighting Level 5 Level 5 Level 4
Electrical work Level 5 Level 5 Level 4
WP (toilet/ balcony/ terrace) Level 5 Level 5 Level 4
Flooring (Supplier) Level 3 Level 3 Level 2
Flooring (Vendor) Level 5 Level 5 Level 4
Window Level 6 Level 6 Level 7
Internal painting Level 12 Level 12 Level 12
Ext painting Terrace Terrace Terrace
Readymade door Level 12 Level 19 Level 23
17. Fastest achievements in GPL - Substructure
HEAD ACTIVITY ACHIEVEMENT PROJECT - TOWER ZONE FREQUENCY
PILING &
EXCAVATION
Shore piles (300 mm dia ) (avg 15 m depth) 18 piles/day RK STUDIO MMR Overall
Excavation hard rock with blasting (project avg) 439 cum/day RK STUDIO MMR Overall
Excavation for buildings with no basement 13 days INFINITY – T5 WEST - PUNE
FOUNDATION
Regular raft/ footing 15 days WOODS Sec 43 – T4 NCR 1 slab
Complicated raft (pit parking) 16 days URBAN PARK – T7 MMR 1 tower
FOUNDATION TO
PLINTH
Foundation to Plinth 30 days EMERALD – T6 MMR 1 tower
BASEMENT Basement slab cycle (up to 4.5 m)
16 days RKS - TA MMR 1 slab
16 days AIRNXT - TJ SOUTH 1 slab
PODIUM Podium slab cycle(up to 4.5 m) 11 days REJUVE – T11 B WEST - PUNE 1 slab
18. Fastest achievements in GPL - Superstructure
HEAD ACTIVITY ACHIEVEMENT PROJECT - TOWER ZONE FREQUENCY
ALUMINIUM
FORM TECH
NEW ALUFORM MATERIAL - 1st setup of aluminium
formwork
15 days WOODS SEC 43 – T2 NCR 1 tower
2nd slab after 1st set up (100% Aluform) 8 days WOODS SEC 43 – T6 NCR 1 tower
Tower (19 to 30 floor height) (Level 3 to terrace)
except service floor, refuge floor , change of shuttering
4 days NURTURE – T2, T3, T7 SOUTH 3 slabs
4 days REJUVE – T10A, T7A WEST- PUNE 4 slabs
4 days SOUTH ESTATE – SB2 NCR 2 slabs
4 days HILLSIDE 1 – T1 WEST- PUNE 1 slab
4 days AIR – A5 NCR 1 slab
Average slab cycle (typical floors) (3rd
floor to Terrace) 8.35, 8.45 days NURTURE – TD, TC SOUTH 2 towers
Maximum no. of slabs cast in a tower in a month 7 slabs in 30 days NURTURE – TC (L16 to terrace) SOUTH 1 tower
Maximum no. of slabs cast in a tower in a calendar
month
6 slabs (Mar-22) AIR – A5 (L21 to L26) NCR 1 tower
19. Fastest achievements in GPL – Lift, Finishing, NTA, OC Readiness
HEAD ACTIVITY ACHIEVEMENT PROJECT - TOWER ZONE FREQUENCY
LIFT COMPLETION
Lift completion (lift NOC) (lag from terrace
completion to lift installation)
36 days AVENUES – TD SOUTH 1 tower
FINISHING
ACTIVITIES
COMPLETION
Blockwork completion (from Terrace) 10 days AVENUES - TA SOUTH 1 tower
Internal Plaster completion (from Terrace) 63 days NURTURE – TD SOUTH 1 tower
Flat Flooring completion (lag from terrace) 68 days NURTURE – TA SOUTH 1 tower
Common area flooring completion (from Terrace) 121 days AVENUES PH1 - TA SOUTH 1 tower
O.C. READINESS
FROM COMPLETION
OF TERRACE
OC Application from completion of Terrace 90 days 24 – E3 WEST - PUNE 1 tower
CONSTRUCTION
START TO OCA
Construction start to OC Application
21.4 months (651
days)
HILLSIDE 2 (T1, T2, T3) WEST - PUNE 3 towers