Home > Subcommittees > BIFA Subcommittee

Subcommittees

BIFA Subcommittee

There are a multitude of agencies from numerous jurisdictions (federal, state, provincial) that operate at or on the approach to Canada-U.S. border crossings. Many of these agencies are currently planning or implementing technology and information systems to help them accomplish their work. Representatives of some of these agencies attending the Transportation Border Working Group (TBWG) meeting in Vermont in June, 2003, identified the need for a “process for institutional cooperation and coordination to ensure that decision-making related to the selection of technologies by individual agencies will result in interoperability”.

The development of a Border Information Flow Architecture (BIFA) could help guide a deliberate effort to ensure the systems deployed at the border are able to interact with each other. The development process could follow a process similar to that used to develop an Intelligent Transportation Systems (ITS) Regional Architecture.

What is an Architecture?

An Architecture is the communications and information backbone that supports and unites key technologies enabling them to work together and communicate with each other. It describes the interaction among various physical components of the transportation system, such as travellers, vehicles, sensors, databases, and control centres.

The TBWG is applying the concept of an architecture to the border “region” to develop a framework which identifies agencies operating at or on the approach to the border and maps the information flows between them. The framework describes how components interact and work together, i.e. what each component does and what information is exchanged among components to achieve total system goals.

An architecture is made up of Subsystems and Information Flows:

Subsystems perform particular functions such as managing traffic, providing traveler information, or enforcing regulations, and are usually associated with a particular organization such as departments of transportation, information service providers, or public safety agencies. They are sources and/or users of information provided by other subsystems.
Information flows define information that is exchanged between subsystems such as traffic information, driver and vehicle information, or surveillance and sensor control data. They depict system integration by illustrating the information links between subsystems. This integration is not only technical but institutional as well. The system interfaces that are defined require cooperation and shared responsibilities on the part of owners and operators of each participating system.

The architecture does not dictate which technologies an agency must use, but rather helps procurers ensure that the technologies they choose are interoperable with other systems, making them easier to upgrade and cheaper to produce. It ensures that agencies deploying new technology and systems retain the option of securely exchanging data and information with other agencies or systems, thereby enabling access to higher-order benefits.

The architecture is not a Strategy or Plan. Rather, its real value is as a tool to support the planning and project development processes. A Border Information Flow Architecture can be a powerful tool for planning the integration of systems at the border. Indeed the very process of creating an architecture can enhance planning by bringing together a diverse array of agencies and stakeholders to discuss future needs and how these might be met.

A Border Information Flow Architecture Working Group (BIFAWG) composed of representatives from agencies involved in processes at or on the approach to the border, was established in February 2004. The working group will coordinate the development and maintenance of the BIFA, and report back to the TBWG on a semi-annual basis. Information on future developments will be forthcoming on this website as the work of the BIFAWG continues to progress.

Uses of the Architecture

To foster border region coordination and cooperation
Border project development
Border Region Architecture – either as input to a Regional ITS Architecture, or as a standalone regional BIFA

Feedback

Do you think the Border Information Flow Architecture will be a useful planning tool for your organization? How do you plan to use it? What border projects do you think are most applicable?

Email us your comments or BIFA examples for posting on this site.

For further information contact:

Jonathan Sabean, Transport Canada (sabeanj@tc.gc.ca)

Crystal Jones, Federal Highway Administration (crystal.jones@fhwa.dot.gov)

View the draft architecture at the BIFA Web Site.