SADARA PROJECT
LSPB CONTRACT
TECHNICAL DATA BOOK
ATTACHMENT IV TO SCHEDULE B
15.2.1 BUILD INTERFACE MANAGEMENT
PLAN
Document No: A554-R-730-IN-GEN-INT-001
RTIP Rev: 1 2 3 3 FW Prepared by: Majid M Alghamdi Majid M Alghamdi Majid M Alghamdi FW Approved
by: Mike Dowden Mike Dowden Mike Dowden Owner
Approved by: Daniel Abanto Daniel Abanto Daniel Abanto
Revision Date: 11 July 2012 28 Aug 2012 10 Sept 2012
Issue
Purpose: ITB IFT IFT
This document contains technical information that may be subject to the export control regulations of the United States and/or other jurisdictions. It may not be exported or re-exported except as authorized under applicable U.S. or other export control regulations.
SUMMARY OF DOCUMENT REVISIONS Rev. No. Date Revised Section
Revised Revision Description
1 3 July-12 Issued for Client Review
2 28 Aug-12 Attachment 2 Interface Dependency Table Update 3 10-Sept-12 Attachment 2 Interface Dependency Table Update
TABLE OF CONTENTS Section Topic 1.0 PURPOSE ... 4 2.0 SCOPE ... 4 3.0 DEFINITIONS ... 4 4.0 RESPONSIBILITIES ... 5 4.1 INTERFACE PARTIES ... 6 4.2 CONTRACTOR F ... 6 4.3 CONTRACTOR O ... 7
4.4 PROGRAM INTERFACE MANAGEMENT TEAM (PIMT) ... 8
5.0 INTERFACE TYPES ... 8
5.1 EXTERNAL INTERFACE ... 8
5.2 INTERNAL INTERFACE ... 9
6.0 INTERFACE NUMBERING ... 9
7.0 COMMUNICATION ... 10
7.1 INTERFACE QUERIES (IQS) ... 11
7.2 IQ NUMBERING ... 11
7.3 TRANSMISSION OF DOCUMENTATION ... 11
8.0 INTERFACE GUIDELINES ... 11
8.1 PIPING ... 12
8.1.1 ABOVE GROUND PIPING INTERFACES ... 12
8.1.2 UNDERGROUND PIPING INTERFACES ... 12
8.2 CIVIL INTERFACES ... 13
8.2.1 ROAD INTERFACE ... 13
8.2.2 PAVING INTERFACES ... 14
8.2.3 DITCH INTERFACES ... 14
8.2.4 TELECOMMUNICATION CONCRETE ENCASED DUCT BANKS ... 15
8.3 TELECOMMUNICATIONS ... 16
8.4 ELECTRICAL ... 16
ATTACHMENT 1 – IQ GUIDELINES ... 17
1.0 PURPOSE
This document defines how interfaces are to be managed by the Packages Contractors. It defines the role and responsibilities of each interface Party. It does not define the engineering requirements of each interface.
This document is intended to:
• Ensure all interfaces are identified
• Define clear responsibilities for each Party • Ensure there are no interface gaps or overlaps
• Define the physical method of making the interface (flange, junction box, etc) • Ensure schedule compatibility, relating to interfaces
2.0 SCOPE
This document defines the requirements for the management of interfaces during construction phase
The physical interface definition includes the following connections: • Piping (above and underground)
• Civil (roads, paving, ditches, ducts) • IT/Telecoms
• Electric power cable and Control Cable 3.0 DEFINITIONS Title Definition BL Battery limit Contractor “Package A, B, C, Or D Contractor”
The SDL Building Project is divided into four Packages, A, B,C and D. Each Package will be constructed by a Package contractor
Package contractor The Contractor responsible for Construction of a Package. Finalization
Contractor “Contractor F”
Contractor F effectively will accept the works of Contractor O and will complete the Interface Point works. Contractor F will maintain responsibility for the Interface Point until construction turnover.
Originator
Contractor “ Contractor O”
Contractor O is the Contractor who initiates the works at an IP. Contractor O will provide Contractor F the required support to allow Contractor F to complete the works at subject interface point.
3rd Party contractor Contractors nominated for works outside of the building battery limit or not included in Contractor A,B,C& D scope of work
ICF Interconnecting Facilities Contractor ITC Information Technology Contractor
EW Early Work Contractor
IDT Interface Dependency Table
External Interface External Interface is an interface between any Package Contractor and a third party contractor e.g. between Package C Contractor and ICF Contractor
Internal Interface An Internal Interface is an interface between any two Package Contractors
IP Interface Point
IQ Interface Query
ISBL Inside Battery Limit. A category of work scope for facilities inside a process Unit BL
OSBL Outside Battery Limits. Outside the Process Unit BL but within the Site boundary
PMT Project Management Team
SPOC Single Point of Contact
4.0 RESPONSIBILITIES
This section outlines the respective responsibilities of the Project Management Team and the Packages Contractors.
Package Contractors are wholly responsible for the completion of all Interface Points within the parameters of the contract price. Package Contractor shall be responsible to communicate with any other Package Contractor as required to complete all works relating to the Interface Points. Package Contractor shall also be responsible for all documentation and communication with the PMT.
The following is the general frame of responsibilities
I. PMT will: Oversee the interface process and nominate contractor (F) Finalization Contractor or (O) Originator Contractor in each IP.
II. It is the responsibility of a Package Contractors to coordinate with the other Package Contractors to establish schedule of activities at each Interface Point (IP). Agreeing to the sequence of activities, and finalizing the proper sign off and required testing for each (IP) based
on the role they will be assigned to as an Originator contractor Or Finalization contractor.
III. Contractor O will be the first contractor to install their works in a condition that Contractor F will be able to complete the IP per the Contract Documents.
IV. Contractor F prior to starting any works at an IP shall confirm Contractor O installation is acceptable to complete the IP per the terms of the contract documents. This is to include layout and elevations and general soundness of the installation.
V. Contractor O shall facilitate Contractor F as required to complete the IP, providing required access or traffic control, etc. etc.
VI. Upon completion of any irregularities and acceptance of Contractor O IP works, Contractor F shall complete the IP per the requirements of the contract documents.
VII. Contractor F shall be responsible for future protection of the IP and all snag list works associated with the said IP.
VIII. It is the responsibility of the parties involved to ensure that the appropriate Non-Disclosure Agreements are in place where the exchange of information and / or drawings & documents as specified in this document.
4.1
Interface PartiesThere are four parties involved in the management of interface points: • Finalization Contractor “ Contractor F”
• Originator Contractor “ Contractor O” • 3rd party Contractor
• Project Management Team
For each IP, Contractor F and Contractor O will be identified by the PMT.
4.2
Contractor F Contractor F shall:1. Be the contractor that finalizes the works at an IP
2. Participate in the creation and maintenance of the IDT Interface Dependency Table
3. Participate in all requested IP coordination meetings
4. Mutually agree with Contractor O that the IP and associated data is correct, consistent and complete.
6. Populate interfaces completion dates in the Interface Dependency Schedule (See Attachment 2) and update regularly to manage and monitor the timing of completion of interface points and gates. Copy to be provided to PMT. 7. Reach agreement on interfaces with other Contractors in a timely manner to
support the overall Project schedule.
8. Identify and agree with Contractor O the inspections, tests and construction and pre-commissioning records that are required to be performed and/or maintained by itself and Contractor O. This applies to situations where both Contractors have an overlap of activities at the interface such as the joint hydrotest of both sides of an interface point at the same time. Otherwise the Contractors shall each be responsible for their 'side' of the interface.
9. Identify and agree with Contractor O any inspections, tests, drying and any other requirements to be witnessed by itself and Contractor O.
10. Prior to starting any interface works, confirm the acceptability of the in-place works instated by Contractor O. This confirmation shall include the overall acceptability of the in place IP works, including: layout, alignment elevation and the integrity of the elements being attached to or abutted. If any unacceptable conditions are identified then an equitable resolution shall be sought with Contractor O and the PMT. If Contractor F connects to an IP without identifying any deficiencies then Contractors O IP works will be considered as accepted without exception. This will not include any “latent or impossible to identify” problems. The PMT will act as arbitrator as required. 11. Upon acceptance of Contractor O works at IP Contractor F shall complete the
IP works and provide protection until final turnover of the works. 12. Complete all Snag list works associated with the IP
13. Be fully responsible for the procurement and construction of the part of system within its own area.
14. Identify IPs that are no longer relevant, and communicate such to Contractor O and the PMT in a timely manner. .
4.3
Contractor O Contractor O shall:1. Be the contractor that starts the works at an IP
2. Participate in the creation and maintenance of the IDT Interface Dependency Table
3. Participate in all requested IP coordination meetings
4. Mutually agree with Contractor F that the IP and associated data is correct, consistent and complete.
5. Provide all necessary input and support to the PMT
6. Populate interfaces completion dates in Interface Dependency Schedule (See Attachment 2) and update regularly to manage and monitor the timing of completion of interface points and gates. Copy to be provided to PMT. 7. Reach agreement on interfaces with other Contractors in a timely manner to
support the overall Project schedule.
8. Identify and agree with Contractor F the inspections, tests and construction and pre-commissioning records that are required to be performed and/or maintained by itself and Contractor F. This applies to situations where both Contractors have an overlap of activities at the interface such as the joint
hydrotest of both sides of an interface point at the same time. Otherwise the Contractors shall each be responsible for their 'side' of the interface.
9. Identify and agree with Contractor F any inspections, tests, drying and any other requirements to be witnessed by itself and Contractor O.
10. Complete the first stage of the works relating to subject IP per the documented agreements made with Contractor F.
11. Facilitate all requested inspections of the IP with Contractor F and or the PMT to confirm installation is installed per the contract requirements, position and elevation. Any and all unacceptable conditions shall be rectified promptly to prevent any schedule disruption of Contractor F and the overall program schedule.
12. Provide all required interface assistance including access, traffic control and any other reasonable or required assistance to allow Contractor F complete the IP.
13. Identify IPs that are no longer relevant, and communicate such to Contractor F in a timely manner. Also communicate to PMT.
14. Be fully responsible for the procurement and construction of the part of a System within its own area.
4.4
Project Management Team (PMT) will:1. Develop, communicate and maintain the Interface Management Plan and associated guidelines for:
• Identifying and defining interface points
• Assigning responsibilities of parties at each IP
• Data required to define each interface point construction phase 2. Provide Final resolution of any queries at interface points
5.0 INTERFACE TYPES
5.1
External InterfaceExternal Interface specifically refers to 3rd parties outside of the contractors nominated for the building envelope.
5.2
Internal InterfaceInternal Interface is an interface between Package Contractors nominated for the Building scope.
6.0 INTERFACE NUMBERING
The IP number will be assigned as follow
IP-d-w/u-nnnn Where:
Internal Interface Point Unit 1
Unit 2
Unit 3
Envelope
Internal Interface Point Package A
Package C
Package B
Unit
External Interface Point Unit 1
Unit 2
Unit 3
Envelope
External Interface Point Package A
Package C
Package B
d Discipline code, see below w/u Package Contractors Code
The first number shown (w) is Contractor O and the second number (u) is Contractor F.
nnnn Serial number (a unique number will be assigned for each discipline)
Discipline codes:
CAE Cable Tray - Electrical CAT Cable Tray – IT
CBE Cable Trench – Electrical CBT Cable Trench/Duct Bank - IT CC Civil Open Ditch
CF Civil Fence Crossing CR Civil Road CRT Road Crossing - IT E Electrical Cable F Firewater P Piping S Structural T Telecommunications Cable
TS Miscellaneous IT (Supplementary Interface Table) U Underground Piping (gravity flow only)
The following is the specific Package Contractors Codes, which will be used to provide clarity.
A Package A Contractor B Package B Contractor C Package C Contractor D Package D Contractor
For example: “IP-P-A/B-000004” would be a piping IP between the Package A Contractor and Package B Contractor.
7.0 COMMUNICATION
Packages Contractors shall communicate directly with each other to agree definition and completion of interfaces. PMT will maintain, the master SPOCs List which will include the names and contact details of the interface coordinators (Single Points of Contact) for all parties.
Communication may take place in a combination of the following formats: • Interface Queries (IQs)
• Transmission of documentation
• Meetings (with decisions subsequently recorded by IQs using MOM as a proof of agreements)
• Emails
Each Package Contractor shall appoint a SPOC to efficiently manage such communications. Each Package Contractor shall maintain a log of all IQs sent/received. IQs raised by any Contractor shall be addressed to the other Party’s Contractor SPOC’ and shall also be copied to the ‘PMT SPOC – additional people may be copied but all IQs must be sent only ‘To’ the Package Contractor SPOC’
7.1
Interface Queries (IQs)Interface Queries (IQs) may be raised by any Party to make a query, provide or request information or to confirm an agreement, using the form in Attachment P,
Contractors shall communicate directly with all other Contractors having an interest in the interface. All formal agreements and requests shall be recorded in an IQ.
7.2
IQ NumberingIQs shall be numbered in the form:
IQ-x-y-nnnn Where:
x Querying Party code y Responding Party code
nnnn Serial number (assigned by the querying Party)
The Party codes are included within the ‘SPOCs List’ which is maintained by PMT and regularly issued to all parties. The ‘SPOCs List’ also identifies which units are associated with each Party. For example, the second IQ from Package B Contractor to Package C contractor would be numbered IQ-B-C-002.
7.3
Transmission of DocumentationA record shall be kept of all documentation (documents and drawings) transmitted between Contractors and IQs shall be used for the transmittal.
8.0 INTERFACE GUIDELINES
The following defines the split of responsibilities between Contractors during construction at IPs and provides guidance on how to implement interfaces for different situations that may arise. The engineering requirements are defined in the relevant Program documents and drawings. The list of IPs are listed in Attachment 2
The following is general guidance
• For external interfaces between a Package and a 3rd Party contractor, then
the Package Contractor will be Contractor F.
• For internal interfaces between Packages, then Contractor F will be assigned by the Project Management Team.
8.1
Piping8.1.1 Above Ground Piping Interfaces 8.1.1.1 General
1. The default position shall be that Contractor F shall provide the required isolation, based on the service, at the IP for commissioning and operating purposes. This isolation could be blind flanges, figure 8 blinds, valves or other means. Contractor F shall provide any final spacers, gaskets and bolts required for the final closure of the IP.
2. Contractor F and Contractor O shall each provide their own test gaskets, blind flanges and bolts to allow testing of the piping within their respective scope. 3. After completion of flushing, testing, etc by each Contractor of his own
section of piping, Contractor F, after agreement with the other Contractor, remove the blind, install the spacer, and bolt up the flanges to complete the joint.
4. Each Contractor shall be responsible for the design and installation of insulation up to the Interface Point with Contractor F responsible for final closure of the joint.
CONTRACTOR F CONTRACTOR O
8.1.2 Underground Piping Interfaces 8.1.2.1 Firewater
1. Contractor O shall provide fire mains and appurtenances along the main roads for the overall firemain outside Buildings area and provide spurs off the ring main at the indicated on the drawings
2. The IP, which consists of a valve supplied by Contractor O will be installed in a valve box constructed by Contractor O. Contractor F will be responsible for grouting and sealing the valve box where his pipe protrudes.
3. Contractor O shall install and test the fire main up to the IP.
4. Contractor F shall install and test his fire main up to the isolation valve. 5. Contractor F shall provide the gaskets, bolts etc to make the final closure. 8.1.2.2 Other services
1. Each contractor shall construct, test, flush, clean, and back fill their piping up to their respective battery limits. Contractor F will then complete the system with a short section of pipe. These final joints will be considered “Golden Joints” followed by service test before backfilling.
8.2
Civil Interfaces 8.2.1 Road Interfaces1. Contractor O shall lay and compact the pavement materials to an acceptable stable slope beyond the extent of his wearing surface slope.
2. Contractor F shall ensure the soundness of this material prior to laying all subsequent layers.
CONTRACTOR F ANCHOR
ANCHOR TEMPORARY END
PIECES FOR TESTING
FINAL SPOOL, JOINTS & TESTING BY CONTRACTOR O
ANCHOR
ANCHOR TEMPORARY END
PIECES FOR TESTING
FINAL SPOOL, JOINTS & TESTING BY CONTRACTOR F
It is the responsibility of Contractor F to complete the interface, unless PMT instructed otherwise, recognizing that the edge of the courses, shown above, may have worn during the interim period. They will be responsible for rectification work to the edge.
8.2.2 Paving Interfaces
1. Paving interface shall typically be at the high point of paving.
2. Contractor O shall lay and compact the pavement materials to an acceptable stable slope beyond the extent of his wearing surface slope.
3. Contractor F shall ensure the soundness of this material prior to laying all subsequent layers.
CONTRACTOR O CONTRACTOR ICF
1.0m* 1.0m*
*Dimensions to be confirmed by CONTRACTOR F Asphalt/concrete paving
Base course
Interface
Centreline of Road
Interface
CONTRACTOR F CONTRACTOR ICF
*Dimensions to be confirmed by CONTRACTOR F 1.0m*
1.0m*
Surface wearing course Base course
Sub –base (if required) Sub -grade Interface Interface PLAN PLAN CONTRACTOR F CONTRACTOR F
CONTRACTOR ICF CONTRACTOR ICF
8.2.3 Ditch Interfaces
1. If the IP is a direct tie-in to the Contractor O ditch, Contractor O will Construct the ditch without provision for Contractor F, who will tie-in in accordance with Project Specifications.
2. If the IP is not a direct tie-in to the Contractor O ditch, Contractor O shall extend the reinforcement to permit continuity by Contractor F. 3. Contractors O & F shall provide initial construction joint with
Water stops.
8.2.4 Telecommunication Concrete Encased Duct Banks
1. The Contractor O ensures the integrity of the conduits to be free from damage. 2. Conduit ends shall be cap and plugged at the interface point to ensure that no
un-desired material will enter into the conduits.
3. The Contractor O shall leave at least 300mm of the conduit, free of concrete for the Contractor F to conveniently place the couplings.
4. Contractor F shall provide and install the couplings to properly connect the conduits. 5. Contractor F shall provide and install the completion of concrete encasement for the
conduit protection.
6. Contractor F shall coordinate with the Contractor O to execute mandrel throughout the length of the involved duct bank
CONTRACTOR F CONTRACTOR O 0.5m * exposed reinforcement Expansion Joint Slope Plan Elevation Section
8.3
IT/ Telecom InterfaceAll telecommunication cables inside buildings will be supplied and installed by Package Contractors as per Package Contractor scope, however ITC will terminate the cables at the wall faceplates and at the building interface terminal strip; Package Contractor will supervise terminations within the building.
8.4
Electrical InterfaceATTACHMENT 1 – INTERFACE QUERY FORM
No. Interface Point O F Type IP Status Days
ELECTRICAL
1 IP‐CBE‐B/A‐0001
B
A
Electrical Trench
2 IP‐CBE‐B/A‐0002
B
A
Electrical Trench
3 IP‐CBE‐B/A‐0003
B
A
Electrical Trench
4 IP‐CBE‐B/ICF‐0004
B
ICF
Electrical Trench
5 IP‐CBE‐B/ICF‐0005
B
ICF
Electrical Trench
6 IP‐CBE‐B/ICF‐0006
B
ICF
Electrical Trench
7 IP‐CBE‐B/C‐0007
B
C
Electrical Trench
8 IP‐CBE‐B/C‐0008
B
C
Electrical Trench
9 IP‐CBE‐D/C‐0009
D
C
Electrical Trench
10 IP‐CBE‐B/C‐0010
B
C
Electrical Trench
11 IP‐CBE‐D/A‐0011
D
A
Electrical Trench
12 IP‐CBE‐C/A‐0012
C
A
Electrical Trench
13 IP‐CBE‐D/C‐0013
D
C
Electrical Trench
14 IP‐CBE‐D/C‐0014
D
C
Electrical Trench
15 IP‐CBE‐D/C‐0015
D
C
Electrical Trench
16 IP‐CBE‐C/A‐0016
C
A
Electrical Trench
17 IP‐CBE‐C/A‐0017
C
A
Electrical Trench
18 IP‐CBE‐C/A‐0018
C
A
Electrical Trench
19 IP‐CBE‐C/A‐0019
C
A
Electrical Trench
Tray
21 IP‐CAE‐A/ICF‐0002
A
ICF
Electrical Cable
Tray
22 IP‐CAE‐A/ICF‐0003
A
ICF
Electrical Cable
Tray
IT
1 IP‐CBT‐ B/A‐0001
B
A
IT Duct Banks
2 IP‐CBT‐ B/A‐0002
B
A
IT Duct Banks
3 IP‐CBT‐ A/ICF‐0003
A
ICF
IT Duct Banks
4 IP‐CBT‐A /ICF‐0004
A
ICF
IT Duct Banks
5 IP‐CBT‐ A/ICF ‐0005
A
ICF
IT Duct Banks
6 IP‐CBT‐B/C‐0006
B
C
IT Duct Banks
7 IP‐CBT‐D/C‐0007
D
C
IT Duct Banks
8 IP‐CBT‐ D/C‐0008
D
C
IT Duct Banks
9 IP‐CBT‐D/C‐0009
D
C
IT Duct Banks
10 IP‐CBT‐ D/C‐0010
D
C
IT Duct Banks
11 IP‐CBT‐ D/C‐0011
D
C
IT Duct Banks
12 IP‐CBT‐B/C‐0012
B
C
IT Duct Banks
13 IP‐CBT‐ B/ICF‐0013
B
ICF
IT Duct Banks
14 IP‐CBT‐ B/A‐0014
C
ICF
IT Duct Banks
15 IP‐CBT‐C/A‐0015
C
A
IT Duct Banks
16 IP‐CBT‐D/A‐0016
D
A
IT Duct Banks
18 IP‐CBT‐ D/C‐0018
D
C
IT Duct Banks
19 IP‐CBT‐D/C‐0019
D
C
IT Duct Banks
20 IP‐CBT‐ A/C‐0020
A
C
IT Duct Banks
21 IP‐CBT‐ C/ICF‐0021
C
ICF
IT Duct Banks
22 IP‐CBT‐D/A‐0022
D
A
IT Duct Banks
23 IP‐CBT‐ B/C‐0023
B
D
IT Duct Banks
24 IP‐CBT‐ B/D‐0024
B
D
IT Duct Banks
25 IP‐CBT‐D/C‐0025
D
C
IT Duct Banks
26 IP‐CBT‐B/ICF‐0026
B
ICF
IT Duct Banks
27 IP‐CBT‐B/ITC‐0027
B
ITC
IT Duct Banks
28 IP‐CBT‐B/ITC‐0028
C
ITC
IT Duct Banks
29 IP‐CBT‐B/ITC‐0029
B
ITC
IT Duct Banks
30 IP‐CBT‐B/ICF‐0030
B
ICF
IT Duct Banks
31 IP‐CBT‐/‐0031
Intentionally
Not Used
32 IP‐CBT‐D/A‐0032
D
A
IT Duct Banks
33 IP‐CBT‐ C/EW‐0033
C
EW
IT Duct Banks
34 IP‐CBT‐ C/EW‐0034
C
EW
IT Duct Banks
35 IP‐CBT‐ D/EW‐0035
D
EW
IT Duct Banks
36 IP‐CBT‐ D/EW‐0036
D
EW
IT Duct Banks
37 IP‐CBT‐ D/EW‐0037
D
EW
IT Duct Banks
38 IP‐CBT‐ D/EW‐0038
D
EW
IT Duct Banks
3 3
40 IP‐CBT‐ D/EW‐0040
D
EW
IT Duct Banks
41 IP‐CBT‐ D/EW‐0041
D
EW
IT Duct Banks
42 IP‐CBT‐ D/EW‐0042
D
EW
IT Duct Banks
43 IP‐CBT‐ D/EW‐0043
D
EW
IT Duct Banks
CIVIL
1 IP‐CR‐A/ICF‐0001
A
ICF
Road
2 IP‐CR‐A/ICF‐0002
A
ICF
Road
3 IP‐CR‐A/ICF‐0003
A
ICF
Road
4 IP‐CR‐A/ICF‐0004
A
ICF
Road
5 IP‐CR‐A/ICF‐0005
A
ICF
Road
6 IP‐CR‐A/ICF‐0006
A
ICF
Road
7 IP‐CR‐A/ICF‐0007
A
ICF
Road
8 IP‐CR‐A/ICF‐0008
A
ICF
Road
9 IP‐CR‐A/ICF‐0009
A
ICF
Road
10 IP‐CR‐B/ICF‐0010
B
ICF
Road
11 IP‐CR‐A/B‐0011
A
B
Road
12 IP‐CR‐A/B‐0012
A
B
Road
13 IP‐CR‐A/B‐0013
A
B
Road
14 IP‐CR‐A/B‐0014
A
B
Road
15 IP‐CR‐A/B‐0015
A
B
Road
16 IP‐CR‐A/B‐0016
A
B
Road
17 IP‐CR‐A/B‐0017
A
B
Road
18 IP‐CR‐A/B‐0018
A
B
Road
3 3
19 IP‐CR‐B/ICF‐0019
B
ICF
Road
20 IP‐CR‐B/ICF‐0020
B
ICF
Road
21 IP‐CR‐B/ICF‐0021
B
ICF
Road
22 IP‐CR‐C/ICF‐0022
C
ICF
Road
23 IP‐CR‐D/C‐0023
D
C
Road
24 IP‐CR‐D/C‐0024
D
C
Road
25 IP‐CR‐D/C‐0025
D
C
Road
26 IP‐CR‐D/C‐0026
D
C
Road
27 IP‐CR‐A/C‐0027
A
C
Road
28 IP‐CR‐A/C‐0028
A
C
Road
29 IP‐CR‐A/C‐0029
A
C
Road
30 IP‐CR‐A/C‐0030
A
C
Road
31 IP‐CR‐D/C‐0031
D
C
Road
32 IP‐CR‐D/PREP‐0032
D
PREP
Road
33 IP‐CR‐D/PREP‐0033
D
PREP
Road
34 IP‐CR‐D/PREP‐0034
D
PREP
Road
35 IP‐CR‐D/PREP‐0035
D
PREP
Road
36 IP‐CR‐D/C‐036
D
C
Road
37 IP‐CR‐C/ICF‐0037
C
ICF
Road
38 IP‐CR‐C/ICF‐0038
C
ICF
Road
39 IP‐CR‐D/ICF‐0039
D
ICF
Road
40 IP‐CR‐D/PREP‐0040
D
PREP
Road
3 3
42 IP‐CR‐D/PREP‐0042
D
PREP
Road
43 IP‐CR‐D/PREP‐0043
D
PREP
Road
44 IP‐CR‐D/ICF‐0044
D
ICF
Road
37 IP‐CC‐A/B‐0001
A
B
Storm Ditches
38 IP‐CC‐A/B‐0002
A
B
Storm Ditches
39 IP‐CC‐A/ICF‐0003
A
ICF
Storm Ditches
40 IP‐CC‐A/ICF‐0004
A
ICF
Storm Ditches
41 IP‐CC‐A/ICF‐0005
A
ICF
Storm Ditches
42 IP‐CC‐B/ICF‐0006
B
ICF
Storm Ditches
43 IP‐CC‐C/PREP‐0007
D
C
Storm Ditches
44 IP‐CC‐D/C‐0008
D
C
Storm Ditches
45 IP‐CC‐ ‐0009
Intentionally Not Used46 IP‐CC‐D/C‐0010
D
C
Storm Ditches
47 IP‐CC‐C/A‐0011
C
A
Storm Ditches
48 IP‐CC‐A/C‐0012
A
C
Storm Ditches
49 IP‐CC‐ 0013
Intentionally Not
Used
50 IP‐CC‐C/A‐0014
C
A
Storm Ditches
51 IP‐CC‐A/RC‐0015
A
RC
Storm Ditches
52 IP‐CC‐D/C‐0016
D
C
Storm Ditches
53 IP‐CC‐D/C‐0017
D
C
Storm Ditches
54 IP‐CC‐C/RC‐0018
C
RC
Storm Ditches
55 IP‐CC‐D/C‐0019
D
C
Storm Ditches
56 IP‐CC‐D/C‐0020
D
C
Storm Ditches
57 IP‐CC‐B/C‐0021
B
C
Storm Ditches
58 IP‐CC‐B/RC‐0022
B
RC
Storm Ditches
59 IP‐CC‐B/C‐0023
B
C
Storm Ditches
60 IP‐CC‐B/C‐0024
B
C
Storm Ditches
61 IP‐CC‐C/ICF‐0025
C
ICF
Storm Ditches
62 IP‐CC‐C/ICF‐0026
C
ICF
Storm Ditches
PIPING
1 IP‐P‐B/A‐0001
B
A
Sanitary System
2 IP‐P‐B/A‐0002
B
A
Return ‐ Chilled
Water
3 IP‐P‐B/A‐0003
B
A
Supply ‐ Chilled
Water
4 IP‐P‐ ‐0004
Intentionally
Not Used
5 IP‐P‐ ‐0005
Intentionally
Not Used
6 IP‐P‐ ‐0006
Intentionally
Not Used
7 IP‐P‐ ‐0007
Intentionally
Not Used
8 IP‐P‐B/A‐0008
B
A
Potable Water
9 IP‐P‐B/A‐0009
B
A
Compressed Air
10 IP‐P‐B/A‐0010
B
A
Return ‐ Chilled
Water
11 IP‐P‐B/A‐0011
B
A
Supply ‐ Chilled
Water
12 IP‐P‐B/A‐0012
B
A
Sanitary System
13 IP‐P‐B/C‐0013
B
C
Return ‐ Chilled
Water
14 IP‐P‐B/C‐0014
B
C
Supply ‐ Chilled
Water
15 IP‐P‐B/C‐0015
B
C
Potable Water
16 IP‐P‐B/C‐0016
B
C
Potable Water
17 IP‐P‐B/C‐0017
B
C
Sanitary System
18 IP‐P‐B/C‐0018
B
C
Sanitary System
19 IP‐P‐D/C‐0019
D
C
Sanitary System
20 IP‐P‐D/C‐0020
D
C
Potable Water
21 IP‐P‐B/C‐0021
B
C
Utility Water
22 IP‐P‐B/C‐0022
B
C
Compressed Air
23 IP‐P‐B/C‐0023
B
C
Potable Water
24 IP‐P‐C/A‐0024
C
A
Potable Water
25 IP‐P‐C/A‐0025
C
A
Utility Water
26 IP‐P‐C/A‐0026
C
A
Sanitary System
27 IP‐P‐D/C‐0027
D
C
Supply ‐ Chilled
Water
Water
29 IP‐P‐ ‐0029
Intentionally
Not Used
30 IP‐P‐D/C‐0030
D
C
Potable Water
31 IP‐P‐ ‐0031
Intentionally
Not Used
32 IP‐P‐A/C‐0032
A
C
Potable Water
33 IP‐P‐A/C‐0033
A
C
Return ‐ Chilled
Water
34 IP‐P‐A/C‐0034
A
C
Supply ‐ Chilled
Water
35 IP‐P‐ ‐0035
Intentionally
Not Used
36 IP‐P‐D/C‐0036
D
C
Sanitary System
37 IP‐P‐D/C‐0037
D
C
Sanitary System
38 IP‐P‐D/C‐0038
D
C
Potable Water
39 IP‐P‐D/C‐0039
D
C
Sanitary System
40 IP‐P‐D/C‐0040
D
C
Sanitary System
41 IP‐P‐D/B‐0041
D
B
Potable Water
42 IP‐P‐ ‐0042
Intentionally Not Used43 IP‐P‐B/C‐0043
B
C
Sanitary System
44 IP‐P‐ ‐0044
Intentionally Not UsedUsed
46 IP‐P‐ ‐0046
Intentionally Not Used47 IP‐P‐ ‐0047
Intentionally Not Used48 IP‐P‐ ‐0048
Intentionally Not Used49 IP‐P‐ ‐0049
Intentionally Not Used50 IP‐P‐B/A‐0050
B
A
Sanitary System
51 IP‐P‐B/A‐0051
B
A
Potable Water
52 IP‐P‐B/A‐0052
B
A
Compressed Air
53 IP‐P‐C/A‐0053
C
A
Potable Water
54 IP‐P‐C/A‐0054
C
A
Compressed Air
55 IP‐P‐C/A‐0055
C
A
Utility Water
56 IP‐P‐C/EW‐0056
C
EW
Sanitary System
MUSSALA & CAFÉ
4
57 IP‐P‐C/EW‐0057
C
EW
Potable Water
MUSSALA & CAFÉ
4
58 IP‐P‐D/BRINE‐0058
D
BRINE
Sanitary System
GATE 459 IP‐P‐D/BRINE‐0059
D
BRINE
Potable Water
GATE 460 IP‐P‐D/EW‐0060
D
EW
Potable Water
GATE 561 IP‐P‐D/ICF‐0061
D
ICF
Sanitary System
GATE 562 IP‐P‐D/ICF‐0062
D
ICF
Sanitary System
GATE763 IP‐P‐D/ICF‐0063
D
ICF
Potable Water
GATE 7 33 3 3
64 IP‐P‐D/ICF‐0064
D
ICF
Sanitary System
PEDESTRIAN
SOUTH
65 IP‐P‐D/ICF‐0065
D
ICF
Potable Water
PEDESTRIAN
SOUTH