Search
  • Search


Finland: Tenders/Helsingin seudun liikenne -kuntayhtymä/Invitation for market dialog: solution for driver terminal as part of HSL information system
  1. Planning notice published

    Feb 13, 2025 11:50 AMFebruary 13, 2025 11:50 AM

Brief

Invitation for market dialog: solution for driver terminal as part of HSL information system

Planned

The competition has not been announced yet.

Deadline
Feb 12, 2025Expired
Agreement
Buying services

Brief

Helsinki Region Transport, HSL in short, is a joint local authority whose member municipalities include Helsinki, Espoo, Vantaa, Kauniainen, Kerava, Sipoo, Tuusula, Kirkkonummi and Siuntio. HSL procures bus, tram, metro, ferry, and commuter train services and is responsible for public transport marketing and passenger information. The new driver terminal solution will be implemented in all HSL buses, trams, metros and commuter trains: 1300 buses, 200 trams, 80 trains and 50 metros. Values are approximate and subject to change if HSL traffic increases. The bus traffic and train traffic are procured publicly from private operators. Metro and tram traffic is due to be publicly procured in the future but is currently operated by Helsinki City Transport Ltd. The current HSL information system has been provided and integrated by an overall supplier and is already a modular entirety, thus aiming towards a system migration in phases is probable choice of plan for the future. The current system is based on FARA vehicle configuration, Hogia PubTrans backend system and Mattersoft (part of INIT) operation monitoring and management software (OMM) and traffic light priority planning and management software (JLVEP). System components are integrated to each other with IBM ESB platform and most of the components are running on physical servers. The intent of this invitation is to give participants an opportunity to present and discuss their solutions, one scenario being for example a proprietary software implemented as an Android/iOS application or a web application. The application will use onboard ITxPT services and possible other onboard services. The application may use also microservices offered from Azure cloud. Here is a list of possible minimum set of applications in the driver terminal (MVP approach; not necessarily limited to these): 1. Vehicle assignment application: Provide a view to assign vehicle to a block and to a vehicle journey. 2. Vehicle progress application: Display route pattern and geometry. Display vehicle position on route pattern. Display schematic view for driver. 3. Driving aid application: Inform regulated timing point. Deviation route information. 4. Notices and messages application: Provide disruption notices browsing and reading view. 5. Driver terminal frame: Display official date and time. Produce audio notification. Display disruption notice indicator. 6. Outer display control application: “Bus full” -button in driver terminal. Vehicle environment provides additional services for the driver terminal including vehicle computer with built in 5G and GNSS capabilities (router). The vehicle computer also provides a x64 Debian based Docker environment for driver terminal software which is required to be used in rail transport modes and is optionally available for buses. All specialized IO is available in the vehicle computer (serial ports, CAN connection etc.). Buses have FMStoIP available for driver terminal. The purpose of the driver terminal procurement is to procure mostly software, and that the provider will use HSL hardware platform for the solution. It is possible that the driver display hardware is part of this procurement, but this is something that will be discussed within the technical discussions. However, the solution should be such that it is able to run on any given hardware, for example integrated touchscreen display as it is in the trams currently. The main idea behind this vehicle solution is that HSL will provide information of the current situation and the interfaces, and that the provider will give solution. HSL prefers not to specify the solution too much and thus find a mostly ready-made solution that fits the HSL's needs. We want to avoid technical tailoring, in other words, build to suit to our needs. Mostly the solutions should include all the tools for the driver to be able to do all the necessary actions to drive the route and the assistance for the driving. So, we want to discuss with providers to find the most suitable solution for our needs, including an open competition for tendering.

Datamaskinhandel og tilhørende utstyr

Register interest in Tarjouspalvelu

Custom Assessment Criteria

  • Get answers to your bid/no-bid criteria

    Set them up once and Cobrief answers them in every tender

Will you bid?

The agent sets up the bid and writes the first draft. Free for 14 days.

Previous winners

  • Who are you up against?

    The suppliers who have won similar contracts at Helsingin seudun liikenne -kuntayhtymä

From the notice

  • Helsinki Region Transport, HSL in short, is a joint local authority whose member municipalities include Helsinki, Espoo, Vantaa, Kauniainen, Kerava, Sipoo, Tuusula, Kirkkonummi and Siuntio. HSL procures bus, tram, metro, ferry, and commuter train services and is responsible for public transport marketing and passenger information. The new driver terminal solution will be implemented in all HSL buses, trams, metros and commuter trains: 1300 buses, 200 trams, 80 trains and 50 metros. Values are approximate and subject to change if HSL traffic increases. The bus traffic and train traffic are procured publicly from private operators. Metro and tram traffic is due to be publicly procured in the future but is currently operated by Helsinki City Transport Ltd. The current HSL information system has been provided and integrated by an overall supplier and is already a modular entirety, thus aiming towards a system migration in phases is probable choice of plan for the future. The current system is based on FARA vehicle configuration, Hogia PubTrans backend system and Mattersoft (part of INIT) operation monitoring and management software (OMM) and traffic light priority planning and management software (JLVEP). System components are integrated to each other with IBM ESB platform and most of the components are running on physical servers. The intent of this invitation is to give participants an opportunity to present and discuss their solutions, one scenario being for example a proprietary software implemented as an Android/iOS application or a web application. The application will use onboard ITxPT services and possible other onboard services. The application may use also microservices offered from Azure cloud. Here is a list of possible minimum set of applications in the driver terminal (MVP approach; not necessarily limited to these): 1. Vehicle assignment application: Provide a view to assign vehicle to a block and to a vehicle journey. 2. Vehicle progress application: Display route pattern and geometry. Display vehicle position on route pattern. Display schematic view for driver. 3. Driving aid application: Inform regulated timing point. Deviation route information. 4. Notices and messages application: Provide disruption notices browsing and reading view. 5. Driver terminal frame: Display official date and time. Produce audio notification. Display disruption notice indicator. 6. Outer display control application: “Bus full” -button in driver terminal. Vehicle environment provides additional services for the driver terminal including vehicle computer with built in 5G and GNSS capabilities (router). The vehicle computer also provides a x64 Debian based Docker environment for driver terminal software which is required to be used in rail transport modes and is optionally available for buses. All specialized IO is available in the vehicle computer (serial ports, CAN connection etc.). Buses have FMStoIP available for driver terminal. The purpose of the driver terminal procurement is to procure mostly software, and that the provider will use HSL hardware platform for the solution. It is possible that the driver display hardware is part of this procurement, but this is something that will be discussed within the technical discussions. However, the solution should be such that it is able to run on any given hardware, for example integrated touchscreen display as it is in the trams currently. The main idea behind this vehicle solution is that HSL will provide information of the current situation and the interfaces, and that the provider will give solution. HSL prefers not to specify the solution too much and thus find a mostly ready-made solution that fits the HSL's needs. We want to avoid technical tailoring, in other words, build to suit to our needs. Mostly the solutions should include all the tools for the driver to be able to do all the necessary actions to drive the route and the assistance for the driving. So, we want to discuss with providers to find the most suitable solution for our needs, including an open competition for tendering.

  • Contact

    hankinnat@hsl.fihankinnat@hsl.fi
  • Type
    Planning
  • Main code
    IT services: consulting, software development, Internet and support
    72000000
  • 30200000Computer equipment and supplies

Similar active competitions

  • Liikenne- ja viestintävirasto

    Kontor- og utskriftsløsninger

    Markkinavuoropuhelu: lippu- ja maksujärjestelmä (LMJ) PSO-henkilöjunaliikenteeseen / Invitation to market dialogue – ticketing and payment system (TPS)

    Liikenne- ja viestintävirasto Traficom valmistelee PSO-henkilöjunaliikenteen lippu- ja maksujärjestelmän hankintaa palveluna, mukaan lukien järjestelmän toteutus, junien laitteet sekä niiden ylläpito, kehittäminen ja operointi; kokonaisuuteen kuuluvat myös digitaaliset asiakaskanavat ja matkustajainformaatio. Järjestelmän tulee tukea päivä- ja yöjunien lippuja, maksuja ja paikanvarauksia sekä avoimia rajapintoja ja usean liikennöitsijän toimintaa. Traficom kutsuu toimittajia markkinavuoropuheluun antamaan näkemyksiä ratkaisusta ja hankinnan valmistelusta.

    Planning
  • Helsingin seudun liikenne -kuntayhtymä

    Regnskaps- og rådgivningstjenester

    KUTSU MARKKINAVUOROPUHELUUN: HSL:n talous- ja palkkahallinnon palvelut

    Helsingin seudun liikenne -kuntayhtymä (HSL) valmistelee talous- ja palkkahallinnon palveluiden hankintaa, jotka sisältävät muun muassa kirjanpito-, ostolasku-, myyntilaskutus-, palkanlaskenta- ja HR-järjestelmäpalveluita. HSL kutsuu palveluntarjoajia osallistumaan markkinavuoropuheluun, jossa he voivat antaa palautetta hankinnan osa-alueista, tuotantomalleista, palvelutasovaatimuksista, hinnoittelumalleista sekä uusien teknologioiden hyödyntämisestä. Nykyinen palveluntuottaja on Sarastia.

    Planning
  • Stara (Helsingin kaupungin rakentamispalveluliikelaitos)

    IT-rådgivning og strategi

    Tietopyyntö ja kutsu markkinavuoropuheluun: Kaupunkitekniikan toiminnanohjausjärjestelmä

    Helsingin kaupunki, kaupunkiympäristön toimiala, valmistelee kaupunkitekniikan toiminnanohjausjärjestelmän hankintaa, jonka tarkoituksena on korvata nykyinen järjestelmä valmiilla ohjelmistoratkaisulla ulkovalaistuksen ja liikennevalojen investointi- ja kunnossapitotöiden suunnittelua, tilaamista ja hallintaa varten. Hankintaan sisältyy lisenssejä, integraatioita, ylläpito- ja tukipalveluita sekä käyttöönottoon liittyvää asiantuntijatyötä. Toimittajat voivat antaa palautetta ja osallistua markkinavuoropuheluun vastaamalla tietopyynnön Forms-kyselyyn, jossa voi myös ilmoittautua markkinavuoropuhelutilaisuuksiin.

    Planning