
4sight assessed a portfolio of enterprise and cloud facilities across more than one Middle East market against one technical baseline. The owner decided to hold the portfolio to that baseline while each market kept its own authority conditions and its own design. Local contractors, local authority requirements and hosting conditions still differed by market. The baseline gave the owner one way to compare every site and see which gaps belonged to the program.
The challenge
Without a common baseline, each market's design, bill of quantities and test record would answer a different question. The owner could not see which gaps were local and which sat in the program.
The baseline also had to absorb differences it could not erase. Local contractors built the work. Local authority requirements governed it. Regulated tenants brought hosting conditions that differed by market.
What 4sight did
4sight assessed the portfolio to one baseline and delivered these owner-side services:
- Planning for the portfolio and for each facility in it.
- Multidisciplinary design across architecture, mechanical, electrical and plumbing (MEP), and information and communications technology (ICT).
- Bills of quantities for the sites in the program.
- Fit-out assurance and testing support.
- Standards-alignment evidence against the baseline the owner adopted.
A portfolio baseline is a comparison method. It does not claim that the facilities are identical.
What the owner received
One baseline for the whole portfolio, with each market's design, quantities and test record measured against it. The standard and rating level used for the baseline are not published, and the case claims no shared certification status, authority approval or operating result across the markets.
Frequently asked questions
The owner decided to hold this enterprise and cloud portfolio to one technical baseline while each market kept its own authority conditions and its own design. 4sight assessed the facilities across more than one Middle East market against that baseline, so the owner could see which gaps belonged to the program. The case claims no shared certification status, authority approval or operating result across the markets.
This cross-border portfolio used one technical baseline as the comparison method. The standard and the rating level used for that baseline are not published. 4sight delivered planning, multidisciplinary design, bills of quantities, fit-out assurance, testing support and standards-alignment evidence against the baseline the owner adopted. Local contractors, authority requirements and hosting conditions still differed by market. The facilities are not claimed to be identical.
Another owner can copy the comparison method from this cross-border enterprise and cloud portfolio by 4sight. Hold every site to one baseline for design, quantities and test records, so local gaps and program gaps can be told apart. Let each market keep its own design where contractors, authority requirements or hosting conditions differ. Do not read the baseline as a claim that the facilities are identical.