TWIC rules will impact the day-to-day workflows at several thousand \u201cwaterfront facilities\u201d \u2013 both public and private handling facilities \u2013 around the US, physical layouts (encompassing \u201csecure\u201d and \u201crestricted\u201d areas of terminals) and personnel management for longshoremen, lorry drivers and terminal workers. The US Coast Guard (USCG) estimates that 750,000 workers, whose backgrounds will be checked as part of the application process, will be affected.<\/p>\n
But while TWIC has been long awaited, a port-by-port roll-out schedule does not yet exist, even though the first implementation at Wilmington, Delaware, is marked for as soon as third quarter 2007.<\/p>\n
Another concern is the need to match technologies with program objectives. Already blunders have occurred since the TWIC concept was first announced early in 2002 and the final specifications for TWIC card readers, which face yet another round of pilot testing, have still not been issued. Rules regarding access devices for secure areas at facilities are also still noticeably absent.<\/p>\n
US port security has been a front page news item since the DP World debacle of early 2006 and with container scanning now receiving attention again \u2013 as the US Congress thrashes through implementation of the September 11 Commission recommendations \u2013 the maritime industry is back in the media glare. We can only hope that the Transportation Security Administration, the USCG, and its TWIC hardware and software contractor, Lockheed Martin, will get the TWIC right this time and spare the US ports industry further embarrassment.<\/p>\n
Barry Parker<\/p>\n","protected":false},"excerpt":{"rendered":"
Much discussed, long overdue and after numerous stumbles the Transportation Worker Identity Credential (TWIC) is, again, moving closer to real implementation by the stated deployment target date: September, 30, 2008. Workers at ports and terminals, and those needing access to them, will be required to obtain the TWIC, a smart card with a digital photo and fingerprint, before the program implementation.\u00a0<\/p>\n","protected":false},"author":8,"featured_media":1390,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[40],"tags":[],"sponsor":[],"class_list":["post-1389","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-the-new-yorker"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.portstrategy.com\/greenport-congress\/wp-json\/wp\/v2\/posts\/1389","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.portstrategy.com\/greenport-congress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.portstrategy.com\/greenport-congress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.portstrategy.com\/greenport-congress\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/www.portstrategy.com\/greenport-congress\/wp-json\/wp\/v2\/comments?post=1389"}],"version-history":[{"count":1,"href":"https:\/\/www.portstrategy.com\/greenport-congress\/wp-json\/wp\/v2\/posts\/1389\/revisions"}],"predecessor-version":[{"id":1391,"href":"https:\/\/www.portstrategy.com\/greenport-congress\/wp-json\/wp\/v2\/posts\/1389\/revisions\/1391"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.portstrategy.com\/greenport-congress\/wp-json\/wp\/v2\/media\/1390"}],"wp:attachment":[{"href":"https:\/\/www.portstrategy.com\/greenport-congress\/wp-json\/wp\/v2\/media?parent=1389"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.portstrategy.com\/greenport-congress\/wp-json\/wp\/v2\/categories?post=1389"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.portstrategy.com\/greenport-congress\/wp-json\/wp\/v2\/tags?post=1389"},{"taxonomy":"sponsor","embeddable":true,"href":"https:\/\/www.portstrategy.com\/greenport-congress\/wp-json\/wp\/v2\/sponsor?post=1389"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}