Requirement Specification General

Transcription

1 Requirement Specification General National and uniform replacement "Landelijk en uniform vervangen (LUV)" of the radar target tracking system "Radardoelvolg-keten" as part of Vessel Traffic Services (VTS systems) in the management area of Rijkswaterstaat, the Public Works and Water Management Department, including support and maintenance. Case number: Date: 3 June 2016

2 Imprint Contracting Authority (Principal) Project Compiled by Ministry of Infrastructure and the Environment, Rijkswaterstaat Information Supply "Ministerie van Infrastructuur en Milieu, Rijkswaterstaat Centrale Informatievoorziening" National, uniform and future-proof replacement of VTS "Landelijk, uniform and toekomstvast vervangen van VTS" Project team LUV-VTS Date 3 June 2016 Status Final Version number 1

3 Contents 1 Layout Requirement specification Purpose of the Requirement Specification General Document structure of the Requirement Specification 6 2 Mission and objectives Principal Mission Objectives 7 3 Starting points of the agreement Spirit of the agreement Basic principles of the agreement The agreement Relation Principal Contractor 10 4 Essence of the Contract The current scope and future-proof Current situation Scope Marine traffic station Wadden Sea (Terschelling and Schiermonnikoog) Traffic station Wemeldinge Traffic station Nijmegen Traffic station Drechtsteden For the time being, the following aspects do not come within the scope of this contract: Future-proof I-strategy Implementation plan Maritime traffic management Optional Traffic Station Tiel Management and maintenance 15 5 Contract form, including control 17 6 Definitions and abbreviations Definitions Glossary 19 RWS Company information Page 3 of 20

4

5 1 Layout Requirement specification 1.1 Purpose of the Requirement Specification General The Requirement Specification General is part of the document structure referred to at 1.2, with case number , and involves the National and Uniform Replacement "Landelijk and Uniform Vervangen - LUV" and the management and maintenance of the Radar Target Tracking system "Radardoelvolg-keten", including registration and logging, as part of Vessel Traffic Services (VTS systems) along the main waterways network (HVWN) in the management area of Rijkswaterstaat (RWS). The scope involves the first tranche of RDV chains at the traffic stations at Wemeldinge, Nijmegen, Drechtsteden and Wadden Sea (Terschelling and Schiermonnikoog). The contract will offer possibilities to connect the other traffic stations as well. In addition to replacement and management and maintenance of the RDV chain, this Requirement Specification General also covers the other activities listed below: Integrating the RDV system with the Hydro/Meteo and the existing chains AIS / Diamonis, IVS Next, VHF and CCTV (video images); Monitoring of and informing about state and availability of the RDV chain, Hydro/Meteo chain and the existing chains; Principal envisages the following optional additions: o Realising functional additions, update and upgrade work on the above chains; o Management and maintenance, including: The Hydro / Meteo chain; The other change, including: VHF and video images (CCTV). The Requirement Specification General describes the principal's requirements with regard to replacement, management and maintenance, the other work and the work processes that Principal considers at least necessary for a controlled realisation of replacement, management and maintenance, and other work. RWS Company information Page 5 of 20

6 Requirement Specification General Case number May Document structure of the Requirement Specification The Requirement Specification is composed of three parts with schedules: (model) Agreement Requirement Specification Requirement Specification General Schedules Requirement Specification Technical Requirement Specification Process Requirement Specification General. This part describes the essence and scope of the contract and the layout of the contract documents, the starting points for the agreement, for the Contractor. In addition, it contains definitions and concepts; Requirement Specification Requirements: The Requirement Specification Requirements have been drawn up in accordance with the System Engineering (SE) method. This part describes the requirements that the replacement, management and maintenance, and other work have to satisfy; Requirement Specification Process: This part describes the requirements that replacement, management and maintenance, and other work have to satisfy and must be incorporated in the Contractor's project-specific quality system; Schedules: The schedules are an integrated part of the Requirement Specification and contain, among other things, the region-specific data. To sum up, this document refers to the Requirement Specification General as part of the total Requirement Specification. The other documents referring to the RDV system Requirement Specification Requirements Technical, Requirement Specification Process and Schedules will be published at a later date. Page 6 of 20 RWS Company information

7 2 Mission and objectives Principal 2.1 Mission RWS is the executive agency that is commissioned by the Minister and Secretary of State for Infrastructure and the Environment to manage and develop the infrastructure networks to ensure that they optimally satisfy the public demand. RWS implements this by ensuring: 1. Dry feet 2. Sufficient and clean water 3. Safe and smooth traffic by roads and waterways 4. Reliable and practical information In doing so, RWS wants to be viewed as: 1. Public-oriented Network Manager 2. Leading Principal 3. Decisive Crisis Manager 2.2 Objectives Principal's aims under the agreement and the requirements contained in the Requirement Specification are as follows. Aim 1: Replacing the chain Replacing the RDV system and carrying out the other work in the traffic stations at Wemeldinge, Nijmegen, Drechtsteden and Wadden Sea (Terschelling and Schiermonnikoog). Aim 2: Management and maintenance of the RDV chain, including registration and logging, within the pre-set requirements indicated in the Requirement Specification Requirements and Process. Optionally, management and maintenance of the other chains (VHF, CCTV and Hydro/Meteo). Aim 3: Other work Integrating the RDV system with the other chains aimed at: 1. Realising an integrated traffic image suitable for traffic guidance. 2. Monitoring the state of the various chains on behalf of management and maintenance and realising functional additions (updates and upgrades) for the chains covered by this Requirement Specification General. Aim 4: Preserving an acceptable maintenance level Management and maintenance of the chains must be carried out in such a way that it satisfies the defined requirements, guarantees the safety of people and environment, and makes the use of the Waterways Network a comfortable experience for the user. Aim 5: Minimum nuisance / maximum fluidity Management and maintenance of the chain and, optionally, the other chains, must be realised in such a manner that the performance of the chain or chains is not affected, with the aim that the system adequately supports the traffic managers in the performance of their traffic guidance tasks (VTS services). This contributes to the realisation of the RWS aim of safe and smooth vessel traffic flows. Aim 6: Public-oriented operations Management and maintenance of the chain or chains must allow for the wishes of the public and the users of roads and waterways. RWS Company information Page 7 of 20

8 Requirement Specification General Case number May 2016 Aim 7: Sustainability Management and maintenance of the chain or chains must take place in such a manner that the environment will not be affected, or if inevitable, as little as possible. Aim 8: Integral safety Integral safety refers to managing all relevant safety aspects in one or more chains in mutual relation. The aim is to manage the risks that may occur in replacement, management and maintenance, and other work. Aim 9: Preservation ecological values Management and maintenance of the chain or chains must be carried out in such a manner that natural values in verges, riverbanks and other green areas and water bodies are preserved and, where possible, promoted. Disturbances of flora and fauna due to activities will be avoided wherever possible. Contractor is expected to be able to demonstrate at all times that the works Contractor is carrying out to comply with the obligations under the agreement contribute to the aims listed above. Page 8 of 20 RWS Company information

9 3 Starting points of the agreement 3.1 Spirit of the agreement The agreement covers the replacement, management and maintenance, carrying out other work, monitoring of and informing about - the state of - the Functioning and Performance of the chain or chains. It is expected of Contractor that carrying out management and maintenance will result in preservation and, if agreed, improvement of the functionality and performance of the chain or chains. It is also expected of Contractor to identify, optimise and realise the necessary activities and to verify, analyse and improve the results of those. In the framework of the agreement, Contractor is also expected to carry out the activities in such a manner that those make a maximum contribution to the mission and objectives of Principal, among other things by: 1. Clearly observing due care on identifying and carrying out the activities and, if necessary in consultation with Principal, making proposals for improvements and/or investments during the performance of the agreement; 2. Operating public-oriented while maximising the safety, the availability and the reliability of the functions and the Functioning and Performance of the chains; 3. Broadening the scope of Contractor's task by complementing the performance of management and maintenance by maintenance management and risk management in order to promote sustainability and life-cycle management; 4. Managing the data required for the Functioning and Performance of the chains in such a manner that both Contractor and Principal have available a substantiated, real-time, reliable and usable overview of the condition of the chains; 5. Making data available to Principal and supplying information on the development and condition of the chains, to enable Principal to manage the Functioning and Performance of the chains in a controlled manner, to update maintenance strategies, to determine or have determined the connected required investments and to adjust or have adjusted the schedule of already prognosticated investments. 3.2 Basic principles of the agreement The agreement Principal desires to manage the chains in an effective, efficient and user-friendly manner. Principal manages the chains, among other things, by identifying and prioritising the risks of loss of Functioning and Performance of the chains (in the long run) and subsequently defining programming measures to control these risks. The choices with regard to the measures to be taken constitute the management regime. The management regime may be aimed at continuously maintaining a certain preservation level in order to already warrant the Functioning and Performance of the chains as a matter of routine for an indefinite period. The management regime may also be aimed at, while preserving the Functioning and Performance of the chains, letting the maintenance level develop in a controlled manner as far as a certain lower limit in combination with a plannable, variable upgrade of the maintenance level. RWS Company information Page 9 of 20

10 Requirement Specification General Case number May 2016 The activities pursuant to the agreement aim at: 1. Warranting the Functioning and Performance of the chains; 2. Monitoring and managing the development of risks with regard to Functioning and Performance of the chains; 3. Informing Principal on the Functioning and Performance of the chains and the development of the Functioning and Performance of the chains and the connected risks as well as to warrant this in management systems; 4. Carrying out any other activities on instruction. The agreement offers Contractor maximum freedom in the manner of organisation and realisation of the activities. Contractor must integrate its own processes and the processes resulting from the requirements of the agreement in a Project Management Plan (PMP) Relation Principal Contractor The agreement assumes equivalence between Contractor and the Principal and focuses on positive cooperation between the parties, while taking into account each other's interests and objectives. Page 10 of 20 RWS Company information

11 4 Essence of the Contract 4.1 The current scope and future-proof Services VTS VTS is a service with a legal basis that is delivered by RWS from regional traffic stations to vessels and that contributes to a safe and smooth flow of maritime traffic on our waterways. The performance of traffic control requires the presentation of a current traffic image combined with sufficient supporting information that enables the traffic manager to adequately perform his task. On the basis of international recommendations and national frameworks, the traffic and water management authority "Verkeer and Watermanagement (VWM)" has defined the functional and quality requirements that the RDV system must satisfy to implement the VTS services for the purpose of safe and smooth maritime traffic Current situation In the current situation, the services are regionally oriented while a national and corridor-geared service does not yet exist, and every traffic station has its own VTS system. In addition to the differences in services, the chains and their operation also differ. The chains, hardware and software, do not have a national and uniform basis which makes management and maintenance of the chains complicated. 4.2 Scope The national, uniform and future-proof replacement of the RDV chain, including management and maintenance for a period of 10 years with an option of 5 times an annual renewal up to a period of 15 years. This document now refers to the first tranche of RDV chains, located at the traffic stations at Wemeldinge, Drechtsteden, Nijmegen, and Wadden Sea (Terschelling and Schiermonnikoog). The contract will offer possibilities to connect the other traffic stations as well. In addition to replacement and management and maintenance of the RDV chains, the contract also comprises other work: Integrating the Hydro/Meteo chain (still to be procured) and integrating the existing chains: Diamonis, IVS Next, VHF and CCTV (video images) in the RDV chain; Monitoring of and informing about state and availability of the RDV chain, the Hydro/Meteo chains, and the existing chains; Presentation and operation at the workstation using screens and control elements for, among other things, RDV, VHF and CCTV; Integration of the RDV system with existing sensors, workstations (presentation and operation) and other chains, including: AIS/Diamonis, IVS-Next and Hydro/Meteo; Registration and logging (of radar images, VHF, telephone and Hydro/Meteo information); Monitoring & Facilities chain (for reporting malfunctions and the like at the workstation); Project Supervision & Implementation (including communication, training, testing and roll-out plan, etc.); Management and maintenance, including maintenance for the radar sensors to be replaced (in so far as these must be replaced); RWS Company information Page 11 of 20

12 Requirement Specification General Case number May 2016 Principal envisages the following optional additions: o Realising functional additions, update and upgrade work on the above chains; (RDV, CCTV, Hydro/Meteo and VHF); o Management and maintenance, including: The Hydro / Meteo chain; The other chains, including: VHF and video images (CCTV). The scope has been detailed for every site and includes the following replacements Marine traffic station Wadden Sea (Terschelling and Schiermonnikoog) Replacement of the RDV system with integration of 4 existing radar sensors; Presenting the integrated traffic image on the workstations to be replaced for guidance purposes. Integrated traffic image is inclusive of AIS, RDF, VHF, CCTV, IVS90/IVS Next and Hydro/Meteo information; Integrating the KA workstation; Integrating AIS information received from the coastguard "Kustwacht"; Integrating information received from the RDF; Integrating traffic information received from IVS90/IVS Next; Realising the registration and logging chain for registering and logging of the integrated traffic image; If applicable for objects, such as object access and security and nautical lighting Traffic station Wemeldinge Replacement of the RDV system with integration of 8 existing radar sensors; Presenting the integrated traffic image on the workstations to be replaced for control purposes. Integrated traffic image is inclusive of AIS, VHF, CCTV, IVS90/IVS Next and Hydro/Meteo information; Integrating the KA workstation; Integrating AIS received from Diamonis; Integrating traffic information received from IVS Next; Realising the registration and logging chain for registering and logging of the integrated traffic image; If applicable for objects, such as object access and security and nautical lighting Traffic station Nijmegen Replacement of the RDV system with integration of 12 existing radar sensors and replacement of 2 radar sensors; Presenting the integrated traffic image on the workstations to be replaced for guidance purposes. Integrated traffic image is inclusive of AIS, VHF, CCTV, IVS90/IVS Next and Hydro/Meteo information; Integrating the KA workstation; Integrating AIS received from Diamonis; Integrating traffic information received from IVS Next; Realising the registration and logging chain for registering and logging of the integrated traffic image; If applicable for objects, such as object access and security and nautical lighting Traffic station Drechtsteden Replacement of the RDV system with integration of 14 existing radar sensors and replacement of 4 radar sensors; Page 12 of 20 RWS Company information

13 Presenting the integrated traffic image on the workstations to be replaced for control purposes. Integrated traffic image is inclusive of AIS, VHF, CCTV, IVS90/IVS Next and Hydro/Meteo information; Integrating the KA workstation; Integrating AIS received from Diamonis; Integrating traffic information received from IVS Next; Realising a registration and logging chain for registering and logging of the integrated traffic image; If applicable for objects, such as object access and security and nautical lighting; Additions possible during this contract: Replacement and maintenance of the buildings, the connected building-specific installations, networks, the vertical structures housing the VTS systems and the unmanned radar posts (ORP) to be replaced and management and maintenance of the current VTS systems. Replacement of the current data connections for current and future systems. Though the VHF chain does constitute an integrated part of the VTS system, its replacement remains outside the scope of this contract. System integration comes under the direction of RWS. The national department central information supply "Centrale Informatievoorziening (CIV)" is responsible for and coordinates system integration of the various technical chains and interfaces. Contractor is responsible for system integration in Contractor's own chain. 4.3 Future-proof In addition to national and uniform procurement, future-proof procurement will also be part of the project. Relevant for implementation of future-proof are mainly the strategy plan "I-strategy' and the implementation plan maritime traffic management "Uitvoeringsplan Scheepvaartverkeersmanagement" For this first tranche this means the first step to enable centralisation of traffic management for the corridor Rotterdam - Germany, including renewed roles and unified workstations referred to as operational operating and guiding station "(Operationele Rijkswaterstaat Bedienand Begeleidingsplek (ORBB))" I-strategy RWS increasingly focuses on standardisation and unification of IV infrastructure (Istrategy). This is realised by using prescribed architecture and standardised generic building blocks wherever possible. In addition, the computer centres of the national government are used in so far as possible. That optimally centralises and unifies the hardware and software systems and management and maintenance can be set up in a more efficient way. The essence of the I-strategy is: Optimum application of an RWS Company information Page 13 of 20

14 Requirement Specification General Case number May 2016 'open' architecture and generic and reusable building blocks aimed at maximum unification of the IV infrastructure to set up management and maintenance in an effective and efficient manner. It is being investigated further whether a first step can be made in the application of generic building blocks, including: Operational RWS operating and management workstation (ORBB)', RDV system and generic radar sensors, linked (through the RWS network) and integrated in the RDV chain Implementation plan Maritime traffic management RWS focuses on the further improvement of services for shipping and an even more efficient set-up of the organisation and the maritime traffic management process. This means that the waterways network must be utilised optimally and corridororiented and that the traffic management tasks must be performed even more efficiently and as uniformly as possible. Realising this objective requires that the workstations are equipped nationally and uniformly. Corridor-oriented operation and guidance "Bediening en Begeleiding (CBB)" will contribute to making shipping a suitable and reliable transport modality for the complete logistic chain. The objective is to develop the current regional services into a more national and corridor-oriented service (operation and guidance). That will make the services more efficient and more focused on maximum utilisation of the waterway network and improve traffic flow. Waterway users will get optimum support with reliable and maximally up-to-date traffic information necessary for a safe and smooth traffic flow and efficiently completing the entire shipping trip, combined with an increased reliability of the expected passage, travel and arrival times. In the near or later future, CBB must make centralised operations possible, including the possibility to take over traffic management areas (routing of traffic images) as backup of a relevant traffic station Optional Traffic Station Tiel If Principal opts for implementing CBB, management and maintenance of traffic station Tiel also becomes optional and possibly part of future-proof and this scope. This involves the following replacements: Replacing the RDV system with integration of seven existing radar sensors and optionally incorporating one new radar sensor; Presenting the integrated traffic image at the workstations to be replaced by uniformed workstations (ORBB) for traffic management. The integrated traffic image includes Diamonis, VHF, CCTV, IVS Next and Hydro/Meteo information; Integrating the KA workstation; Integrating AIS received from Diamonis; Integrating traffic information received from IVS Next; Realising a registration and logging system for registering and logging of the integrated traffic image; If applicable for objects, such as object access and security and nautical lighting. Page 14 of 20 RWS Company information

15 4.4 Management and maintenance Contractor must manage and maintain the state of Functioning and Performance as found in the chains as well as the reported risks and intervention moments. Acts or failure to act on the part of Contractor must not affect the state of Functioning and Performance of the chains as found or let it drop below the required maintenance level before the stated intervention moment. In addition, acts or failure to act on the part of Contractor may also not increase the reported risks or make planned maintenance interventions (measures) required earlier than before. In order to realise the above, Contractor must bring the activities pursuant to the agreement under the operation of Contractor's quality system. Through the realisation of Maintenance Activities, Contractor must: 1. maintain the Functioning and Performance of the chains on the basis of the requirements contained in the agreement; 2. maintain the required preservation level on the basis of the requirements contained in the agreement; 3. monitor and maintain the (quality) development of the risks and maintenance interventions (measures) reported by the Principal with the connected schedule in such a way that these risks do not increase and the intervention moments are not required earlier than indicated in the schedule; 4. timely inform Principal of modifications in the risks or development of those in the Functioning and Performance of the chains, in so far as this follows logically from the scope of the agreement. In its operations, Principal uses widely adopted standards and/or best practices. That also applies to the Principal's work processes. These work processes are mainly based on BiSL, ASL2 and ITIL. Principal distinguishes four management types: 1. Functional management (BiSL) Part of Functional Management under BiSL is, among other things, initiating modifications and management of company information. With regard to the latter, for Systems a distinction is made between organisation-wide date used for more than just the RDV systems. To identify the distinction, the terms reference data and configuration data are used. Management of configuration data comes under Functional Management in this Requirement Specification. Management of reference data comes under separate Data Management. 2. Data Management Data management is defined as the management of reference data. 3. Application Management (ASL 2) This management is defined as adjusting the Systems on the basis of faults found or changing technical or functional requirements. 'This expressly refers to existing Systems and not to new developments. ASL2 is the standard in this respect. This refers to (executive) application management. Application management complies with ASL and takes into account the interfaces with technical management and functional management. In addition, application management must link up with data management. 4. Technical Management (ITIL) Technical management aims at management of the IT infrastructure and uses ITIL as standard. The IT infrastructure is the basis on which the Systems are running. RWS Company information Page 15 of 20

16 Requirement Specification General Case number May 2016 Configuration management of this basis as well as installation of the Systems on this basis is part of technical management. Page 16 of 20 RWS Company information

17 5 Contract form, including control Contract form The scope is covered by the general national conditions for IT agreements "Algemene Rijksvoorwaarden bij IT overeenkomsten" ARBIT On the basis of these general conditions, within the format of the model agreement ARBIT 2014 an agreement will be drawn up, specifically geared to replacing the RDV chain, management and maintenance, and other work, including integration of the other chains. Contract control In accordance with the RWS policy, contract control will be based on the internal quality system of Contractor, geared to the specific nature of this project. Primary purpose is that contract control is effective and efficient. Additional purpose is, that contract control based on the internal arrangements can be used to demonstrate the legitimacy of payment. An important aspect of this type of contract control under SCB is, that at all times Contractor demonstrates that the defined requirements, preconditions and interfaces are complied with. That means verification and validation is an important process of the Contractor. Of course there will be explicit attention for these processes on risk-controlled auditing. Quality management system Contractor must use a quality management system that complies with the standards NEN-EN-ISO 9001 and apply these to the performance of the contract. Every quality management system is acceptable, as long as it complies with the requirements laid down in the NEN-ISO standard. Project stages and schedule In outline, the project is divided into the following stages: Specification state, tendering and award stage, execution stage (preparation, roll-out and follow-up) of the 1st tranche VTS systems; Parallel to these points, drawing up a management and maintenance vision and subsequently setting it up. RWS Company information Page 17 of 20

18 Requirement Specification General Case number May 2016 The table below shows the critical path based on the Project Planning Infrastructure (PPI) schedule and contains the following activities and connected milestones. Activity Milestone Requirement Specifications RDV version 1.0 (VSA and VSE) Q Tender RDV chain, including PoA (PoA Q1 - Q3 2017) Q Requirement Specifications RDV version 2.0 (VSE + implementation futureproof) Q Final award RDV chain Q Preparations for roll-out Q Start national roll-out Q Completion national roll-out Q Start national management and maintenance Q End national management and maintenance Q Page 18 of 20 RWS Company information

19 6 Definitions and abbreviations 6.1 Definitions In the following Definitions, the connected meaning is attached to the following words written with a capital in the Requirement Specification: 1. Functioning: demonstrable compliance of a product or service with the intended operation or act expected from it. 2. Performance: achieving that the intended operation or act of a product or service up to the moment of intervention is warranted. 6.2 Glossary Parties attach the connected meaning to the following words used in the Requirement Specification (without capital). 1. Management and maintenance: Functioning and Performance of the chains to be maintained during the service life in an efficient manner, including the prevention of faults and remedying faults. 2. Corridor-geared Operation and Guidance: the current, primarily locally oriented services to be developed into a more corridor-oriented operation and Traffic guidance. The services will become more efficient and more geared for optimum utilisation of the total waterways network and improved flow. Corridor-oriented Operation and Management will contribute to making shipping a suitable and reliable transport modality for the complete logistic chain. 3. Due care: ensuring to the best of one's ability and in all reasonableness that the entire condition of an object, a building and/or of installations complies with the generally accepted performance level. 4. Integral safety: Integral safety refers to managing all relevant safety aspects in one or more chains in mutual relation. The aim is to manage the risks that may occur in replacement, management and maintenance, and other work. 5. Chain: A logical sequence of functional components that enable collection, processing and presenting of information. In the case of the RDV chain, this includes the sensor, processing and presenting and operating layer. 6. Chains: A logical sequence of functional chains which together form an integrated system. In this case the VTS system. 7. Quality requirements: The IALA VTS Guidelines and de inland VTS (Vessel Traffic Services) guidelines describe the starting points and provisions on shore and on board necessary for traffic guidance at sea, in ports and on inland waterways. The inland VTS guidelines are based on the IALA VTS guidelines and they are in line with chapter 5 of the SOLAS (Safety of Life at Sea) convention of the IMO (International Maritime Organization). Authorities that intend to introduce traffic guidance or have implemented traffic guidance, must comply with the IALA VTS Guidelines or the Inland VTS guidelines respectively. 8. Other work: miscellaneous activities with the aim of integrating the RDV system with the other chains to realise and maintain an integrated traffic image suitable for traffic guidance. Monitoring the state of the various chains on behalf of preventive and corrective maintenance and realising functional additions (updates and upgrades) for the chains covered by the Requirement Specification. 9. System or systems: a collection of coordinated, but independent components, each of which have a function in achieving a common goal. 10. System Engineering: SE decomposes and describes the design in a structured manner. 11. Future-proof and I-strategy: Implementation plan. Maritime traffic management By commission of the board, VWM developed a vision Maritime traffic management (SVM) 2025, in close cooperation with most of the RWS divisions involved. This vision has been detailed in an RWS Company information Page 19 of 20

20 Requirement Specification General Case number May 2016 implementation plan with measures covering areas such as traffic guidance, object control, incident management and enforcement. I-strategy: RWS increasingly focuses on standardisation and unification of IV infrastructure This is realised by using prescribed architecture with generic and reusable building blocks wherever possible. That optimally unifies the hardware and software systems and management and maintenance can be set up in a more efficient way in the long run. Page 20 of 20 RWS Company information