Microsoft Word - Volume 2_Information_Requirements ... Web viewFIDIC. Fédération ... then the space should be expanded (if the information is captured electronically within the SANRAL

Reg: No. 1998/009584/06

THE SOUTH AFRICAN NATIONALROADS AGENCY LIMITED

INVITATION TO PRE-QUALIFY FOR THE PROCUREMENT OF A NATIONAL INTELLIGENT TRANSPORT SYSTEM AND INTEGRATED SUPPORTING SYSTEMS SOFTWARE AND THE DEPLOYMENT THEREOF IN GAUTENG, KWAZULU-NATAL AND THE WESTERN CAPE

MARCH 2010 VOLUME 2 OF 3: INFORMATION, REQUIREMENTS AND APPLICATION FORMS FOR THE DBOM COMPONENT

THE REGIONAL MANAGER NORTHERN REGIONSOUTH AFRICAN NATIONAL ROADS AGENCY LIMITED38 IDA STREETMENLO PARKPRETORIASOUTH AFRICA

NAME OF APPLICANT: ..............................................................

PRE-QUALIFICATION NOTICE PQD: VOLUME 2

PRE-QUALIFICATION NOTICE

Refer to Volume 1 of the Pre-qualification Documents for the Pre-qualification Notice.

1

TABLE OF CONTENTS PQD: VOLUME 2

TABLE OF CONTENTS

SECTION I: INSTRUCTIONS TO APPLICANTS 6

1. GENERAL (REFER TO VOLUME 1) 6

2. DEFINITIONS AND INTERPRETATION 6

3. ABBREVIATIONS 12

SECTION II: SCOPE OF SUPPLY 15

4. GENERAL DESCRIPTION OF THE PROJECT WORKS 15

5. WORKS NOT INCLUDED IN THE MAIN CONTRACTOR’S SCOPE 16

6. KEY ASPECTS OF THE PROJECT WORKS INCLUDED WITHIN THE MAIN CONTRACTOR’S RESPONSIBILITIES 16

6.1 DESIGN AND BUILD ITS ELEMENTS 17

6.2 TMC OPERATIONS 17

6.3 INCIDENT MANAGEMENT SYSTEMS OPERATIONS 18

6.4 OPERATE A NATIONAL ITS 19

6.5 PROVIDING AND INTEGRATING SYSTEMS SOFTWARE FOR ATMS 19

6.6 MAINTENANCE 20

SECTION III: PRE-QUALIFICATION DATA SHEET (PDS) 21

SECTION IV: QUALIFICATION CRITERIA, REQUIREMENTS 23

7. MINIMUM CRITERIA 23

8. ASSESSMENT CRITERIA 24

9. ADJUDICATION USING A POINT SYSTEM 24

10. INSTRUCTIONS TO APPLICANTS 26

11. FORMS TO BE COMPLETED 26

SECTION V: APPLICATION FORMS FOR APPLICANT 27

2


A. COMPOSITION, MEMBER DETAILS AND UNDERTAKINGS 30

FORM 2.A: APPLICATION SUBMISSION FORM 31

FORM EL 2.1: COMPOSITION OF THE APPLICANT GROUPING (DBOM) 35

FORM EL 2.1 (CONTINUED): SUBCONTRACTORS UNDERTAKING KEY ELEMENTS (DBOM) 36

FORM EL 2.2: MEMBER DETAILS (DBOM) 29

FORM EL 2.2:MEMBER DETAILS (CONTINUED) 30




FORM EL 2.3: OCCUPATIONAL HEALTH AND SAFETY ACT (DBOM) 34

FORM EL 2.4: QUALITY SYSTEM (DBOM) 38

FORM EL 2.5: DECLARATION ON THE ACCURACY OF THE INFORMATION PROVIDED (DBOM) 39

FORM EL 2.6: COMMITMENT BY THE LEAD MEMBER OF THE APPLICANT FOR THE D B O M C O M P O N E N T TO SUBMIT RESPONSIVE TENDER(S) 40

FORM EL 2.7: PRO FORMA GUARANTEE (IF THE LEAD MEMBER FOR DBOM COMPONENT IS ALSO LEAD MEMBER AS MAIN CONTRACTOR) 41

FORM EL 2.8: ATTENDANCE OF CLARIFICATION MEETING (DBOM) 43

B. LITIGATION AND ARBITRATION HISTORY 44

FORM LI 2.1: LITIGATION AND ARBITRATION HISTORY (DBOM) 45

C. FINANCIAL STANDING 46

FORM FI 2.1: BANKER REFERENCE, ASSETS, LIABILITIES, PROFIT, TURNOVER, ETC (DBOM) 47

FORM FI 2.1: CONTINUED 48

FORM FI 2.2: TURNOVER RELATED TO SPECIFIC ACTIVITY (DBOM) 49

FORM FI 2.3: COMMITTED WORKLOAD 50

D. EXPERIENCE 51

FORM EX 2.1: EXPERIENCE (DBOM AS MAIN CONTRACTOR) – SUMMARY 52

FORM EX 2.2: EXPERIENCE (DBOM AS MAIN CONTRACTOR) – PROJECT 1 53



3


FORM EX 2.5: SYSTEM INTEGRATOR EXPERIENCE – SUMMARY 59

FORM EX 2.6: SYSTEM INTEGRATOR EXPERIENCE – PROJECT 1 60

FORM EX 2.7: SYSTEM INTEGRATOR EXPERIENCE – PROJECT 2 62

FORM EX 2.8: ITS DESIGN EXPERIENCE – SUMMARY 64

FORM EX 2.9: ITS DESIGN EXPERIENCE – PROJECT 1 65

FORM EX 2.10: ITS DESIGN EXPERIENCE – PROJECT 2 67

FORM EX 2.11: ITS BUILD EXPERIENCE – SUMMARY 69

FORM EX 2.12: ITS BUILD EXPERIENCE – PROJECT 1 70

FORM EX 2.13: ITS BUILD EXPERIENCE – PROJECT 2 72

FORM EX 2.14: ITS OPERATING EXPERIENCE – SUMMARY 74

FORM EX 2.15: ITS OPERATING EXPERIENCE – PROJECT 1 75

FORM EX 2.16: ITS OPERATING EXPERIENCE – PROJECT 2 77

FORM EX 2.17: ITS MAINTENANCE EXPERIENCE – SUMMARY 79

FORM EX 2.18: ITS MAINTENANCE EXPERIENCE – PROJECT 1 80

FORM EX 2.19: ITS MAINTENANCE EXPERIENCE – PROJECT 2 82

FORM EX 2.20: PERSONNEL – SUMMARY 84

FORM EX 2.21: EXPERIENCE OF SENIOR PROJECT MANAGER 85

FORM EX 2.22: EXPERIENCE OF CONTRACTS MANAGER 86

FORM EX 2.23: EXPERIENCE OF SYSTEM INTEGRATION MANAGER 87

FORM EX 2.24: EXPERIENCE OF MAINTENANCE ENGINEER 88

FORM EX 2.25: EXPERIENCE OF ITS DESIGN ENGINEER 89

FORM EX 2.26: EXPERIENCE OF OPERATIONS MANAGER 90

FORM EX 2.27: EXPERIENCE OF CONSTRUCTION MANAGER 91

E. PROGRAMME INFORMATION (SCHEDULE) 92

FORM P 2.1: PROGRAMME INFORMATION (SCHEDULE) 93

F. DATA, INFORMATION & SPECIFICATIONS 94

FORM D 2.1: SYSTEM INTEGRATION 95

G. CERTIFICATES AND SUPPORTING INFORMATION 96

FORM S 2.1: LIST OF SUPPORTING DOCUMENTATION 97

4


LIST O F TABLES

Table 7-1: Minimum turnover....................................................................................................................... 23

Table 7-2: Minimum historic contract value..................................................................................................23

Table 7-3: Minimum number of projects.......................................................................................................23

Table 9-1:Maximum number of points for each criterion..............................................................................24

Table 11-1: Forms to be completed by the Applicant (DBOM Component).................................................27

LIST O F FIGURES

Figure 1: Envisaged Contracted Entity Responsibilities...............................................................................16

5

SECTION I: INSTRUCTIONS TO APPLICANTS PQD: VOLUME 2

SECTION I: INSTRUCTIONS TO APPLICANTS

1. GENERAL (REFER TO VOLUME 1)

This section (as contained in Volume 1) specifies the procedures to be followed by Applicants in the preparation and submission of their Applications for Pre-qualification. It further contains provisions that are to be applied without modification.

2. DEFINITIONS AND INTERPRETATION

2.1 In this PQD the following words shall, unless inconsistent with the context, bear the following meanings:

Term Description

115 Prospective nationwide traffic information phone number with interactive voice recognition and associated website

10111, 10177 Examples of nationwide public safety emergency phone numbers

Act The South African National Roads Agency Limited and National Roads Act, 1998 (Act No. 7 of 1998)

Agency South African National Road Agency Limited (SANRAL)

Alarm An Alarm is a system action that occurs when a device or system meet defined criteria that is intended to solicit the attention of a system user

ApplicantA Person who applies in terms of the PQD for purposes of being Pre-qualified. An Applicant may apply to be Pre-qualified for the DBOM Component or the SSP Component

Application

The application submitted by an Applicant for purposes of being Pre-qualified in accordance with this PQD, together with all annexures thereto. In such Application, Applicants are to clearly identify what Components they are pre-qualifying for i.e. the DBOM Component or the SSP Component

Advanced Traveller Information System

Advanced Traveller Information System, including a range of information dissemination tools to provide road users with access to transportation network information. Includes roadside infrastructure (including VMS), Internet, phone, mobile applications, email alerts, media traffic updates. The private sector also operates traveller information services, often using a subscription-based business model

ATIS Gateway

The SANRAL ATIS Gateway is a system that shares information amongst various agency systems and/or provides traveller information to agency personnel, subscribers and/or the public at large. Information provided is envisaged to include traffic flow information, event information, and current field device message information (e g , VMS, HAR)

Advanced Traffic Management System The hardware and software system included in the scope of this document

ATMS InstanceAn ATMS instance corresponds to an installation of the software on one or more servers, such as at a TMC Each ATMS instance is separate and distinct from one another apart from a separate data exchange interface

Automatic Vehicle Location

Wireless transmitter on a vehicle that enables real-time vehicle information, including current location and speed. Most often uses a GPS, a communications link between vehicle and dispatcher, and tracking software program

Broad-based Black Economic Empowerment

Broad-based Black Economic Empowerment as contemplated in the Broad-based Black Economic Empowerment Act, 2003 (Act No. 53 of 2003) of South Africa, and any specific conditions or requirements of SANRAL

6


Business Model

A planned approach taken to achieve a desired return on an expense or investment. For a private sector for-profit entity, this is the plan for achieving a profit that will sustain or grow the business. For the public sector, it defines its role with respect to the private sector for the procurement or exchange of goods to meet goals of the agency

Computer-aided dispatch

Most commonly associated with public safety/law enforcement dispatch functions. In the context of SANRAL’s ITS programme, a police or emergency services CAD would provide real-time incident data and details and updated as dispatchers update the progression of the incident

Closed Circuit Television Cameras which are deployed on roadways to provide traffic surveillance for traffic management agencies

Commercial Vehicle Management System

A Commercial Vehicle Management System is a system used to manage the commercial vehicles and their contents as they travel through the Country

Concept of Operations A Concept of Operations (ConOps) defines the overall scope and needs of a system

Concessionaire Contracted operator of systems or roads; could include toll facilities, traffic management system control facilities

Contract

The contract which emanates from the award of a Tender pursuant to this Pre-qualification process and by which the Main Contractor is appointed to undertake Project Works (refer to Section 1b of the Pre-qualification Notice in Volume 1)

Contractor The Contractor is the successful Tenderer awarded the contract to supply goods and services for the ATMS project

Commercial off-the-shelfEquipment or systems that are pre-designed to perform specific functionality and can be implemented in an interoperable system easier than a proprietary system

Comma-Separated Values A common text-based data format

Comprehensive Traffic Observation Stations

Comprehensive Traffic Observation Stations collect traffic data for use by management agencies

Data Aggregation/ Fusion

Consolidation of data from more than one source, and formatting data for re-use in other applications. Commonly found in traveller information systems where multiple data types from different sources are consolidated and formatted, and made available for redistribution through multiple channels

Data Validation

Process whereby data from an external source is verified for accuracy and completeness. In this context, private sector speed data would need to be validated as a viable source of network speed data to support traveller information, performance monitoring and other functions

Design-Build-Operate-Maintain

Type of procurement and deployment model including building out system and then operating and maintaining that system

Dynamic message sign Interchangeable term with VMS, although not commonly used in South Africa

Department of Transport Refers to the National DOT entity in South Africa

Dube TradeportNew airport, trade zone and cyber port located just north of KZN region along coast; new airport expected to launch in May 2010, Tradeport is envisioned to be a major inter-modal hub in the KZN region

Emergency Management Services

Emergency Management Services, including fire, ambulance, and other incident and emergency responders

Engineer The Engineer is the ITS Project Manager appointed by SANRAL

eThekwini Transport Authority

eThekwini Transport Authority is the metro roads authority in the Kwazulu-Natal region. ETA manages arterial and freeway operations in the eThekwini metro area, including ITS

EventAn Event is a system record of a traffic related activity such as an accident, stall, debris, sporting event, special event or any other activity in the real world that could affect traffic

7


Event Planner

An Event Planner is any organization that holds events that are large enough to require special planning with SANRAL prior to the event in order to address transportation concerns. Examples include sporting arenas and organizations responsible for parades or marathons

External Event An External Event is a traffic related event provided to the ATMS from another system, not originating from an ATMS System Operator

External System Any system to which the ATMS connects

Facilities Maintenance The maintenance of buildings and infrastructure utilised for ITS operations and equipment installations

Freeway management system

Software, field devices, communications infrastructure and personnel that collectively manage traffic on the freeway network

Field Equipment Field Equipment includes any device controlled or monitored by the TMC that is located outside of the TMC

Gauteng Freeway Improvement Project Freeway expansion implementation project in the Gauteng region

Geographic Information System

A Geographic Information System (GIS) is a system for creating, storing, analyzing and managing spatial data and associated attributes A GIS is a tool that allows users to create interactive queries (user created searches), analyzes spatial information, and edits data

Highway advisory radio Highway advisory radio provides traveller information via radio to travellers. Can be permanent installations, or portable equipment.

Hosted Services Contracted services for SMS/email/web traveller information systems

IEEE Institute of Electrical and Electronics Engineers is a standards set used for interoperability of systems

Intelligent Devices, Inc Intelligent Devices, Inc – the developer of the current SANRAL device management system

Intergovernmental Agreement

An Intergovernmental Agreement formalizes relationships between public agencies

Incident Management System

SANRAL’s nationally-focused programmed aimed at improved coordination and response to incidents on the national road network. Multi-agency, cooperative strategy

Integrated Rapid Transport Integrated Rapid Transport is the transit provider in the KZN region

Information Technology Electronic systems management and support

Intelligent Transportation System

Intelligent Transportation System is a term used to encompass intelligent devices deployed on roads as well as the systems that communicate to those devices

ITS ArchitectureAn ITS Architecture is a planning tool that is technology-neutral and explains the use of a system or systems from the perspective of stakeholders and sets functional goals and expectations for ITS projects

i-traffic www.i-traffic.co.za – SANRAL’s traveller information website and brand for SANRAL’s national ITS programme

Joint Command CentreEmergency operations involving multiple entities within one area, collocated in an emergency operations centre, able to coordinate strategic and tactical responses to incidents and emergencies

Key Performance Indicators

Key Performance Indicators are measures that are used to evaluate performance of systems and agencies

Lane Control Signals Lane Control Signals, used to designate available or restricted lanes of freeway traffic using overhead electronic signs

Lane Link A Lane Link is a representation of a single lane along a logical section of roadway and is bounded by either a Node or the start or end point of the lane

Lead Member

The Member of an Applicant group, who shall lead the group (i.e. consortium, joint venture or partnership) constituted for purposes of this Pre-qualification process. For clarity, if an Applicant has only one Member, that Member will be the Lead Member

8


Link A Link is a connection between any two points along a roadway segment

Maintaining Agency Agency, firm, or entity under contract or arrangement to maintain and/or operate a portion of the FMS

Main Contractor

The Pre-qualified Applicant for the DBOM Component and the Pre-qualified Applicant for the SSP Component who Tendered in joint venture (or other association) and who have been appointed for the execution of the Contract pursuant to the Tender process initiated by SANRAL

Maintenance SystemA Maintenance System is a system that assists SANRAL in managing outstanding maintenance requests and evaluating the performance of equipment

Market Package Customised diagrams that illustrate the information exchanges between agencies or centre-to-field connections within each regional ITS Architecture

Media The media is any outlet that provides news and other information to the public at large

MemberIn respect of any Applicant, any Person, whether as a single entity or as a member of a consortium, joint venture or partnership who submits an Application pursuant to the Pre-qualification Notice in Volume 1

Mobile Applications Applications which are accessible via a mobile phone, including graphics-based maps, alerts, and other information

N1, N2 National roads operated and maintained by SANRAL

National ITS Architecture The National ITS Architecture is the framework that the United States uses as a basis for Regional ITS Architectures

Node A Node is a point along or at the end of a Roadway Segment that defines the logical start and end of Lane Links

National Transportation Communications for ITS Protocol

National Transportation Communications for ITS Protocol is a standards set used for interoperability of systems

Open Road TollingThe levying and collection of toll in a free flow electronic tolling environment without the use of toll lanes at conventional toll plazas, also known as “Multi Lane Free Flow tolling”

Other Traffic Centre

Any other traffic management system to which the ATMS connects is called an "Other Traffic Centre " This may be another ATMS located within the same TMC (e g , the traffic signal system) or another ATMS located within another regional centre

Other ATMS Instance

Another ATMS Instance is another Traffic Centre that happens to use the same software package that is used by the subject ATMS and is technically capable and institutionally authorized to serve as a redundant system to the ATMS, if needed

Overload Control Enforcement of height and weight restrictions for commercial vehicles on certain routes

Pan-Tilt-Zoom Refers to camera control capabilities

Parallel Event

A Parallel event refers to a specific event's unique existence in an external system, such as a computer aided dispatch system or other system outside of the ATMS The ATMS maintains an event record that includes a unique ATMS Event ID and the event ID as defined in the external system

Performance MeasurePerformance Measures are methods of collecting and analyzing specific types of data to measure the performance of the network, system, or agency against predefined goals

Performance MonitoringPerformance Monitoring is the ongoing management of performance measures and data quality, quantity, and availability to support performance measures

Person Any natural or juristic person, partnership, corporation, firm or other entity

Portable Sign A Portable Sign is a Variable Message Sign that is mounted on a trailer and can be readily relocated

9


Premium Services

Represents value-added information and services available from traveller information service providers (typically private sector), for a subscription fee. Examples include customised route guidance, navigation support or customised alerts

Pre-qualification Document Volumes 1, 2 and 3 as defined in the Pre-qualification Notice in Volume 1

Pre-qualified

In relation to an Applicant, the Applicants having been short-listed having met the Pre-qualification requirements based on the criteria of the PQD for purposes of selection and/or participation in the Tender in a form most beneficial to SANRAL. “Pre-qualify” and “Pre-qualification” shall have a corresponding meaning

Preset Scene A Preset Scene shall comprise camera position (pan and tilt), zoom, focus, and other controller selection options for a given camera

Private Sector DataPrivate Sector Data is traffic conditions data that is collected by private sector companies which utilizes a number of methods such as vehicle location (probe/GPS), historical data, and sensor-based detection devices

Private Sector Traveller Information Service

Private Sector Traveller Information Services are provided by the private companies which collect and disseminate their own information typically provided by subscription services or publicly accessible websites

Probe Data Probe Data is real-time traffic data that is collected using vehicle location and timed collection of that data; most often represented as speed or travel times

ProjectThe design, build, operation and maintenance of a national ITS and integrated supporting systems software and the deployment thereof in Gauteng, Kwazulu-Natal and the Western Cape

Project WorksThe works envisaged to be undertaken by the Main Contractor, and which are described in more detail in Section 1b of the Pre-qualification Notice in Volume 1

Public Safety Agency A Public Safety Agency is an agency that is responsible for maintaining the safety of the public, such as a police department, fire department, etc

Ramp Meters Ramp Meters are signals at an on-ramp to freeways that regulate the vehicle traffic onto the freeway in order to maintain a consistent freeway travel time

Real-Time Traveller Information

Information that provides travellers across a variety of transportation modes with situational awareness regarding current infrastructure conditions including information related to incidents, congestion, service disruptions, weather, and associated fees

Remote Device A device under the control of another ATMS Instance

Remote User A Remote User is a user of the ATMS located at a remote location, which may be another TMC, another SANRAL office, a residence, or elsewhere

Response Plan

Response Plan is the set of recommended actions that the ATMS Operator can take in response to an event These actions include four areas 1) The Operator may use the ATMS to select and recommend modifiable

VMS and VMS messages 2) The Operator may create and edit Highway Advisory Radio Messages 3) The Operator may create and edit an Advanced Traveller Information

System message for dissemination to external systems 4) The Operator may create and edit a list of relevant personnel to contact for

a specific event

Response Plan Template

A Response Plan Template is a defined message structure for an Event, for a specific response type such as VMS, ATIS, or HAR based upon the combination of location, lane blockage type and pattern, impact, and type of event

Road Works Construction and maintenance activities on roadways

Roadside Devices Devices that collect traffic information on the road network conditions and typically send that information to operations centres for use

10


Roadway Segment

A Roadway Segment is a logical representation of a roadway as stored within a GIS The start and end points of Roadway Segments within a GIS do not necessarily line up with the definition of Links within an ATMS Thus, the ATMS defines a link-node network on top of the Roadway Segment definition of the GIS

Roadway Service Patrol

A Roadway Service Patrol (RSP) is a person that patrols the transportation network in order to provide a quick response to events The patroller normally travels the transportation network in a truck that contains basic vehicle repair equipment, gasoline to refuel vehicles, and basic safety equipment that can be deployed to divert traffic around an incident scene

Service Level Agreement A Service Level Agreement formalizes relationships between agencies

Standard Operating Procedure Standard Operating Procedure – defined operational processes

Subsystem Elements that represent the source of multiple levels of information transfer – such as a centre, a device, a software system

Supervisor A Supervisor is a System Operator who is authorized to perform control functions that require special permissions

System Map

The System Map is the main graphic display screen of the system providing a visual image of the relative location of field devices and the transportation network It is fully expected that the map will consist of numerous layers/themes or objects describing spatial features

System IntegratorThe Person who will take on the technical responsibility of combining all the subsystems and ensuring that these subsystems interface and function as is required and “System Integration” shall have a corresponding meaning

System Operator A System Operator is any user of the ATMS who is authorized to enter information or control devices

System Requirements A System Requirement defines how the operational procedures, processes, interactions, and outcomes are achieved

System User A System User is any person with access to log into the ATMS via a valid user name and password

Systems EngineeringSystems Engineering is an interdisciplinary approach to developing systems and, through checkpoints back to the beginning of concept development, ensures that the design and what is deployed meets the project intent

Tender

The Tender pursuant to this Pre-qualification process in terms of which SANRAL shall enter into a Contract for purposes of appointing the Main Contractor who shall be responsible for the Project Works. In this regard, only Pre-qualified Applicants who have applied and Pre-qualified for the DBOM Component and applied and Pre-qualified for the SSP Component in terms of this Application process, shall be invited to participate in the Tender process for purposes of being appointed as Main Contractor.

Transport Information Call Centre Centralised information centre for City of Cape Town

Traffic Management Centre

Any facility that houses one or more dedicated workstations for the ATMS – term also used is TCC for Traffic Control Centre

Traffic Signals Traffic Signals provide regulated access through intersections of roadways

Turbo ArchitectureSoftware tool that provides a database to develop customised and region-specific ITS Architectures as well as update the architecture based on new implementation and growth

Urban Traffic Control ATMS system used in Cape Town and KZN regions to control arterial traffic management devices

Vehicle Detector StationA location with one or more detectors covering one or more lanes of traffic, where traffic data for individual lanes is typically aggregated into a single measure

Video Management System

Allows for control, monitoring, and archiving of video images obtained from CCTV cameras.

11


Variable Speed Limit Sign Variable Speed Limit Sign used to regulate traffic on roadways based on real-time road conditions

Wireless Communications Wireless Communications is a media used to send data from one system/device to another system/device without requiring physical connection

2.2 Any reference to:

2.2.1 Any one gender includes the other genders;2.2.2 a natural person includes an artificial person and vice versa; and2.2.3 the singular includes the plural and vice versa.

2.3 The headings of the clauses in the PQD are used for reference purposes only and shall in no way affect their interpretation.

3. ABBREVIATIONS

The following reflects a list of the key abbreviations used in this PQD:

Term DescriptionAMS Arterial Management System

ATIS Advanced Traveller Information System

ATM Active Traffic Management

ATMS Advanced Traffic Management System

AVI Automatic Vehicle Identification

AVL Automatic Vehicle Location

BBBEE Broad-based Black Economic Empowerment

BRT Bus Rapid Transport

CAD Computer-Aided Dispatch

CCB Change Control Board

CCC Central Communication Centre

CCTV Closed Circuit Television

COTS Commercial off-the-shelf

CSV Comma-Separated Values

CTO Stations Comprehensive Traffic Observation Stations

DBOM Design-Build-Operate-Maintain

DMS Dynamic Message Sign

BO Back Office

DOT Department of Transport (National Entity in South Africa)

DSRC Dedicated Short Range Communications

EMS Emergency Management Services

ESRI Environmental Systems Research Institute

ESS Environmental sensor station

ETA eThekwini Transport Authority

FMS Freeway Management System

12


FIDIC Fédération Internationale des Ingénieurs-Conseils or International Federation of Consulting Engineers

GB Gigabit

GFIP Gauteng Freeway Improvement Project

HAR Highway Advisory Radio

HOV High Occupancy Vehicles

IDI Intelligent Devices, Inc.

IGA Intergovernmental Agreement

IMS Incident Management System

IP Internet Protocol

IRT Integrated Rapid Transport

ISP Information Service Provider

IT Information Technology

ITS Intelligent Transportation Systems

JCC Joint Command Centre

KPI Key Performance Indicators

LAN Local Area Network

LCS Lane Control Signals

MOU Memorandum of Understanding

NMC Network Management Centre

No Number

NTCIP National Transportation Communications for ITS Protocol

OD Origin-Destination

ORT Open Road Tolling

OS Operating System

PDS Pre-qualification Data Sheet

PSA Public Service Announcement

PTZ Pan-Tilt-Zoom

RDBMS Relational database management system

RFP Request for Proposals

PQD Pre-qualification Document

RSP Roadway Service Patrol

RTMC Road Traffic Management Corporation

RWIS Road Weather Information System

SAN Storage Area Network

SANRAL South African National Roads Agency Limited

SLA Service Level Agreement

SMS Short Message Service – also known as text messaging

SAPS South African Police Service

SQL Structured Query Language

13


SLA Service Level Agreement

SMS Short Message Service

SOP Standard Operating Procedure

SSP Systems Software Provider

SQL Structured Query Language

TDM Travel Demand Management

TIC Traffic Information Centre

TMC Traffic Management Centre, and in the case of the Western Cape, Transport Management Centre

UPS Uninterruptible Power Supply

UTC Urban Traffic Control

VKT Vehicle Kilometres Travelled

VMS Variable Message Sign

VSLS Variable Speed Limit Sign

WIM Weigh-In-Motion

XML eXtensible Mark-up Language

ZAR South African Rand

14

SECTION II: SCOPE OF SUPPLY PQD: VOLUME 2

SECTION II: SCOPE OF SUPPLY

This section provides a general description of the Project Works, and expands on key aspects of the Main Contractor’s responsibilities. The Main Contractor can be a single Member entity or a joint venture, consortium or membership together with a Lead Member, as defined in Section 1. Applicants should note that the descriptions provided herein are for information purposes only, and are provided in order that Applicants can extract a better understanding what may ultimately be required.

Applications however, will be evaluated on the information provided in the Application Forms (Section V). In this regard, Applicants are referred to the Pre-qualification Notice in Volume 1 which outlines the Pre-qualification process, structure and intent.

4. GENERAL DESCRIPTION OF THE PROJECT WORKS

4.1 It is envisaged that a Main Contractor will be contracted for the Project, who shall assume full responsibility for:

• Providing design capacity to design ITS elements to add functionality to and/or expand the SANRAL ITS deployment based on achieving the programme goals. This function is described in this Volume 2 of the PQD.

• Providing build (construct) capacity to build ITS elements to add functionality to and/or expand the SANRAL ITS deployment based on achieving the programme goals. This function is described in this Volume 2 of the PQD.

• The operation of the SANRAL ITS. This operation is described in this Volume 2 of the PQD

• The supply and maintenance of all SANRAL ITS field and central devices and systems.

• Providing and integrating systems software and accompanying 3rd party ‘commercial of the shelf’ (COTS) software (e.g. database applications, operating systems, etc) to operate the SANRAL ITS including ATMS software to support incident management activities and manage ITS devices, Advanced Traveller Information System (ATIS) software and Hosted Internet solution to support the aggregation and dissemination of real-time and non-real time traveller information, computer aided dispatch (CAD)/automated vehicle identification (AVI)/automated vehicle location (AVL) software to facilitate the dispatch of incident response. These systems and services are described in Volume 3 of the PQD.

• Developing software data exchange interfaces for systems software provided under this Project as well as interfaces with 3rd party platforms to uni-directionally or bi-directionally exchange data including toll AVL/AVI system, external CAD platforms, and external traveller information platforms and services. These systems and services are described in Volume 3 of the PQD.

• Providing systems software maintenance and support services including for all systems software and accompanying 3rd party software supplied under this Project.

* It is envisaged that the Main Contractor will be contracted for five (5) years with an option available to SANRAL, at its sole discretion, to either extend the period for another three (3) years.

The envisaged contracted entity responsibilities, as described above, are indicated in the following organogram:

15

SANRAL

Main Contractor

ITS Field and Central

Devices and Systems

CADSystems Supply &

Maintenance

DESIGN & BUILD

OPERATIONS & MAINTAIN

SYSTEMS SOFTWARE

INTEGRATION

ITS

Back Office Automation

Hardware Maintenance

ATMS

Gauteng

KZN

Western Cape

National

ATIS

Software Maintenance

Software Maintenance


Figure 1 : E n v i sa g ed C o n tr a c t ed E n t i t y R espons i b ili t i es

5. WORKS NOT INCLUDED IN THE MAIN CONTRACTOR’S SCOPE

The following works are not envisaged to be included in the Project Works, but Applicants are required to take note of the content thereof, as it may influence the delivery management and interface requirements of the Project:

A separate telecommunications operator shall be responsible for the fibre backbone component, i.e. delivery of services from each outstation to the central ITS control room.

6. KEY ASPECTS OF THE PROJECT WORKS INCLUDED WITHIN THE MAIN CONTRACTOR’S RESPONSIBILITIES

This section describes certain key operations and maintenance aspects of the Project Works which are envisaged to be included in the Main Contractor’s responsibilities. These key operations and maintenance responsibilities include:

- Design ITS elements

- Build (Construct) ITS elements

16


- Operate regional traffic management centres

- Operate various support IMS

- Develop national ITS programme

- Provide and integrate systems software

- Maintenance of the above works.

6.1 DESIGN AND BUILD ITS ELEMENTS

The Main Contractor will be required to provide design and build capacity to add functionality to and/or expand the ITS infrastructure to achieve SANRAL’s strategic objectives and programme goals. The envisaged ITS elements include the following

ITS element Functional Description

CCTV Surveillance Visual monitoring & detection of incidents

Traffic data collection & detection

Automated traffic flow monitoring (including speed, flow, and density)

Data exchange Exchange of data with other centres and media

Ramp MeteringProvide ramp meter systems along selected sections of freeway system

Variable Speed LimitsIntroduce variable speed limit strategy along selected freeway links

VMS information disseminationProvide VMS systems. Based on current network status, determine most appropriate VMS for message placement, set messages and remove messages.

HAR information disseminationProvide recording of HAR messages and provide supporting environment for implementation

Civil Infrastructure condition monitoring

Monitor condition of civil works by means of manual CCTV surveillance as well as roaming teams

Communications

Provide last mile communications to field devices and various centres.

Provide radio communications system for vehicle to centre communications

TMC Back office automationProvide work stations, hardware for storage, video display, LAN and supporting software

6.2 TMC OPERATIONS

The TMC operational focus will be that of pro-active and active freeway traffic management through the application of management strategies and the provision of information to road users and various partnering regional stakeholders. Functions of the TMC operations include:

Active traffic management that responds to dynamically changing conditions Active monitoring of traffic conditions through CCTV surveillance and various traffic

detection equipment

17


Incident management operations (see Section 6.3) Traffic Data management. This includes data collection and use of real-time data to

positively affect network operations Automating processes, resulting in streamlined operational functions to promote greater

accuracy and consistency. These processes should also provide consistent messaging to foster greater public trust in SANRAL traveller information.

Administration, ensuring staff and technology resources are maximized, Call taking on traffic related queries will be required.

Active liaison with various supporting authorities, SANRAL partner stakeholders and CCC’s Performance monitoring and management of KPI’s as per desired specified outcome Traffic Law Enforcement interaction and operations support Overload Control monitoring ORT interaction and operations support

The regional involvement of the Main Contractor in TMC operations is foreseen to be as follows:

Gauteng: Take over current operations, TMC staff and expand as deemed necessary to meet SANRAL requirements

KZN: Take over current limited operations, TMC staff and expand as deemed necessary to meet SANRAL requirements

Western Cape: limited operational involvement (subject to change).

6.3 INCIDENT MANAGEMENT SYSTEMS OPERATIONS

It is envisaged that the Main Contractor will be responsible for managing and operating various elements of the Incident management systems on the regional freeway system. These operations will be integrated with the TMC operations. The envisaged functional elements are listed and described below.

Function Description

Incident (planned & current) logging

The process of capturing all necessary data (as supported by the ATMS software) from incident detection, notification, mobilisation, services arrival on site, services departure from site, incident clearance to the normalization of traffic conditions

Post-Incident Data Exchange with service providers

Pending the data to be entered into the ATMS software, data is to be exchanged with service providers to complete each incident record

Incident DetectionIdentification of incidents through various means, including caller notification, automated detection and manual surveillance

Incident Notification Dissemination of incident information to service providers & on-road personnel/vehicles

Vehicle Dispatch ( services under Main Contractor control)

Dispatch support vehicles including tow and recovery, medical assistance unit, incident response units including interfacing with traffic enforcement

Incident Data management Analysis, reporting and archiving of incident data

Incident response planning, review and debriefing

Regular review of response plans and debriefing to improve incident coordination

Tow and recovery services Provision of tow and recovery services for light and heavy

18


vehicles to tow vehicles from the scene

Incident Response (for purpose of making site safe - deploying high-visibility signs, closing lanes, screening incidents from onlookers, clearing minor debris, etc)

Provision of the service, including a purpose-equipped vehicle to assist in incident response procedure including securing a site, screening the incident from passers-by, clearing minor debris, carrying higher level life-support equipment, and other equipment as may be required for various incident types

Medical Assistance Provision of the service whereby a medically trained person can respond promptly to incidents

The regional involvement of the Main Contractor in IMS operations is foreseen to be as follows:

Gauteng: full implementation as indicated above,

KZN: primarily interaction and interface with current IMS services

Western Cape: primarily augmentation, interaction and interface with current IMS services.

6.4 DEVELOP NATIONAL ITS PROGRAMMEIt is envisaged that the Main Contractor will be responsible for developing and managing various elements of the national ITS programme. It is likely that the national ITS programme will be collocated within the Gauteng Regional TMC. Functionality will initially be limited, but will be phased and extended over time to include the elements below.

Function Description

National data aggregation and monitoring

Performance measurements (SANRAL KPI’s) and overload control data, regional traffic and incident data

National Data ArchivingStorage of data received from the various functions of each regions, including roadway state data, incidents and environmental data

Tolling related operationsQueue length monitoring, plaza operations monitoring via CCTV (where applicable)

Overload Control Data Aggregation

Aggregation of overload monitoring data from all sources for national assessment of OLC Programme

Advanced traveler information dissemination

Account management, development and hosting of website for all regions, Dissemination of real-time data to Mobile and other applications

Centre to centre networking services

Simultaneous monitoring of all three centres

Research and Development Management of data for R & D purposes

6.5 PROVIDING AND INTEGRATING SYSTEMS SOFTWARE FOR ATMS

This aspect is described in Volume 3 of the PQD.

6.6 MAINTENANCE

19


This aspect of the envisaged works includes the maintenance of all elements of the above works taken over and implemented by the Main Contractor. Scheduled and emergency maintenance will be required on elements, including:

Field Devices

Last Mile communications

Radio communications

Back office equipment

Electrical and mechanical maintenance, for example, the maintenance of the generators, uninterruptible power supplies, etc.

Note: excludes building maintenance, HVAC maintenance, operational & infrastructure security at facilities, except in the case of the TMC in KwaZulu-Natal, the following maintenance will be required;

Upkeep and maintenance of the SANRAL TMC building space

The assumption of responsibility for all utility services (e.g. electricity)

Maintenance of all TMC equipment and furnishing, TMC generator, UPS and HVAC

Operational and infrastructure security at the facility.

20

SECTION III: PRE-QUALIFICATION DATA SHEET PQD: VOLUME 2

SECTION III: PRE-QUALIFICATION DATA SHEET (PDS)

This Section consists of provisions that supplement the information or requirements included in, Section I of Volume 1, Instructions to Applicants. References to clauses in this PDS are a reference to the clause within Volume 1.

A. GENERAL

PDS 1.1 Employer: The South African National Roads Agency Limited

PDS 1.2

The name of the Project is: INVITATION TO PRE-QUALIFY FOR THE PROCUREMENT OF A NATIONAL INTELLIGENT TRANSPORT SYSTEM AND INTEGRATED SUPPORTING SYSTEMS SOFTWARE AND THE DEPLOYMENT THEREOF IN GAUTENG, KWAZULU-NATAL AND THE WESTERN CAPE

PDS 1.3(Clause 3) Application Process

PDS 1.4(Clause 12) Application Documents

PDS 1.5(Clause 6)

(i) The Pre-qualified Applicants in joint venture (or other association) for the DBOM Component and the SSP Component as the Main Contractor is liable to pay SANRAL, on written demand, compensation in the amount of ZAR Fifty Thousand (ZAR 50,000-00) applicable for the non-submission of a responsive Tender. To this end, a guarantee is required to be submitted to SANRAL by al l Applicants, within forty(48) hours from Pre-qualification (Refer Form EL 2.7 in th is Volume 2 and Form EL 3.7 in Volume 3)

(ii) Maximum number of partners in the joint venture shall not be limited.

B. CONTENTS OF THE PRE-QUALIFICATIONDOCUMENTATION

PDS 1.6(Clause 8.1)

Applicants should submit all enquiries per email or facsimile:

Techso (Pty) Ltd

A t t e n t i o n : Mr. F van der Walt F ax : +27 12 844 0156e - M a i l : frans@ techso. co . z a

No queries will be entertained after 28 March 2010.

PDS 1.7(Clause 8.2)

A compulsory clarification meeting will be held on 17 March 2010 at 10h00 South African time (GMT + 2 hours) at the Gauteng TMC of:

The South African National Roads Agency Ltdc/o No 2 First and Smuts AvenueHalfway HouseMidrandJohannesburgSouth Africa

Non-attendance of the clarification meeting will disqualify the

21

mailto:[email protected]

SECTION III: PRE-QUALIFICATION DATA SHEET PQD: VOLUME 2

Applicant.The meeting must be attended by an authorised representative of the Applicant. No Application will be considered for Pre-qualification if the Applicant has not submitted documentary evidence of their attendance at the clarification meeting.Applicants should note that Applications will not be received at the above- listed address (refer to PDS 1.11 below).

C. PREPARATION OF APPLICATIONS

PDS 1.8(Clause 11)

Language: The language of the Application and all correspondence shall be English.

PDS 1.9(Clause 12)

All Applications shall include the following documents: Audited financial statements including balance sheets and income statements, letter of good standing from their bankers, and other supporting documentation as is required in the Application forms of the PQD.

PDS 1.10(Clause 13.2)

In addition to the original, the number of hard copies to be submitted with each Application is: Two (2) and the number of electronic copies is Two (2) on CD or DVD media.

D. SUBMISSION OF APPLICATIONS

PDS 1.11(Clause 14)

Hard copies (the original Application plus t w o (2) additional copies), and electronic copies (2 x CD or DVD media) of the Application shall be placed in the tender box at SANRAL’s Northern Region offices or couriered to arrive at the address shown below, on or before 14h00 South African time (GMT + 2 hours) on 7 April 2010.

The address for the submission of the Application is:

The South African National Roads Agency Ltd: Northern RegionTender Box38 Ida Street Menlo Park Pretoria South Africa

A t t e n t i o n : Ms. G Bester (Tel: +27 12 426 6200)

Applications via telefax or email will not be accepted.

PDS 1.12(Clause 16)

Closing Date: The closing date for Application submissions is:Date: 7 April 2010Time: 14h00 South African time (GMT + 2 hours)

PDS 1.13(Clause 17) Late Applications shall be returned unopened to the Applicant.

22

SECTION IV: QUALIFICATION CRITERIA, REQUIREMENTS PQD: VOLUME 2

SECTION IV: QUALIFICATION CRITERIA, REQUIREMENTS

This Section contains the general methods, criteria, and requirements to be used to determine how Applicants will be evaluated for Pre-qualification purposes.

7. MINIMUM CRITERIA

The minimum criteria that each Application must satisfy in order to be considered for Pre-qualification are as follows:

a) The Applicant or Lead Member for the re levant Component must complete, sign and provide a responsive Application Submission Form (Form 2 .A in the Application Forms);

b) If a Member is required to complete a form, then all Members of the Applicant group for the relevant Component shall complete the applicable form;

c) The average annual turnover (defined as the gross revenue for a financial year from income related to sales, services rendered and yields on assets) of the Applicant or the combined turnover of the Members o f the App l i can t Group fo r t he re l evan t Componen t over the last two (2) financial years must equal or exceed the amounts in the table below (in ZAR, based on the exchange rate on the date of the clarification meeting);

Table 7 - 1 : Mi n i m um t u r no v er

Description Minimum average turnover over last 2 financial years

DBOM ZAR 100 million per year

d) The Applicant or any individual Member must have successfully completed or started with at least one ITS design, I T S s u p p l y a n d / o r i n s t a l l a t i o n , I T S m a in t e n a n c e a n d r e l e v a n t o p e ra t i o n a l e x p e r i e n c e ( i . e . o n e o f e a c h ) during the last five (5) years, with a value greater than the amounts in the table below (in ZAR, based on the exchange rate on the date of the clarification meeting);

Table 7 - 2 : Mi n i m um h i s t o r i c co n tr a c t v a l ue

Description Value of any similar contracts awarded during last 5 years

DBOM ZAR 40 million (combined)

e) The Applicant or any individual Member must have completed the following number of projects in the last five (5) years cumulatively;

Table 7 - 3 : Mi n i m um nu m b e r o f p r o j ec t s

Description Minimum no. of projects in last 5 years

Multi-disciplinary (systems and operations) project roll-out management

2 projects

f) The Applicant shall provide a guarantee, when requested, in the form attached to the PQD and in accordance with clause 6 of Volume 1 (Form EL 2 .7 in the Application Forms);

23


g) The Applicant must include the requisite System Integration experience. This key element may not be subcontracted and must form part of the Applicant grouping; and

h) The Applicant is not subject to the following:

Insolvent or being wound up;

Subject to proceedings for a declaration of insolvency;

Convicted of a criminal offence or an offence concerning his professional conduct;

Found guilty by a professional body of professional misconduct;

Unfulfilled obligations relating to the payment of taxes in accordance with the legal provisions;

Guilty of serious misrepresentation in supplying or failing to supply the information requested by an authority; or

In the reasonable opinion of SANRAL, guilty of a corrupt practice, fraudulent practice and/or collusive practice (all as defined in Volume 1).

8. ASSESSMENT CRITERIA

Applications shall be measured against the following criteria:

A. COMPOSITION, MEMBER DETAILS AND UNDERTAKINGS

B. LITIGATION AND ARBITRATION HISTORY

C. FINANCIAL STANDING

D. EXPERIENCE (INCL. TECHNICAL AND PROJECT MANAGEMENT)

E. PROGRAMME INFORMATION

F. DATA, INFORMATION & SPECIFICATIONS

9. ADJUDICATION USING A POINT SYSTEM

The above stated criteria shall be used to adjudicate the Pre-qualification of Applicants. The following maximum number of points may be awarded for each criterion:

Table 9 - 4 : M a x i m um n u m ber o f po i n t s f or each c r i t e r ion

CRITERIA POINTS

A. COMPOSITION, MEMBER DETAILS AND UNDERTAKINGS 5

B. LITIGATION AND ARBITRATION HISTORY 5

C. FINANCIAL STANDING 30

D. EXPERIENCE 35

E. PROGRAMME INFORMATION 10

F. DATA, INFORMATION & SPECIFICATIONS 15

TOTAL 100

The number of points awarded to the stated criteria will be calculated as follows:

Allocated points for criteria = max no of points (in table above) × P/MP

where P equals the points scored by the Applicant for the criteria under consideration;

and

24


where MP equals the highest number of points achieved amongst all Applicants for the criteria under consideration

For e x a m p l e:

If Applicant “Company A” scores 24 points for the “Experience” criteria and the maximum score by “Company B” for the “Experience” criteria is 32, then the allocated points for “Company A” is:

Allocated points for criteria for Company A = 45 (from table above) × 24/32

= 45 × 0.75

= 33.75

whereas the allocated points for “Company B” is:

Allocated points for criteria for Company B = 45 (from table above) × 32/32

= 45 × 1

= 45

25


10. INSTRUCTIONS TO APPLICANTS

Applicants shall complete all forms and provide all information and documents referred to in the relevant Applications Forms.

11. FORMS TO BE COMPLETED

A list of the Application submission forms required to be submitted with the Application is provided in Section V. Applicants shall provide all the information and documents requested in these forms. Each Applicant is required to complete the forms where the Applicant's name is required whereas each and every Member, which makes up the Applicant group, shall complete the forms where the Member name is required. The Member, in case of an Applicant which contains a single Member only, shall complete all the forms, including that for the Lead Member.

If an Applicant or Member cannot complete the information in the allocated space, then the space should be expanded (if the information is captured electronically within the SANRAL provided Microsoft Word document) or an additional page with the same page number should be added immediately after the page without adequate space.

26

27

SECTION V: APPLICATION FORMS FOR APPLICANT PQD: VOLUME 2

SECTION V: APPLICATION FORMS FOR APPLICANT

This Section contains the Application Submission Forms required to be submitted with the Application. The Applicant shall indicate in the list below, included within the Application submission, if a form was or was not provided (or completed).

A list of the forms to be completed for this section is provided below.

Table 11 - 5 : Fo rm s t o be co m p l e t ed b y t he A pp li cant (DBOM Component)

Form Form description To becompleted by

ProvidedYes No


Form 2.A: Application Submission Form Lead and otherMembers

Form EL 2.1: Composition of Applicant grouping ApplicantProject organisation chart Applicant

Form EL 2.2: Member details All MembersCompany registration detail / certificate All Members

Company profile All MembersForm EL 2.3: Occupational Health and Safety Applicant

Health and Safety compliance within own country All Members

Form EL 2.4: Quality system All MembersISO 9001 or other certificate ofRegistration

All Members

Form EL 2.5: Declaration on the accuracy of theinformation provided

All Members

Form EL 2.6: Commitment by the Lead Member tosubmit responsive Tender

Lead Member

Form EL 2.7: Pro-forma guarantee Lead MemberForm EL 2.8: Attendance of clarification meeting Applicant and

SANRAL

B. LITIGATION AND ARBITRATION HISTORYForm LI 2.1: Litigation and arbitration history All Members

Litigation and arbitration detail Members with alitigation history

C. FINANCIAL STANDINGForm FI 2.1: Assets & liabilities All Members

Letter of Good Standing from bankers,including the current bank rating

All Members

Extracts from audited statementsincluding balance sheet, income statement, notes and auditors report

All Members

28



ProvidedYes No

Substantiation on the reason forwithholding projected financial information

If no informationwas provided

Form FI 2.2: Turnover related to specific activity All MembersForm FI 2.3: Committed workload All Members

D. EXPERIENCE (INCL. TECHNICAL AND PROJECT MANAGEMENT)

Form EX 2.1: DBOM (main contractor) experience – summary

Applicant

Form EX 2.2: DBOM (main contractor) experience – project 1

Applicant

Form EX 2.3: DBOM (main contractor) experience – project 2

Applicant

Form EX 2.4: System Integrator experience –Summary

Applicant

Form EX 2.5: System Integrator experience – project 1

Applicant


Applicant


Applicant

Form EX 2.8: System Design experience – summary ApplicantForm EX 2.9: System Design experience – Project 1 ApplicantForm EX 2.10: System Design experience – Project 2 ApplicantForm EX 2.11: System Build experience – summary ApplicantForm EX 2.12: System Build experience – Project 1 ApplicantForm EX 2.13: System Build experience – Project 2 ApplicantForm EX 2.14: ITS Operation experience –summary ApplicantForm EX 2.15: ITS Operation experience – Project 1 ApplicantForm EX 2.16: ITS Operation experience – Project 2 ApplicantForm EX 2.17: ITS Maintenance experience –

SummaryApplicant

Form EX 2.18: ITS Maintenance experience – Project 1

Applicant

Form EX 2.19: ITS Maintenance experience – Project 2

Applicant

Form EX 2.20: Personnel – summary ApplicantForm EX 2.21: Experience of senior project manager ApplicantForm EX 2.22: Experience of contracts manager ApplicantForm EX 2.23: Experience of systems integration

managerApplicant

Form EX 2.24: Experience of maintenance engineer ApplicantForm EX 2.25: Experience of ITS design manager ApplicantForm EX 2.26: Experience of operations manager ApplicantForm EX 2.27: Experience of construction manager Applicant

29



ProvidedYes No

E. PROGRAMME INFORMATION

Form P 2.1 Programme information (Schedule) Applicant

F. DATA, INFORMATION AND SPECIFICATIONS

Form D 2.1 System Integration Applicant

G. CERTIFICATES AND SUPPORTING INFORMATION

Form S 2.1: List of supporting documentation Applicant

30



31


FORM 2.A:APPLICATION SUBMISSION FORM

[Letterhead paper of the Applicant or Lead Member responsible for a joint venture, including full postal address, and telephone, facsimile and telex numbers, and cable address]

Date: The South African National Roads Agency Ltd: Northern Region38 Ida Street Menlo Park Pretoria South Africa0102

Attention: Mr. I Essa

Dear Sir

INVITATION TO PRE-QUALIFY FOR THE PROCUREMENT OF A NATIONAL INTELLIGENT TANSPORT SYSTEM AND INTEGRATED SUPPORTING SYSTEMS

SOFTWARE AND THE DEPLOYMENT THEREOF IN GAUTENG, KWAZULU-NATAL AND THE WESTERN CAPE

1. Being duly authorised to represent and act on behalf of _______________ (name of Applicant) (hereinafter referred to as the “Applicant”), and having reviewed and fully understood all of the Pre-qualification requirements and information provided, the undersigned hereby applies to submit an Application for the Project for Pre-qualification purposes.

2. Attached to this letter are the completed Application forms as contained in the Pre-qualification Document, together with the originals of the signed documents as required.

3. SANRAL and its representatives are hereby authorised to conduct any enquiries or investigations to verify the systems, statements, documents, and information submitted in connection with this Application, and to seek clarification from our bankers and clients regarding any financial and technical aspects. This letter of Application will also serve as authorisation to any individual or representative of any institution referred to in the supporting information to provide such information deemed necessary and as requested by you to verify systems, statements and information provided in this Application, such as the resources, experience, and competence of the Applicant.

4. This Application is made with the full understanding that:

a) Applications by Applicants who wish to Pre-qualify may be subject to verification of information submitted for Pre-qualification at the time of the Application;

32


b) SANRAL reserves the right to reject or accept any Application, cancel the Pre-qualification process, and reject all Applications.

c) SANRAL shall not be liable for costs or losses suffered due to any such actions under 4(b) above.

5. Appended to this Application and included in form EL 2.1, we give details of the participation of each Member, including the percentage financial commitment, and the responsibilities of each for execution of the work.

6. I/we shall provide a guarantee to SANRAL when requested, which guarantee shall serve as security for the obligation to submit a responsive Tender (as per form EL 2.7).

7. I/We understand that I/we shall not be invited to tender for the Tender for the Project described in the Pre-qualification Documents unless I/we are Pre-qualified, at the sole discretion of SANRAL, as an Applicant (in this case for the DBOM Component).

8. I/We choose domicilium citandi and executandi at:

Address:

Telephone:

Telefax:

9. We undertake and agree that if we are Pre-qualified and invited by SANRAL to submit a Tender/s we will:

a) Submit a responsive Tender as a potential Main Contractor;

b) Sign the necessary Contract should our Tender be accepted; and

c) Submit any joint venture agreement anticipated in the PQD to SANRAL.

10. We accept that the information recorded herein shall not supersede or replace our obligations and responsibilities in terms of the Application and should there be any conflict between that recorded in this Application Submission Form and the provisions of the Pre-qualification Document (i.e. Volumes 1, 2 and 3), the provisions of the Pre-qualification Document shall prevail.

11. The undersigned declare that the statements made and the information provided in the duly completed Application are complete, true, and correct in every detail. The undersigned hereby authorises the Lead Member of the Applicant (for the DBOM component) to sign all other forms and documents on our behalf.

33


SIGNATURE OF AUTHORISED REPRESENTATIVE: FOR AND ON BEHALF OF LEAD MEMBER OF

THE APPLICANT (DBOM COMPONENT)

NAME (BLOCK LETTERS) : DATE :

SIGNATURE OF AUTHORISED REPRESENTATIVE: FOR AND ON BEHALF OF MEMBER








34





FORM EL 2.1: COMPOSITION OF THE APPLICANT GROUPING

1. Member name

2. Type of o

rganisation (Public,

Private, etc)

3. Proposed Project Works to be executed by Member

4. % Financial share /

commitment

5. Country of registration

6. Contractingrelationship

7. Years ofexperience

a. S

ingl

e M

embe

r

b. J

oint

Ven

ture

c. O

ther

(not

e 1)

a. In

Sou

th A

frica

b. In

tern

atio

nally

Note 1: Provide the contracting relationship if not a single Member or Joint Venture:

35


FORM EL 2.1 (CONTINUED): SUBCONTRACTORS UNDERTAKING KEY ELEMENTS

(As required by clause 21 of volume 1)

1. Subcontractor name

2. Type of organisation (Public, Private, etc)

3. Proposed Project Works to be executed by subcontractor

4. Country of Registration share / commitment

5. Years of experience

a. In South Africa b. Internationally

Each Applicant shall attach a one page project organization chart of their grouping which indicates the project responsibilities.

36

37


FORM EL 2.2: MEMBER DETAILSDESIGN:Name of Member:Provide information requested in the table below for each Member. Use a separate form for each Member.1. Company name

2. Company type (Public, Private, etc )

3. Company registration number

4. Registered address5. Head office street

address6. Head office postal

address

7. Contact person:a. Name:b. Tel. No.:c. E-mail:

If any Member is a non South African organisation, does the Member have a r ep r ese n t a t i v e o ffi c e i n S ou t h A fri ca (RSA), and if so, provide the following details8. Name of RSA

representative organisation

9. Registered office street address of RSA representative organisation

10. RSA office postal address

11. Contact person: a. Name:b. Tel. No.:c. E-mail:

12. If the Member does not have a r ep r ese n t a t i v e o f f i ce i n S o u t h A fri ca (RSA), does it intend to either have a representative office in South Africa or does it intend to appoint an entity as its representative in South Africa? (state intention)

In addition, each Member shall provide the following:

13. A certified copy of the company registration details

38


FORM EL 2.2: MEMBER DETAILS (CONTINUED)

14. E ach M e m ber shall provide a two page (maximum) company profile(PRE-PRINTED BROCHURES WILL NOT BE ACCEPTABLE)

BUILD:

Name of Member:

Provide information requested in the table below for each Member. Use a separate form for each Member.

1. Company name



4. Registered address

5. Head office street address

6. Head office postal address

7. Contact person:

a. Name:

b. Tel. No.:

c. E-mail:





11. Contact person: a. Name:

b. Tel. No.:

c. E-mail:


39






OPERATE:

Name of Member:


1. Company name






7. Contact person:

a. Name:

b. Tel. No.:

c. E-mail:






40


b. Tel. No.:

c. E-mail:


41






MAINTAIN:

Name of Member:


1. Company name






7. Contact person:

a. Name:

b. Tel. No.:

c. E-mail:






b. Tel. No.:

42


c. E-mail:








43


FORM EL 2.3: OCCUPATIONAL HEALTH AND SAFETY ACT

Each Applicant/Member is to make the following declaration:

DESIGN:

Name of Applicant/Member:

I / We, the under-mentioned, in my / our capacity as indicated hereby acknowledge that:

1. SANRAL will require the successful Tenderer pursuant to the Tender to be compliant with the Occupational Health and Safety Act No. 85 of 1993, and any amendments thereto; and

2. that the successful Tenderer pursuant to the Tender implements an appropriate Health and Safety plan for the Project; and

3. should we be the successful Tenderer pursuant to the Tender process, we shall comply with 1 and 2 above.

In addition, each Applicant/Member shall provide the following:

4. one page (maximum) statement regarding compliance with Health and Safety (or letter of good standing from the Department of Labour or similar institution) within their own country.

SIGNATURE OF AUTHORISED REPRESENTATIVE: FOR AND ON BEHALF OF APPLICANT/MEMBER

NAME (BLOCK LETTERS): DATE:

44



BUILD:










45



OPERATE:










46



MAINTAIN:










47


FORM EL 2.4: QUALITY SYSTEM

Name of Member:

1. Each Member shall attach to this form a copy of a Certificate of Registration confirming that the Member’s Quality Management System complies with an internationally recognized quality system, such as ISO 9001:2000; or

2. If not, provide a statement with regards to the quality system utilized by the Member.



48


FORM EL 2.5: DECLARATION ON THE ACCURACY OF THE INFORMATION PROVIDED

Name of Member:

Each Member of the Applicant grouping is to make the following declaration:

I/We acknowledge that:

1. The information provided in the Application forms is, to the best of my knowledge, true and accurate.

2. If any information is subsequently found to be incorrect, SANRAL may, in addition to any other remedy:

• Disqualify the Applicant and/or Member from the Pre-qualification process and/or the Tender process

• Circulate and publicize the nature of the contravention and the changes on the accreditation status of the entity to all potential users of the supplier (in both the public and private sectors).



49


FORM EL 2.6: COMMITMENT BY THE LEAD MEMBER OF THE APPLICANT FOR THE DBOM COMPONENT TO SUBMIT RESPONSIVE TENDER(S)

Name of Lead Member:

The Lead Member is to make to following declaration:

In the event that the Application by the group led by ourselves is successful, we as the Lead Member hereby agree to:

1. Submit a responsive Tender as a Main Contractor;

2. Maintain the Members identified in our Applicant group;

3. Submit a guarantee in the required form when requested; and

4. Not to withdraw from the Applicant group after being Pre-qualified.

SIGNATURE OF AUTHORISED REPRESENTATIVE: FOR AND ON BEHALF OF LEAD MEMBER OF

THE APPLICANT (DBOM)


50


FORM EL 2.7: PRO FORMA GUARANTEE

[LETTERHEAD OF BANK]

Chief Executive OfficerSouth African National Roads Agency LimitedDitsela Place1204 Park Street (Corner of Park & Duncan Street) Hatfield0083GautengSouth Africa

Dear Sirs

DEMAND GUARANTEE: PROCUREMENT OF A NATIONAL INTELLIGENT TRANSPORT SYSTEM AND INTEGRATED SUPPORTING SYSTEMS SOFTWARE AND THE DEPLOYMENT THEREOF IN GAUTENG, KWAZULU-NATAL AND THE WESTERN CAPE

We, [ ] ("the Bank"), undertake to pay the South African National Roads Agency Limited ("the Beneficiary") the sum of ZAR 50 000 (ZAR fifty thousand) ("the Guaranteed Amount") on receipt of a first written demand for payment from the Beneficiary stating that the amount is due and payable by [ ] ("the Lead Member ") pursuant to a breach by the Applicant or the Lead Member of the Applicant of undertakings provided by it to the Beneficiary in terms of an application under an invitation to Pre-qualify for the Procurement of a National Intelligent Transport System and Integrated Supporting Systems Software and the Deployment thereof in Gauteng, Kwazulu-Natal and the Western Cape.

The Bank's liability under this guarantee is principal in nature and is not accessory to the Invitation. The Bank's liability shall not be reduced, or in any way be affected by any alteration of the terms of the Invitation, or any other arrangements made between the Lead Member and the Beneficiary.

The Bank will pay on demand and will not determine the validity of the demand or the correctness of the amount demanded, or become party to any claim or dispute of any nature which any party may allege.

This guarantee is neither negotiable nor transferable, is restricted to the payment of a sum of money only and is limited to the Guaranteed Amount.

51


This guarantee will expire on 3 0 S e p t e m b e r 2 0 1 0 , or upon payment of the Guaranteed Amount, whichever event occurs first, and further claims will then be considered by the Bank.

The cancellation of, or any change to the terms and/or conditions of this guarantee, must first be agreed to in writing by the Beneficiary, the Lead Member and the Bank.

Payment will be made at the [ ] Branch of the Bank and against return of this original guarantee by the Beneficiary or the Beneficiary's duly authorised agent.

This original guarantee must be returned to the [ ] Branch of the Bank by the Beneficiary or the Beneficiary's duly authorised agent either:

on expiry of the guarantee; or

against payment of the Guaranteed Amount; or

on cancellation of the guarantee.

Signed at [ ] on [ ]

For: [ ]

52


FORM EL 2.8: ATTENDANCE OF CLARIFICATION MEETING

Any one Member of each Applicant should ensure that this form is completed and signed at the clarification meeting:

This is to certify that I, (name)

representative of (Member)

of (address)

(telephone number)

(fax number)

(e-mail)

attended the clarification meeting on (date)

conducted by SANRAL’s representative (name)

SIGNATURE OF MEMBER’S REPRESENTATIVE:

SIGNATURE OF SANRAL’S REPRESENTATIVE:

53


B. LITIGATION AND ARBITRATION HISTORY

54


FORM LI 2.1: LITIGATION AND ARBITRATION HISTORY

Name of Member:

Each Member is to make the following declaration on its Litigation and Arbitration History:

1. I / We the under-mentioned in my / our capacity as indicated hereby declare that there are no criminal proceedings instituted against us, neither are any investigation/s pending or that I / we have previously been found guilty of theft or fraud; and

2. I / We the under-mentioned in my / our capacity as indicated hereby declare that, save as disclosed in this Application, there are no litigation or arbitration proceedings instituted against the Member, neither are any such procedures pending; and

3. I / We the under-mentioned in my / our capacity as indicated hereby declare that, save as disclosed in this Application, there is no litigation or arbitration proceedings instituted by the Member, neither are any such procedures pending against any previous Employer / Client or Authority; and

4. I / We the under-mentioned in my / our capacity as indicated hereby declare that:

a. I / we are not insolvent and/or or are not subject to proceedings for a declaration of insolvency;

b. I / we have not been convicted of a criminal offence or an offence concerning my / our professional conduct;

c. I / we have not been found guilty by a professional body of professional misconduct;

d. I / we have no unfulfilled obligations relating to my / our payment of taxes;

e. I / we are not guilty of serious misrepresentation in supplying or failing to supply the information requested by an authority; or

f. I/we are not guilty of a corrupt practice, fraudulent practice and/or collusive practice (all as defined in Volume 1).

If not, the Member must cross out the declaration that is not applicable and provide thelitigation or arbitration details on a separate page attached to this form



55


C. FINANCIAL STANDING

56


FORM FI 2.1: BANKER REFERENCE, ASSETS, LIABILITIES, PROFIT, TURNOVER, etc.

Name of Member:

Each Member shall provide contact details for their Banker in the form of the table below:

1. Name of banker:

2. Address of banker:

3. Contact name and title :

4. Telephone no.:

5. Fax :

6. e-mail :

Each Member shall attach a letter of Good Standing from their Bankers, which also include the current bank rating.

57


FORM FI 2.1: CONTINUED

Summarise actual assets and liabilities (in the reported currency as per the financial statements) for the previous five financial years. Based upon known commitments, summarise projected assets and liabilities for the next two financial years, unless the withholding of such information by stock market listed public companies can be substantiated by the Member.

Financial information

Values from audited financial statements – ‘in millions (in reported currency in ‘000,000)

Actual - previous five years Projected: next two years

a. b. c. d. e. f. g.

Financial year

7. Cash/Cash equivalent

8. Debtors

9. Total assets

10. Non-current liabilities

11. Total liabilities

12. Total turnover

13. Profits after tax

14. Reported currency (provide name of currency)

15. ZAR exchange rate (at the end of the respective financial year)

Not Applicable

Each Member shall attach copies of extracts from their audited financial statements (including balance sheet, income statement, notes to the balance sheet / income statement and the auditors report) for the previous three audited years as well as latest un-audited period.

58


FORM FI 2.2: TURNOVER RELATED TO SPECIFIC ACTIVITY (DBOM)

Name of Member:

Each Member is to provide a turnover percentage attributable to each of the stated products or activities, if applicable (the turnover refers to the “Total turnover” provided in form FI 5.1 above):

Actual - previous five years Projected: next two years

a. b. c. d. e. f. g.

Financial year

% turnover attributable to being the (if applicable):

1. Main

Contractor2. D e s i g n e n g i n e e r

3. B u i l d c o n t r a c t o r

4. O p e r a t i n g e n t i t y5. M a i n t e n a n c e c o n t r a c t o r



59


FORM FI 2.3: COMMITTED WORKLOAD

Name of Member:

Each Member is to provide information on its committed workload, resulting from contracts already awarded to the Member (in reported currency) for each financial year starting in2008 in the form below:

Yeara. Committed design workload

(For 2010, indicate % completed)

b. Committed build workload


1. 2010

2. 2011

3. 2012

4. 2013

Year c. Committed operation workload


d. Committed maintenance workload


5. 2010

6. 2011

7. 2012

8. 2013

9. Reported currency (provide name of currency)



60


D. EXPERIENCE

61


FORM EX 2.1: DBOM EXPERIENCE (IN MAIN CONTRACTOR ROLE) – SUMMARY

Name of Applicant:

Each Applicant is to list below up to three (3) relevant projects involving the multidisciplinary (systems and operational) rollout management as a Main Contractor, which have been completed during the last five years, or which are currently in progress. Note that completion implies that consent has been given to contact the references provided.

1. Name of contract and brief description

2. Employer, contact address/tel/fax

3. Contract Value (current ZAR equivalent)

4. Completion

date

5. Duration

The contract value should be based on the payment currencies of the contracts converted into ZAR, (at the date of substantial completion, or for ongoing contracts, the exchange rate on the date of the clarification meeting).

Using the format attached (Forms EX 2.2 to EX 2.4), the Applicant is requested to provide details of the above projects, on separate sheets.

62


FORM EX 2.2: DBOM EXPERIENCE (IN MAIN CONTRACTOR ROLE) – PROJECT 1

Name of Applicant:

Each Applicant is to provide the following details for each of the multi-disciplinary (systems and operational) projects listed in the summary – form EX 2.1. Use a separate numbered form for each project. (not more than three (3) projects and which have been completed within the last five (5) years, or which are currently in progress)1. Contract number: 2. Country:3. Contract name: 4. Name of employer:

5. Employer address:

6. Employer contact (Name, Tel & E- Mail):

7. Nature of works and special features relevant to the Project for which the Applicant wishes to emphasize (250 words maximum):

8. Provide the amount of the total contract/subcontract/partner share in equivalent amount ZAR for the project? (Strike through option that is not applicable)

a. Total Contract (ZAR) b. Subcontractor (ZAR) c. Partner Share (ZAR)9. Provide the ZAR exchange rate and name of payment currency10. Date of award: 11. Date of

63


completion:12. Provide a short description of the major sub-system/s that were supplied and managed for this project?

13. Was the total project completed later than originally scheduled? (If yes, provide reasons)

14. Was there any significant software or hardware development required and was this managed and delivered within the project time constraints? (If no, provide details)

15. What were the project management tools employed to support the project?

16. How many of the Applicant’s personnel were involved in this project?

17. Was the project satisfactorily completed? (If “No”, provide brief explanation of the reasons)

64



Name of Applicant:

Each Applicant is to provide the following details for each of the multidisciplinary (systems and operational) projects listed in the summary – form EX 2.1. Use a separate numbered form for each project. (not more than three (3) projects and which have been completed within the last five (5) years, or which are currently in progress)1. Contract number: 2. Country:3. Contract name: 4. Name of employer:





a. Total Contract (ZAR) b. Subcontractor (ZAR) c. Partner Share (ZAR)

65


9. Provide the ZAR exchange rate and name of payment currency

10. Date of award: 11. Date of completion:

12. Provide a short description of the major sub-system/s that were supplied and managed for this project?






66



Name of Applicant:

Each Applicant is to provide the following details for each of the multidisciplinary (systems and operational) projects listed in the summary – form EX 2.1. Use a separate numbered form for each project. (not more than three (3) projects and which have been completed within the last five (5) years, or which are currently in progress)1. Contract number: 2. Country:3. Contract name: 4. Name of employer:





a. Total Contract (ZAR) b. Subcontractor (ZAR) c. Partner Share (ZAR)

9. Provide the ZAR exchange rate and name of payment currency10. Date of award: 11. Date of

67


completion:12. Provide a short description of the major sub-system/s that were supplied and managed for this project?






68


FORM EX 2.5: SYSTEM INTEGRATOR EXPERIENCE – SUMMARY

Name of Applicant:

Each Applicant is to list below up to three (3) relevant projects involving the ITS integration as a System Integrator, which have been completed during the last five (5) years, or which are currently in progress. Note that completion implies that consent has been given to contact the references provided.




4. Completion

Date

5. Duration

The contract value should be based on the payment currencies of the contracts converted into ZAR (at the date of substantial completion, or for ongoing contracts, the exchange rate on the date of the clarification meeting).

Using the format attached (Forms EX 2.6 to EX 2.7), the Applicant is requested to provide details of two (2) of the above projects, on separate sheets.

69


FORM EX 2.6: SYSTEM INTEGRATOR EXPERIENCE – PROJECT 1

Name of Applicant:

Each Applicant is to provide the following details for each of the ITS Integration projects listed in the summary – form EX 2.5. Use a separate numbered form for each project. (not more than three (3) projects and which have been completed within the last five (5) years, or which are currently in progress)1. Contract number: 2. Country:3. Contract name: 4. Name of employer:




8. Provide the amount of the total contract/subcontract/partner share in equivalent amount ZAR

for the project? (Strike through option that is not applicable)


70


completion:12. Provide a short description of the ITS that was supplied for this project, include the different types of field devices?

13. Provide a short description of the major sub-system/s that were supplied and integrated for this project?

14. Provide a short description of the external system interfaces that were provided / established

(excluding the internal interfaces between the supplied sub-systems)?

15. Was the total project completed later than originally planned? (If yes, provide reasons)



18. List any and provide a copy of the test certificate/s completed by the Engineer, Independent Engineer, Test facilitator or any other independent test laboratory for this project, if applicable?a. b.c. d.19. Was the project satisfactorily completed? (If “No”, provide brief explanation of the reasons)

71


FORM EX 2.7: SYSTEM INTEGRATOR EXPERIENCE – PROJECT 2

Name of Applicant:

Each Applicant is to provide the following details for each of the ITS Integration projects listed in the summary – form EX 2.5. Use a separate numbered form for each project. (not more than three (3) projects and which have been completed within the last five (5) years, or which are currently in progress)1. Contract number: 2. Country:3. Contract name: 4. Name of employer:







72


completion:12. Provide a short description of the ITS system that was supplied for this project, include the different types of field devices?








73


FORM EX 2.8: ITS DESIGN EXPERIENCE – SUMMARY

Name of Applicant:

Each Applicant is to list below up to three (3) relevant projects involving ITS design experience, which have been completed during the last five (5) years, or which are currently in progress. Note that completion implies that consent has been given to contact the references provided.




4. Completion

date

5. Duration



74


FORM EX 2.9: ITS DESIGN EXPERIENCE – PROJECT 1

Name of Applicant:

Each Applicant is to provide the following details for each of the ITS design projects listed in the summary – form EX 2.8. Use a separate numbered form for each project. (not more than three (3) projects and which have been completed within the last five (5) years, or which are currently in progress)1. Contract number: 2. Country:3. Contract name: 4. Name of employer:






75


completion:12. Provide a short description of the ITS design for this project?

13. Provide a short description of the engineering discipline involved in the design of this project.

14. Provide a short description of the ITS functional elements included in the design?


76


FORM EX 2.10: ITS DESIGN EXPERIENCE – PROJECT 2

Name of Applicant:

Each Applicant is to provide the following details for each of the ITS design projects listed in the summary – form EX 2.8. Use a separate numbered form for each project. (not more than three (3) projects and which have been completed within the last five (5) years, or which are currently in progress)1. Contract number: 2. Country:3. Contract name: 4. Name of employer:






77


completion:12. Provide a short description of the ITS design for this project?

13. Provide a short description of the engineering disciplined involved in the design of this project.

14. Provide a short description of the ITS functional elements included in the design.


78


FORM EX 2.11: ITS BUILD EXPERIENCE – SUMMARY

Name of Applicant:

Each Applicant is to list below up to three (3) relevant projects involving ITS build experience, which have been completed during the last five (5) years, or which are currently in progress. Note that completion implies that consent has been given to contact the references provided.




4. Completion

date

5. Duration



79


FORM EX 2.12: ITS BUILD EXPERIENCE – PROJECT 1

Name of Applicant:

Each Applicant is to provide the following details for each of the ITS build projects listed in the summary – form EX 2.11. Use a separate numbered form for each project. (not more than three (3) projects and which have been completed within the last five (5) years, or which are currently in progress)1. Contract number: 2. Country:3. Contract name: 4. Name of employer:






80


completion:12. Provide a short description of the ITS that was supplied for this project, which includes the different types of field devices?








81


FORM EX 2.13: ITS BUILD EXPERIENCE – PROJECT 2

Name of Applicant:

Each Applicant is to provide the following details for each of the ITS build projects listed in the summary – form EX 2.11. Use a separate numbered form for each project. (not more than three (3) projects and which have been completed within the last five (5) years, or which are currently in progress)1. Contract number: 2. Country:3. Contract name: 4. Name of employer:







82


completion:12. Provide a short description of the ITS that was supplied for this project, which includes the different types of field devices?


14. Provide a short description of the external system interfaces that were provided / established (excluding the internal interfaces between the supplied sub-systems)?





83


FORM EX 2.14: ITS OPERATING EXPERIENCE – SUMMARY

Name of Applicant:

Each Applicant is to list below up to three (3) relevant projects involving ITS operating experience, which have been completed during the last five (5) years, or which are currently in progress. Note that completion implies that consent has been given to contact the references provided.




4. Completion

date

5. Duration



84


FORM EX 2.15: ITS OPERATING EXPERIENCE – PROJECT 1

Name of Applicant:

Each Applicant is to provide the following details for each of the ITS Operating projects listed in the summary – form EX 2.14. Use a separate numbered form for each project. (not more than three (3) projects and which have been completed within the last five (5) years, or which are currently in progress)1. Contract number: 2. Country:3. Contract name: 4. Name of employer:






85


completion:12. Provide a short description of the operational project.

13. Provide a short description of the operational environment including reference to staff ing levels, hours of operation.

14. List the typical operating procedures used on this project.

15. Describe the required reporting mechanisms for this project.

16. What KPI’s were measured to assess operational performance on this project?

17. What specific skills and level of education were required for this project?

18. Provide details regarding your training program for this project?

19. List the main operating challenges encountered on this project.

86


FORM EX 2.16: ITS OPERATING EXPERIENCE – PROJECT 2

Name of Applicant:

Each Applicant is to provide the following details for each of the ITS Operating projects listed in the summary – form EX 2.14. Use a separate numbered form for each project. (not more than three (3) projects and which have been completed within the last five (5) years, or which are currently in progress)1. Contract number: 2. Country:3. Contract name: 4. Name of employer:







87


completion:12. Provide a short description of the operational project.

13. Provide a short description of the operational environment including reference to staff ing levels, hours of operation.

14. List the typical operating procedures used on this project.


16. What KPI’s were measured to assess operational performance on this project?


18. Provide details regarding your training program for this project?

19. List the main operating challenges encountered on this project.

88


FORM EX 2.17: ITS MAINTENANCE EXPERIENCE – SUMMARY

Name of Applicant:

Each Applicant is to list below up to three (3) relevant projects involving ITS maintenance experience, which have been completed during the last five (5) years, or which are currently in progress. Note that completion implies that consent has been given to contact the references provided.




4. Completion

date

5. Duration



89


FORM EX 2.18: ITS MAINTENANCE EXPERIENCE – PROJECT 1

Name of Applicant:

Each Applicant is to provide the following details for each of the ITS Maintenance projects listed in the summary – form EX 2.17. Use a separate numbered form for each project. (not more than three (3) projects and which have been completed within the last five (5) years, or which are currently in progress)1. Contract number: 2. Country:3. Contract name: 4. Name of employer:







90


completion:12. Provide a short description of the maintenance project.

13. Provide a short description of the maintenance environment including reference to staff ing levels, hours of maintenance.

14. List the typical maintenance procedures used on this project.


16. What KPI’s were measured to assess maintenance performance on this project?


18. Provide details regarding your training program for this project.

19. List the main maintenance challenges encountered on this project.

20. Provide details regarding your maintenance support mechanisms for this project in terms of call response and resolution.

91


FORM EX 2.19: ITS MAINTENANCE EXPERIENCE – PROJECT 2

Name of Applicant:

Each Applicant is to provide the following details for each of the ITS Maintenance projects listed in the summary – form EX 2.17. Use a separate numbered form for each project. (not more than three (3) projects and which have been completed within the last five (5) years, or which are currently in progress)1. Contract number: 2. Country:3. Contract name: 4. Name of employer:


6. Employer contact (Name, tel & e-mail):




92


completion:12. Provide a short description of the maintenance project.

13. Provide a short description of the maintenance environment including reference to staff ing levels, hours of maintenance.

14. List the typical maintenance procedures used on this project.


16. What KPI’s were measured to assess maintenance performance on this project?


18. Provide details regarding your training program for this project.

19. List the main maintenance challenges encountered on this project.

20. Provide details regarding your maintenance support mechanisms for this project in terms of call response and resolution.

93


FORM EX 2.20: PERSONNEL – SUMMARY

Name of Applicant:Each Applicant is to provide the number of full time personnel employed by the Applicant, in the stated categories.

PR

OJE

CT

MA

NA

GE

RS

CO

NTR

AC

TS M

AN

AG

ER

S

SY

STE

M I

NTE

GR

ATI

ON

M

AN

AG

ER

S

SY

STE

M IN

TEG

RA

TIO

N

EN

GIN

EE

RS

MA

INTE

NA

NC

E

EN

GIN

EE

RS

ITS

DE

SIG

N E

NG

INE

ER

S

OP

ER

ATI

ON

S M

AN

AG

ER

S

CO

NS

TRU

CTI

ON

M

AN

AG

ER

S

OTH

ER

PE

RS

ON

NE

L

1. With less than 5 years relevant experience (per category)

2. With more than 5 years but less than 10 years relevant experience (per category)

3. With more than 10 years relevant experience (per category)

94


FORM EX 2.21: EXPERIENCE OF SENIOR PROJECT MANAGER

Name of Applicant:

Each Applicant is to provide details of the proposed project manager for the Project

3. Person’s full names:4. Profession:

5. Name of firm: 6. Nationality:

7. Years with firm: 8. Date of birth:

9. Education:

10. Years experience in similar positions:

11. Short description of key experience (not more than 250 words):

12. Language capability in English, categorized as poor, fair, good or excellent:

a. Speak b. Read c. Write

95


FORM EX 2.22: EXPERIENCE OF CONTRACTS MANAGER

Name of Applicant:





9. Education:





96


FORM EX 2.23: EXPERIENCE OF SYSTEM INTEGRATION MANAGER

Name of Applicant:





9. Education:





97


FORM EX 2.24: EXPERIENCE OF MAINTENANCE ENGINEER

Name of Applicant:





9. Education:





98


FORM EX 2.25: EXPERIENCE OF ITS DESIGN ENGINEER

Name of Applicant:





9. Education:





99


FORM EX 2.26: EXPERIENCE OF OPERATIONS MANAGER

Name of Applicant:





9. Education:





100


FORM EX 2.27: EXPERIENCE OF CONSTRUCTION MANAGER

Name of Applicant:





9. Education:





101


E. PROGRAMME INFORMATION (SCHEDULE)

102


FORM P 2.1: PROGRAMME INFORMATION (SCHEDULE)Name of Applicant:

Each Applicant shall provide short and concise answers to the following questions This information must relate to any two of your projects listed previously reflecting your experience:

Project 1:1. ITS scoping:

a. Project definition phase Months

b. Field device procurement Months

c. ITS Back offices procurement or development Months

d. Installation and integration Months

e. Testing and commissioning Months

f. Operations Training Months

g. System dry run Months

Total period MonthsProject 2:1. ITS scoping:

a. Project definition phase Months

b. Field device procurement Months

c. ITS Back offices procurement or development Months

d. Installation and integration Months

e. Testing and commissioning Months

f. Operations Training Months

g. System dry run Months

Total period Months

103


F. DATA, INFORMATION & SPECIFICATIONS

104


FORM D 2.1: SYSTEM INTEGRATION

Name of Applicant:

Each Applicant shall provide short and concise answers to the following questions:

1. How long have you been involved in the System Integration of large IT or ITS type projects with complex electronic interfaces?

2. Provide the total number of ITS contracts that you have integrated in the last five and the last ten years respectively?

a. last 5 years b. last 10 years

3. What are your perceived major integration risks for undertaking this project in South Africa?

4. Can you analyse potential failure modes of an ITS to identify the effect of such failure, known as Failure Mode and Effects Analysis (FMEA) (yes/no)?

5. Have you ever completed a Failure Mode and Effects Analysis (FMEA) (yes/no)?

6. Further to this, can you undertake a Failure Mode, Effects, and Criticality Analysis (FMECA) of an ITS, of which the goal is to identify and eliminate failure modes with a high severity and high probability (yes/no)?

7. Have you ever completed a Failure Mode, Effects, and Criticality Analysis (FMECA) (yes/no)?

8. Do you execute projects to a formalized system engineering process (yes/no)?

9. If yes, is this document available on request (yes/no)?

105


G. CERTIFICATES AND SUPPORTING INFORMATION

106


FORM S 2.1: LIST OF SUPPORTING DOCUMENTATION

Name of Applicant:

Each Applicant shall list all the supporting documents and certificates that has been included in this Pre-qualification package:

a. Document name

b.Document description

c. Pages