|
Fritz Jooste Administrator Posts: 81
2/24/2020
|
Fritz JoosteAdministrator Posts: 81
JunoViewer has a built-in, optional Traffic Model that can be used for your deterioration model. To use this model, go to the "Traffic" sheet of your DMS. Note that "Traffic" sheet is a mandatory sheet of a DMS but if you are not using the Traffic Model, then you can hide (not delete!) this sheet in your DMS. Also note that if you are basing your DMS on one of our default DMS setups, then the Traffic sheet may be hidden by default.
Note that the traffic model is mainly useful if you need to perform calculations of remaining structural life based on traffic loading and current structural capacity. The traffic model takes care of compound traffic growth calculations and calculating the remaining life as well as the traffic over the design period. The remaining life and "MESA over Design Period" values are then placed into the placeholder cells on the "Placeholder" sheet of your DMS.
Note that advanced users can also set up their DMS to perform these calculations in the DMS instead of relying on the Traffic Model. This approach is actually now favoured by many clients since it is more transparent and does not have such strict requirements for lane definitions etc. (as explained below). If you already have lane specific traffic data in a column of your FWP, and also if you do not anticipate multiple growth periods over the modelling period, then you may want to skip the use of the Traffic Model and rather do your own thing in your DMS.
If you do decide to use the traffic model, it is your responsibility to carefully check the inputs and model outputs to ensure that the calculations are being performed correctly. Lane definitions, growth rates and growth periods need to be specified accurately and consistently. Also note that, for multi-carriageway situations, the traffic model assumed the use of a "L1", "L2", etc. and "R1", "R2" etc. convention for different directions.
On the Traffic Sheet, you will find the required parameters for the Traffic Model, together with example values and explanations. The required parameters for a traffic model are explained below. You may want to first look at this post, which explains how the JunoViewer traffic model calculates traffic based on different growth rates.
Parameter: Do Traffic Modelling
Explanation: Flag to indicate if the model should do Traffic projection modelling. This should only be true if you have valid traffic data in your FWP. Also note that some traffic model options require the use of Defined Lane Segments (see this post for more details on Lane Segment Definitions)
Parameter: FWP Column containing ESA per Day for each segment
Explanation: Name of the info column in the FWP that holds, for each segment, the daily Equivalent Single Axles (ESA) per day. The data in this column can be lane specific, or it can be carriageway-specific (i.e. total traffic across all lanes). If the latter is the case, the traffic will need to be split into lane specific values - you can use the next parameter to do this for you.
Parameter: Split ESA across lanes based on lane count
Explanation: Flag to indicate if the Traffic in the FWP table should be split across lanes using the lane count factor. This flag should only be TRUE if you have valid lane segments data and if flag "Use Defined Lane Segment Data" on the "General" tab is set to TRUE. Also note that this option will only work if you have fixed lane definitions for all slow lanes. If your lanes are numbered from the inside to the outside (see this post for details), you cannot use this option and will need to manually pre-process your data so that the traffic column in your FWP (previous parameter) holds lane specific data.
Parameter: Lane codes for Slow lane delimited by pipe symbol
Explanation: Pipe delimited codes for the lane that represents the slow lane for the case where traffic should be split across lanes. For example, if your slow lanes are all coded as "L1" and "R1", then use "L1|R1". Note the caveat above regarding certain lane definition protocols where this feature will not work. Not needed if the value of the previous parameter is set to FALSE.
Parameter: Traffic Percentage in lanes OTHER than Slow lane
Explanation: Percentage of total traffic that use the lanes other than SLOW lane, as a percentage (e.g. '15'). This is needed for the case where traffic should be split across lanes. The specified percentage will be split across all lanes other than slow lanes. So for example, if there are three lanes, and this parameter value is set to 20, then the slow lane will be assigned 80% of the traffic. The remainder will be split equally between all non-slow lanes. Please check your model outputs carefully to ensure that this feature is working as expected before you put your DMS into production.
Parameter: End Year of Growth Period 1
Explanation: Year at the END of which the first growth period ends. Start of first growth period is assumed to be the model initialization year as specified on the 'General' sheet. See this post for details on how traffic growth is handled in the traffic model.
Parameter: End Year of Growth Period 2
Explanation: Year at the END of which the second growth period ends. Start of second growth period is assumed to be the same as the end of the first growth period. Third growth period goes from end of second growth period to year 9999. See this post for details on how traffic growth is handled in the traffic model.
Parameter: FWP Column containing ESA Growth Rate (%) in Growth Period 1
Explanation: Name of the info_column in the FWP that holds, for each segment, the ESA growth rate for growth period ONE. Values should be in percent, e.g. '6.7' to represent 6.7%. See this post for details on how traffic growth is handled in the traffic model
Parameter: FWP Column containing ESA Growth Rate (%) in Growth Period 2
Explanation: Name of the info column in the FWP that holds, for each segment, the ESA growth rate for growth period TWO. Values should be in percent, e.g. '6.7' to represent 6.7%. See this post for details on how traffic growth is handled in the traffic model
Parameter: FWP Column containing ESA Growth Rate (%) in Growth Period 3:
Explanation: Name of the info column in the FWP that holds, for each segment, the ESA growth rate for growth period THREE. Values should be in percent, e.g. '6.7' to represent 6.7%. See this post for details on how traffic growth is handled in the traffic model
Parameter: FWP Column containing ESA per Day for each segment
Explanation: Name of the parameter that holds structural capacity, and from which remaining life (in years) can be calculated for placeholders. Enter 'none' if no remaining life calculation is needed. See this post for details on how traffic growth is handled in the traffic model
edited by admin on 2/24/2020
edited by admin on 2/24/2020
|