|
 |
Border Information Flow 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 travelers, vehicles,
sensors, databases, and control centres.
The TBWG could apply 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 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. For more
information, please contact Jonathan Sabean at sabeanj@tc.gc.ca.
|
