Enhancement speed 2
Document analytical engine input file format 2
Optimizing for design 2
Include ability to add backcalculation results for rehabilitation projects.
This would allow the analysis of multiple locations and determine overlay 2
thickness at each location.
Agency specific libraries (materials, traffic, climate) 2
Master default settings 2
Help files 2
Database - file management (ability to store, manipulate, retrieve state
DOT input data)
Monte Carlo simulation 2
Enhanced climate file creation 2
Most DOT's do not use effective binder content - modify to use percent
Spec check summary of inputs (identify what inputs were used compared
to state default values)
Use percent passing not percent retained for HMA aggregate input 2
Security for product 2
The equation for converting structural coefficient to resilient modulus is
missing the exponent in the ‘view equation’ button in Level 2 analysis for 2
crushed rock base. The calculations is correct. Exponent should be 3
Additional analysis models
Previous version control
Include additional programs to make a pavement design suite.
Batch run outputs
Import and export data
Include all LTPP sites modeled for national calibration with the release of
the AASHTOWare version.
In ‘Batch” mode the Excel files should be created but NOT OPENED on
the desktop by default (memory usage issue with large number of batch
It would be very helpful if the MEPDG provided an option to predict the E*
data at 10 and 130°F (both temps are required input at Level 1. Without it
the Level 1 analysis does not work!)
Documentation is needed for all of the intermediate and temporary files
Include NCHRP 1-39 or other applicable traffic software (Atlas) with
Include stand alone version of EICM with MEPDG software so user can
create new weather stations
Eliminate aggregate input for PCC or have software input default CTE
value based on type of aggregate selected based on drop-down menu with
option for level 1 input.
Include warning screen for PCC mix and strength input screens that
changing value in mix input screen will not adjust defaults in strength input
screen and vice versa where in reality the inputs are related.
Friction between JPCP and stabilized base layers
Including negative traffic growth for calibration purposes
Virtual weather station interpolation (include elevation in selection process)
Stability and improved error handling
Include printout of frost depth/freeze
Additional detailed outputs
Include batch solver
Additional climatic sites
The ICM has been increased in speed. The asphalt engine still needs major speed improvements. It is
ARA's belief that major decreases in run time are possible with a reasonable amount of work.
I think this is probably the highest priority of things that should be done. It allows the individual engines to
be run as stand-alone, with better control over their exact behaviors.
Definitely possible. It should run in a very reasonable amount of times.
Would require fixing input variables and calculating for thickness (HMA overlay options).
Same as master default settings.
A tool for agencies to set their defaults and ranges would be helpful. Would be beneficial to have this
information on one screen.
An updated version is still coming from ARA and ASU for the version 1.0 release.
This remains undone. I still highly recommed it. This will allow users to mix and match their projects, to
query their projects for certain locations or outcomes.
Would include optimizing for thickness. I believe a strait out, brute force method of Monte Carlo is beyond
even a ME-PDG with models improved for speed. With that said, I also believe a modified Monte Carlo
method is well with in what could be accomplished during the AASHTOWare project.
Ability to add additional weather sites.
Security of inputs (default data) within a given agency.
The ME-PDG analytical engine format needs to be completely defined to allow more "plug and play"
French and Spanish
The ability to run with previous releases out of one interface is very important. If a design is checked in
2017 the program could show that the pavement "fails", even though it passed with the 2011 version. The
ability to run all models is a very useful forensic tool.
ARA is willing to commit the following programs to create a pavement design suite along with the current
MEPDG; Standalone ICM, ISLAB Rigid pavement FEM, Deflexus FWD analysis tools, ATLAS traffic file
creation software and RoadCare pavement management modeling tool.
When running a batch of files, it would be useful to include summaries of all runs in a master output. It
would be a quick way to check many designs for suitability.
Be able to export all layer properties (thickness, material properties, etc.). Export/reimport an entire
project. Export intermediate files (deflections, stress, strain, etc.).
Gives states somewhere to start when doing their own calibrations. Data is now included as text files as
part of the documentation. Example files.
Files should be sent to HTML.
Getting clarification from FHWA.
Obtain source code from NCHRP to make an AASHTOWare product.
Have FHWA contract to ARA - Develop User Manual and provide to states (updates to AASHTO). Linda
will contact FHWA with suggestion.
Need to define what each aggregate type means (or what it is based on) in Manual of Practice.
Checking with Mike Murphy on status.
Version 1.0 is more stable than previous versions. As always, this is an infinite sink to dump time into. No
piece of software including Windows itself is 100% stable.
Included in version 1.0.
Delivered as part of 1.0.
Delivered as part of 1.0.
ARA is working with Climate Canada to get data for Canada.