List view
Tickets that will not be moved ADO.
No due date•1/65 issues closedEri moduulit läpileikkaava kokonaisuus. Versiohistoria. Selvitettävä: käytetäänkö HSL ID:tä vai AD:tä
No due date•0/2 issues closed- Database is based on Tiamat - Handles all the necessary info regarding asset management in stops, terminals and passenger information - Location data from stops is in module Routes and lines 2 (verkko) - Make sure that user needs have been taken into consideration, and the version has been tested with users adequately - Concerns trams, metros, ferries - Exclude trains. Check if train data can be imported from Digitraffic
Overdue by 1 year(s)•Due by December 31, 2024•0/5 issues closed- Scope is to support the other means of transport (trams, metros, ferries) - Trams: Same than metros, ideaalia käyttää Digiroadia - Metro: Metron rataverkko HSL oma tekemänä tai Digiroadista (TBD) - Ferries: Map is not separately needed. Lines are handled as U-lines - Note: exclude trains - See Miro for potential blockers - Make sure that user needs have been taken into consideration, and the version has been tested with users adequately - Include the infralink update
Overdue by 1 year(s)•Due by June 30, 2024•7/43 issues closed- Future production releases (to be further defined). - The goal is to shut down Jore3 and replace it completely by Jore4 or other projects - Aim is to start replacing existing consumers one by one in the upcoming production releases. Replace other exports and tailored integrations, if GTFS/Netex haven't been adequately: 1. HIA (HSL integrations platform. Hae HSL:n arkkitehtuurilinjaus HIA:n käyttöön): contract management (JuBuMeRa = sopimusseuranta), vehicle export (kalustopoiminta ja -rekisteri), DW export 2. Infopoiminta. Consumers: Reittiloki, karttatuotanto, Digiroad. Note: voiko infopoiminnan korvata GTFS:llä? 3. Selvitettävät: HFP analytical, junajärjestelmät (Viriato, VR platform, Digitraffic), infonäytöt (Mono, onko muita?) - User feedback has been taken into consideration
No due date- This is the first Jore4 production release which involves necessary functions and integrations - It provides the GTFS (through Netex conversion) exports, and integrations to other key systems: Pubtrans (LIJ, ABTBO. It is critical to specify is the GTFS or other standard export ok) - Note: GTFS V1 doesn't support ticketing and tariffs enough, consider whether GTFS V2 suffices - Note: Discuss with ABTBO and Lipputilihanke - This is the most business critical goal, and requires discussion inside HSL and Waltti (Lippujärjestelmien toimittaja). - Possibly involves audit (cyber security) - Consider HSL needs concerning the production release (e.g. IT change management process). Specify the testing requirements with the team and HSL. - Note: this phase might require that users are filling data in Jore3 and JoreMapUI and Jore4 in the same time. Process should be decided with the business. If not possible, then export from Jore4 to Jore3 is necessary. - Consider developing simultaneously once the Production release 0.1 is done, and modules Routes and lines 2 & Timetables 2 are in development - All the "Hallitusti kohti tuotantoa" workshops are done
Overdue by 1 year(s)•Due by December 31, 2024•1/5 issues closed- This is first test release that's compatibility can be tested within a larger environment - Note: not yet in production - Goal is to have a first test export (GTFS/Netex). Different consumers should have possibility to test it. (E.g. Digitransit that means HSL's journey planners - reittiopas and other). Iterate the development with other key projects: Pubtrans. Contact: Mika T. Heikkilä (Tieto), Axel Aumasto (HSL) 1. ABTBO (Account-based Ticketing Back Office, Lipputilihankkeen taustajärjestelmä). Contact: Roope Ahola (Waltti Solutions), Jenni Riikonen (Waltti Solutions) 2. Digitransit. Contact: Katja Ravolainen (HSL) 3. Jubumera. Contact: Veli-Pekka Nurmi (2day), Rauli Rinnekangas (HSL) 4. InfoDevOps. Contact: Teemu Laaksonen (HSL) 5. HSL DW (=DataWarehouse). Contact: Taneli Niemi (HSL) - Maintenance process should be decided (done either within the scrum team, or separate people added from Vincit). - - This includes specifying e.g. monitoring needs and necessary documentation. - First release involves only bus data. If exports are not good enough, consider making other modules or aggregating data from Jore3. - Project infrastructure is production ready - Accessibility, cyber security and testing have been taken into consideration (scope to be defined) - Define either GTFS export or Netex is available (what is easiest and brings most value) - Proceed with this goal simultaneously with other module goals (Timetables 1&2, Stop registry 1&2, Routes and lines 2)
Overdue by 1 year(s)•Due by September 30, 2024•71/97 issues closed- Database is based on Tiamat - Handles all the necessary info regarding asset management in stops, terminals and passenger information - Location data from stops is in module Routes and lines 1 (verkko) - Make sure that user needs have been taken into consideration, and the version has been tested with users adequately - Concerns buses, and yhteiskäyttöpysäkit possibly (bussit + ratikat)
Overdue by 1 year(s)•Due by February 29, 2024•42/97 issues closed- Primarily means the other means of transport than buses (trams, metros, ferries) - Trams: Hastus is used - Metros: Hastus is used - Ferries: Hastus is used - Consider the other features and functionalities that are not in the Timetables 1 scope, they might not have business case - If possible work in this module together with Routes and lines 2 module - Note: exclude trains. There might not be a business case, meaning the train data is managed in Väylä's and Fintraffic's systems. If necessary data can be imported from Digitraffic. Import from there is in production release 1.x. - Make sure that user needs have been taken into consideration, and the version has been tested with users adequately
Overdue by 1 year(s)•Due by July 31, 2024•2/22 issues closed- Imports data from Hastus and supports export in GTFS standard - Transmodel compatibility - Scope according to GTFS (parts that HSL uses) - Version 1 concerns only buses - Make sure that user needs have been taken into consideration, and the version has been tested with users adequately
Overdue by 2 year(s)•Due by September 30, 2023•154/156 issues closed