Toward a Multi-State Consensus on Rural Intersection Decision Support: Objectives u Gain understanding of issues involved with national rural intersection.

Slides:



Advertisements
Similar presentations
Roadmap for Sourcing Decision Review Board (DRB)
Advertisements

TITLE OF PROJECT PROPOSAL NUMBER Principal Investigator PI’s Organization ESTCP Selection Meeting DATE.
ATTENTION This presentation breaks down the purchasing process into 6 steps, which are then detailed in the subsequent slides. While responding from either.
The System Development Life Cycle
Bringing Technology to the Rural Hospital Rural Telecon ‘07 October 17, 2007.
Evaluating and Revising the Physical Education Instructional Program.
Jump to first page Chapter 2 System Analysis - Determining System Requirements.
7.2 System Development Life Cycle (SDLC)
Welcome to CMPE003 Personal Computer Concepts: Hardware and Software Winter 2003 UC Santa Cruz Instructor: Guy Cox.
SystematicSystematic process that translates quality policy into measurable objectives and requirements, and lays down a sequence of steps for realizing.
LSU 01/18/2005Project Life Cycle1 The Project Life Cycle Project Management Unit, Lecture 2.
LSU 07/07/2004Communication1 Communication & Documentation Project Management Unit – Lecture 8.
Introduction to Information System Development.
Systems Analysis and Design: The Big Picture
1 Building and Maintaining Information Systems. 2 Opening Case: Yahoo! Store Allows small businesses to create their own online store – No programming.
Unit 2: Engineering Design Process
9 Closing the Project Teaching Strategies
MN IDS Intersection Construction Update. MN IDS Test Intersection u Design Completed 15 Jan 2004 u Design review with Mn/DOT traffic, geometric, district,
Literature Review and Parts of Proposal
Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.
1 ITS America Palm Springs, CA June 6, 2007 SunGuide SM Software – Florida's ITS Software ITS America Palm Springs, CA June 6, 2007 Trey Tillander, P.E.
ADC Meeting ICEO Standards Working Group Steven F. Browdy, Co-Chair ADC Workshop Washington, D.C. September, 2007.
E N T E R P R I S E Developing Consistency in ITS Safety Solutions – Intersection Warning Systems ENTERPRISE PROJECT OVERVIEW JUNE 15, 2011.
Phil Cronin Anne Hill Allen Schones CIS841 Summer on Campus 1998 IN-PROCESS INSPECTIONS FOR OBJECT ORIENTED DESIGNS.
© 2015 Cengage Learning. All Rights Reserved. May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part.
SE&A GTS – Ga r d n e r T ra n s p o r t a t i o n S y s t e m s © Siemens E&A, GTS Kittelson Associates, Inc. Protected Permitted Left Turn Displays NCHRP.
Interaction Modeling. Overview The class model describes the objects in a system and their relationships, the state model describes the life cycles of.
Meeting of State Pooled Fund Partners April 20, 2005 "Reducing Crashes at Rural Intersections: Toward a Multi-State Consensus on Rural Intersection Decision.
High Level Architecture Overview and Rules Thanks to: Dr. Judith Dahmann, and others from: Defense Modeling and Simulation Office phone: (703)
Systems Development AIMS 2710 R. Nakatsu. Overview Why do IT projects succeed and fail? Two philosophies of systems development –Systems Development Life.
Statistics Monitor of SPMSII Warrior Team Pu Su Heng Tan Kening Zhang.
Test Intersection: Status, Results, Preparation for State Data Collection Lee Alexander Pi-Ming Cheng Alec Gorjestani Arvind Menon Craig Shankwitz Intelligent.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
MD Digital Government Summit, June 26, Maryland Project Management Oversight & System Development Life Cycle (SDLC) Robert Krauss MD Digital Government.
NHTS Update and Data Analysis Plans presented to Florida Model Task Force presented by Krishnan Viswanathan November 10, 2009.
1-1 System Development Process System development process – a set of activities, methods, best practices, deliverables, and automated tools that stakeholders.
© 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S.
Project Outline City of Mountain View – need image !
Log files presented to : Sir Adnan presented by: SHAH RUKH.
Assessing the influence on processes when evolving the software architecture By Larsson S, Wall A, Wallin P Parul Patel.
September 25, 2013 Greg Davis FHWA Office of Safety Research, Development and Test Overview of V2I Safety Applications.
TEMPERATURE MEASUREMENT & CONTROL DIVISION EVITHERM - WP 8 - Meeting 26 march 2003 Task 8.2 – CAP Compile database content of equipments and service providers.
THE PROJECT LIFE CYCLE PROJECT MANAGEMENT LIFE CYCLE LSU 01/18/2005 PROJECT LIFE CYCLE 1.
Cooperative Intersection Collision Avoidance Systems – Stop Sign Assist (CICAS-SSA) ITS America 2007 Annual Meeting Session.
System Construction System Construction is the development, installation and testing of system components.
NWPP Multiple-Award Technical Support Contract (eff. 08/2005) Unit 8 Unit 8 “Managing the Task Order”
Page 1 JUSTIFY define and validate REQUIRE- MENTS define initial management DOCUMENTS define INFRA- STRUCTURE allocated maintenance changes management.
Motivation, high level description for a portable IDS system Lee Alexander Pi-Ming Cheng Alec Gorjestani Arvind Menon Craig Shankwitz Intelligent Vehicles.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
MN IDS Project Progress Update. MN IDS Update Progress to date v Test Intersection v Sensor evaluation results v Benefit:cost efforts progress v Human.
ITPD ISSUE MANAGEMENT PROCESS SEPTEMBER 5, 2008
INTERSECTION WARNING SYSTEMS Jon Jackels Mn/DOT ITS Program Engineer Traffic Topics April 7, 2011.
ASTRA Update Sunflower Project Statewide Management, Accounting and Reporting Tool (SMART) February 12, 2009.
Human Factors Progress IDS Project Nicholas Ward Jason Laberge Mick Rakauskas HumanFIRST Program.
ILC 2007 Global Design Effort 1 Planning Damping Rings Activities in the Engineering Design Phase Andy Wolski Cockcroft Institute/University of Liverpool.
National Workshop on ANSN Capacity Building IT modules OAP, Thailand 25 th – 27 th June 2013 KUNJEER Sameer B Pool of experts database and further enhancements.
Collaborating for Quality Quality Assurance (QA) & Quality Control (QC) in the Accelerator Project (ACCSYS) Matthew Conlon ACCSYS QA/QC
Rural Intersection Decision Support - Crash Analysis Rural Intersection Decision Support - Crash Analysis Presented at Pooled Fund Meeting April 19, 2004.
Statistical process model Workshop in Ukraine October 2015 Karin Blix Quality coordinator
Strana 1MBA kurz informačního inženýrství INITIATE CONSTRUCT DELIVER MAINTAIN & SUPORT quality assurance, manage project, trainig&education, manage.
 System Requirement Specification and System Planning.
New Task on DSM and Climate Change Dr David Crossley Managing Director Energy Futures Australia Pty Ltd IEA DSM Executive Committee Meeting Brugge, Belgium.
Collaborating for Quality through the Project Quality Plan Matthew Conlon ESS ACCSYS QA/QC Quality Learning & Planning.
The System Development Life Cycle
HMA Follow On Activities
Software Project Configuration Management
TechStambha PMP Certification Training
The System Development Life Cycle
CLINICAL INFORMATION SYSTEM
UNIT No- III- Leverging Information System ( Investing strategy )
Presentation transcript:

Toward a Multi-State Consensus on Rural Intersection Decision Support: Objectives u Gain understanding of issues involved with national rural intersection crashes by collecting and analyzing information from participating states. u Develop system that meets national needs for rural intersections. u Identify intersections in participating states having crash rates and severities above critical levels, and validate need for a nationally deployable rural intersection decision support system. u Provide design guidelines and assist with the installation of intersection instrumentation in participating states. u Analyze data returned from test intersections to identify whether regional differences exist in driver behavior at rural intersections. u Validate system performance and create foundation for a multi-state field operational test of a rural intersection decision support program.

Task1 Project Management u Coordinate state activities (between states participating in this pooled fund study and with the national IDS program) u Schedule the driver interface workshop (April 20) u Disseminate research results to participating states. u Travel coordination for state representatives to pooled fund meetings performed by Mn/DOT.

Task 2 State Crash Analysis u For each member state, analyses focused on identifying critical rural intersections will be performed. u Will request specific crash information from the crash database in each state. We will then provide to each state a list of intersections with crash rates and severities above the critical level as well as a recommendation for the experimental intersection. u In the event that some states lack particular data in their crash reporting/recording systems, modifications to the analysis developed for the national IDS project will be made to best compute similar statistics. u Deliverables: Reports summarizing the rural intersection crash problem in each member state, a list of rural intersections with crash rates above the critical level, and a recommendation for an intersection to be instrumented and studied further.

Task3 Intersection Design Workshops u Two interactions with the representatives from each member state are planned. v First: A design brief describing the proposed driver infrastructure interface(s) will be provided to each of the member states; a review/critique of the proposal will be requested. Feedback provided by participants will be used to determine which interface(s) will be replicated in the HumanFIRST driving simulator. Early FEBRUARY (mailing) v Second: Once the interface design set has been defined, a workshop will be held for representatives of the participating states. 20 APRIL in Minnesota

Task 3 Intersection Design Workshops u Once the design is “finalized,” it will be tested under the national IDS program in the HumanFIRST driving simulator to determine driver response and acceptance. (This is primarily the IDS project) u Deliverables: A prototype design, drawings and specifications for a rural IDS driver-infrastructure interface.

Task4 State Intersections u Facilitate construction of a data collection system for installation at experimental intersections in those states who wish to collect data regarding the behavior of its citizens at rural intersections, and who wish to participate in the anticipated FHWA sponsored Field Operational Test of this IDS program. u The instrumentation of these intersections will be a joint process between Minnesota and the participating states. Minnesota will send an engineer to each state to analyze and model chosen intersection. u We will provide intersection design guidance and assistance in bringing the intersection online. u Each state will be responsible for the purchase of the surveillance equipment to be installed at each intersection and the construction of the infrastructure needed to support the surveillance equipment.

Task 4: Purpose u Data collected from multiple states can be used to determine whether regional differences in the gaps that motorists accept and how they proceed through an intersection. u Results will indicate whether a single DII design will function throughout the US, or if the system will have to be modified to accommodate regional differences. v Display differences v Timing issues u We will be well positioned to participate in a national operational test of these rural intersection decision support systems. System will be nationally deployable.

Task 4: Two phases u Intersection design u Intersection build

Sub-Task4.1 Intersection Design u Will travel to each state that chooses to instrument an intersection. u Will create a high accuracy geospatial database of the experimental intersection. A request will also be made to the state DOT to provide design, as-built, planametric, digital terrain models (DTM), and photogrammetric data if such data is available. u Once the database and other design data is available, will provide a design of the intersection indicating the location of sensors, control cabinets, power drops, and phone lines. Details regarding sensor foundations and masts, power requirements, etc. will be provided. u From this design document, each state will then be able to build the infrastructure needed to support the IDS instrumentation as well as procure parts based on a detailed parts list to be provided. u Each state will be financially responsible for the construction of the infrastructure and the procurement of the surveillance system which will be installed in subtask 4.2.

Sub-Task4.1 Intersection Design u Deliverables: A design document from which a test intersection data collection system can be built and a parts list for the experimental intersection so necessary equipment may be purchased and subsequently installed.

Sub-Task4.2 Intersection Build u Once the infrastructure has been completed and states complete the equipment procurement process, we will travel to each state to assist with/guide the installation of sensors, communication, and computational equipment at the intersection and bring it on line. u Once the system is brought on line, its performance will be validated and the system will be released. A data communications line to the University of Minnesota will also be completed and validated. u Deliverables: Technical support for installation and testing of the data collection system in each state.

Task 5 Intersection Data Collection u Data from each of the test intersections will be collected via a phone line from each intersection daily for subsequent analysis. u To facilitate this data collection activity, a data server and data backup system will be procured and application specific software written. (Provisions can be made to provide states with data from their experimental intersections.) u Once the system is designed, tested, and validated, data will be collected daily, archived, and backed up to assure data integrity. u Data will be collected from the time an intersection is brought on line until the project ends.

Task 5 Intersection Data Collection u On occasion, as part of the data collection process, limited demographic data for the drivers making intersection entry decisions will likely be required. u Each member state will be asked to collect its demographic data. The data collected will include age, gender, and time. u Deliverables: An operational remote data collection system with archival and data back-up capabilities. Data can be provided to each state if requested.

Task 6 Intersection Data Analysis u Will determine whether statistically relevant regional differences exist in the gaps drivers accept and the trajectories taken to enter the mainline traffic stream. u If differences are found to exist, quantification of these differences can be used to determine the degree to which the baseline rural IDS system needs to be modified to accommodate these differences. u Deliverables: A national database describing the behavior of drivers at rural expressway intersections. A report summarizing the results of the data analysis and quantification of regional differences in driver behavior will also be provided.