T3 Webinar Presentation

A Sign of the Times: Using the ITS Standard (NTCIP 1203) for Dynamic Message Signs (September 26, 2007)

Presenter:   Ken Vaughn
Presenter's Org:   Trevilon
Presenter:   Ashwin Amanna
Presenter's Org:   VTTI
Presenter:   Tom Stout
Presenter's Org:   Federal Highway Administration (FHWA)

HTML version of the presentation
Image descriptions are contained in brackets. [ ]
Back to Webinar Files

T3 Webinars are brought to you by the ITS Professional Capacity Building Program (ITS PCB) at the U.S. Department of Transportation's (USDOT) ITS Joint Program Office, Research and Innovative Technology Administration (RITA)


Slide 1: NTCIP 1203 (DMS) Deployment Experiences

T3 Webinar
September 26, 2007

Slide 2: Agenda

  1. Version 1 Lessons Learned
  2. Version 2 Development
  3. Version 3 Early Deployment

Slide 3: Version 1: Deployments

[Map of the US, showing deployment of DMS by state.]

Slide 4: Version 1: Lessons Learned

Slide 5: Version 1: Lessons Learned

Slide 6: Version 1: Lessons Learned

Slide 7: Version 1: Lessons Learned

Slide 8: Version 1: Lessons Learned

Slide 9: Version 1: Lessons Learned

Slide 10: Version 1: Lessons Learned

Slide 11: Version 1: Deployments

Slide 12: Version 2: Development

  1. Addressing Lessons Learned
  2. Summary of Changes
  3. Backwards Compatibility
  4. Status

Slide 13: Version 2: Development

Lessons LearnedV2 Solution
  1. Define Process
  2. V&V Standard
  3. Easy–to–use
  4. Improve Specs
  5. Define Testing
  6. Encourage Testing
  7. Advertise Solution
  1. Follow SEP
  2. Correct Standard
  3. V1 Compatible
  4. Develop Guides
  5. Define Test Proc.
  6. Testing Tools
  7. Workshops&Asst

Slide 14: Version 2: Follow SEP

Slide 15: Version 2: Follow SEP

Slide 16: Version 2: Follow SEP

Slide 17: Version 2: SEP: PRL

[Table showing Protocol Requirements List (PRL)]

Slide 18: Version 2: SEP: PRL

[Table showing Traceability to Requirements]

Slide 19: Version 2: SEP: Requirement

Slide 20: Version 2: SEP: Specification

[In specifying Version 2, a PRL is filled out with selections that are in agreement with the remainder of specification]

Slide 21: Version 2: SEP: Specification

[PRL with additional details for some requirements.]

Slide 22: Version 2: SEP: RTM

[Requirements Traceability Table.]

Slide 23: Version 2: SEP: Dialog

[Dialogue Diagram.]

Slide 24: Version 2: SEP: Object

Slide 24: Version 2: SEP Summary

Slide 25: Version 2: Correct Standard

Slide 26: Project Prioritization Process

New Features Corrections Changes
Graphics
24-bit Color
Msg Positioning
Critical Temp
Add'l Diagnostics
Add'l Config items
Time
Font Definition
Brightness Ctrl
Fan Diagnostics
Auxiliary I/O
All of these support "Backwards Compatibility"

Slide 27: Backwards Compatibility

Slide 28: Version 2: V1 Compatible

[V1 compatibility matrix.]

Slide 29: Version 2: Deployment

Daniel S. Blevins
Principal Transportation Planner
email: dblevins@wilmapco.org

For more CMP material, visit our website at http://www.wilmapco.org

Slide 29: Version 2: Deployment

  1. Guides
  2. Test Procedures
  3. Test Tools
  4. Workshops and Assistance

Slide 30: Version 2: Guides

Slide 31: Version 2: Test Procedures

Slide 32: Version 2: Test Tools

Slide 33: Version 2: Workshops, etc.

Slide 34: VTTI Early Deployment

Slide 35: VDOT/VTTI Early Deployment

Slide 36: VDOT/VTTI Early Deployment

Slide 37: VDOT/VTTI Early Deployment

Procure Test Sign Test Central
RFP for Sign
RFP for Central
Evaluate Proposals
Select Vendors
Issue POs
Implement
Pre-test (Controller)
Initial Test
Final Test
Pre-test
Initial Test
Final Test
2005–2006 Nov í06–Feb '07 Dec í06–Mar '07

Slide 38: Userís Perspective

Slide 39: VDOT/VTTI Early Deployment

Slide 40: Userís Perspective

Slide 41: Userís Perspective

Slide 42: VDOT/VTTI Early Deployment

Slide 43: VDOT/VTTI Early Deployment

Slide 44: VDOT/VTTI Early Deployment

Slide 45: VDOT/VTTI Early Deployment

Slide 46: VDOT/VTTI Early Deployment

Ken Vaughn, Trevilon
kvaughn@trevilon.com

Ashwin Amanna, VTTI
AAmanna@vtti.vt.edu

Tom Stout, FHWA
Tom.Stout@dot.gov

back to top