12 May 2006 Integrating smart container technology into existing shipping and law enforcement infrastructure
Author Affiliations +
While there has been important research and development in the area of smart container technologies, no system design methodologies have yet emerged for integrating this technology into the existing shipping and law enforcement infrastructure. A successful deployment of smart containers requires a precise understanding of how to integrate this new technology into the existing shipping and law enforcement infrastructure, how to establish communication interoperability, and how to establish procedures and protocols related to the operation of smart containers. In addition, this integration needs to be seamless, unobtrusive to commerce, and cost-effective. In order to address these issues, we need to answer the following series of questions: 1) Who will own and operate the smart container technology; 2) Who will be responsible for monitoring the smart container data and notifying first responders; 3) What communication technologies currently used by first responders might be adopted for smart container data transmission; and 4) How will existing cargo manifest data be integrated into smart container data. In short, we need to identify the best practices for smart container ownership and operation. In order to help provide answers to these questions, we have surveyed a sample group of representatives from law enforcement, first responder, regulatory, and private sector organizations. This paper presents smart container infrastructure best practices recommendations obtained from the results of the survey.
© (2006) COPYRIGHT Society of Photo-Optical Instrumentation Engineers (SPIE). Downloading of the abstract is permitted for personal use only.
Dale Ferriere, Dale Ferriere, Khrystyna Pysareva, Khrystyna Pysareva, Andrzej Rucinski, Andrzej Rucinski, } "Integrating smart container technology into existing shipping and law enforcement infrastructure", Proc. SPIE 6204, Photonics for Port and Harbor Security II, 620405 (12 May 2006); doi: 10.1117/12.670046; https://doi.org/10.1117/12.670046

Back to Top