Mn/DOT Office of Technical Support—Consultant Services
Work Type Definition
Rev. 1.1 (1/7/08)
Work Type Name
/14.8 Freeway Modeling
Work Type Owner / Metro Division’s Traffic Engineering Modeling & System Analysis UnitWork Type Input / Inputs may include some or all the following:
- Federal Highway Administration’s (FHWA) policy from NS 23 CFR 630C, item #3.
- American Association of State Highway & Transportation Officials (AASHTO) policy on Geometric Design of Highways and Streets.
- AASHTO Roadside Design Guide.
- Mn/DOT’s Advanced CORSIM Manual.
- Mn/DOT’s Modeling Guidelines.
- Mn/DOT’s Signal Optimization and Timing Manual.
- Mn/DOT Signal Design Manual.
- Current Mn/DOT Road Design Manual.
- Current Highway Capacity Manual.
- Current Traffic Software Integrated System (TSIS) software or equivalent micro-simulation software package pre-approved by Mn/DOT and FHWA.
- Current Synchro/SimTraffic software.
- Manual of Transportation Engineering Studies.
- Geometric layout.
- Roadway and signing plans.
- Traffic control for signals and ramp meters.
- Traffic Demand Data for arterials (turning movements) and freeway systems (mainline and ramp counts).
- Field review.
Work Type
Definition / Any new or modified access points to the Interstate system, regardless of funding source, will require Interstate access approval by the FHWA. Approval ofInterstate Access Requests (IAR) is required by Federal regulations as Non-regulatorySupplement (NS) 23 CFR 630C, item #3 ( The Engineering and Operational Analysis is a report containing sufficient information to allow the FHWA to independently ascertain that all pertinent factors and alternatives have been appropriately considered.
Freeway modeling includes developing models to evaluate the operational conditions of both the AM and PM peak traffic periods for the existing roadway, the build-year conditions, and the design-year conditions. This includes the collection of all required data, field site investigations, software data entry and analysis, model validation and calibration, alternative analysis, and Measures of Effectiveness (MOE) summaries and graphics.
Work Type Name
/14.8 Freeway Modeling
Work Type Deliverables / Operational analysis to fulfill requirements for Interstate Access Requests (IAR)Specific Examples of Deliverables / Outputs include:
- Link-Node Diagram.
- Lane Schematics.
- Balanced Traffic Dataset.
- Origin-Destination (O-D) Matrix.
- Calibration graphics and charts.
- Quality Assurance/Quality Control (QA/QC) worksheets.
- Electronic CORSIM and Synchro files or approved equal micro-simulation package and Synchro files..
- MOE Graphic and Tabular Results.
- Interstate Access Justification Report.
Quality Attributes of Deliverables /
- The operational analysis meets Federal IAR Requirements.
- The models conform to Mn/DOT’s Modeling Guidelines and Calibration Parameters.
- The models are built in accordance with Mn/DOT’s Advanced CORSIM Manual.
- Firm deliverables must include a documented Quality Assurance/Quality Control (QA/QC) process.
Work Type Name
/ 14.8 Freeway Modeling Minimum Technical QualificationsLevels of Work Type Output (Compare & Contrast)
Level 1
Basic Freeway Modeling / Level 2
Intermediate Freeway Modeling / Level 3
Complex Freeway Modeling / Level 4
Freeway Modeling Support
Level 1 projects include modeling for the following Project Types in the categories Interstate and Non-Interstate National Highway System (NHS). Projects in this level must meet at least one of the following criteria:
- AADT < 40,000.
- New or modified service interchange in rural MN.
- Service interchange outside of I-494/I-694 beltline.
- Un-instrumented system.
- 40,000 > AADT < 75,000.
- Construction or reconstruction of a service interchange.
- Modeling influence area between 4 and 6 miles.
- Un-instrumented or instrumented system.
- AADT> 75,000.
- Construction or reconstruction of a system interchange.
- Construction or reconstruction of a freeway commons area.
- Instrumented freeway system.
- Modeling influence area > 6 miles.
- Peer to peer model review.
- Planning, research, and studies that provide data, modeling, and analysis needed to address the modeling.
- Supportive studies.
- Modeling support services including but not limited to model review, calibration, and validation assistance, technical support, and training.
14.8 Freeway Modeling Minimum Technical Qualifications
Requirements of the Professional StaffMinimum Number of Staff /
- At least two professional licensed engineers are required for Level 1 and Level 2 projects and have demonstrated experience in the activities normally associated with the modeling category under consideration. One of the professionals is required to perform independent checks of data, review model validation and calibration, and reports of the other.
- At least three professional licensed engineers are required for Level 3 and 4 projects. One of the professionals is required to perform independent checks of data, review model validation and calibration, and reports of the others.
- Sufficient professional and technical support personnel to complete the work must be documented.
Professional Certification/LicensurePast Record & Experience of Firm /
- The qualified engineering personnel must have engineering training, experience, knowledge, and expertise in the appropriate areas necessary to do the project in accordance with AASHTO, FHWA, Mn/DOT, and all other applicable design policies, procedures, practices and standards.
- Projects must have been produced in accordance with Federal and Mn/DOT’s guidelines and standards.
- At least one of the engineers must be a Minnesota Board Registered Professional Civil Engineer as specified under Minimum Number of Staff.
Qualifying Experience / Level 1 and Level 2 modeling requires approval from the local FHWA District Office.
- Satisfactory experience must be demonstrated on at least two modeling projects for the level of modeling for which pre-qualification is sought, either Level 1 or Level 2 complexity projects, that have been completed within the last four years; and
- Satisfactory experience on at least one modeling project for the level for which pre-qualification is sought on the Minnesota State Highway System or NHS. The purpose of this qualification is to demonstrate an understanding of Mn/DOT’s modeling guidelines and standards; and
- Staff of local office must be capable of total completion of the project.
- Satisfactory experience must be demonstrated on at least three modeling projects meeting Level 3 modeling criteria that have been completed within the last six years; and
- Satisfactory experience on at least one Level 3 modeling project on the Minnesota State Highway System or NHS within the last four years. The purpose of this qualification is to demonstrate an understanding of Mn/DOT’s modeling guidelines and standards; and
- Demonstrate they have the tools and expertise to quickly and efficiently restructure the model to evaluate and test alternatives; and
- Staff from firm’s out-of-state offices may provide project specific expertise to support the modeling, but the project management or QA/QC must be by the local office.
Level 4 Modeling
- Satisfactorily demonstrate that they have provided peer-to-peer review for modeling projects of Level 3 complexity; and
- Satisfactorily demonstrate that they have prepared and delivered TSIS training; and
- Meet the Level 3 requirements; and
- At least one of the professional licensed engineers must have a minimum of six years of work experience and knowledge with CORSIM, and have demonstrated advanced modeling expertise with large, complex projects.
Requirements of the Firm
Past Record & Experience of Firm /
- Firm must have demonstrated the ability to successfully deliver complete operational analysis that meet Federal Interstate Access Requests (IAR) requirements.
- Satisfactory experience of the firm in the category must be documented by reference to the number of projects completed and year of completion the modeling level for which pre-qualification is desired.
Submittal Requirements: See FORM 1408
Requirements of Professional Staff /
- Qualifying experience of staff in the category/level of work must be documented by Individual Education and Experience Reports (EDUCATION & EXPERIENCE REPORT 1408) of the firm’s principals or key personnel that would be assigned the work.
- Experience of the qualified staff must be demonstrated by reference to completed projects in the activities for the modeling level for which pre-qualification is desired. Reference must include a description of the projects, date of completion, as well as the individual roles and responsibilities in the modeling process.
- Other professional and technical personnel used to support pre-qualification must also be documented.
Requirements of Firm /
- Experience of the firm in the category must be demonstrated by reference to completed projects per the requirements above(see Form 1408 for link to firm Matrix- for appropriate level). Reference must include a description and period of performance of the projects, date of completion, as well as the individual roles and responsibilities for the project. Experience by qualified professional staff may be cited in lieu of experience by the firm (these projects may be from Minnesota or other states).
- Work examples of current key personnel may be submitted in lieu of work examples of the firm. To qualify as relevant work example plans of key personnel, that personnel must still be employed with the firm and was responsible for a significant portion of the modeling work.
- Submit one example modeling project performed on the Minnesota State Highway System or NHS representative of the modeling level for which pre-qualification is being sought. Projects performed for entities other than Mn/DOT will be acceptable. The submittal must include the firm’s procedures for calibrating and validating the model and QA/QC process.
Project Documentation /
- 4 copies of Firm’s project examples must be submittedbothelectronically on CD’s and in hard copy (i.e. reports, plans, etc.).Note: No spiral bound documents.(See FORM 1408)
This area Reserved for Mn/DOT use:
Authorizing Signature/Date______/ Authorizing Signature/Date
______/ Authorizing Signature/Date
______/ Version 1.1
Page 1 of 6