Loren Data Corp.

'

 
 

COMMERCE BUSINESS DAILY ISSUE OF MAY 19,2000 PSA#2604

CORRECTION TO MAY 4,2000 SPECIAL NOTICE: REQUEST FOR INFORMATION: NEXT GENERATION OF TRAFFIC SIMULATION MODELS -- SOFTWARE DEVELOPMENT NEXT GENERATION SIMULATION MODEL: REQUEST FOR INFORMATION Introduction This request for information (RFI) solicits information regarding the next generation of traffic simulation models. The Federal Highway Administration (FHWA) has long believed that traffic simulation models offer significant potential for conducting research, analyzing alternative highway improvements, developing and testing traffic control systems and strategies, etc. Consequently, the agency is presently studying the feasibility of and options for developing a next generation model. Over the years FHWA has developed and supported a series of simulation models. Currently, FHWA supports a suite of models that are linked by the Traffic Software Integrated System (TSIS). At the core of TSIS is CORSIM which supports microscopic simulation of freeways and surface streets. CORSIM has its roots in FRESIM, a freeway simulation model, and NETSIM, a network simulation model. Development of FRESIM and NETSIM began nearly 30 years ago. Consequently, they were written in FORTRAN IV, the dominant source code of the 70's and 80's. Because CORSIM is essentially a marriage of FRESIM and NETSIM, it, too, is written in FORTRAN IV. So while CORSIM is an adequate tool for many applications, it is based on relatively old, unstructured code. This continues to cause significant technical and maintenance problems and limits the computational speed and size of network that can be simulated. Because programming languages and hardware have evolved significantly since the original coding of FRESIM and NETSIM, considerable efficiencies and advantages can result from housing the "engine" of CORSIM within a modern language and architecture. In addition, any restructuring of CORSIM should address many of the current shortcomings of CORSIM such as its inability to simulate certain roadway configurations and travel behaviors. The current thinking of FHWA, based on some preliminary analysis, is that re-engineering CORSIM would be the fastest and least expensive way to develop a next generation simulation package. However, at this time, FHWA is very much open to studying other options as well. Scope In advance of any development of a next generation simulation model, FHWA must address a number of issues centered around what to build and how to build it. An effort to study the feasibility of re-engineering CORSIM has recently been awarded. Focus group meetings to discuss the research and application requirements as well as intellectual property rights and related issues will be part of the process as well. The information gathered through this RFI will be of great assistance in guiding these efforts and identifying individuals and organizations that would be good candidates for focus groups. Based on the results of these efforts, FHWA will generate a road map for development, testing, refinement and delivery. Subsequent to approval of the road map, FHWA will go forward with the necessary requests for proposal (RFP's) to launch the development efforts. Objectives of this RFI This RFI seeks information from the user community, the development community, researchers, practitioners and others on what a next generation simulation package should contain, how it should be designed and structured, and how it should be supported and maintained. Information Being Requested FHWA is seeking information relative to next generation modeling in the following areas: State-of-the-Practice Are there traffic simulation packages currently available that you consider adequate for current and future research? If so, what are they? If not what are the major deficiencies in the state-of-the-practice? Are there traffic simulation packages currently available that you consider adequate for evaluating and designing transportation facilities and systems? If so, what are they? If not what are the major deficiencies in the state-of-the-practice? ∙ Are there examples of simulation outside of transportation that can we draw from? Technical Requirements for Next Generation Traffic SimulationModel What are the most important technical requirements for a next generation model? FHWA has generated a list of what it considers important. Some of the major items include: ▸ ability to model large, integrated networks in real time ▸ microscopic modeling capability ▸ real time or better operating speed ▸ on-line functionality ▸ simulation fidelity of 1 second, 1/10 of a second and 1/100 of a second -- user selectable ▸ operability on PC and/or LAN platforms ▸ object oriented modularity ▸ open architecture ▸ distributed processing options ▸ travel behavior logic ▸ traffic assignment functionality ▸ multimodal capabilities including pedestrians and bicyclists ▸ 2 dimensional and, possibly, 3 dimensional animation Which of these requirements are most essential. Which are least important? What other requirements should be considered? Development ∙ What are the options for developing a functionally precise and robust model? How should the model be coded? What would constitute the best architecture? ∙ Which options offer the greatest economy of time and resources? What is a realistic level of effort and time frame? ∙ Are there feasible partnerships and/or cost sharing options? What are the potential legal, copyright and intellectual property issues? ∙ Is CORSIM re-engineering the best option? Is it advisable to retain TSIS and TRAFVU? ∙ How important is animation? Is TRAFVU adequate? Should 3D animation be considered? ∙ What application features, currently not simulated by CORSIM, should be developed? Maintenance and Enhancement ∙ Once the software has been distributed, where should the source code reside? With the developer? With FHWA? What are the potential legal, copyright and intellectual property issues associated with your views? ∙ Should the source code be readily available or limited to selected researchers? ∙ How should maintenance be sponsored and managed? ∙ How should enhancements be sponsored and controlled? What about third party enhancements to an open architecture? Who May Respond to this RFI Any person, company, organization, institution or public agency is invited to respond. FHWA especially encourages users and researchers to specify their simulation requirements. Developers of models are encouraged to share their insights as well as address the possibilities of leveraging their products in the development of a next generation model. Instructions and Schedule for Responding Organizations responding to this RFI shall designate a single contact within that organization for receipt of all subsequent information regarding this RFI. Response to this RFI must be received by FHWA no later than June 30, 2000. Respond only to those points for which you or your organization have interest or expertise. Pre-existing documentation can be included, but should preferably be organized and presented in accordance with this RFI. It is recommended that your response include: ∙ A cover letter which should include a brief summary of your response, an indication of which areas you are responding to, and a short listing of any supporting documentation you are including in the response. ∙ Your formal response to any or all of the areas of information requested by this RFI. ∙ Appendices containing supporting documentation. How to submit FHWA prefers that responses be submitted by e-mail to the following address: hcrump@fhwa.dot.gov Hard copies of responses and support materials can be mailed to FHWA at the following address: Mr. Ronald Giguere FHWA -- HOTM 400 7th St., SW Washington, DC 20590 If you have any questions regarding the RFI or your response, please contact Mr. Giguere by mail, e-mail (ron.giguere@fhwa.dot.gov) or phone (202-366-2203). WEB: click here to go to the Turner Fairbank Highway Research, http://www.tfhrc.gov. E-MAIL: click here to contact Federal Highway Administration, Ron.Gigurere@FHWA.DOT.GOV (202) 366-2203. Posted 05/17/00 (W-SN455816).

Loren Data Corp. http://www.ld.com (SYN# 0453 20000519\SP-0012.MSC)


SP - Special Notices Index Page