Via - Rev 4

Doc. No.
HM - LE - PRWIDE M0101 - DOC - MA -PMC -
Project: Hyderabad Metro Rail
Date: 29-11-2012
00 - 002
Revision. 3
Title: Interface Management Plan
Prepared by: D Srinath
Checked by : CS
Nagaraja
Page 1 of 28
Table of Contents
1
Introduction..........................................................................................................
1.1
1.2
Overview.............................................................................................................. 7
Objective..............................................................................................................8
Resource Management........................................................................................
2.1
2.2
3
Organisation and Roles & Responsibilities...........................................................8

Resource Requirement......................................................................................10
Interface Requirements......................................................................................
3.1
3.2
3.3
4
Allocation of Interface requirements...................................................................11

Interface description between contractors..........................................................11
Areas of concern................................................................................................13
Process Management........................................................................................
4.1
4.2
4.3
4.4
5
Change of interfacing requirement.....................................................................15

Verification and Validation of Interfacing Requirements......................................15
Testing and Commissioning on Interfaces..........................................................15
Quality Procedures.............................................................................................15
Document Management.....................................................................................
5.1
5.2
5.3
6
Reference Documents.......................................................................................16
Structure of Reference Documents....................................................................17
Version Control of Interface Documents.............................................................17
Communication..................................................................................................
6.1
Terms of Reference of Interface Meetings..........................................................19
6.2
Exchange of Information between Contractors..................................................20
6.3
Submission
to Employers Representative.........................................................20
18-05-2012
0
New
6.4
Request
for
Employer/ Employers
Representative Attention.............................20
DATE
REV. NO. Preparation
DESCRIPTION
Designed Checked Approved
7
REVISIONS
Interface Hazard Management...........................................................................
Programme........................................................................................................
LARSEN & TOUBRO LIMITED
8.1
8.2
CLIENT :
8.3
Key Activities......................................................................................................22
Key Dates.......................................................................................................... 24
CONSULTANT :
Critical Items / Critical Path................................................................................24
M/S LOUIS BERGER CONSULTING PVT.
RAIL (HYDERABAD) LIMITED

9L&T METRO Records.............................................................................................................
LTD
PROJECT :
HYDERABAD METRO RAIL PROJECT
List of Figures
SUPPLIER / CONTRACTOR:
LIMITED, Construction Viaduct

Figure
1LARSEN & TOUBRO
:
Interface
JOB No. LE 100514
Organisation.
10
TOTAL NO. OF PAGES
TITLE : :
Figure
2
Project
Life
Cycle
NAME
SIGN
DATE
.
INTERFACE MANAGEMENT PLAN FOR
DSGN
13 DS
Figure
3
:
Flow
chart
for
Interface
Management
Plan
CHKD
Process..
16
APPD
DOC. No.
RELEASED FOR
CODE
REV.
HM - LE - PRWIDE M0401 - DOC - MA -PMC - 00 - 002
PRELIMINARY
CONSTRUCTION
TENDER
INFORMATION
APPROVAL
Doc. No. HM - LE - PRWIDE M0101 - DOC - MA
Date: 27-12-2012
-PMC - 00 - 002
Revision. 4
Checked by : CS
Nagaraja
Page 2 of 28
List of Appendices
Appendix A.........................................................................................................................
Appendix B: Interface Specification Form.....................................................................
Appendix C: Interface Change Request Form (ICRF)..................................................
Acronyms & Definitions

The following definitions apply throughout this procedure and will be used in
interpreting the meaning of terms used in this document
Term
Definition
AFC
Automatic Fair Collection
ASS
Auxiliary sub-station
COM
Communication
CSD
Combined Services Drawings.
CW
DBS
DCIV
DME
DMP
ER
GS
HVAC
IM
IMP
IMPG
MIM
MSS
OETS
PSS
Civil Works
Depot building services
Depot civil
Depot Maintenance equipment
Design Management plan
Employers Representative
General Specification
Heating ventilation air conditioning
Interface Manager
Interface Management Plan
Interface Management Programme
Master interface matrix
Manual of Specification and Standards
Overhead Electrical traction system
Power supply and Supervisory Control And Data Acquisition
system
Quality Management plan
Rolling stock
Receiving sub-station
Signal and train control
Station building services
Station civil
Track work
Technical Specification
Viaduct
QMP
RSK
RSS
S&T C
SBS
SCIV
TRW
TS
VIA
Date: 27-12-2012
-PMC - 00 - 002
Revision. 4
Checked by : CS
Nagaraja
Page 3 of 28
Introduction
The Hyderabad Metro is a proposed rapid transit system for the city of
Hyderabad, Andhra Pradesh, India. The present scope of project includes three
corridors along high-density traffic corridors, spanning approximately 71kms.
Corridor-1 will run from north to south and will be 28.87 km long, connecting 27
stations from Miyapur to L. B. Nagar. Corridor-2 will be 14.78 km long, connecting
14 stations from Parade Grounds to Falaknuma. The Corridor-3 will run from north
to south and will be 27.51 km long, connecting 23 stations from Nagole to
Shilparamam.
The Hyderabad Metro will be an elevated system with a 9m-wide viaduct
structure. The viaduct will run from the central median of the road and will have
two tracks. The tracks will be 1435 mm standard gauge. The system's electrical
traction will be AC and power will be supplied through the overhead electric
system.
1.1
Purpose of Document
This plan is wholly based on requirements captured in General Specification for

each interface, wherein the Contractor shall develop, an IMP which is mutually
acceptable to other interfacing Contractor/s. The purpose of this plan shall
identify the system and the sub-systems as well as the civil works and facilities
with interfacing requirements. It shall define the authority and responsibility of
the Contractor's and Other Contractors' staff involved in interface management
and development.
This Plan describes the methodology for managing interfaces to achieve a
comprehensive design covering all foreseen aspects specific to the VIA system. It
shall identify the information to be exchanged, precise division of responsibility
between the Contractors and integrated tests to be performed at each stage of
the Contractor's works. It addresses the works programme of the Contract to
meet the key dates of each Contractor and highlight programme risks if any to
Employer Representative. It shall also indicate dates for the commencement and
completion of each principal activity and the key dates for exchanging system
data and interface design information by the Contractor and the Interfacing
Other Contractor.
This Interface Management Plan (IMP) outlines the activities to demonstrate how
the Contractor proposes to achieve a coordinated VIA System, compatible with
design and construction carried out by other interfacing contractors. The plan
describes the methods and strategies for managing interfaces. It also provides
control of associated interfaces as the project grows through engineering,
construction, installation and closeout.
1.2
Overview
The plan outlines the process for effective exchange of information for a safe &
effective execution of the Hyderabad Metro project especially with large number
of interfaces that increase the task complexity. The Interface Management Plan
allows identification of critical interfaces through a structured approach leading
to early identification of potential issues and resolution thereon.
Date: 27-12-2012
-PMC - 00 - 002
Revision. 4
Checked by : CS
Nagaraja
Page 4 of 28
The interfaces covered in this document is specifically for VIA system, but with
its association with other contractors, which are different in their nature, the
document is therefore organized considering how these interface activities would
be managed as a whole. This interface management plan shall be applicable
from Design, Execution and handing over the VIA system
The Interface management process would involve various stages from design,
manufacturing, construction, installation, testing & commissioning including final
acceptance of the Employer.
1.2.1 Objective
The objective of the Interface management plan is to facilitate agreements with
other stakeholders regarding roles & responsibilities, providing interface
information and identification of critical interfaces. It also ensures that all
interfaces between the VIA & other Contractors as required for the completion of
scope of works of the Contract are identified and controlled. This shall ensure
integrity between the different elements associated with the project.
Management
2.1
Organisation and Roles & Responsibilities
The following organogram shows the roles and responsibilities identified to

coordinate all interface activities under the Contract with that of the Interfacing
Parties.
Team level VIA Interface Organisation
Date: 27-12-2012
-PMC - 00 - 002
Revision. 4
Checked by : CS
Nagaraja
Page 5 of 28
Figure 1 : VIA Interface Organisation
Responsibility and authorities of the identified Interface members are as follows:
2.1.1 Project Manager

The Project Manager for VIA shall be responsible for all contractual, cost and
project delay issues for all interface activities. This may include resolution of
interface conflicts on scope of supply and responsibilities, and specific arbitration
that may be required among the interfacing parties.
Project Manager shall extend his support to the Interface Manager for achieving
interface settlement according to the time schedule.
Shall also be responsible for ensuring that interface agreement does not conflict
with any other Contractor interfaces and scope of responsibilities
2.1.2 Chief Interface Manager

The roles of Chief Interface Manager shall be to support the coordination of the
Interface Manager (VIA ) with other nominated Interface Managers of L&TC. .The
Chief Interface Manager shall ensure the overall Interface Management plan is
followed throughout the Project Delivery phase.
The Chief Interface Managers responsibilities are:
Date: 27-12-2012
-PMC - 00 - 002
Revision. 4
Checked by : CS
Nagaraja
Page 6 of 28
1) Facilitate consultations with nominated Interface Managers within L&T C on

regular basis to achieve agreements on interfaces;
2) Facilitate consultations between Interface Managers of L&T C and that of
Client Contractors, as required
3) Develop and manage the Interface Action Log for all interface issues that
provided status of interfaces, closed out issues;
4) Resolution of the interface issues and conflicts arising between Interface
Managers;
5) Facilitate specific meeting on request of any interfacing parties;
6) Monitor and validate the exchange of Interface data between the various
package Contractors;
7) Extend the information to the Client L&T Hyderabad Metro Rail Limited.
2.1.3 Interface Manager

Interface Manager (IM) of VIA is primary contact person for internal and external
personnel and will establish direct lines of communication between the interface
partners of the distinct interfaces. IM shall be the single point of contact for
interface meetings, actions, planning, scheduling and coordination. The IM shall
manage all interface/issues between design and execution teams. The IM shall
ensure that all interface issues are captured, managed and brought to the
Interface Meeting for a timely resolution.
The IM ensures that the process identified in this plan is adhered to and followed.
The IM will coordinate the interfaces activities performed under the responsibility
of the Project Manager and the Chief Interface Manager.
The Interface Managers responsibilities are:
1) Identifying, verify and record the interfacing activities of the system and
interfacing sub-system and provide latest information to Chief Interface
Managers for review;
2) Note the changes and inform the impact to other Interface Manager through
the Interface meetings;
3) To communicate with the Interfacing contractors for information that can
impact the coordination Drawings. Keep the Project Manager, Design
Manager, and Construction Manager abreast of the current interface issue.
4) To coordinate for all Interface activities where VIA is the Lead & Match
Contractor;
5) To convene meetings with the Match Contractors wherever VIA is the Lead
Contractor and subsequently prepare the necessary Interface Specification
Sheets and DID for sign off with the respective Match Contractor. Updation of
the signed off documents shall be posted to all concerned;
6) To ensure that this plan, associate program and subsequent procedures are
kept updated;
7) To support the Project Manager in developing interfaces verification &
validation test plans and activities;
8) Develop and maintain Detailed Interface Document;
9) Following-up the Interface Requirement Specifications;
10)
Coordinate with the other Contractor to establish coordinated CSD & SEM
Drawings [case to case];
11)
IM shall ensure compliance to the Works program of VIA and exchange
data in time for other Contractors to meet their Works program;
12)
To identify & resolve the Interfaces with Employers Contractors who may
be subsequently identified during the course of the Project. To keep up to date
the VIA and other contractors interface list.
Date: 27-12-2012
-PMC - 00 - 002
Revision. 4
Checked by : CS
Nagaraja
Page 7 of 28
2.1.4 Execution Manager
Execution of works implementing interface actions agreed in the

interface meetings and in interaction with Interface Manager.
Taking up evolving Interface issues to Interface Manager for
resolutions
2.1.5 Design Manager
2.2
Preparation of GFC drawings incorporating resolved interface issues

in line with section 4
Preparations of as built drawing after the works are executed
incorporating the Interfaces, as part of validation of interfaces.
Update Interface Manager VIA of all such information and
incorporation.
Resource Requirement
The resource requirements of manpower is the allocation/mobilisation of staff for

VIA. This description of the manpower shall be explicitly for the VIA team, the
other contractors shall be limited to the interface manager.
The resource requirement for implementation of IMP is broadly classified to
manpower, tools and logistics.
The manpower allocation is described in section 2.1 and the roles identified in
referred section is mentioned in Appendix A
The tools which are used for effective interfacing are
Interface management plan (IMP)
Detailed Interface Document(DID)
Interface Action Log register
Interface Demarcation Document
Request for information and.
Information change request form
Logistics of VIA contractor will be adhered to/by the other interfacing contractors
and the project schedule. All interface logistics issues will be based on Section
8.1 Key activities and Section 8.2 Key dates.
Interface Requirements
The interface requirements management system is to be implemented between

the Lead Contractor and Match Contractor. It is considered that the above
management provides effective control of information flow related to systems
requirements and in particular the preservation of information for the project life
of the system with respect to the changes in the system and its environment.
The approach proposed in this plan is considered sufficient to meet the package
requirements in order to successfully deliver the Hyderabad Metro Project.
Date: 27-12-2012
-PMC - 00 - 002
Revision. 4
Checked by : CS
Nagaraja
Page 8 of 28
The interface requirements shall be identified prior to the Design & Execution
stages by all interfacing parties and entities so that re-design, re-work and
associated costs and schedule impacts are minimized. This shall be
communicated to all affected entities.
The main sources of interface requirements to be imported and traced originate
from:
General Specification;
Technical specification
Interface specification [Appendix A1 to A8];
The Interface Requirements shall be tabulated in Task Allocation Table (TAT) for
all the interfaces listed in the VIA IRS and additional, if any.
3.1
Allocation of Interface requirements
The interface requirements are generally classified in to Design & Execution

Interfaces and the communication shall be established with each of the Other
Contractor. The information shall be regularly updated and periodically reported
to Employer as per the template in Section 3.2 below.
3.2
Interface description between contractors
In continuation to the allocation of interface requirementError: Reference source

not found the following Task Allocation table (TAT) sections identify the
description between the contractors.
Interface ID
Interface
Category
Interface
Description
Responsibi
lity
Of VIA
Responsibility
of Other
Contractor
Remarks
This table (TAT) indicates the responsibility and status in remarks column of all
the interfaces identified and evolved in the design and execution process.
Supporting documents for this table shall be the Interface Specification Forms
(refer Appendix B) and DIDs.
VIA Contractor has responsibility for the design, installation, coordination, testing
and commissioning of the Viaduct systems. Deal with problems occurring during
the implementation of interfaces and ensure the integrity of the interfaces
between the VIA and interfacing partners.
The interfacing partners with Viaduct are listed below:
1) Interface with Communications (COM)
2) Interface with Depot Civil Works (DCIV)
3) Interface with Overhead Electric Traction System (OETS)
Date: 27-12-2012
-PMC - 00 - 002
Revision. 4
4)
5)
6)
7)
8)
Interface
Interface
Interface
Interface
Interface
with
with
with
with
with
Checked by : CS
Nagaraja
Page 9 of 28
Signaling & Train Control (S&TC)

Station Building Services (SBS)
Station Civil Works (Station Civil (SCIV)
Track work (TRW)
Power Supply (PSS)
The interfaces listed in the IRS of the VIA provide the baseline for the interfaces
identified.
Further based on the allocation of roles of via as lead or match contractor with
other interfacing partners is listed below.
Interfacing
Partners
with VIA
OETS
TRW
SBS
SCIV
DCIV
COM
S&TC
PSS
Lead
Match
Contractor
Contractor
OETS
VIA
SBS
SCIV
VIA
COM
S&TC
PSS
VIA
TRW
VIA
VIA
DCIV
VIA
VIA
VIA
The details on the above interfaces shall be as per the respective Detailed
Interface Document to be established with each of the above Contractors.
Both the Lead and Match have similar obligations towards interface management
process. The Roles and Responsibilities of Lead and Match Contractor are
tabulated in the table below:
Responsibility Matrix of the Lead and Match

contractors
Role & Responsibility
1. Initiating the arrangements for interface meetings
2. Arranging the recording and issuing minutes,
(Action Log ) of Interface Management Meetings
3. Preparation of jointly prepared documents and
their
subsequent
revisions
viz.
Interface
Management Plans ( IMP ); Detailed Interface
Lead
Match
Date: 27-12-2012
-PMC - 00 - 002
Revision. 4
3.3
Checked by : CS
Nagaraja
Role & Responsibility

Documents ( DID), method statements, interface
test specifications and reports
Initiation for preparation of the jointly prepared
document.
Preparation of document with respect to Lead
Contractors scope of work and responsibility
Preparation of document with respect to Match
Contractors scope of work and responsibility
Signing of the jointly prepared document and
submission
individually
to
the
Employers
Representative
for
information
comments/
approval
Lead
Page 10 of 28
Match
Areas of concern
Any two Contractors of an interface will have an equal degree of responsibility for
achieving interface settlement according to the time schedule, under the
coordination and supervision of the Interface Manager with support from the
Project Manager.
The concerned Contractor shall ensure that all resolutions will be documented
through technical specifications, drawings and detailed schedules agreed by the
affected Contractors. The Project Manager will approve the final resolution.
Ensure that the resolved or unresolved Interface is brought to the notice of
Employer or Employers Representative
Process Management
Various elements in association with the IMP that encompass the entire process
in identified in the
section
Date: 27-12-2012
-PMC - 00 - 002
Revision. 4
Checked by : CS
Nagaraja
Page 11 of 28
Figure 1: Illustrated Flow chart for VIA Interface

Management
4.1
Change of interfacing requirement
The change shall be initiated formally through an Interface Change Request Form
(ICRF). This should be circulated to all the stakeholders for their reviews and
comments. When an ICRF is initiated to propose a change in interface
Date: 27-12-2012
-PMC - 00 - 002
Revision. 4
Checked by : CS
Nagaraja
Page 12 of 28
requirements it shall be captured in the interface action log. If one of the

interfacing contractors requests for a change, this will be managed through an
ICRF, please refer Annexure C for the template. The form shall be used only if
an interfacing contractor requests a change to some aspect which has been
previously agreed in the Interface meeting. The originator has to declare the
close-out of the ICRF in the subsequent Interface meeting, and accordingly
reflect in the action log.
However, during the process if any conflict/ clarification arise, the decision by the
Employers representative shall be final and binding on partners. The same will
be dealt under respective contract conditions and obligations.
4.2 Verification
Requirements
and
Validation
of
Interfacing
Testing activities shall be based on the requirements capture and referred in

Detailed Interface Document. This shall ensure compatibility between systems
and that every component functions and performs in tandem. Task Allocation
Table shall be made to ensure that the identified interface requirements are
verified and validated. This will be developed systematically and shall thoroughly
evaluate all individual system components and their integrated performance.
The V&V needs shall be captured in the T&C Plan, if applicable, which will cover
subsystem qualification testing, factory inspection and testing, installation tests,
on-site inspection, on-site integrated test and finally system acceptance test and
inspection.
As part of verification the preliminary drawings/documents shall then be
updated, revised and issued to relevant Interfacing Parties for review and
confirmation, to resolve any outstanding interface coordination issues. The entire
process of review, comment, feedbacks and meetings shall be repeated until the
final set of coordinated and refined DWGs are completed and submitted to the
LTMRHL/CE for second stage verification before they are progressively issued for
site construction use.
4.3
Testing and Commissioning on Interfaces
The approach to be adopted by the Contractor for the management of interface

in the Testing and Commissioning stage shall be addressed in the respective VIA
Testing & Commissioning Plan
HM-LE-PRWIDE-M0101-DOC-MA-PMC-00-xxx
4.4
Quality Procedures
All activities and works described in the present document would be performed
in line with the approved Quality Management System confirming to
requirements of ISO 9001:2008.
Date: 27-12-2012
-PMC - 00 - 002
Revision. 4
Document Management
5.1
Reference Documents
Title of Document
Checked by : CS
Nagaraja
Page 13 of 28
Reference
Detailed Interface Document of VIA with

OETS
TRW
HM - LE - PRWIDE M0101 - DOC - MA

-PMC - 00 -XXX
-PMC - 00 - XXX

SBS

-PMC- 00 - XXX

SCIV

-PMC- 00 - XXX
Detailed
DCIV
Detailed
COM
Detailed
S&TC
Detailed
PSS
General
Interface Document of VIA with

-PMC- 00 - XXX
Interface Document of VIA
with
with
with

PMC - 00 - XXX
-PMC- 00 - XXX
-PMC- 00 - XXX
Specification
Architectural
works
for
and
Civil
MEP
Works
works
January 2012
Interface Requirement Specifications (IRS)
HM-AC-PRWIDE-M0101-DOC-CD-VIA01-001
Manual of Standards and Specifications

(MSS)
Contract Agreement and Conditions of
Contract (COC) Vole II Jan 2012
Co-ordinated Construction Plan
Combined Services Drawings (CSD)
Structural
Electrical
Mechanical
(SEM)
drawings
Interface Demarcation Diagrams (IDD)
Detailed Interface Documents (DID )
Project Management Plan
Work
Plan
(incorporating
HM-LE-PRWIDE- M0101-DOC-MA-PMC00-001
Works
Programme and Submittals Schedule)

Quality Plan
Date: 27-12-2012
-PMC - 00 - 002
Revision. 4
Quality Assurance Management Plan
Checked by : CS
Nagaraja
Page 14 of 28
HM-LI-PRWIDE- M0101-DOC-MA-QMS00-001
System Assurance (RAMS) Management

Plan
Design Management Plan
Environmental Plan
Installation Plan
Testing and Commissioning Management
Plan
Defects Liability Management Plan
Maintenance Plan
5.2
Structure of Reference Documents
Apart from the plans, the reference Interface documents, namely the following -DID for each contractor
-
No.
DID for each Contractor

o The template and structure of the document shall be as per the
detailed document developed and mutually agreed upon with each
of the other Contractors and Employer
Weekly Interface Action Log shall have the following tabular structure
System
5.3
Dated
Interface Issue From

Raised
To
Remarks
Status
Interface Change Request Form shall be as detailed in Appendix C

Interface Specification Form detailed in Appendix B shall form a part of the
DID, made for each of the Interface activity.
Version Control of Interface Documents
Respective Quality management system for VIA informs on the version control of
all documents for the project, this includes the interface documentation.
Configuration management addressed as part of Quality Management System for
the project is equally applicable to the Interface Management. The same
guidelines are applicable and followed through the Interface Documentation
included in this plan.
Date: 27-12-2012
-PMC - 00 - 002
Revision. 4
Communication
Checked by : CS
Nagaraja
Page 15 of 28
Date: 27-12-2012
-PMC - 00 - 002
Revision. 4
6.1
Checked by : CS
Nagaraja
Page 16 of 28
Terms of Reference of Interface Meetings
The terms of reference of interface meetings is drawn out as per below example.
The document reference is provided in the Reference document
6.2
Exchange of Information between Contractors
Date: 27-12-2012
-PMC - 00 - 002
Revision. 4
Checked by : CS
Nagaraja
Page 17 of 28
The process for the exchange of information between the contractors has been
identified in the Interface Management flow chart, please refer section 4.1 on a
more specific note that exchange of information shall be captured in interface
register and shall be available for engineering traceability
The registers of the interface information and Interface Logs shown below are the
core tools that shall be used for communication on interface issue.
a) RFI Form - Request for Information(Refer Appendix F) ;
b) Interface Action Log;
c) RFI Status Register;
d) Interface Change Request Form (ICRF);
6.3
Submission to Employers Representative
The approach to be adopted by the contractors on the submission of the

Interface Management Plan to Employers Representative shall be through
Electronic Document Management System (EDMS).
6.4 Request for Employer/ Employers Representative

Attention
The main criteria in requesting for Employer / Employers Representative
attention is to request intervention if an issue is not resolved between two
interfacing contractors
Any major re-work or delay arising due to fulfilment of interface requirements
due to improper/inadequate/absence of information, same shall also be brought
to the attention of Employer / Employers Representative.
The clarifications and conflicts shall be dealt under respective contract conditions
and obligations.
The Project identified Electronic Document Management System (EDMS) as
formal method of transmission of information, shall be used to bring Employer /
Employers Representative attention
Interface Hazard Management
7.1
Strategy and Approach
The foreseen interface hazards shall be brainstormed as part of Interface

meeting and the outcome captured in the interface hazard log. This shall be
managed by the Interface Manager and periodically reviewed with the Project
Manager.
Please refer table the following foreseen Interface Hazard table that shall be
followed as part of the Interface management. The interface hazard log as per
below shall be updated continuously during the project life cycle.
ID
VIA_HA
Z-001
Syste
m
OETS
Hazard
Cause
Consequence
Mitigation
plan
Falling of OHE Inadequate
System failure 1)
Ensure
mast.
threaded length of followed
with sufficient
the U bolt for fixing other losses.
threaded length
the OHE mast.
in
design/drawing.
2) Inspect bolts
Date: 27-12-2012
-PMC - 00 - 002
Revision. 4
ID
Syste
m
Hazard
Cause
Checked by : CS
Nagaraja
Consequence
Page 18 of 28
Mitigation
plan
during deliver.
3)
Inspect
available length
during casting.
4) Rejection of
parapet
segment
with
improper
threaded length.
Definition of the terms used in Interface Hazard log as follows:

ID: Unique identifier to distinguish every Interface Hazard;
System: The system from which this hazard is originating from;
Hazard: A physical situation resulting in system failure;
Cause: reasons how and why a particular hazard may come into existence;
Consequence: an unintended event or series of events that results in death,
injury, loss of a system or service, or environmental damage.
Programme
The interface activities as detailed in the IRS of VIA TS and any other as required
for the project shall be ensured in a timely manner to meet the Key dates of the
respective VIA Works program and also ensure that the other Contractors
achieve their respective milestone dates.
8.1
Key Activities
The following table shows the Key activities envisaged for the establishment of
the Interface and sign off on the DID with each Contractor. However, the detailed
interface requirements along with additional interfaces as required with each
Contractor shall be established and mutually agreed with other Contractors.
Sl
no
1
2
3
4
VIA Activity
Interface Contractor/s
Area of interface
Casting of Piers, Segments

OETS/PSS
Respect the SOD
and Parapets
/TRW/SBS/SCIV/DCIV/COM/S&TC clearances
Provision of OHE
Casting of Parapet walls
Masts
OETS
including design
Provisions for SME
Coordination for exact
Provide necessary openings
requirement
of
in Viaduct structures for
OETS/SBS/SCIV
openings for location
cable crossing /openings
and size
Piers,
segments
and
OETS/SBS
Detailed drawing and
ParapetsProviding
of
installations of the
earthling
connections,
earthling arrangement
earthling connection for
, connections and
Date: 27-12-2012
-PMC - 00 - 002
Revision. 4
Hand Rail
OETS/PSS
Design and construction of

Sub Structure
TRW
7
8
9
10
11
12
13
Coordinate
Design of the station
viaducts including providing
dowel bars in pier and pier
cap and diaphragm for
further
construction
by
others
Construction and installation
of precast Box girder for the
main Viaduct within the
station location.
Construction of all the piers
including those supporting
the station Viaduct
Shall
coordinate
and
provide additional width (if
required) to accommodate
the egress steps as per the
requirements of statutory
clearances
seamless
cable
duct
13 containment from viaduct to
station
14 Design and construct the
depot access ramp.
Page 19 of 28
continuity
Leaving openings in Viaduct

Structure and later on
sealing
Design and provide the

transition slabs at the
junction of ballast less and
ballasted track on the ramp
and further shall prepare the
ground ( including sub
grade ) with grading and
drainage
in
remaining
portion of the ramp
Design and construction of
Drainage system for Viaduct
Clear and hand over the
Track construction envelope
Checked by : CS
Nagaraja
TRW
TRW
TRW
TRW
Providing Cable and

dropping from Viaduct
to ground for 25 KV ,
LT and control cables
etc
Construction of Track
plinth / slab/ turn out/
cross over locations/
Provision of transition
slabs between ballast
less and ballasted
track
and
further
laying of track on the
ramp
Details
of
Track
Design
Clearance of track
construction envelope
viaduct lighting and
Emergency
socket
outlets.
SCIV
Supply of dowel bars

and construction of
concourse
and
platform level cross
girders
SCIV
Construction
and
installation of precast
Box girder
SCIV
Construction of all the

piers
SCIV
Egress Steps
SCIV/PSS
DCIV
Seamless cable duct

containment
from
viaduct to station and
vice versa.
Civil interfaces and
Alignment
Date: 27-12-2012
-PMC - 00 - 002
Revision. 4
Checked by : CS
Nagaraja
Page 20 of 28
coordination
15
16
17
18
19
20
21
Design, coordinate, supply

and
install
the
cable
containment/ cable trough
etc. and provide openings in
the cable trough as per
COM
contractors
requirements
Design and coordinate the
cable containment, cable
trough along with any
openings required for cable
crossings towards the track
for signalling cables along
Track side
Shall also keep provision
of space for line side
equipments
Coordination and Provision
of adequate space for SAB (
Signaling Apparatus Box )
along Viaduct
Coordination and Provision
of adequate space for signal
mast along Viaduct
Allow the side wall of
viaduct for fixing cable
containment
by
PSS
Contractor.
Provide necessary openings
in Viaduct structures for
cable crossing from viaduct
to station and vice-versa,
inside the station from one
side to other on both ends,
viaduct to viaduct and
trackside
to
top
of
flange/cable trough/parapet
wall/any part of the Viaduct.
Develop SEM drawings
based on requirement
COM
COM
cable
containment system
along trackside and
station platform
S&TC
Installation
of
Trackside equipment
and
cabling
infrastructure
for
signalling along the
viaduct
for
all
corridors
S&TC
Mounting of SAB /
trackside box and
other
line
side
equipments
S&TC
Mounting
post
of
signal
PSS
Arrangement
for
laying power and
control cables on the
Viaduct
PSS
Providing openings in
Viaduct structures
PSS
SEM Provisions
Doc. No. HM - LE - PRWIDE M0101 - DOC - MA -PMC -
Date: 29-11-2012
00 - 002
Revision. 3
Checked by : CS
Nagaraja
Page 21 of 28
KEY DATES SCHEDULE FOR VIADUCT

SL.N
O
KEY DATE
DISCRIPTION
ACCESS TO SITE
RESPONSIBILITY
EMPLOYER
STAGE 1
STAGE 2
STAGE 3
STAGE 4
STAGE 5
STAGE 6
START
COMPLETE
START
COMPLET
E
START
COMPLETE
START
COMPLETE
START
COMPLETE
START
COMPLETE
4/13/12
7/13/12
4/13/12
11/13/12
4/13/12
12/13/12
4/13/12
9/13/13
4/13/12
3/13/13
4/13/12
6/13/14
Date: 27-12-2012
-PMC - 00 - 002
Revision. 4
Checked by : CS
Nagaraja
Page 22 of 28
PERMANENT
WORKS FOR
VIADUCT WORKS
CONTRACTOR
7/14/12
4/13/2014
11/14/12
10/13/14
12/14/12
2/13/15
9/14/13
8/13/15
3/14/13
4/13/15
6/14/14
12/13/2015
PARAPET AND
OTHER FINISHES
CONTRACTOR
3/14/13
6/13/2014
7/14/13
12/13/14
6/14/13
4/13/15
3/14/14
10/13/15
10/14/13
6/13/15
3/14/15
2/13/2016
8.2
Key Dates
Based on the contract schedule, Employers requirement and interface meetings/agreements, the following table will be used for
monitoring the duration of the agreed up on key dates for the interfacing actives / Issues
Key Dates Schedule for Viaduct
Doc. No. HM - LE - PRWIDE M0101 - DOC - MA -PMC -
Date: 29-11-2012
00 - 002
Revision. 3
Checked by : CS
Nagaraja
Page 23 of 28
1. Access to Site Availability of 8m ROW (within Barricading) free from

Encumbrances and Utilities to commence construction.
8.3
Critical Items / Critical Path
The critical Items/Critical Path shall be as per the Overall master Works Program
to which the VIA Works Plan meets the requirements.
Accordingly Interface activities shall be relevantly lined up with the Works Plan,
as required
Records
All records shall be maintained as per the table below:
Document Number
APPENDIX A
Description
Retention Period Minimum
Date: 27-12-2012
-PMC - 00 - 002
Revision. 4
Checked by : CS
Nagaraja
Page 24 of 28
List of Role Players for Interface Requirements

Role
Contact
number
Sesha +91
9959022309
Name
Project Manager
Mr K
reddy
Email
k_sr@lntecc.com
VIA
Manager
1,3,5/2
Execution Mr AH Khan
Stage
+91
9502009990,
ahkhan@lntecc.com
VIA
Manager
2,4,5/1
Execution Mr K Mohan
Stage
+91
9000012265,
kmohan@lntecc.com
VIA
Execution Mr
D +91
Manager -ROBs
Sukumaran
9912199910
dsukumaran@lntecc.co
m
+ 0404023687173
raghavendrapandey@lnt
ecc.com
Chief
Manager
Interface Mr
Sanjeev +91
Sharma
9949922377
sanjeev.sharma@lntec
c.com
Interface
VIA
Manager Mr
C.
Nagaraja
csn@lntecc.com
Interface
SCIV,SBS
Manager Mr
Duvvuri +919849471
Gangadhara
934
Sastry
Manager
dgsastry@lntecc.com
Interface
OETS
Manager Mr
Srihari
rsrihari@lntecc.com
Interface
PSS
Manager Mr PVS Pawan +91

Kumar
8886856717
Interface
TRW
Manager Mr Rajan
Kumar
VIA Design Manager
Interface
DCIV, DBS
Interface Manager RS
Mr R Pandey
Mr
Alston
S. +91
9000222047
Ravi +91
9878166363
D +919989993
685
pvspk@lntecc.com
rajand.kumar@lnties.c
om
John +91
7893223964
Interface
S&TC
Manager Boyd
Mckillican
Interface
COM
Manager Diogo Cortez
boyd.mckillican@thale
sgroup.com
+351
320663
915 Diogo.cortez@thalesgr
Rem
arks
Date: 27-12-2012
-PMC - 00 - 002
Revision. 4
Checked by : CS
Nagaraja
oup.com
Interface
AFC
Manager TBD
TBD
TBD
Page 25 of 28
Date: 27-12-2012
-PMC - 00 - 002
Revision. 4
Checked by : CS
Nagaraja
Page 26 of 28
Appendix B: Interface Specification Form
INTERFACE
SPECIFICATION
Ref: VIA -00001-A-01
Contractors
Sequence
Number
Contract
Designation
Date of Issue
d/m/y
Initiating
Contractor
Interface Manager
Responding
Contractor
Interface Manager
Interface
Specification
Required for;
Response
Required by;
Signature
Signature
Reviewed by;
Design
Sections
Track
work/OETS
Civil Work
Station Arch. /
Building
Services
Systems
Description of the Interface
Specific Details of the Interface
Location
Drawings / Specifications Attached

Title
Document
Prepared by:
Drawing / Specification Ref.
Name
Date
Drg. Issue
Document References (if any)
Date: 27-12-2012
-PMC - 00 - 002
Revision. 4
Checked by : CS
Nagaraja
Page 27 of 28
Appendix C: Interface Change Request Form

(ICRF)
Discipline/Contract Package:
Name:
Unique ICR No:
Ref.
Attachments
Subject
Attribute:
Date:
Title:
Description:
Detailed Recommendation:
Reasons for Change/Justification: (Problem/Error/Non Conformance/ Improvement/
Enhancement/ Change due to other factors)
Implications:
Cost:
Importance
to
Originator:
(Critical/ High/ Medium/
Low)
Time:
Implications Remarks:
Areas of Impact:
Documents and Deliverables requiring updates:
Risk involved (if any):
Recommende
d
for
Approval
Recommen
ded
for
Approval
Proposal
Finalizatio
n
Interface
Manager
Discipline
Head/
Project
charge
Interface
Partners
&
Approved by
LTMRHL and
CE
(Technical)
In
Approved
by
LTMRHL
(Project
Control)
Distribution:
Client Advice
Date:
Date: 27-12-2012
-PMC - 00 - 002
Revision. 4
Checked by : CS
Nagaraja
issued
Appendix D: Request for Information (RFI)
Page 28 of 28

Via - Rev 4

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Via - Rev 4

Hochgeladen von

Copyright:

Verfügbare Formate

Doc. No.

HM - LE - PRWIDE M0101 - DOC - MA -PMC -

Project: Hyderabad Metro Rail

Organisation and Roles & Responsibilities...........................................................8

Allocation of Interface requirements...................................................................11

Change of interfacing requirement.....................................................................15

RAIL (HYDERABAD) LIMITED

HYDERABAD METRO RAIL PROJECT

LIMITED, Construction Viaduct

HM - LE - PRWIDE M0401 - DOC - MA -PMC - 00 - 002

Doc. No. HM - LE - PRWIDE M0101 - DOC - MA

Project: Hyderabad Metro Rail

Acronyms & Definitions

Automatic Fair Collection

Combined Services Drawings.

Project: Hyderabad Metro Rail

Doc. No. HM - LE - PRWIDE M0101 - DOC - MA

This plan is wholly based on requirements captured in General Specification for

Project: Hyderabad Metro Rail

Doc. No. HM - LE - PRWIDE M0101 - DOC - MA

Organisation and Roles & Responsibilities

The following organogram shows the roles and responsibilities identified to

Project: Hyderabad Metro Rail

Doc. No. HM - LE - PRWIDE M0101 - DOC - MA

Figure 1 : VIA Interface Organisation

Responsibility and authorities of the identified Interface members are as follows:

2.1.1 Project Manager

2.1.2 Chief Interface Manager

Project: Hyderabad Metro Rail

Doc. No. HM - LE - PRWIDE M0101 - DOC - MA

1) Facilitate consultations with nominated Interface Managers within L&T C on

2.1.3 Interface Manager

Project: Hyderabad Metro Rail

Doc. No. HM - LE - PRWIDE M0101 - DOC - MA

2.1.4 Execution Manager

Execution of works implementing interface actions agreed in the

2.1.5 Design Manager

Preparation of GFC drawings incorporating resolved interface issues

The resource requirements of manpower is the allocation/mobilisation of staff for

The interface requirements management system is to be implemented between

Project: Hyderabad Metro Rail

Doc. No. HM - LE - PRWIDE M0101 - DOC - MA

Allocation of Interface requirements

The interface requirements are generally classified in to Design & Execution

Interface description between contractors

In continuation to the allocation of interface requirementError: Reference source

Project: Hyderabad Metro Rail

Doc. No. HM - LE - PRWIDE M0101 - DOC - MA

Signaling & Train Control (S&TC)

Responsibility Matrix of the Lead and Match

Project: Hyderabad Metro Rail

Doc. No. HM - LE - PRWIDE M0101 - DOC - MA

Role & Responsibility

Doc. No. HM - LE - PRWIDE M0101 - DOC - MA

Project: Hyderabad Metro Rail

Figure 1: Illustrated Flow chart for VIA Interface

Change of interfacing requirement

Project: Hyderabad Metro Rail

Doc. No. HM - LE - PRWIDE M0101 - DOC - MA

requirements it shall be captured in the interface action log. If one of the

Testing activities shall be based on the requirements capture and referred in

Testing and Commissioning on Interfaces

The approach to be adopted by the Contractor for the management of interface