Evaluation of travellers processing through a GBA+ lens:
4. Data challenges

Example: There is [*] (where a traveller is referred and examined) and data on enforcement actions (e.g. results, search and arrests and AAMPS). This makes it difficult to calculate a resultant rate based on demographic GBA+ factors.

The agency does not currently have a comprehensive integration of data across the travellers continuum, which limited the evaluation in conducting a complete GBA+ assessment. The agency collects operational data at various points in the continuum, e.g. API/PNR pre-arrival data, passage data when travellers arrive at the port of entry, and (when applicable) secondary and enforcement data. [*] because the demographic data of travellers is kept separately in various operational systems and databases.^{Footnote 30}

Performance of risk identification activities in the travellers program are partially measurable with existing performance indicators set by the Travellers Branch and Intelligence and Enforcement Branch. However, there are currently several challenges associated with using these metrics as part of a GBA+. For example, risk identification based on a resultant rate cannot be disaggregated by the demographic characteristics of the incoming traveller population.

The agency has initiatives, which will address existing data challenges in the future, including the introduction of Information Business Architecture as a cornerstone for new IT and system development projects. Also, wider deployment of Master Data Management (MDM), currently being used in the Entry and Exit program, will be able to assign a unique identifier for each traveller [*]. Once these have been widely adopted and implemented, GBA+ can be conducted on an ongoing basis with relative ease. The agency will be able to optimize its travellers processing activities to balance facilitation and compliance.