Kafd Systra Phb Te All Lst 4010 a1 Master Vol 2 Part 1 Epco

7/27/2019 Kafd Systra Phb Te All Lst 4010 a1 Master Vol 2 Part 1 Epco

1/240

KING ABDULLAH FINANCIAL DISTRICT

Monorail System - Riyadh

VOLUME 2 TECHNICAL DOCUMENTS PART 1 GENERAL SPECIFICATIONS Sept 2009

Filename: KAFD-SYSTRA-PHB-TE-ALL-LST-4010-A1 Master - Vol 2 Part 1.doc Page 1 / 240

VOLUME 2

PART 1 - GENERAL SPECIFICATIONS

1. PROJECT MANAGEMENT (3605) ....................................................................3

2. PRELIMINARY OPERATION PLAN OF THE MONORAIL SYSTEM (2003) .. 47

3. GENERAL DESIGN CRITERIA (3604) ............................................................ 64

4. SYSTEM TECHNICAL REQUIREMENTS (3602) ............................................90

5. OPERATION AND MAINTENANCE REQUIREMENTS (3609) ..................... 117

6. INTERFACE MANAGEMENT (3603)............................................................. 125

7. TRAINING (3601)........................................................................................... 146

8. VERIFICATION, TESTS AND ACCEPTANCE (3600)................................... 151

9. BUILDINGS REQUIREMENTS (3608)........................................................... 180

10. CONSTRUCTION AND SITE ARRANGEMENT REQUIREMENTS (3606)... 199

11. RIYADH CLIMATIC CONDITIONS (3607) ..................................................... 220


2/240



VOLUME 2 TECHNICAL DOCUMENTS PART 1 GENERAL SPECIFICATIONS Sept 2009


This page left blank


3/240



Revision Date Subject of issue / Revision Author

A0 16/06/2009 First issue D.M.

A1 22/07/2009 Revision according to Hill Intl comments D.M. / O.B.

Revision: A1 Name Date Signature

Prepared by D. Massat 22 July 2009

Checked by L. Fontaine 22 July 2009

Approved by O.Bouhier 22 July 2009

Date: 22 July 2009 Package: DB07

VOLUME 2 - TECHNICAL DOCUMENTS

PART 1 - GENERAL SPECIFICATIONS

Title: PROJECT MANAGEMENT

Document number:

KAFD SYSTRA PHB PE PMG ALL 3605 T A1

Project Transmitter Phase Type Discipline Subject Doc. Number Family Revision

It is the responsibility of the addressee to destroy the previous edition or to indicate Superseded.


4/240



PROJECT MANAGEMENT (3605) 22 July 2009


TABLE OF CONTENTS

1. INTRODUCTION ................................................... ........................................................... ................................. 7

2. GLOSSARY ................................................... ............................................................ .......................................... 8

3. PROJECT MANAGEMENT PLAN.................................................... ........................................................... ... 9

3.1 PROJECT MANAGEMENT PLAN ELEMENTS............................................................ ........................................ 10

3.1.1 Contractor's Organisation ....................................................... ........................................................... . 103.1.2 Key Personnel ...................................................... ........................................................... ..................... 103.1.3 Web Based Management Information System....................................................... ............................... 113.1.4 Performance Measurement ...................................................... ........................................................... . 113.1.5 Schedules ................................................... ........................................................... ............................... 113.1.6 Progress Schedules ........................................................ ........................................................... ........... 133.1.7 Schedule Updating Requirements ...................................................... .................................................. 143.1.8 CDRL Report-Project File ....................................................... ........................................................... . 153.1.9 Design Control....................... ............................................................ .................................................. 163.1.10 Manufacturing and Procurement Control ...................................................................... ..................... 163.1.11 Installation Control.......................... ............................................................ ........................................ 163.1.12 Integrated Verification............................................................. ........................................................... . 163.1.13 Configuration Management ..................................................... ........................................................... . 16

3.1.14 Change Control Procedure...................................................... ........................................................... . 173.1.15 Requirements Management........................ ........................................................... ............................... 173.1.16 Formats, Submittals, Review and Approvals ........................................................ ............................... 18

3.2 CONFIGURATION MANAGEMENT ...................................................... ........................................................... . 193.2.1 Configuration Management Plan............................................. ........................................................... . 193.2.2 Records and Documentation.............................................................. .................................................. 193.2.3 Configuration Control ................................................... ........................................................... ........... 20

3.3 DOCUMENT/AS BUILT DRAWING MANAGEMENT .......................................................... ............................... 203.3.1 Drawing and Document List or Tree ........................................................... ........................................ 203.3.2 Construction Documentation ................................................... ........................................................... . 20

3.4 DESIGN REVIEWS AND AUDITS ......................................................... ........................................................... . 223.4.1 Design Reviews .................................................... ........................................................... ..................... 223.4.2 Final Design Review...................................................... ........................................................... ........... 22

3.5 DOCUMENT FLOW ORGANISATION AND CONTROL......................................................... ............................... 223.5.1 Project Documentation Update ......................................................... .................................................. 233.5.2 Photography............................................... ........................................................... ............................... 23

3.6 INTERFACE MANAGEMENT ..................................................... ........................................................... ........... 233.7 REVIEWS AND REPORTS.......................................................... ........................................................... ........... 23

3.7.1 General ...................................................... ........................................................... ............................... 233.7.2 Initial Activities Report ............................................................ ........................................................... . 243.7.3 Progress Meetings and Reports ......................................................... .................................................. 243.7.4 Contract Deliverable Requirements Report .......................................................... ............................... 26

4. QUALITY MANAGEMENT PROGRAM.................................................... .................................................. 26

4.1 GENERAL.................................................. ............................................................ ........................................ 264.1.1 Scope......... ........................................................... ........................................................... ..................... 27


5/240





4.1.2 Evidence of Compliance ....................................................................................... ............................... 274.1.3 Quality Management Plan ....................................................... ........................................................... . 274.1.4 Verification .......................................................... ........................................................... ..................... 284.1.5 Organisation ........................................................ ........................................................... ..................... 284.1.6 Certification of Personnel........................................................ ........................................................... . 284.1.7 Certification of Equipment......................... ........................................................... ............................... 28

4.2 PROCUREMENT QUALITY ASSURANCE ....................................................... .................................................. 284.2.1 Supplier Selection .......................................................... ........................................................... ........... 284.2.2 Supplier Control/Inspection... ............................................................ .................................................. 29

4.3 INSPECTION AND TEST.................................................. ........................................................... ..................... 294.3.1 General ...................................................... ........................................................... ............................... 294.3.2 Inspection............ ........................................................... ........................................................... ........... 304.3.3 Testing.................................... ............................................................ .................................................. 304.3.4 Receiving Inspection ...................................................... ........................................................... ........... 304.3.5 In-Process Inspection................................. ........................................................... ............................... 304.3.6 Shipping Inspection.................................... ........................................................... ............................... 31

4.4 STATISTICAL SAMPLING PLANS ........................................................ ........................................................... . 314.5 IDENTIFICATION AND INSPECTION STATUS ........................................................... ........................................ 314.6 HANDLING,STORAGE AND DELIVERY ........................................................ .................................................. 314.7 CORRECTIVE ACTION ................................................... ........................................................... ..................... 314.8 NON-COMPLIANT ITEM ........................................................... ........................................................... ........... 324.9 AUDITS ..................................................... ............................................................ ........................................ 324.10 QUALITY ASSURANCE RECORDS ...................................................... ........................................................... . 324.11 QUALITY REQUIREMENTS ON DOCUMENTATION ........................................................... ............................... 334.12 DEFECTS IN ITEMS OR WORK............................................................ ........................................................... . 33

4.12.1 Shipping Cost....................................................... ........................................................... ..................... 334.12.2 Removal Correction ....................................................... ........................................................... ........... 334.12.3 Inspection............ ........................................................... ........................................................... ........... 33

4.13 SUPPLIER CERTIFICATION ....................................................... ........................................................... ........... 334.14 CONSTRUCTION,MANUFACTURING AND INSTALLATION CONTROL................................................... ........... 33

5. SYSTEM ASSURANCE REQUIREMENTS.......................................................... ........................................ 35

5.1 SYSTEM ASSURANCE .................................................... ........................................................... ..................... 355.2 RELIABILITY,AVAILABILITY &MAINTAINABILITY REQUIREMENTS.................................................. ........... 355.3 MAINTAINABILITY ANALYSIS........................................................... ........................................................... . 365.4 RECOVERY ANALYSIS................................................... ........................................................... ..................... 365.5 STANDARDS........................................................ ........................................................... ............................... 365.6 SYSTEM SAFETY MANAGEMENT....................................................... ........................................................... . 37

5.6.1 General ...................................................... ........................................................... ............................... 375.6.2 Contractor Responsibilities............................................ ........................................................... ........... 375.6.3 General Requirements ................................................... ........................................................... ........... 38

5.7 OPERATIONS AND MAINTENANCE PERSONNEL SAFETY........................................................... ..................... 385.8 SAFETY TRAINING ........................................................ ........................................................... ..................... 39

6. SECURITY PROGRAM................................................... ........................................................... ..................... 40

6.1 SECURITY COMMITTEE ........................................................... ........................................................... ........... 406.2 SECURITY COMMITTEE ORGANISATION...................................................... .................................................. 406.3 SECURITY PROGRAM POLICIES ......................................................... ........................................................... . 406.4 ENGINEERS RESPONSIBILITIES......................................................... ........................................................... . 416.5 CONTRACTOR RESPONSIBILITIES ...................................................... ........................................................... . 416.6 SECURITY TASKS .......................................................... ........................................................... ..................... 41

6.6.1 Preliminary Security Assessment ....................................................... .................................................. 416.6.2 Detailed Security Assessment................................................... ........................................................... . 42

6.7 PROGRAM AUDITS ........................................................ ........................................................... ..................... 43


6/240





6.8 PROGRESS AND STATUS REPORTS..................................................... ........................................................... . 436.9 ACCESS CONTROL PLAN......................................................... ........................................................... ........... 436.10 ENGINEER SECURITY VERIFICATION........................................................... .................................................. 44

7. SYSTEM OPERATION AND MAINTENANCE MANAGEMENT PROGRAM......................................45

7.1 GENERAL.................................................. ............................................................ ........................................ 457.2 FORM AND UPDATES OF DOCUMENTATION .......................................................... ........................................ 457.3 FOLLOW UP......................................................... ........................................................... ............................... 457.4 PUBLIC INFORMATION .................................................. ........................................................... ..................... 46


7/240





1. IntroductionThe Contractor shall establish and be fully responsible for the Project Management Organisation to beimplemented to accomplish the KAFD Monorail System. All elements of the Project ManagementOrganisation described in this Section are subject to review and approval by the Employer or by theEngineer. The Contractor shall use a system for planning monitoring and controlling that encompasses allthe Work to be performed.

The Contractor shall establish procedures to ensure that all plans produced as a result of therequirements of this Section remain updated throughout the Contract performance period.

In this document, when the Operator or the O&M Contractor appears, it must be understood as theoperating part of the EPCO Contractor.


8/240





2. Glossary

AC Alternative current

CDRL Contract Deliverable Requirements List

DCP Design Control Point

DMIS Database Management Information System

EMC Electro Magnetic Compatibility

EMI Electro Magnetic Interference

EN European Standard

HVAC Heating, Ventilation ,Air ConditioningIEC International Electrotechnical Convention

ISDP Integrated System Demonstration Program

LSFH Low Smoke, Fume and Halogen

NFPA National Fire Protection Association

MMS Maintenance Management System

MTTR Mean Time To Repair

NTP Notification to proceed

OCC Operation Control Centre

PMP Project Management Plan

PVC Polyvinyl Chloride

RAM Reliability Availability Maintainability

RAMS Reliability Availability Maintainability Safety

SIL Safety Integrity Level

SAMP System Assurance Monitoring Plan

SAP System Assurance Plan

TOC Take Over Certificate

UIC International Union of Railways

VTA Verification, Tests and Acceptance

WBS Work Breakdown Structure


9/240





3. Project Management Plan

The nature of the Work dictates that formal plans must be developed to address the Contractorsapproach to implement the Works. In order to minimise the total number of documents to be originated bythe Contractor, the Contractor may, due to Organisation structure or for other reasons, choose to groupthe requirements differently and submit a different number of documents.

Such variations shall be clearly identified by the Contractor and submitted to the Engineers approval.

The Contractor management documentation shall be structured so that passive efforts that can beexpected to require only infrequent revision and active efforts that can be expected to require frequentrevision will be included in different documents. Specifically, efforts such as schedules and the ContractDeliverable Requirements List should be revised and submitted frequently for consideration. Regardlessof management documentation separation selection, all documents shall be maintained current at all

times.

The Contractor shall submit a Project Management Plan to the Employer and the Engineer for review andapproval.

This Plan shall be consistent with the Organisation and Management information presented by theContractor in his proposal. It must clearly demonstrate the integration of the individual companies of theContractor into one management structure. Any alteration to this proposal shall require the Employer'sapproval. Within 28 calendar days after the issuance of Notice To Proceed (NTP), the Contractor shallrevise and submit to the Employer his updated and completed Project Management Plan (PMP).

The Contractors PMP shall include but not be limited to:

1) A listing of key personnel, together with their qualifications, responsibilities and involvement inthe Project.

2) Dates at which the key staff shall be on duty for the project, ensuring that there is always asufficient period for project information acquisition by the personnel coming during the project.

3) A complete Work Breakdown Structure (WBS), indicating the source/responsibility for completingeach aspect of the Work. As a basis for organizing any work under the Contract, the WBS shallbe consistent with the Organisation of the Progress Schedule, Pricing Forms, and Schedule ofUnit Prices in the Catalogue of Prices.

4) A description of the cost estimating services for the duration of the Project.The Contractor shall maintain a current working estimate including all costs of the project. TheCurrent Working Estimate shall utilize the Contractor's Pricing Structure and Catalog of Prices.Historical records shall be kept current and include all changes. When requested, the Contractorshall prepare estimates to assist the Employer and its representative in evaluating changes orimpacts to the Project.Cost Trend Analyses shall be performed by the Contractor periodically and the projectionsincluded in the monthly progress reports. The Contractor shall provide cost estimating servicesas required under the direction of the Employer and Engineer, to assist in cost analysis, life cyclecost studies, and/or cost impacts resulting from construction of the System. The Contractor shallalso provide a cash flow.

5) The Original Baseline Schedule, due within 28 calendar days after the issuance of NTP, shallamong others, identify one or more critical paths through the network. The level of scheduledetail shall include activities for each Work Category described in Sections 4.2.1.5 to 4.2.1.7 ofthis document.

6) The Progress Schedule showing cost loaded activities by application of the Contractor's prices toeach individual WBS Work Category in combination with its applicable Specific Stations, LineSegments and Buildings. As the Work progresses, the resulting budgeted value for work


10/240





accomplished shall be used to check the progress payment requests in accordance with thepayment milestones.

7) A Submittal Schedule for all deliverables and design review data.8) An Organisation Chart showing the Contractor's Organisation (including main subcontractors

organisations), accompanied with a report describing how each entity will be implied in eachProject Phase, defining their responsibilities in general and in the Project, and detailing how eachentity will coordinate its work with others.

9) A numbering system for all documents and correspondences, and a distribution listing for allcorrespondence and transmittals under this Contract shall be submitted to the Employer andEngineers acceptance within 7 days after the issue of NTP.

The Project Management Plan shall also address the following elements:

- Information Management System,- Contract Performance Chart,

- Progress Schedules,- Progress Reviews and Reports,- Contract Deliverable Requirements Report, as defined in clause 3.7.4,- Progress of procurement and manufacture,- Installation Control,- Change Control Procedure,- Configuration Management Plan,- Design Review Requirements,- Interface Management,- Security Management Program,- Quality Assurance Program,- Safety Program,- Verification, Test and Acceptance Program,

- Operations and Maintenance Plans.

Detailed information on these elements is given in further Sections of the present General Specification.

3.1 Project Management Plan Elements

3.1.1 Contractor's Organisation

The Contractor shall prepare and update regularly the Organisation Chart reflecting his ownOrganisational structure in relation with authorities involved in the performance of the Contract.

The Contractor shall nominate his Project Director in charge of the accomplishment of the System.

Formal communications shall be addressed to the Contractor's Project Director who shall have fullauthority to represent the Contractor and to act on his behalf. The Contractor's Organisation Chart willshow the positions and names of key personnel in Organisational units and their reporting relationships tothe Contractor's Project Director.

3.1.2 Key Personnel

The Contractor shall identify all key personnel and positions of the Organisation required to accomplishthe System. These personnel shall be identified by title and position in the Contractor's Organisation asreflected on the Organisation Chart. The assigned titles shall be reflective of responsibilities and duties.


11/240





The Contractor shall include a resume for each identified Key Person. These personnel shall beresponded to the Contractor's Project Director for the System.

All key personnel and positions shall be subject to interview and to the Employer and Engineer approval.

3.1.3 Web Based Management Information System

The Contractor shall implement a Web based Management Information System so as to identify, control,and store data of the System. Such system will allow ease of retrieval and will ensure delivery to relevantparties, project staff, consultant, contractors, suppliers and others. It shall contain all data developed forthe design and construction, correspondences between parties, management and financial data,schedules, reports, public complaints and all relevant issues.

A formal numbering system for all the documents and correspondences for all the stages of theimplementation of the project (design, construction, testing and commissioning, as-built etc) shall be

provided by the Contractor for the Employer and Engineer approval within 14 days after the issuance ofthe NTP.

The Contractor shall provide the Employer and the Engineer full access to the proposed Web basedManagement Information System and without any limitation in term of licences or/and users.

This Management Information System shall be used to produce the Monthly Progress Reports and otherrelevant documents.

3.1.4 Performance Measurement

On a monthly basis, the Contractor shall update and submit with the Monthly Progress Report, a ContractPerformance Chart reflecting the progress of major Program milestones versus Contract expenditures.

The Chart milestone activities shall be directly comparable to the major milestones reflected on theProgress Schedules. The Chart format shall visually reflect progressive status between milestones anddisplay planned and actual percent earned value curves overlaying scheduled activities.

3.1.5 Schedules

The Contractor shall provide, maintain and update Progress Schedules, reflecting the full scope of Work,including all scope changes, in the form of activities, access dates, milestones and relationships betweenactivities/milestones, and clearly identifying the critical path(s) necessary to meet schedule requirements.

He shall in this respect provide bar-diagram schedules and location-timeline programmes.

The Schedules shall show the sequence and interdependence of submittals, material procurement,equipment manufacture and construction activities, etc., and shall include, at a minimum the start datesand completion dates of all items of the System, their major components and milestone completion dates,as well as all relationships to the work of other Contractors affecting the System to be performed underthis Contract.

The critical paths shall include all efforts under the Contractor responsibility as well as the activities ofothers which potentially constrain the Contractor's ability to meet schedule requirements. If the Float orSlack value for the critical path ever becomes negative, a Negative Slack Recovery Plan" for notexceeding the relevant late dates must be submitted within seven (7) calendar days to the Engineer.Slack (or Float) shall be measured not only against the Completion Dates", but also against anyintermediate milestone dates as identified by the Engineer.


12/240





The Progress Schedules shall be used to verify the Contractor's progress payment requests.Schedule Levels:

LEVEL 1:These are summary schedules with varying levels of detail and content adapted to the intended use andthe recipient of the schedule. A typical application would be the display of an overview of the entire projectfor a Management review.

A Level 1 summary schedule suitable or inclusion in a Project Management Plan should identify:

1) the major milestones and main items of the Contract Deliverable Requirements Lists(CDRL) (refer to section 3.1.8),

2) the major fixed facilities, specifically the major Line Sections design and constructiondurations.

To verify progress payment requests, the Contractor shall prepare a cost loaded summary schedule thatcontains activities and milestones representing the Payment Milestones.

LEVEL 2:Detailed schedule is the minimum acceptable level of detailed schedule to be included in the TenderersProposal. These schedules should directly relate to the cost information provided in the Proposal andshould be cost loaded in order to generate the preliminary cash flows for the project.

Level 2 Progress Schedules shall include activities for each individual Work Category to Level 2 WBSlevel and associated with work location and milestones.

LEVEL 3:The schedule shall contain details defining measurable and deliverable activities and milestones for work

programming, for progress reporting and controlling and for determining the budget value for workaccomplished. Cash flow reports and graphics shall be developed using this level of detail. Activities andmilestones making up the construction Work shall be scheduled at Level 3 of the WBS, and whennecessary, at Level 4 detail of the WBS. The first version of a level 3 Progress Schedule, developed andprovided as part of the Management Plan, is referred to as the "Original Baseline Schedule'.

The objective of the WBS associated with the Level 3 Schedule is to have a cost loaded ProgressSchedule by applying the Contractor's Prices for each individual WBS Work Category up to Level 3 of theWBS in combination with its applicable Specific Stations, Line Segments and location

The Level 3 schedule shall be updated and submitted, on at least a monthly basis, each and every monthof the project duration. Monthly submittals shall coincide with the Contractor's submittal of the MonthlyProgress Reports. The update shall consist of changes in scope, logic changes and progress input in

terms of actual start dates, actual finish dates, remaining duration, etc., and shall identify the exact causeof changes to the critical path and the resolution of negative slack situations. Changes in scope and logic,including any modifications to relationship lag and lead times, shall be marked-up on the latest prior logicdiagram(s), so that these types of changes can be easily seen. In no event shall changes in logic be madewithout prior approval from the Engineer.

LEVEL 4Level 4 schedules are detailed construction schedules which shall be developed, as necessary, in order todefine the day-to-day activities of each construction effort, including the construction. Typical constructionefforts shall include each Guide way line segment, each Station, each Building and, as appropriate, sub-segments of the Guideway. As the various testing phases approach, such as integration testing anddemonstration testing, they shall be scheduled at Level 4 detail.


13/240





Level 4 details may be a further detailing of activities within the Level 3 Progress Schedule itself, or it mayreside in a separate stand-alone schedule, as long as the calculated schedule dates, estimates tocompletion, etc. are accurately reflected in the Level 3 Progress Schedule. Activity definition shall show allrequired interfaces (or "hand-offs" of information) between disciplines, crafts, contractors or other thirdparties, highlighting any problem areas. Specific problem areas that need to be resolved shall be isolated.Activities that define the action taking place shall include, but not be limited to, any of the actions identifiedfor any of the WBS up to level 5 (or more if defined by the Contractor).

This level of schedule detail shall be developed 3 months or more prior to performing the actual work.Situations requiring earlier activity definition to Level 4 detail might include manufacturing work so that thecritical aspects of the project can be concentrated upon in time to take any corrective action.

It is anticipated that Level 4 detail will be requested for submittal on an exception basis, but this isdependent upon the schedule progress of the project. In any event, this level of detail shall be maintainedand updated by the Contractor.

3.1.6 Progress Schedules

The Contractor shall prepare, maintain and update detailed Progress Schedules for the approval of theEmployer and the Engineer, as described in this Section.

The schedules shall be prepared in such a manner as to permit the orderly planning Organisation, andexecution of the Work and shall be sufficiently detailed and cost loaded to accurately depict all the Workrequired by the Contract and to substantiate the budgeted value of the System completed in accordancewith the price of each Work Category by Specific Location.

The methods for distributing the costs assigned to the activities over time shall be approved by theEngineer. The budgeted value for the completed System will be compared to the Contractor's Payment

Applications in order to verify the Contractor's estimate of progress payments due. Progress Scheduleupdates shall include the depiction and reporting of the actual performance and progress of the Work.

Electronic files and hard copies, as required, containing the project files and layouts in `Backup"compressed format, shall be submitted with the proposal and with each update of the Progress Schedule.Progress Schedules shall graphically represent the logical sequence of the activities necessary tocomplete the Contract in accordance with the requirements of the Contract.

Progress Schedules shall include activities involving the procurement, manufacture and delivery ofconstruction materials and equipment, whether such materials and equipment are provided by theEngineer, the Contractor or by others.

The information provided in Progress Schedules shall also include, but not be limited to, the

interdependencies between the Contractor activities and all other activities required for the successfulcompletion of the Contract.

Moreover, each Progress Schedule shall include activities for, among other things: obtaining permitswhen required; preparing drawings, designs, and other submittals; and obtaining approvals of theEngineer. The Contractor shall allow the durations shown in the "Review Period" column of the CDRLSchedule, for the Engineer review of submittals where approvals and/or acceptances are required.

Activities shall be sufficiently detailed to assure adequate planning execution and progress evaluation ofthe Work within the significant dates provided for in the Contract.

The Original Baseline Schedule shall be included in the Project Management Plan and shall be referred toas 'Revision 0". Subsequent revisions to the Progress Schedule shall be via the schedule updating


14/240





procedure, and it shall be maintained current on at least a monthly basis. Each time a different currentProgress Schedule is developed, the revision number shall be increased by one (1), and the old scheduleshall be archived, so as to permit an audit trail. The Original Baseline Schedule, and any subsequentlyapproved Baseline Schedules, shall always be available on file for comparison purposes.

The Progress Schedules shall comprise measurable and deliverable activities and milestones for planningthe Work, for reporting and controlling progress and to serve as a basis for determining the budgetedvalue for work accomplished for verifying the Contractor's progress payment requests. These activitiesand milestones shall include all Specific Location/individual Work Category elements of the WorkBreakdown Structure and all other costs not included in the WBS, and they shall be cost loaded so thatthe Contractor's progress payment requests can be verified. In this regard, the schedule activities shouldbe coded so that the detailed costs can be automatically rolled-up in the relevant software to the paymentmilestones.

Comparisons of the current Progress Schedule to the latest approved Baseline Schedule shall be made

each month so that any schedule slippage can be readily observed and tracked .The Contractor shall berequired to prepare a monthly Analysis Report explaining how it intends to make up any slippage inschedule, especially slippage that affects the critical path.

The Original Baseline Schedule shall always be available as it originally existed. It shall be updated forapproved scope changes only. The updates shall occur each month, but only after the precise nature ofthe change has been approved by the Engineer. In the event of extreme changes or unforeseeablecircumstances, a formal rebaselining of the schedule may be permitted subject to the agreement with theEmployer and Engineer and only after rebaselining has been approved by the Engineer.The timing of the initial submittals shall be in accordance with the submittals for the Project ManagementPlans. Thereafter, all remaining Progress Schedules will build upon and be monthly updates of theOriginal Baseline Schedule

3.1.7 Schedule Updating Requirements

Once each month, or as frequently as deemed necessary by the Engineer, the Contractor shall participatewith the Engineer in a progress update of the current Progress Schedule. At least five (5) working days inadvance of such meeting, the Contractor shall provide for review by the Engineer:

a) A current schedule at Level 3 detail suitable for updating purposes, showing at least one monthof history and three months of future work. The Bar Chart shall include, at a minimum, thefollowing activity data fields: Activity ID, Original Duration, Remaining Duration, Early/ActualDates, Late Dates. The Activity Title shall be displayed above each bar.

b) Updated revision of the Time/location Schedule if required.c) A Logic Diagram encompassing the activities/milestones appearing in the above Bar Chart, plus

any other activities involved in planned or actual logic revisions. Any revisions shall be supported

by a mark-up by hand of the previous Progress Schedule for the affected scope of workd) A narrative report which shall include, at a minimum, the following. (1) progress during the

period, (2) progress scheduled during the next period, as currently forecasted and as planned inthe Baseline schedule; (3) anticipated problems and proposed solutions, particularly thoseinvolving lateness or slippage in schedule; (4) discussion of each one of the logic revisionsidentified , covering the impact on the schedule; (5) analysis and discussion of alternativemethods to mitigate accumulated delays.

e) Once the progress and logic changes have been reviewed and agreed to by the Engineer at themonthly progress meeting the Contractor shall computerize and formalize the Progress Scheduleand update report and submit these to the Engineer for final approval no later than seven (7)calendar days following the monthly progress meeting. Any revisions to the logic shall beaccompanied by a written explanation of these revisions in detail. At the discretion of the


15/240





Engineer, the Contractor may also be requested to prepare and submit marked-up drawingssuch as cross-sections, profiles and plan views of the area under analysis.

Part of the monthly report will be in the form of a schedule report and shall include the following:

a) Bar charts at different levels of detail and covering varying periods of time, such as:i. Level 1 summary schedule for the entire project duration.ii. Level 3 detail schedule showing two months of history and three months of future

Workiii. Level 3 Comparison Bar Chart so that lateness and slippage may be viewed on the

same output display for two months of history and three months of future Work.b) Network Logic Diagrams for the entire project or other selected portions of the project may be

specified for inclusion by the Engineer.c) Activity Reports, together with appropriate Analysis Reports, such as: (1) recovery plans for

negative slack in the critical path and (2) causes and corrective actions for schedule slippagefrom the latest approved Baseline Schedule, based upon the "Baseline (Target) / CurrentSchedule Comparison Report".

d) Cash Flows in graphical format.e) CDs containing the Project Planner and the Time/location schedule project files and layouts in

`Backup" compressed format.

The Engineer may require the Contractor to provide a revised update which shall include any otherinformation needed in evaluating the Contractor's progress and future needs, including, but not limited to,the following: manpower loading charts, equipment schedules, multiple shifts or overtime requirements tomaintain approved schedules, Estimates to Complete, Estimates at Completion.

In the event that the Engineer requests the Contractor to revise the updated Progress Schedule

submitted, and/or to submit such additional information, the Contractor shall make the requested revisionsand/or submit the updated Progress Schedule to the Engineer for approval along with the additionalinformation requested within seven (7) calendar days of the request by the Engineer.

The Contractor acknowledges and agrees that if an Activity with Free Float is delayed due to change orvariation on the part of the Engineer for any reason, it will not thereby become entitled to an extension oftime.

3.1.8 CDRL Report-Project File

The Contract Deliverable Requirements List (CDRL) identifies individual deliverable requirements. TheContractor shall expand the requirements contained in the CDRL, as necessary, to ensure that integrationof the deliverables is accomplished and that all interdependence is recognized. The Tenderer will submit

an updated list with his Tender. The Project Management Plans shall contain the details of how theContractor will accomplish this integration, including sample forms to be used. The Contractor shall issueand maintain CDRL status reports separately from the Management Plan.

The Contractor shall submit a revised version of CDRL to the Engineer for review and comment 28 daysafter the issuance of the NTP.

This revised version of the CDRL items will then replace the preliminary version. The data in the CDRLgenerally do not include financial reports, invoices, and other information incidental to Contractadministration.

On completion of the Contract, the Contractor will provide a final version of the CDRL in a Project File.Presentation will be in CDs or a hard drive format.


16/240





3.1.9 Design Control

The Contractor shall include in the Project Management Plans a Design Control summary of all activitiesrequired to translate technical specification requirements into detailed designs to the point of release tomanufacturing and procurement, including all Contractor inter-organisational involvement. In addition tothe contracted requirements of milestone progress and design reviews, requirements internal to theContractor which support or drive the efforts shall be included. These events shall be reflected on theProgress Schedules, which shall be initially included as supporting information, but updated anddistributed through the Contractor scheduling procedures and maintained current in the ProjectManagement Plan.

3.1.10 Manufacturing and Procurement Control

As a sequel to the Design Control summary, the Contractor shall include in the Project Management Plan

activities of Manufacturing and Procurement Control which translate technical specification requirementsand Contractor detail designs into factory tested and shipped products. All Contractor Organisations andefforts to be accomplished shall be described. This Manufacturing and Procurement Control summaryshall be prepared in accordance with Quality Assurance requirements and shall be supported by ProgressSchedules which time phase the events defined in the summary. The Progress Schedules shall be initiallyincluded as supporting information, but updated and distributed through the Contractor schedulingprocedures and not maintained current in the Management Plan.

3.1.11 Installation Control

The Contractor shall summarily define, in the Project Management Plans, the activities associated withreceiving inspection, site preparation, installation of equipment and materials and acceptance of the

installation by the Engineer. This summary shall reflect all critical activities associated with equipmentdelivery, storage (if required); release of installation drawings, procedures, and processes (whererequired), installation and checkout, pre-installation inspection of facilities where equipment is to beinstalled, and numbers of installations to be worked concurrently. Installation Control activities shall befully coordinated and compatible with Quality Assurance requirements.

The Contractor shall clearly define the process by which all installation interfaces are identified and themethod(s) to be used to obtain the Engineer and other agencies' or jurisdictions' approval of installationsupport or interface requirements.

3.1.12 Integrated Verification

The Contractor shall establish the management process to be used to identify all verification activities to

be performed, assignment of the verification efforts to specific contracts or subcontracts, preparation ofverification documentation, approval of documentation by the Contractor and the Engineer, witnessing oftests, and assessment and approval of verification results. This section shall contain a summary of allContractor management activities associated with Integrated Verification. This is in addition to therequirements detailed in Section Verification, Test and Acceptance of this document.

3.1.13 Configuration Management

The Contractor shall provide a summary of the Configuration Management (CM) efforts to be put intoplace to implement all requirements of Section 3.2 of this document. This information shall includeidentification of Organisation roles involved in the CM activities and the summary procedures to be usedto accomplish effective CM.


17/240





3.1.14 Change Control Procedure

The Contractor shall implement a system identifying the changes and provide procedures and a summary

schedule for accomplishing the reviews and incorporating changes.

Changes in the project are to be considered from accepted or contractual documents, such as:

- final design drawings or specifications,- interface documents,- other projects in the vicinity of the Transit System Works- contractual performance requirements,- laws and standards.

After a need for change is taken to the knowledge of the Contractor, he shall within fifteen calendar daysissue a Project Change Control Form to the Engineer, with indication of :

- the type of modification : type 1 : internal to the project, either because of subsystem specification evolution,

or to correct an item that had not been taken into account,

type 2 : modification of program issued by the employer or consequence of otherprojects,

type 3 : modification of law or standard requirements.- the impact on the detailed schedule and actions to be undertaken to remain within the

general schedule,- The impact on contract requirements, using the procedure and tools described below,- the impact on the programme, including VTA plan modification,- the impact on RAMS and security works,- the technical impact on subsystems, including those in interface, that may also include

request for other project adaptations,

- the list of documents to be updated,- the cost of the modification, only for type 2 and some of type 3 modifications.

The Project Change Control Form shall be submitted to the Engineer, who may ask for alternativesolutions to be studied by the Contractor prior to decision to proceed.

Any modification shall be granted a decision to proceed within one month of the Project Change ControlForm issuance.

3.1.15 Requirements Management

Requirements management is a systematic approach to eliciting, organising, documenting and managingthe changing requirements of the project. It is an integral part of configuration management, especially inthe design phases, when there are no physical objects to configure on the railway. The Contractor shallproduce a requirements management plan with the following objectives:

- to explain to all parties in the project the need for RM,- to define the overall strategy and key objectives of RM,- to define the methodology for implementing a coordinated RM system at Lead Contractor

and subcontractor and supplier level,- to define the methodology for tracing requirements from contract specifications to

subcontract specifications to module specifications to module tests, integration tests andfinal acceptance.


18/240





Requirements to be managed include contract, functional, technical, performance, system assurance(RAMS) and acceptance requirements.

A dedicated RM tool should be used to support RM activities, including

- identification of requirements,- allocation of requirements to subsystems,- identification of interfaces, when allocation of a requirement is to more than one subsystem,- configuration management of physical and software objects including change control- base lining of configurations,- Validation and verification activities.

3.1.16 Formats, Submittals, Review and Approvals

The Progress shall be updated on a monthly basis and submitted with the Monthly Progress Reports. Of

particular importance during the Program will be findings or otherwise that indicate potential scheduleimpacts. Such impacts will be discussed at the weekly Progress Meetings and, based on the directionprovided by the Engineer. Progress Schedule will be revised accordingly and submitted with the MonthlyProgress Reports. No changes to Progress Schedules shall be made without the approval of theEngineer.

Within 28 calendar days after the issuance of NTP, the Contractor shall submit to the Engineer forapproval the Baseline Schedule. The Baseline Schedule shall be version at Level 3 detail.

The Engineer will review the Baseline Schedule and return it to the Contractor within twenty one (21)calendar days. If it is not approved, the Contractor shall revise it in accordance with comments receivedfrom the Engineer, and resubmit it in the formats and quantities specified for the approval of the Engineer,within seven (7) calendar days of the receipt by the Contractor of the comments from the Engineer. Until

such time as the Engineer approves it, the Contractor shall resubmit the Baseline Schedule as required bythe Engineer by the same time and in the same format as required in this paragraph for the initialresubmission.

Updates of Progress Schedules shall be reviewed by the Engineer and returned to the Contractor withinseven (7) calendar days. If such updated Progress Schedules are not approved, the Contractor shallrevise them in accordance with the comments from the Engineer, and resubmit them in the formats andquantities specified for the approval of the Engineer, within seven (7) calendar days of the receipt by theContractor of the comments from the Engineer. Until such time as the Engineer approves any updatedProgress Schedule, the Contractor shall resubmit such updated Progress Schedules as required by theEngineer by the same time and in the same formal as required in this paragraph for the initialresubmission. Any changes to the above time frames shall require the approval of the Engineer.

After approval of any Progress Schedule required by this Section, no change shall be made therein forsubmittal purposes without the approval in writing of the Engineer. No other act or omission on the part ofthe Engineer shall be deemed to constitute such approval. The Contractor shall not be entitled to anycompensation by reason of the failure of the Engineer to give timely approval or comments on anyProgress Schedule submitted hereunder.


19/240





3.2 Configuration Management

3.2.1 Configuration Management Plan

1) Configuration Management is a process of defining and controlling a project configuration from apredetermined point (baseline) through the life of the project, thereby providing a definition of theproject configuration at any point and a record of progression from the initially defined baseline.The Contractor shall be responsible for maintaining strict configuration control of all aspects ofthe design, construction, fabrication and installation of the system for which it is responsible.

2) The Contractors plans to accomplish the configuration management effort shall be described ina draft Configuration Management plan which shall be provided to the Engineer for approvalwithin 60 calendar days after the issuance of the NTP.

3) The Contractor will complete the final version of the Configuration Management Plan within 28

calendar days after its receipt of the comments from the Engineer. The Contractor shall beresponsible for carrying out all aspects of this Plan.4) The Configuration Management Plan shall define all the configuration items and describe how

the Contractor will maintain accurate and current configuration records, the format of which shallbe subject to the approval of the Engineer. The configuration items include, but are not limitedto, requirements, hardware elements, software elements, job/task descriptions, rules andprocedures. The current configuration records shall be available to the Engineer at any timethroughout the period of the Contract.

5) All Configuration Items shall be uniquely identified with both a name and number. Theidentification shall be based, in so far as possible, on the descriptions in the Work BreakdownStructure. The identification shall remain specific to the items during the life of the Project.

6) The Contractor shall use specific tools for the configuration management activities (dedicatedsoftware such as DOORS).

7) The Contractor shall provide the Employer and the Engineer with full access to the tools used forthe configuration management activities such software and database.8) When requested by the Engineer, the Contractor shall provide two (2) computer printouts and

one (1) computer CD containing the Projects current configuration status within 21 calendardays of such requests.

3.2.2 Records and Documentation

The Contractor's records and documentation shall:

1) Define the composition of any part, component, subassembly, or assembly, at any level, in termsof subordinate part numbers; either on the part drawing or on a utilization record tabulation.

2) Show the specification document, specification control drawings, or source control drawing

numbers associated with any Subcontractor of the Contractor, industry standard or items, partnumber, or assemblies.

3) Identify engineering changes and retain the records of superseded configuration requirementsaffecting items which are to be or which have been formally accepted.

4) Employ a system of identifying numbers for specifications, drawings, and associated documentswhich shall ensure that the differing parts, assemblies, and installations are uniquely identifiable.

5) Show that each part number used by the Contractor or Subcontractors identifies a specific itemin a specific configuration. All items, beginning with the lowest level of repair and replacementidentified by the same number shall have the same physical and functional characteristics, shallbe equivalent in performance and durability, and shall be interchangeable without alteration tothemselves or associated items, other than field installation adjustments which are a part of eachinstallation procedure. An item shall not be considered interchangeable if it worst be selected forfit or performance. The Contractor's part number and drawing number shall be the same.


20/240





Changes to a component part number shall require a part number change to the next high levelof assembly.

3.2.3 Configuration Control

1) The Contractor shall be responsible for and maintain strict control of the configuration of (1) theFixed Facilities; (2) the System, (3) the interfaces between the System and all related FixedFacilities; and, (4) the interfaces between the System and non-System facilities and entities.

2) Once the configuration for an element of the System is established (for example, at DesignReviews), the configuration of all such elements shall not be changed by the Contractor withoutthe Engineer's approval as provided in the Configuration Management Plan. Once configurationchanges are approved, formal Changed Configuration Documentation shall be circulated inaccordance with a distribution list, which includes the Engineer, developed for that purpose.

3) The Contractor shall maintain configuration control records of all items and the actual

incorporation points (by date, lot, unit, or other specific identification) of changes. The Engineershall have access to all configuration control records related to the Transit System.

4) The Contractor shall apply controls to manage changes either directed by the Employer andEngineer or from suggested change proposals by the Contractor or its subcontractors. TheContractor shall ensure that any and all proposals for changes are screened at all appropriateContractor management levels to ensure that all of the potential impacts of such changes havebeen thoroughly considered and analyzed.

5) The Change Control Procedure shall apply and be adapted when necessary by the Contractor.

3.3 Document/As Built Drawing Management

3.3.1 Drawing and Document List or TreeThe Contractor shall develop drawing and document list, in subsystem oriented hierarchy format (tree).This document shall be updated quarterly, or at some other frequency as determined by the Engineer,and forwarded for the approval of the Engineer. An estimate or firm count of the quantity and submittalstatus of drawings and documents in each major category shall be included.

3.3.2 Construction Documentation

The Contractor shall maintain records such that the configuration of any item delivered or installed shallbe identifiable in terms of its component part numbers. Configuration record shall be maintained by theContractor for each major equipment assembly.The "as-built" configuration of all infrastructures, hardware and software of the System and all worksimplemented by the Contractor shall be documented in detailed drawings, documents, notes and otherdescriptive material as specified herein.

A. As Work Progress. The Contractor shall keep a complete and accurate field and manufacturingplant record of all changes or deviations from the Specifications, the Contractor's subsystemand procurement specifications, and the Contractor's approved equipment assemblydrawings and similar documents indicating the Work as actually, fabricated and installed. Allsuch changes shall be correctly shown on the drawings affected. At the conclusion of theWork, the as-built records shall be consolidated, organized, catalogued and submitted to theEngineer.

B. Mark-up Procedure. During progress of the Work, the Contractor shall maintain a set of RecordDocumentation, with mark-up of actual work which varies from the work as originally shown.The Contractor shall mark whatever document is most capable of showing the actual


21/240





condition, fully and accurately. Where shop drawings are marked up, the Contractor shallmark cross-references on contract drawings at the corresponding locations. The mark-upshall include important additional information which was either shown schematically oromitted from original drawings. Particular attention shall be given to information on workcancelled, which would be difficult to identify or measure and record at a later date. Alternatenumbers, change order numbers and similar identification shall be noted.

C. On Completion of the Work. In accordance with the CDRL, and as a condition of finalacceptance of and payment for the Work, the Contractor shall deliver to the Engineer all as-built drawings, design specifications, and design documents (the 'as-built deliverables").These as-built deliverables shall not be marked up and shall be complete in every detail soas to correctly reflect as-built conditions. The as-built deliverables shall be segregated intothree groups; (1) non-proprietary, (2) proprietary and (3) commercially available products,components, subsystems, or other items. The non-proprietary as-built documents shalldescribe all aspects of the site installation work and conditions and all designs which are

unique to and provided specifically for the Work, including the application design data for anyproprietary and commercially available items. A commercially available item is defined to bea product, component, subsystem, or other item which is produced for a multiplicity of otherpurposes or can be used with other transit system technologies and is not unique to theContractor technology that is being supplied for the ProjectFor all "commercially available" items (including software), the as-built deliverables shallinclude the purchase specifications, the names and address of the Original EquipmentManufacturers from which the items were purchased (i.e., subcontractors or otherwise), theidentifying information/model numbers for reordering, and the documentation supplied withthe items.The "proprietary" as-built documents shall provide all the necessary design information(except for production tooling and manufacturing components that are not commerciallyavailable and not unique to the Project).

D. Certification of As-Built. The Contractor shall certify that each of the revised as-built drawingsand documents is complete and accurate.

E. Software Documentation. Special attention shall be given to documentation procedures for allcomputer software Programs supplied as part of the Work. In accordance with the CDRL, theContractor shall submit to the Engineer for review and acceptance a SoftwareDocumentation Plan, indicating its proposed methods and procedures for softwaredocumentation. The Software Documentation Plan shall be submitted within 90 calendardays after NTP and be corrected by the Contractor, as appropriate, within 28 calendar daysfollowing receipt of the Engineers comments.For all software unique to the System and not "commercially available", the as-builtdocumentation shall include, at a minimum, all of the information necessary to make

revisions in the software Programs applications for the System for changes and/orexpansions or extension of the System, such as functional, performance and interfacerequirements; configuration control documentation; and Programmer and user manualsincorporating appropriate modification and control procedures , including the name of anysubcontractor if employed for preparation of this software. For all "commercially available"software used in the System, the as-built documentation shall include all of thedocumentation which is available from the supplier of such software. One reproduciblemaster and two copies of all Programmer and user manuals and other similar material shallbe provided to the Engineer with the as-built drawings and documents along with a completeand fully documented listing of all software Programs (one copy on CD, two printed copies).


22/240





3.4 Design Reviews and Audits

The design reviews and audits specified in the following paragraph shall be conducted by the Engineer. In

all cases, review and/or approval by the Engineer shall not relieve the Contractor from complying with allrequirements specified. These reviews shall be conducted to evaluate the progress and technicaladequacy of the design and the compatibility with the performance requirements of the Contract. TheContractor shall be responsible for establishing a schedule for the approval of the Engineer for the reviewof designs under this Contract.

3.4.1 Design Reviews

Design reviews shall be conducted for individual or groups of system elements as defined herein for thepurpose of establishing approved baselines. While review of the Contractor designs will be accomplishedby the Engineer at each of the milestone reviews, neither failure of the Engineer to identify a designdeficiency nor the apparent satisfaction of the Engineer with the Contractor's design shall relieve the

Contractor of responsibility for compliance with the requirements of this Contract.

3.4.2 Final Design Review

The Final Design Review results in an approved final design baseline which subsequently falls under theConfiguration Management Program and establishes the production configuration. The Contractor effort todefine the production configuration concurrent with the Final Design Review is significant and theeffectiveness of the Configuration Management Program will greatly depend on the thoroughness of thiseffort.

The design review data to be provided for this review is all inclusive of all data required to establish theproduction baseline. The data shall include: lists of major parts, assembly drawings, layout drawings,intended control data, logic diagrams, schematics, performance characteristics, design limitations, and

details of new materials and processes.

In addition, the data shall include a list of all drawings, in hierarchy format, to the lowest level of repair andreplacement, the documents referred to therein, and standards and specifications, all by revision or issue.

The list shall include all the documentation necessary to define and identify the baseline configuration.

The list shall be the basic configuration control document and shall be maintained current by theContractor throughout the performance of the Contract.

Once the approved production configuration baseline is established, all changes thereto shall beprocessed through the Configuration Management System.

3.5 Document flow Organisation and Control

The Contractor shall establish an electronic document control system to organize, track and identify alldocuments, developed as part of the Work throughout the duration of the Project. As a minimum, theContractor shall serialize all correspondence and transmittals, and establish a logging system forincoming/outgoing correspondence showing action requirements and action(s) taken. Drawings,specifications, subcontract documents, reports, estimates studies, reviews, and computer files, etc., shallbe tracked by the logging system.

Tracking logs for correspondence and documents shall be provided with all payment requests and at suchother times as requested by the Engineer. The Contractor shall establish a single source for transmitting


23/240





and receiving documents and correspondence. Work from subcontractors shall be consolidated andmanaged by the Contractor.

Logs for correspondence and documents controls shall be provided to the Engineer on computer CDs andin reproducible hard copy for use by the Engineer.

All correspondence to and from the Engineer shall be serialized and separate incoming and outgoingcorrespondence logs maintained:

Within seven (7) calendar days of NTP, Contractor and Engineer shall each designate in writing theirauthorized representatives, who shall receive copies of all or specific correspondence.

All correspondence shall include the project name and contact number along with the specific subject ofthe letter. When replying to a specific letter, it is to be referenced.

3.5.1 Project Documentation Update

The Contractor shall immediately include on the field set of drawings, and at appropriate paragraphs inthe specifications, all changes or corrections made by addenda and Change Orders as they are issued.

Accepted copies of all shop drawings and other submittals are to be kept on the job site at all tunes andshall be made available to the Engineer.

3.5.2 Photography

The Contractor shall provide digital colour photographs with sharp and clearly shown details inaccordance with the following requirements. The Engineer shall support the Contractor in implementingsite photography.

Photographs of the work site or the manufacturing site shall be taken from different locations so as tocover all the line work area, in order to clearly depict preconstruction conditions and the current stage ofmanufacturing and/or construction. The Engineer may prescribe specific locations for photographs herequires, and may require elevated photographs to be taken, either from pole or from aircraft.Photographs shall be taken monthly over the duration of the construction. Photographs shall be numberedand dated in a sequence, and located on a key map, indicating an arrow to show the camera's line of sightQuarterly video recording are to be provided showing progress of the Project at judicious locations whichshall be identified by the Employer and the Engineer.

3.6 Interface Management

Please refer to the Interface Management, General Specifications. (ref.: KAFD-SYSTRA-PHB-PE-INT-ALL-3603-T)

3.7 Reviews and Reports

3.7.1 General

The reviews and reports addressed herein reflect only that data associated with the ContractorManagement System, and do not include reports resulting from activities such as tests, inspections, andother requirements which are addressed elsewhere.


24/240





The Contractor shall provide technical and managerial support for reviews required by this Contract.

3.7.2 Initial Activities Report

The Initial Activities Report, submitted by the Contractor within 10 calendar days after the issuance ofNTP, shall identify critical activities to be initiated within the first 60 calendar days of the Contract. TheInitial Activities Report shall, at a minimum recommend the timing and content of the Contractor/Engineerinitial Organisational meetings, identify data required by the Contractor and not provided in the Contractdocuments, and identify the processes for defining the interfaces between Contractor provided equipmentand Employers provided facilities, equipment, and other third parties.

The report shall include major Contractor activities which will occur prior to submittal of plans in alldiscipline areas.

The Contractor shall issue supplements to this report as the need for additional data is recognized within

the 60-day period.

3.7.3 Progress Meetings and Reports

3.7.3.1 Progress Review Meetings

The Contractor shall attend Progress Review Meetings every week, in order to allow the Engineer andEmployer to assess the Project's status.

During the manufacturing and fabrication phase of the Project, Progress Review Meetings may, at thediscretion of the Engineer, be held at least once per week at the various Contractor facilities involved, andshall include tours of the facilities and Work-in-progress.

As described below, a Monthly Progress Report will be required from the Contractor in advance of everyother two weeks Progress Review Meeting.

The Contractor shall establish the review agenda for all Progress Review meetings which shall addressthe following topics, as applicable :

A. Schedule status,B. Events Planned vs. Events Accomplished,C. Recovery Program for Events not Accomplished,D. Technical/Design Problems Experienced,E. Technical/Design Problems Anticipated,F. Fabrication/Procurement Problems Experienced,

G. Fabrication/Procurement Problems Anticipated,H. Field Construction Problems Experienced ,I. Field Construction Problems Anticipated,J. Installation Problems Experienced,K. Installation Problems Anticipated,L. Field Test Problems Experienced,M. Field Test Problems Anticipated,N. Activities Planned for Next 2 weeks,O. List of evolutions accepted and pending,P. Other issues.


25/240





The proposed agenda for each Progress Review meeting shall be prepared by the Contractor and issuedto the Engineer two days in advance of such meetings and any required agenda changes shall bereturned to the Contractor by the Engineer in due time to allow preparation for the changes.

The Contractor shall assure availability of Contractor personnel to address or support issue discussionswhich have been scheduled. The following disciplines from the Contractor's Organisation shall berepresented at the Progress Meetings, as applicable, per the approved agenda:

A. Project Management: project management, Program control, contract administration,construction management, construction safety, community relations and systems facilitiesdesign;

B. Systems: Transit Vehicles, traction power and communications, signalling, Platform StationDoors, permanent way, system assurance (safety, dependability, security, etc.), operations, etc.

C. Facilities: civil (e.g., field installation), architectural (e.g., Central Control Room layout, lighting,interfaces with others, etc.).

3.7.3.2 Monthly Progress Reports

The Contractor shall prepare and submit to the Engineer five copies of a Monthly Progress Report at leastfive days before the applicable Progress Meeting. The initial format and detail level required for theMonthly Progress Report shall be established jointly by the Engineer and the Contractor within 28 daysafter NTP based on a proposed format prepared by the Contractor. Thereafter, the format and level ofdetail will change as the Work progresses. Topics to be covered in the Monthly Progress Report shallinclude, but not be limited, to:

- Executive Summary,

- Schedule and Resource Status,- Status of Payments, Retention and Withholding,- A Forecast of the amounts of individual Progress Payment Applications for Payment over the

next six months,- Status of Action Items,- CDRL's status,- Drawing Schedule and Transmittal Status,- Subcontract status,- Task Activities Planned for Next Month,- Monthly Task Activity and Accomplishments,- Identification of any Quality Assurance Problems,- Construction and Manufacturing Critical Design Issues,- A list of major equipment and material received in plants or at the Work Site,

- Status of Inspections, Testing and Acceptance,- Manpower and Task completion Variance Analysis, Achieved vs. Planned,- Planned or Proposed Schedule or Budget Revision or other Remedial Actions,- Identification and Analysis of any Scheduling Coordination or Other Problem Areas,- Copies of Logs for Incoming and Outgoing Correspondence and Documents for the Report

Period,- Progress Photos,- Updated submittal schedule on a time-scaled bar chart showing scheduled and actual

progress to date which is derived from the computerized Network Analysis.

When requested by the Engineer at least two weeks in advance, the Monthly Progress Report shall alsocontain appendices dealing with the following topics:


26/240





1) Equipment Deliveries Schedule Status. The Contractor shall provide a schedule status forequipment delivered to the factory and Work Site for all installed equipment. The report shall bebased on the Network Analysis and show the major steps of procurement,fabrication/manufacturing, shipping and delivery. Planned dates shall be compared to actual andforecast each month

2) Field Construction Status. The progress and status of each field construction project or majoractivity shall be reported, based upon the Network Analysis. The major steps of field constructionshall be discussed along with the planned and actual dates of progress and completion forecaststrade.

3.7.4 Contract Deliverable Requirements Report

In order to ensure that the deliverables are thoroughly integrated and that any cross-dependency betweenone submittal and another is recognized, the Contractor shall develop a form and record thereon, for eachCDRL requirement, the following:

A. Title,B. Identifying Number,C. Contract Specification reference,D. Description of Data to be Submitted,E. Approval Requirements (Contractor and the Engineer),F. Frequency of Submittal,G. Identification of other Data Submittals which constrain this Submittal or which would be affected

by a change to this submittal.

These forms shall provide the basis of a Contract Deliverable Requirements Report to be provided by theContractor on a monthly basis along with any Contractor information which will assist in evaluating thesubmittals or describing the Contractor internal procedures for accomplishing this task. This report shall

be maintained current throughout the term of Work.

4. Quality Management Program

4.1 General

This Section specifies the essential elements of the Quality Management Program which shall beimplemented to ensure that:

- design is undertaken under a rigorous method with controlled entry data, controlledinterfaces, and the quality of deliverables is compliant with the requirements,

- works are done under a perfectly set organization, with relevant design documents availableand every work external requirement addressed,

- quality products are provided in a cost-efficient and timely manner.- quality improvement is an objective all along the project, leading to scheduled quality record

reviews.

The concept of Quality Management is based on the principle that quality assurance is a basicresponsibility of each segment of the Contractor's Organisation and that records have to be used topermanently adapt the Quality Management Plan for immediate improvement. Quality of Contactorsproduction shall be evidenced through:

A. Quality synthetic indicators that are presented to the Engineer on a regular basis, leading toquality improvement actions being defined,


27/240





B. Producible designs that can be inspected,C. Firm procurement and job performance specifications,D. Firm procedures for transmission of requirements to Subcontractors and ensuring their

compliance therewith,E. Inspection and testing Programs for manufacturing and installation activities to ensure repetitive

product conformity to design requirements,F. Total Program surveillance and verification of physical conformance and configuration

accountability.

4.1.1 Scope

The requirements of this Section shall apply to all activities related to the quality of items, includingdesign, purchasing, inspection, handling assembly, fabrication, testing storing shipping installation,document production, warranty repair/rework and maintenance.

4.1.2 Evidence of Compliance

The Quality Management Program shall establish and maintain objective, verifiable evidence ofcompliance with all Contract requirements and the Contractor design control systems and procedures.

1) The Contractor may use certificates of compliance for certain materials or products in lieu of thespecified sampling and testing procedures. The batch or lot number of the material or productrepresented shall be included on the certificate to provide traceability Certificates shall be signedby an authorized representative of the manufacturer or producer, stating that the material orproduct complies in all respects with the Contract requirements.

2) Certificates of compliance shall be accompanied by a certified copy of test results, or astatement that such test results are on file with the manufacturer or producer and will beprovided to the Engineer on request. The specified criteria for the material or product

represented, the name and address of the Organisation performing the tests, the date of thetests, and the quantity

Kafd Systra Phb Te All Lst 4010 a1 Master Vol 2 Part 1 Epco

Documents

Transcript of Kafd Systra Phb Te All Lst 4010 a1 Master Vol 2 Part 1 Epco