Border Information Flow Architecture (BIFA)

Presented to TBWG

November 8-9, 2005

Toronto

Fleet and FreightManagement

CommercialVehicle

Administration

Intermodal Container

CommercialVehicleCheck

211/09/2005

Presentation ObjectivesPresentation Objectives

• Provide TBWG members an update on Architecture development

• Identify actions and next steps to complete, market, and use the Architecture

• Future linkages between BIFA and TBWG

311/09/2005

BIFA OVERVIEWBIFA OVERVIEW

• A framework for promoting institutional agreement and technical integration for the implementation of ITS projects or other technology solutions at major land border crossings

• Engage border stakeholders to identify opportunities for coordination and information sharing to improve security and efficiency at ports of entry

411/09/2005

Focus and Objectives of Focus and Objectives of the Initiativethe Initiative

• Identify technologies and agencies that use technologies at or near the border

• Identify priorities of these various agencies

• Promote interoperability of technologies

• Reduce technology investment cost

• Enhance information exchange, coordination and communication

511/09/2005

BIFA Architecture Development ProcessBIFA Architecture Development Process Where Are We and How Did We Get Here? Where Are We and How Did We Get Here?

• Border Information Flow Architecture Working Group (BIFAWG) established under TBWG– Instrumental in establishing needs and processes to be

addressed in architecture– Participated in multiple teleconferences to develop strategy

to create architecture

• BIFAWG Steering Committee– Small subset of BIFAWG representative of major stakeholder

groups. – Participated in Face-to-Face Workshop in March 2005 to

develop initial “draft” Architecture– Participated in Workshop #2 in August 2005 to review draft

architecture and create Final BIFA

611/09/2005

BIFA Architecture Development ProcessBIFA Architecture Development Process Where Are We and How Did We Get Here? Where Are We and How Did We Get Here?

• Near final product available today and facets will be presented to TBWG – Largely based on Canadian and US ITS Architectures but

includes unique border services not contained in either US or Canadian architectures

• Developed as a “generic” architecture

711/09/2005

What does “generic” mean?What does “generic” mean?

• Architecture contains representative elements, services, etc.

• Element example:–State DOT TMC (vs VTrans Statewide TOC)

811/09/2005

Scope of BIFAScope of BIFA

• Geographic Scope–Region covering both sides of US

Canada border

–Representative of border areas from• British Columbia/Washington to Maine/New Brunswick

BIFA Outputs that are BIFA Outputs that are Available!Available!

1011/09/2005

BIFA OutputsBIFA Outputs

• BIFA outputs in 3 forms, all linked together– Database – Web Site – Document– CD?

1111/09/2005

BIFA Outputs - WebBIFA Outputs - Web

• Access web based output at:

– http://www.iteris.com/itsarch/bifa

1211/09/2005

BIFA Outputs – DocumentBIFA Outputs – Document

• Word Document based

• All components included, not all details

• Tables/Figures organize presentation

• Appendices used for lengthy lists

• To be completed as database is completed

1311/09/2005

BIFA- ScopeBIFA- Scope“Surrounding Region” Approach“Surrounding Region” Approach

• Include Border Crossing Systems

• Include Systems that interface to Border Crossing Systems

• Include ITS/ Related Systems that interface across the border

US/Canada

Border Crossing SystemsU.S.

Canada

US

SupportingSystems

Canada

SupportingSystems

US

ITS Systems

Canada

ITS Systems

US

ITS Systems

US

Other Systems

Canada

ITS Systems

Canada

Other Systems

BIFA

1411/09/2005

BIFA StakeholdersBIFA Stakeholders

• 48 Stakeholders documented– US and Canadian government

agencies– Private travelers and companies

• Specific: FMCSA or Transport Canada

• Generic: “County or Municipal Public Safety Agencies”

• Supports goal of using BIFA in many regional or project architectures.

1511/09/2005

BIFA Inventory (Systems)BIFA Inventory (Systems)

• 101 Elements documented– Mostly “Centre” and “Field” elements

• Some are specific: US CBP Website or IFTA Clearinghouse

• Most are generic: State DOT TMC or RCMP Emergency Services

1611/09/2005

• People/ immigration

• Goods

• Conveyances

• Traffic monitoring

• Incident response

• Traveler information

• Inspection-lane opening and closing

• Traffic sorting for primary inspection, including dedicated lanes (NEXUS/FAST)

Tolling

• Bridge

• Tunnel

• Highway

• Safety inspections

• Weights/ Dimensions enforcement

• Credentials

• Permits/ Taxes/ Insurance

•Supply chain security

• Security

• Transportation Operations

• Transportation Planning

• Trade Policy

• Inspection and Enforcement

• POE facility analysis

• Regulatory and legislative policy analysis

• Modeling (using archived statistics)

2. Entry (Pre-clearance)

4. Conveyance Safety and Security

3. Traffic Management and Operations

5. Policy/Planning 1. Inspection

• People

• Cargo

• Outbound clearances (both inspection and “back office”)

• HazMat pre-notification

+1. Post- Clearance

• Safety Inspection

Border ProcessesBorder Processes

1711/09/2005

BIFA Needs and ServicesBIFA Needs and Services

• BIFA Market Package / Service Areas represented– Commercial Vehicle Operations

(includes border crossing activity)– Archived Data Management– Traffic Management– Emergency Management– Maintenance and Construction

Operations– Traveler Information

1811/09/2005

BIFA InterfacesBIFA Interfaces

• Define Interconnects and Information flows between Elements

Bridge or TunnelOperations TOC

Bridge or TunnelOperations TOC

Provincial Emergency

Preparedness Centre

Provincial Emergency

Preparedness Centre

Interconnect

Bridge or TunnelOperations TOC

Bridge or TunnelOperations TOC

Provincial Emergency

Preparedness Centre

Provincial Emergency

Preparedness Centre

Information Flows

incident report

threat informationcoordination

Bridge or TunnelOperations TOC

Bridge or TunnelOperations TOC

Provincial Emergency

Preparedness Centre

Provincial Emergency

Preparedness Centre

Bridge or TunnelOperations TOC

Bridge or TunnelOperations TOC

Provincial Emergency

Preparedness Centre

Provincial Emergency

Preparedness Centre

Information Flows

1911/09/2005

Key Next Steps …. The Key Next Steps …. The Way AheadWay Ahead

• Final Architecture to be complete and available to public by 31 December– Joint Public Release Statement

• Who else should know? – Develop and execute an Outreach Strategy

• How BIFA can be used?– Projects (Security and Prosperity

Partnership initiative)• Funding being pursued• Requires partnership among agencies• Development of Selection Criteria

– Update of existing architectures and for special projects (e.g. IBC project)

2011/09/2005

Key Next Steps …. The Key Next Steps …. The Way AheadWay Ahead

• Webcast planned for December 8, 2005– What’s in the BIFA– Differences between BIFA and

National Architectures– How to use the BIFA– Outreach Strategy

2111/09/2005

Future Linkages between Future Linkages between BIFA and TBWGBIFA and TBWG

• BIFA Sub-Committee charged with developing Architecture– Action will be complete as of 31 December

• TBWG members likely to be “users of BIFA” products

• Propose using TBWG Website to:– Manage “Dynamic” information on BIFA– Manage feedback on usage– Manage pilot project selection, development and deployment processes

(Subject to availability of funding)

• Who Else Should Know? – Determine Outreach Strategy

• How BIFA will be used?– Projects (Security and Prosperity Partnership initiative)

• Funding being pursued• Requires partnership among agencies• Development of Selection Criteria

– Update of existing architectures

2211/09/2005

Future Linkages between Future Linkages between BIFA and TBWGBIFA and TBWG

• Action for this meeting– TBWG members to reaffirm support for BIFAWG Sub-Committee;

key actions for 2006-2007 could be:• Develop and execute an outreach strategy and plan• Encourage border stakeholders to use BIFA • Aid in selection, development, and deployment “proof of concept

project(s)”

• Who Else Should Know? – Determine Outreach Strategy

• How BIFA will be used?– Projects (Security and Prosperity Partnership initiative)

• Funding being pursued• Requires partnership among agencies• Development of Selection Criteria

– Update of existing architectures

2311/09/2005

SPECIAL THANKSSPECIAL THANKS

• TBWG for recognizing the need and adopting BIFA and as an action item

• BIFA Working Group for in-kind support to this initiative

• BIFA Steering Committee for in-kind support and leadership during development process

• Transport Canada ITS Office and US DOT ITS Joint Program Office for funding to support development

• Co-Chairs (Mike Onder and Susan Spencer) and Jonathan Sabean and Crystal Jones for facilitating the development process

• Consultants for outstanding support and technical expertise– US (ITERIS with sub to Consystec, Lockhead Martin, ICE

Corp)– Cda (IBI Group)

• US/Cda Customs organizations for dedicated support throughout the development process