Border Architecture US/Mexico Presented to Border Partnership Working Group 11 January 2006

Project Overview and Goals Develop a Border Information Flow Architecture for US/Mx –Adopted as a JWC Work Plan item at meeting in Las Cruces –Funding acquired from US DOT Intelligent Transportation System Joint Program Office (ITS JPO) to support development –Development process to be modeled after US/Cda effort, scheduled to be complete in Dec 2006 –Included as an initiative on the Security and Prosperity Partnership Use the Joint Working Committee as venue for soliciting working group participation –JWC members encouraged to engage and solicit working group participants (border stakeholders) outside JWC Developed as a “generic” architecture Complete by Dec 2007

The Border Problem Congestion –Long Wait Times –Unpredictability of Crossing Times –Queues Safety Imbalance Between Crossings Adverse Impacts on Local Community Environmental / Health Impacts

The Causes of the Problem Causes Lack of Information and Information Sharing Capacity Constraints Limited Crossing Options Increased Security Focus Jurisdictional Complexity Lack of Traveler/Commercial Preparation Infrastructure

Generic Benefits of Using an Architecture to Guide Deployment of ITS and Other Technology Identification of existing and planned technologies and systems used by agencies at or near the border Promote interoperability of technologies Reduce technology investment cost Enhance information exchange, coordination and communication Guide technology investments and enable agencies to share the costs of addressing border problems

Specific Border Needs and Services that Could be Addressed in the Architecture Architecture Could Describe Information Exchanges and systems that enable border agencies and transportation to share information on : –Crossing Conditions Real-time, accurate and reliable wait time and crossing information Pre-trip & en route information on travel congestion Estimation/prediction of border congestion (1- 2 hours) Traffic volume, incidents, lane closures, surface conditions, video images, vehicle weights, cargo type, etc. Interoperability of electronic devices –Safe Access and Egress to Border Facilities Queue-end warning (congestion, incidents) Access/egress control (traffic signals) Way finding

PROPOSED DEVELOPMENT PROCESS Re-establish/Expand the JWC Sub-Committee tasked with Developing the US/MX –JWC Sub-Committee should engage and invite other border stakeholders to participate in development process Consider establishing a Steering Group –Small subset of JWC Sub-Committee that is representative of major border stakeholder groups. Use US National ITS Architecture and Mexican National Architecture ITS (if available) to guide t he development effort Develop Architecture as a “generic” architecture that can be applied/used at any US/MX border crossing –Architecture to be bi-national in nature, addressing information exchange amount US/MX

LEVEL OF EFFORT AND REQUIRED PARTICIPATION JWC Sub-Committee and Steering Group (if established) –Participate in routine teleconference (at least bi- monthly) to accomplish task associated with architecture development –Instrumental in defining preliminary needs and services to be addressed in the architecture –Gather and validate information on existing/planned border systems, technology projects –Participate in Face-to-Face Workshops (2 planned during development process) –Participate in Web-Conferences –Engage US or Mexican Counterpart if required

Key/Required Project Team Active Participation from the Public Sector (US/MX) –Customs / immigration –Security –Transportation (federal/state/municipal) –Commercial vehicle enforcement /regulation –Emergency response agencies –Border Safety Inspection Private Sector –Crossing Operators –Commercial vehicle operators –Business operators –Customs brokers??? Consultant Support

Draft High Level Deliverables and Timelines DeliverablesTentative Date Web conference to familiarize stakeholders with ITS JAN/FEB 06 Participation in stakeholder meetings (teleconferences) Bi-monthly starting in Jan or Feb 06 Conduct of Workshop 1 (on-site meeting at a location TBD in AZ, TX, NM or CA) Summer st iteration of US/MX border architectureDecember 2006 Gathering and providing information to guide development process As required Conduct of Workshop 2 (on-site meeting at a location TBD in AZ, TX, NM or CA) Spring 2007 Deliver final US/MX Border Information Flow Architecture December 2007

Questions???