border information flow architecture (bifa)
DESCRIPTION
Commercial Vehicle Administration. Fleet and Freight Management. Commercial Vehicle Check. Intermodal Container. Border Information Flow Architecture (BIFA). BIFA Overview. BIFA Overview. Committee developed within the Transportation Border Working Group (TBWG) - PowerPoint PPT PresentationTRANSCRIPT
Border Information Flow Architecture (BIFA)
Fleet and FreightManagement
CommercialVehicle
Administration
Intermodal Container
CommercialVehicleCheck
BIFA Overview
33/14/05
BIFA OverviewBIFA Overview
• Committee developed within the Transportation Border Working Group (TBWG)
• Transport Canada and US Department of Transportation (FHWA) leading the effort
• Work will follow a methodology based on US/Canada Intelligent Transportation System- Regional Architecture
43/14/05
BIFA OverviewBIFA Overview
• A framework for ensuring institutional agreement and technical integration for the implementation of ITS projects or other technology solutions at major land border crossings
• Engages border stakeholders to identify opportunities for coordination and information sharing to improve security and efficiency at ports of entry
53/14/05
Focus of InitiativeFocus of 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
63/14/05
Border Information Flow Border Information Flow Architecture (BIFA)Architecture (BIFA)
• Developed as a “generic” regional ITS architecture
• Will have components of regional ITS architecture except–Project Sequencing–List of Agreements
73/14/05
BIFA Architecture BIFA Architecture Development PlanDevelopment Plan
• Workshop #1– Define Inventory and Services– Initial Architecture Development– March 14-16, 2005
• Complete draft BIFA based on results of workshop 1– Review of material schedule for 7 June
• Workshop #2- – 2-day stakeholder meeting to review draft
architecture – Planned for 3nd Quarter 05 (July or August)
• Create final BIFA– NLT Dec 05
83/14/05
Workshop 1 ObjectivesWorkshop 1 Objectives
• Develop Initial Border Information Flow Architecture
• Identify Actions and Next Steps to Complete Architecture
Fleet and FreightManagement
CommercialVehicle
Administration
Intermodal Container
CommercialVehicleCheck
93/14/05
ITS InventoryITS Inventory
• A list of ITS elements and the elements that interface with them
• And an element is:–The name used by stakeholders
to describe an ITS system or piece of a system
–Related to entities – subsystems and terminators
103/14/05
NeedsNeeds
• Needs are a description of the region’s transportation problems– May be general (e.g. reduce congestion)– May be specific (e.g. provide up to date
weather information to travelers)
113/14/05
TrafficMgmt
Roadway Vehicle
traffic flow
signal control data
signal preemption
request
Architecture FlowsArchitecture Flows
• Interconnects carry architecture/information flows
• Architecture flows identify flow of data– Between subsystems– Between subsystems and terminators
• Architecture flows can then be related to ITS standards
123/14/05
Next StepsNext Steps
• Develop draft BIFA based on results of workshop 1– Potentially contact workshop
participants with follow-up questions
• Conduct Workshop #2- – 2-day stakeholder meeting to review
draft architecture – Planned for 2nd Quarter 05
• Create final BIFA