Internal Code: TV648
Report Writing Assignment Help:
Task:
TITLE: Impact of Incidents on road network performance and how these incidents can be managed using incident
management strategies (Melbourne Case study – Hoddle street)
Incidents mean = 1. Accident , 2. Road works, 3.Construction of building affecting road ,4. traffic increase than usual
Provide sufficient detail to allow the work to be reproduced. Methods already published should be indicated by a reference: only relevant modifications should be described.
The analytical predictive modelling tool required first a multi-layered Melbourne Aimsun Model to be built to which a Predictive Analytical Model could be built off, this was done by performing the following steps:
1. Selection of Case Study Area.
2. Importation of Strategic Model
3. Importation of SCATS database.
4. Calibration.
5. Validation.
6. Predictive Traffic Modelling.
Case Study Area
To reduce computation complexity, the model’s Case Study Area focused on a specific section of Greater Melbourne. The region to the South East of Melbourne’s CBD was chosen to be the Case Study Area Figure 2. The Case Study Area included the major arterials of the Nepean Highway, Princes Highway, the Monash Freeway (M1), Punt Road and Hoddle Street making it ideal for testing smart mobility solutions within a limited space. The Case Study area was broken into two regions based on the simulation type implemented illustrated in Figure 2. The Case study area had two simulation areas with the northern area being the microsimulation and the southern area being the mesoscopic simulation area. The microsimulation area focused on Hoddle Street between the Eastern and Monash Freeway that incorporated 25 SCATS intersections with data coverage. The southern region was the mesoscopic simulation based on the area south of the Monash Freeway that incorporated 134 intersections with SCATS data.
Theory/Calculation
Once the multi-layered model was calibrated and validated the analytical predictive model could then be built. Three different patterns were created to represent the typical traffic scenarios which included an average weekday, a Saturday and a Sunday traffic scenario. The pattern uses the sliced 15-minute matrices from the macro and departure adjustment and applies them over a 24-hour period. The average weekday profile was calculated based on the RDS from Tuesday-Thursday because those days provide the most consistent flows. The average weekday traffic to account for different routes used and different matrices used throughout the 24 hour period. The average weekday has been split into five intervals: Pre AM (midnight to 7 am), AM (7 am to 9 am), Off Peak (9 am to 16 pm), PM (16 pm to 18 pm) and Post PM (18 pm to midnight). Figure 10 is the demand profile showing the 15 minute matrices for the predictive model. The average Saturday traffic uses three intervals midnight to 8 am, 8 am to 8 pm and 8 pm to midnight with Figure 11 showing the demand profile Saturday traffic. The Sunday traffic uses three intervals midnight to 9.00am, 9 am to 9 pm and 9 pm to midnight.
simulation server was set up to feed the predictive model with synthetic data. The user can specify the simulation duration for a ‘typical day’ or to simulate a specific time period. The server then uploads the specified set of matrices and APA files to simulate the specified time period. The simulation will run for the simulation time specified and it has to run from the Mesoscopic experiment. The predictive model has the validation functionality where modelled results can be compared to the observed results from the RDS.
A Theory section should extend, not repeat, the background to the article already dealt with in the Introduction and lay the foundation for further work. In contrast, a Calculation section represents a practical development
from a theoretical basis.
Different scenario as mentions in topic must be discussed separately that how it will affect the road or traffic network in transportation pattern and results need to be generated by each scenario