Alternate transport
How can we make NSW a cycling-friendly state?
Go to Challenge | 12 teams have entered this challenge.
Jarvis
FlexiTrip is a system which monitors the occupancy rate and real time location of public transport in ACT to provde the real-time dynamic pricing to each user.
FlexiTrip believes that a dynamic pricing on public transport will balance the traffic of the whole transport system and let user make a informed decision to choose between time and cost while planning their commute.
The tiered pricing based on near real time service occupancy will help commuters decide their journey in a informed way , which would also benefit governments to outline the Pricing Models flexibly based on the Global Configuration.
FlexiTrip provides ability for Commuters and Government to have Dynamic Pricing Model in place for public transport.
The Dynamic Pricing Model helps Governments set the Pricing based on the Historical Data as well as Near Real Time Occupancy Data . It also helps Government to update the Pricing Model during the Promotional Events.
The FlexiTrip user application is a mobile app which can present users with all possible routes as well as the estimated price based on occupancy rate and distance from one location to the other. Each possible routes will pass differents stops with a changing occupancy rate
It will provide the below functionalites:
The FlexiTrip admin user application is a web applciation which allows admin user to modify the price per kilomemter and occupancy rate threshold for each zone and line.
Let's say user A is trying to go from point P1 to point P2. When user input these two points into the mobile app, the mobile app will talk to the dynamic pricing decision engine and the engine will do:
It is very likely that there are two possible routes:
1) A route with higher estimated price due to the higher occupancy rate though possibly shorter distance and less time
2) A route with lower estimated price due to the lower occupancy rate though possibly longer distance and time
Of course there might be a lot of other routes with slightly different price and distance.
Once user choose one of the route and start the journy, he will use the app to touch on the bus/station reader. When touching on, below information will be collected and sent to the event processor:
Along the journey, other passengers might get off and touch off using the FlexiTrip app. When touching off, below information will be sent to the event processor:
When near the final stop of the user A, the app will detec the current location of the user and remind user to get off and touch off in various ways. When user A touch off, the app will talk to the dynamic pricing engine and does the following:
This API calculates the Dynamic Price for the User Journey.
The User App makes this API call to fetch the Estimated Cost of the Route before Journey.
/v1/DynamicPrice/{journeyID}/estimate
URL : /v1/DynamicPrice/{journeyID}/estimate
Method : GET
Code : 200 OK
Content example
```
json
[
{
id : "11",
route : "ID",
startTime : "19:00 pm",
endTime : "20:00 pm",
estimatedPrice : "3.00",
},
{
id : "12",
route : "ID",
startTime : "19:00 pm",
endTime : "20:00 pm",
estimatedPrice : "4.00",
}
]
```
At the End Of the Journey Mobile App would call
/v1/DynamicPrice/{journeyID}/receipt
This API calculates the Dynamic Price for the User Journey.
URL : /v1/DynamicPrice/{journeyID}/price
Method : GET
Code : 200 OK
Content example
```
json
{
{
id : "11",
route : "ID",
startTime : "19:00 pm",
endTime : "20:00 pm",
cost : "3.00",
}
}
```
This API will provide the Admin View
This API allows the Admin Client of FlexiTrip to View / Update the Dynamic Pricing Configuration. This API can also be used to apply timeboxed promotiions during the events to attract commuters to travel with Public Transport . e.g. Sporting Event Promotion - FlexiRateReduce by 20%
PUT /v1/DynamicPrice/Config -- Update the Dynamic Pricing Model.
GET /v1/DynamicPrice/Config -- View the Dynamic Pricing Model.
By using the proposed solution, users which are price sensitive and not in hurry are gonna take the less occupied route or vehicle with possibly higher distance, longer wait time and cheaper price whereas users in hurry might take the more occupied lines. Eventually, users' dynamic choices will balance the number of passengers on all the routes and give users better experience when taking the public transport.
Description of Use These Data Sets are used to capture current State of the Public Transport Pricing / Usage. This helps to set up the comparison of the Outcome from Dynamic Pricing Model vs Static Pricing Model
Description of Use This Data Set would be used for Building the Journey Model with Bus Stop Inforamtion . Albeit this is a Brisbane City Database , We assume that same / Similar Data can be made available for ACT.
Go to Challenge | 12 teams have entered this challenge.
Eligibility: Must use at least one ACT Government data set, either from the Open Data Portal (data.act.gov.au) or the Geospatial Catalogue (actmapi-actgov.opendata.arcgis.com).
Go to Challenge | 10 teams have entered this challenge.