T3 Webinar Files

ITS Architecture Use & Maintenance
(July 30, 2014)

Presenter: Charles Remkes
Presenter's Org: New Mexico Department of Transportation (NMDOT)

Presenter: Nathan Masek
Presenter's Org: Mid-Region Council of Governments (MRCOG)

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

T3 Webinars are brought to you by the Intelligent Transportation Systems (ITS) Professional Capacity Building Program (PCB) of the U.S. Department of Transportation's (U.S. DOT) ITS Joint Program Office (JPO). References in this webinar to any specific commercial products, processes, or services, or the use of any trade, firm, or corporation name is for the information and convenience of the public, and does not constitute endorsement, recommendation, or favoring by the U.S. DOT.

[All the slides in this presentation have a background of a flowing yellow cloth marked with two red tribal sun symbols.]

Slide 1: T3 Webinar - July 30, 2014 | Regional ITS Architecture | Use and Maintenance

New Mexico

[This slide contains a Regional ITS Architecture diagram.]

Slide 2: We All Know -

ITS Architectures are a common framework transportation systems.

ITS Architectures define -

• functions,
• physical entities or subsystems, and
• information flows and data flows.

ITS Architectures are designed -

• for a specific term,
• for a defined area, and
• for regional transportation.

Slide 3: But…

ITS Architectures -

• Can be a catalyst for change,
• Can bridge historically disparate functions within an agency, and
• Can serve as a basis of cooperation among different agencies,
• And be leveraged further for other mutual gains.

Slide 4: New Mexico Has Five ITS Regional Architectures

[This slide contains a map of New Mexico marked to show its five ITS regional architectures. Four (Farmington, Santa Fe, Albuquerque, and Las Cruces) are associated with the state's MPOs and the fifth one, the statewide architecture, captures the needs of the various RPOs in the state and acts to bridge any overlapping functions between MPOs and RPOs.]

Slide 5: The Beginning

First Regional Architecture Developed in December 2000 for Albuquerque Metropolitan Planning Area

[This slide contains a reproduction of a page from the “Regional Architecture for the Albuquerque Metropolitan Planning Area Version 2.”]

Slide 6: Architecture Development Timelines

• Las Cruces first developed in 2003, updated in 2007, 2^nd update in June 2014
• Santa Fe first developed in 2005, updated in 2011
• Statewide first developed in 2007, updated in 2013
• AMPA first update in 2007,
  • another major update is planned 2014
  • biannual updates align with TIP/MTP cycle
• Farmington first developed in 2006, updated in 2012

Slide 7: More Background Information

• Patterned after the National Architecture
• Turbo Architecture® Format
  • Tied to same database
  • Allows consistency and accuracy at boundaries and for services that cross boundaries
  • Farmington architecture is slated for update and inclusion in that database
• Developed with contractual support
• Architecture Documents Use Visio® Files for Service Packages depictions that define relationships and flows

Slide 8: Typical Service Package Depiction

[This slide contains a diagram that illustrates the functional relationships associated with network surveillance activities by the City of Albuquerque.]

Slide 9: Different Needs - Different Architecture Uses

[This slide contains a collage of photographs of motorists driving and cars moving along the roadway.]

Slide 10: Use of Architecture in the AMPA

[This slide contains logos of twenty-eight agencies that use the Architecture in the AMPA region.]

Slide 11: Architecture Maintenance and Planning

What we had before…frustration!

• TIP and MTP program development was not “ITS Friendly”….Project submittal and review process did not fully recognize all ITS elements
• ITS was project “TYPE” only; ITS elements included in other project types were not being recognized

Only the Major ITS developments were known, smaller-scale ITS Mainstreaming was not being captured

Slide 12: Our fix - ITS in MRCOG's Transportation Program Development

[This slide contains a reproduction of the addendum to MRCOG's TIP Project submittal form. There is also an enlargement of the ITS section of the form.]

Slide 13: ITS in MRCOG's Transportation Program Development:

[This slide contains a flowchart of how ITS is incorporated in MRCOG's Metropolitan Planning Organization TIP Development Process. Sections circled in red represent ITS components.]

Slide 14: ITS in MRCOG's Transportation Planning & Decision-Making committees

[This slide contains a hierarchy diagram showing MRCOG's Transportation Planning and Decision-Making committees. At the top is the Metropolitan Transportation Board (MTB). Below the MTB is the Technical Coordinating Committee (TCC) and the Public Involvement Committe (PIC). Below the TCC is the Transportation Program Task Group (TPTG), the Congestion Management Process Committee (CMP), and the Intelligent Transportation Systems Committee (ITS).]

Slide 15: ITS in MRCOG's Transportation Program: ITS Architecture Maintenance, Systems Engineering Certification

• Architecture Maintenance “Addendum,” coincident with TIP/MTP
  • All TIP projects reviewed, ITS elements identified
  • “Linked” to Regional Architecture, project Service Packages identified
  • Easy planning-level project reference
  • Deployment maps
• Agency/project representation at ITS SC
• Support Systems Engineering project certification
  • NMDOT conducts certification
  • Guidance established on NMDOT's website
  • Certification is required for project approval

Slide 16: Project Tracking as Part of the Maintenance Process

• Summarizes TIP Project Level ITS
• Identifies Incorporated Service Packages
• Also Includes Category II - Transit Projects
• and Category III - Archive Data and Communications Projects

[This slide shows one of the project tables included in the Architecture Maintenance Addendum update. This table includes concise and essential detail related to the project as included in the TIP and/or MTP and is correlated with the appropriate ITS Services from the Regional Architecture.]

Slide 17: ITS Corridors Map

[This slide contains a map of New Mexico's ITS corridors.]

Slide 18: NMDOT Districts and Architecture Use

[This slide contains a map of New Mexico marked to show NMDOT's six districts.]

Slide 19: NMDOT District ITS Planning and Operations

• NMDOT's operations are distributed among Six Districts with support from a centralized G.O.
• ITS Operations for the NMDOT is within the G.O.
• ITS activities and projects within the Six Districts are centrally coordinated and managed by the Department's ITS Bureau
• Associated ITS Architecture(s) Reviewed
• District ITS Strategic Plan Developed
  • Reviewed Annually
  • Contains Mapping Attributes

Slide 20: District Strategic Plan Mapping Feature

[This slide contains a map of NMDOT's strategic plan and mapping feature for the six districts.]

Slide 21: NMDOT District ITS Projects

• Identify District ITS Projects and Deployments for TIP/STIP
  • Recurring Funding
  • One-time Funding
  • Project with ITS Elements

OR

• ITS Bureau's Annual Goals and Objectives
  • Staff Resources
  • Operational Funds
  • Priorities
    • Schedule
    • Needs-driven
  • Used as a Performance Measure

Slide 22: ITS Project Development Flow

[This slide contains a diagram of the six stages of the ITS Project Development Flow.]

Slide 23: Systems Engineering Checklist a.k.a. - ITS Cert

Considerations when Developing

• Easy to Use
• No Impediment to Project Development Process
• Ties Projects Back to Architecture
• Ensure Compliance to 23 CFR 940.11
• On-line Submittal and Training for PMs
• Process Administrators Use a Responsive Customer Service Model
• Patterned from Oregon DOT Model
• Another Opportunity to Identify Non-ITS Projects as Candidate ITS Projects

[This slide contains a reproduction of the Systems Engineering Checklist, also known as the ITS Cert.]

Slide 24: Non-ITS Project Development Flow

[This slide contains a diagram that illustrates the project development flow for non-ITS projects - from long range planning to construction.]

Slide 25: Good - But Not Good Enough

[This slide contains a diagram that represents the project development flow for non-ITS projects - from long range planning to construction. The ITS component is highlighted and illustrates how far into the process this step is located.]

Slide 26: Influential Elements Occur Well Before ITS Is Considered

[This slide contains a diagram that represents the project development flow for non-ITS projects - from long range planning to construction. The ITS, Conduct Location Survey, Programming Funds, and Establish Location Study Team components are highlighted. The diagram illustrates how other decisions are made very early in the process, well ahead of ITS considerations. This demonstrates a lost opportunity for early ITS discussions.]

Slide 27: Programmed Amount vs. Engineer's Estimate

[This slide contains tables that compare the programmed amount vs. the engineer's estimate. The programmed estimate has a green checkmark next to it and the engineer's estimate has a red X next to it.]

Slide 28: Change to Facilitate Earlier Involvement

[This slide contains a diagram that represents the new project development flow for non-ITS projects. The Conduct Location Survey, Programming Funds, and Establish Location Study Team components are highlighted in the process alongside the ITS components. The diagram illustrates how ITS steps take place earlier in the process.]

Slide 29: Contact Information

Nathan Masek, AICP
Mid-Region Council of Governments
809 Copper NW
Albuquerque, NM 87102
(505) 724-3620
nmasek@mrcog-nm.gov

Charles Remkes, P.E.
NMDOT - ITS Operations
809 Copper NW
Albuquerque, NM 87102
(505) 222-6554
charles.remkes@state.nm.us

[This slide contains the NMDOT logo and the MRCOG logo.]

Back to Top