Tender AVMS GVB Amsterdam 20 7 2018 Program

Tender AVMS GVB, Amsterdam, 20 -7 -2018

Program Item Who Role Kick off / introduction Kaspar Guffens Purchasing Program EBS Renewal Remko Zuidgeest Program manager GIVA Introduction Dirk Blaauw Architect GIVA demonstration Wim Dujardin GIVA Consultant GIVA & AVMS Dirk Blaauw Architect Q&A 2

Kick off / introduction Kaspar Guffens 3

Program EBS (=AVMS) Renewal EBS = Exploitatie Beheer System (GVB-language) AVMS = Automated Vehicle Management System Remko Zuidgeest 4

Program EBS (=AVMS) Renewal £ Project 1: EBS Central (upgrade central AVMS software) £ Project 2: EBS Vehicle (new AVMS functionality bus & tram) This Tender is part of Project 2: AVMS Vehicle functionality: 1. New AVMS functionality (software). The new AVMS Software will run on the GIVA Services platform 2. Building new GIVA Platform(hardware & software) 3. Phasing out old hardware (like RIS Computer / MVB etc) 5

Program organization Programmanager AVMS Renewal Projectmanagement Office Soundingboard Projectmanager AVMS Central Product owner GIVA Services Product owner EBS / AVMS Vehicle Projectmanager MVB/ RIS unbundling Projectmanager(s) Rail & Bus (garage) Team Team Supplier: PSI Matrix Mind Supplier: Ximedes Supplier: THIS TENDER Supplier: Tbd (by Tender) Supplier: Ntb. AVMS Vehicle 6

High level product breakdown AVMS Vehicle

GIVA introduction Dirk Blaauw 8

GIVA introduction £ GIVA background £ General vehicle structure £ Service & applications 9 9

GIVA background – what is it £ Hardware l Network based l Generic components ‘off the shelf’ l Functional separation £ Software l (Micro)services l European standards - EN 13149 part 7/8 = IP based data communication - ITx. PT + VDV 301 = services specification § VDV 301 = IBIS-IP German initiative § ITx. PT European initiative 10

GIVA background – goal £ Vendor independency l Clearly defined services and interfaces l European standardisation £ Flexibility l Small (micro) services with limited functionality l Information readily available for any consumer 11

General vehicle structure £ Information domain l Central computer(s) - GIVA services and applications (e. g. RIV) l Equipment - Management service / SNMP monitoring interface - Functional services to provide data (if necessary) - Subscription to GIVA services. £ Vehicle domain - Vehicle. Information service as single point of access - Subscription to GIVA service where necessary 12

Services & applications £ Base platform l System. Mgt, System. Doc, Device. Mgt, Time [VDV 301 based] £ Operation l AVMS, Ne. Tex, Spatial, VKLgateway, Sign. In. £ Migration (for current fleet) l Vehicle. Gateway (IBIS, digital I/O, tacho, MVB) l OVCP gateway, Passenger Counting gateway 13

Services & applications 14

GIVA Demonstration Wim Dujardin 15

AVMS Tender Dirk Blaauw 16

AVMS tender £ AVMS functionality and context £ Dependencies £ Supplier activities £ Support & maintenance 17

AVMS functionality £ AVMS application l Providing AVMS services according to ITx. PT l Receiving information from GIVA services l No other interfaces £ AVMS functionality l Journey selection l Vehicle localization inc. on/off route l Logical position determination (stops, progress) l Deviation determination / expected arrival and departure time l Journey management by central traffic control and/or driver. 18

AVMS context 19

Dependencies £ GIVA platform development l GIVA base platform is operational l Base platform extension is under development £ 15 G tram delivery l Start operational tests November 2018 l Limited functionality required 20

Supplier activities £ Software development l Sprint planning / determination with GVB l Design meetings / reviews with GVB l Coordination with GIVA extension project (directly or indirectly) £ Software testing l Test plans, scripts review GVB l Using own stubs/simulators ór l Using available GIVA tools - Provide/coordinate testpatterns l Functionality, stability, performance, resource usage. 21

Supplier activities £ GIVA integration testing l Test plans, scripts review GVB. l Provide/coordinate testpatterns for GIVA tools. l Optionally using recorded vehicle operation / journeys £ Vehicle integration testing l Focused on actual vehicle behavior (event timing, on/off) and stability l Test plans, scripts review GVB. 22

Support & maintenance £ Framework agreement for l Further development, e. g. - Improved vehicle tracking - Dynamic driving times depending on tourist season, weather - Etc. l Software maintenance l Management of these activities 23

Questions 24