The Role of Container Seals in the Chain of Possession: Concepts of Operations

1
The Role of Container Seals in theChain of
PossessionConcepts of Operations

• Last updated 11 November 2002
• (Revised following meeting at APL on 24 October
  2002)
• Structured for discussion with stakeholders

2
Meeting Objectives

• Refine the concepts of operations related to the
  role of container seals in the chain of
  possession
• Refine the data needs related to the chain of
  possession
• Identify issues and next steps
• Note avoid discussion about
• Particular e-seals
• Software solutions
• Communications protocols/frequencies

3
Outline

• Introduction
• Key Concepts
• Chain of Possession Data and Data Users
• Operational Scenario
• Details - Working Session
• Wrap-Up
• Questions
• Next Steps

Questions for discussion appear throughout
4
The Problem

• Containers carried on one or more modes of
  transport pose a security risk.
• Ultimately, the high-tech container of the
  future and other measures will be deployed to
  minimize security risks.
• In the interim, sealing a container can improve
  security. Sealing the container electronically
  allows the status of the seal to be determined
  without a visual check.

Introduction
5
The Problem (continued)

• If, somewhere en route or at the end of the trip,
  the electronic seal shows signs of tampering, it
  is impossible to know when the tampering occurred
  unless the seal status is recorded throughout the
  trip.
• Knowing who had possession of a container of
  cargo throughout the trip, and what the status of
  the seal was at each hand-off enriches the value
  of sealing the cargo into the container
  electronically.
• So, consider a concept of operations in which the
  chain of possession of a container is known.

Do you concur with this statement of the problem
and the role for a chain of possession in
improving security?
Introduction
6
What do we mean by chain of possession?

• We define the term chain of possession as
  follows
• Documentation that indicates the chronological
  history of who had possession of the freight.
• Chain of possession records should include
  sufficient information to identify who had
  possession of the freight throughout every step
  of the trip from origin to destination, when and
  where the freight was transferred, and the status
  of the container and seal at each hand-off.
• Additional information should be recorded to
  facilitate detailed tracking of freight movement
  and analysis of problems.
• A chain of possession system is the collection
  of chain of possession records and the capability
  to determine gaps.

Do these definitions capture the key ideas?
Introduction
7
Goal for Chain of Possession

• Enhance security, efficiency, and effectiveness
  of the movement of loaded ISO containers from
  origin to destination by establishing a chain of
  possession system.

Is this the goal for chain of possession?
Introduction
8
Benefits for Chain of Possession

• By establishing and maintaining a chain of
  possession, it should be possible to
• Track the progress of the container
• Establish a history of the movement of the
  container
• Know who has a freight container at all times
• Know when and where a particular container was
  last detected
• Trace a problem with a container
• Improving knowledge about the chain of possession
  benefits the carriers and the public by
• Improving security and efficiency
• Recording the container and seal status at
  hand-off
• Providing information access to stakeholders
• Assigning responsibility in the event of a
  problem
• Detecting a problem (e.g., deviation from a
  planned route or schedule, tampering)

Are these benefits complete and correct?
Introduction
9
Chain of Possession for a Freight Container
New Topic
Lock1
Transfer2
Unlockn
Transfer3
Origin0
Custodian1
Custodian2
Destinationn

• The Chain of Possession for a container can be
  broken down into a series of discrete blocks of
  possession.
• The blocks are connected at transfer points where
  possession is transferred from one party to the
  next.
• For Container Seals, the chain of possession is
  delineated by the lock and unlock points of the
  seal. This chain may be a subset of the entire
  Chain of Possession.

Is this overview correct?
Key Concepts
10
Chain of Possession - Queries for Data
Infostructure en route
Gate Query
Customs
Lock1
Transfer2
Unlockn
Transfer3
Origin0
Custodian1
Custodian2
Destinationn

• Queries will be made for different purposes. A
  query may be answered from a database, from a
  simple seal, or from an information-rich seal,
  depending on the architecture.
• Data required will vary by query type. In
  addition to different motivations for issuing a
  query, the queries may occur in real-time at
  hand-off, en route, or after the fact.
• Query requirements define data recording
  requirements.

Is this overview correct?
Key Concepts
11
Chain of Possession for a Freight
ContainerDraft Key Concepts of Operations

• An electronic evidentiary document (known by
  various stakeholders as, for instance, a bill of
  lading, manifest, consist, or waybill) is
  developed at the origin to describe the cargo.
• Subsequent handlers of the freight reference the
  evidentiary document. They may have unique
  additional information relevant to their business
  needs. That additional information may be useful
  for detailed tracking and analyzing problems, but
  is not necessary for routine chain of possession
  documentation.
• An electronic seal is associated with the
  container and locked. The evidentiary document
  and container identifier are linked to the
  electronic seal identifier through the
  information system infrastructure. Information
  about the seal is also captured and stored.

Key Concepts
12
Chain of Possession for a Freight
ContainerDraft Key Concepts of Operations
(continued)

• Subsequently, each time the container changes
  possession or is detected en route, the event
  is logged, along with seal/freight/container
  status information.
• Information about a particular container is
  sensitive, and the information must be
  compartmentalized to protect it from access by
  those who are not authorized to see it. Note
  primary event data should not be sensitive.
• Authorized users may access the chain of
  possession information system to determine who
  has possession of the freight, as well as the
  status of the container, freight, and seal.

Key Concepts
13
Chain of Possession for a Freight
ContainerDraft Key Concepts of Operations
(continued)

• Whatever information system(s) stores the chain
  of possession information must be electronically
  accessible to authorized users (e.g., using a Web
  browser).
• A seal may be unlocked en route (e.g., weigh
  station inspection, customs). If so, the
  unlock/re-lock events must be recorded.

Do you agree with these concepts? Are there any
other key concepts? Could we use the term
manifest?
Key Concepts
14
Chain of Possession - Primary Event and
Ancillary Data Concept
New Topic
Lock1
Transfer2
Unlockn
Transfer3
Origin0
Custodian1
Custodian2
Destinationn

• Primary Event Data
• Seal ID, Container ID
• Seal Condition
• Event Type
• Date, Time, Location
• Relinquished by
• Received by

• Ancillary Data
• Seal ID, Container ID
• Evidentiary Document
• Origin, Destination
• Carrier ID and Type
• Custodian ID
• etc.

• Primary event data should be recorded at the lock
  and unlock points.
• Primary event data should be recorded at each
  transfer and en route.
• Ancillary data should be recorded for each block
  of possession, including origin and destination.

Does the idea of primary event and ancillary
data make sense?
Chain of Possession Data and Data Users
15
Chain of Possession - Data May Come From
Different Sources
Lock1
Transfer2
Unlockn
En Route3
Ancillary Data
Origin0
Custodian1
Custodian2
Destinationn
Reader1
Reader2
Reader3
Readern
Primary Event Data
Station1
Station2
Station3
Stationn
Other1
Other2
Other3
Othern

• Chain of possession data may come from different
  sources
• The person/system who has the container
  (custodian)
• The device that reads the seal (reader)
• The system that controls the seal reader
  (station)
• Other people/systems (e.g., an electronic system
  that identifies the custodian)

Do these data sources make sense?
Chain of Possession Data and Data Users
16
Chain of Possession - Example Primary Event and
Ancillary Data
Container ID Evidentiary Document Originator,
etc.
Ancillary Data
Origin0
Seal Container ID Seal Condition
Reader1
Event Type1 Date1 Time1 Location1
Station1
Primary Event Data
Relinquished by1 Received by1 Container ID (from
container)1
Other1
Well look at the data in more detail later.
Chain of Possession Data and Data Users
17
Custodians in the Chain of Possession

• Originator/Shipper
• Transport Operators (Rail, Dray, Over-the-Road,
  Air, Vessel)
• Recipient
• Freight Forwarder
• Subcontractor (e.g., Consolidator,
  Deconsolidator)
• Bonded Warehouse
• Law Enforcement (e.g., Customs, Weigh Station)

Is this overview correct? Is custodian the
correct term?
Chain of Possession Data and Data Users
18
Chain of Possession Data Users (who will make
queries)

• Originator/Shipper
• Each Custodian
• Recipient
• Law Enforcement
• En Route Detector (e.g., weigh station, etc.)
• Gate Controller (access, entrance, exit)
• Beneficial Owner of the Cargo
• Investigators

Should other types of chain of possession data
users be added?
Chain of Possession Data and Data Users
19
Operational Scenarios
New Topic

• Regardless of the operational scenario, the data
  requirements are essentially the same for the
  same kind of cargo.
• Different kinds of chain of possession data may
  be required for different kinds of cargo (e.g.,
  HazMat).

• Are there any other scenarios to consider?
• Do you agree that the data requirements are
  essentially the same?
• Are the data requirements essentially the same
  for the same kinds of cargo?

Operational Scenario
20
Operational Scenario 1 (page 1 of 2)
CUMULATIVE CHAIN OF POSSESSION DATA
CHAIN OF POSSESSION
Primary Event Data
Ancillary Data
Evidentiary Document Originator Seal Number,
etc. Custodian Data 1 Seal Number Container
ID Carrier Type ID Transport Type ID
Custodian ID Planned Route En Route Tracking
Cargo Type etc. Custodian Data 2 Custodian
Data 3... Custodian Data 4... Custodian Data
4... Custodian Data n
Event Data 1 Seal Number Seal Container ID
Seal Condition Event Type Date Time
Location Relinquished By Received By
Container ID Event Data 2... Event Data
3... Event Data 4... Event Data 5... Event Data
n...
ORIGINATOR
RECIPIENT
Operational Scenario
21
Operational Scenario 1 (page 2 of 2)
DATA USERS
CUMULATIVE CHAIN OF POSSESSION DATA
Primary Event Data
Ancillary Data
Evidentiary Document Originator Seal Number,
etc. Custodian Data 1 Seal Number Container
ID Carrier Type ID Transport Type ID
Custodian ID Planned Route En Route Tracking
Cargo Type etc. Custodian Data 2 Custodian
Data 3... Custodian Data 4... Custodian Data
4... Custodian Data n
ORIGINATOR
Event Data 1 Seal Number Seal Container ID
Seal Condition Event Type Date Time
Location Relinquished By Received By
Container ID Event Data 2... Event Data
3... Event Data 4... Event Data 5... Event Data
n...
RECIPIENT
Operational Scenario
22
Details - Working Session
New Topic

• Proposed Primary Chain of Possession Event Data
• Chain of Possession Data Usage
• Proposed Ancillary Data
• Other?

Details - Working Session
23
Proposed Primary Chain of Possession Event Data

• Seal Number
• Seal Condition
• Container ID (from seal)
• Container ID (from container)
• Event Type (e.g., EDI data element 1650-1651)
• Date
• Time
• Location
• Relinquished By
• Received By

• Possible Data Sources
• Gathered via the reader
• Seal Number
• Container ID (from seal)
• Seal Condition
• Gathered as a result of the read event
• Event Type
• Date
• Time
• Location
• Gathered as a result of ?
• Relinquished By
• Received By
• Container ID (from container)

Note An event record may be incomplete (e.g.,
rail)
Are this list and proposed data sources complete
and correct?
Details - Primary Event Data
24
Chain of Possession - Queries for Primary Event
and Ancillary Data
Infostructure en route
Gate Query
Customs
Lock1
Transfer2
Removaln
Transfer3
Origin0
Custodian1
Custodian2
Destinationn

• Queries will be made for different purposes.
• Data required will vary by query type.
• Query requirements define data recording
  requirements.

Who/what kinds of systems need to use chain of
custody data?
Details - Queries
25
Chain of Possession Example Scenario -Queries
Custody Scenario Shipper ? Dray ? Rail ? Dray ?
Vessel ? (Customs) ? Dray ?
Dray Hold ? Dray ? Rail ? Dray ?
Rail ? Dray ? Truck ? Consignee
Rail En-Route Query
Gate Query
Gate Query
Load Query
Unload Query
Shipper
Drayage Company
Rail Terminal - Transit - Terminal
Custody
(? next page)
Lock
Seal Action
Origin Shipper Empty container is provided
by Drayage Company. Goods are stuffed into empty
container by Shipper. Contents are documented by
Shippers Bill of Lading, certified by Shippers
Export Declaration. Custody is transferred to
Drayage Company. Custody transfer is established
via locking of cargo seal. Dray transfers the
container to Rail Operator at a rail terminal.
The Rail Operator moves the container from one
terminal to another, maintaining custody
throughout.
Is the sequence representative?
Details - Queries
26
Chain of Possession Example Scenario -Queries
Custody Scenario Shipper ? Dray ? Rail ? Dray ?
Vessel ? (Customs) ? Dray ?
Dray Hold ? Dray ? Rail ? Dray ?
Rail ? Dray ? Truck ? Consignee
Gate Query
Customs
Gate Query
Sea En-Route Query
Gate Query
Gate Query
Load Query
Unload Query
(? next page)
Sea Terminal - Vessel - Terminal
Custody
Dray
Dray Hold
Seal Action
Verify
Verify
This page of the scenario begins with Drayage
Company assuming custody in Rail Terminal for
transport to Marine Terminal After unloading the
vessel, custody is transferred to a drayage
company that also has responsibility for
intermediate storage of the sealed container.
Is the sequence representative?
Details - Queries
27
Chain of Possession Example Scenario -Queries
Custody Scenario Shipper ? Dray ? Rail ? Dray ?
Vessel ? (Customs) ? Dray ?
Dray Hold ? Dray ? Rail ? Dray ?
Rail ? Dray ? Truck ? Consignee
Rail En-Route Query
Gate Query
Gate Query
Rail En-Route Query
Load Query
Gate Query
Gate Query
Load Query
Unload Query
Rail Terminal - Transit - Terminal
Custody
Dray
Rail Terminal - Transit-
Seal Action
Verify
(? next page)
This page of the scenario begins with Drayage
Company in custody, removing the container from
their holding facility for transport to Rail
Terminal. At the end of this page, the
container is in transit on rail.
Is the sequence representative?
Details - Queries
28
Chain of Possession Example Scenario -Queries
Custody Scenario Shipper ? Dray ? Rail ? Dray ?
Vessel ? (Customs) ? Dray ?
Dray Hold ? Dray ? Rail ? Dray ?
Rail ? Dray ? Truck ? Consignee
Enforcement
Gate Query
Gate Query
Unload Query
Gate Query
Gate Query
Unload Query
Consignee
Rail - Transit - Terminal
Custody
Truck Terminal - Road
Seal Action
This page of the scenario begins with the
container in transit on rail. The scenario ends
with the transfer of custody from the truck
driver to the consignee in the consignee's
receiving area, and the unlocking of the seal.
Is the sequence representative?
Details - Queries
29
Chain of Possession Data Usage
Are there other kinds of queries? How is this
related to the supply chain manifest?
Details - Queries
30
Query TypeClarification of the Query

• Status
• Where is (or was) the container?
• Is there a problem?
• Is the cargo intact?
• Has the container been tampered with or damaged?
• Directions
• Where is the container going?
• How must the container be handled?
• What are the dimensions?
• What does it weigh?
• Contents
• What is inside the container?
• Do the contents match what is expected?

Are these questions associated with different
kinds of queries correct?
Details - Queries
31
Query TypeClarification of the Query (continued)

• Identity
• What container is this?
• What seal is this?
• Do the seal and container IDs match?
• Where did the container originate?
• Where is the container headed?
• What is the planned route?
• What transport vehicle is this?
• What carrier is this?
• What transport operator is this?

Are these questions associated with different
kinds of queries correct?
Details - Queries
32
Query TypeClarification of the Query (continued)

• Legality
• Is this container legal for the transport
  carrying it?
• Are there any route restrictions?
• Is the transport operator legal?
• Is the carrier legal?
• Is the transport legal?
• Safety
• Is this container safe?
• Should the transport or container be inspected?
• Access
• Should this container be exiting?
• Should this container be entering?
• Is the transport operator authorized for the
  container?

Are these questions associated with different
kinds of queries correct?
Details - Queries
33
Proposed Ancillary Data Categories to beProvided
by Custodians

• Identity, type, status and other information
  (TBD) about the
• Carrier
• Transport
• Custodian
• Container
• Seal
• Route
• Cargo
• Note not all data will be available from all
  custodians (e.g., rail custodians may not always
  be able to assess the status of an individual
  container and seal).

Are these the correct categories of ancillary
data?
Details - Ancillary Data
34
Proposed Ancillary Data about the Carrier

• Type
• Identifier
• Name

What other data belongs in this category?
Details - Ancillary Data
35
Proposed Ancillary Data about the Transport

• Type
• Identifier
• Safety Status
• Security Status
• Container Identifier(s)

What other data belongs in this category?
Details - Ancillary Data
36
Proposed Ancillary Data about the Custodian

• Identifier
• Biometric Data
• Name

What other data belongs in this category?
Details - Ancillary Data
37
Proposed Ancillary Data about the Container

• Type
• Container Identifier
• Container Physical Status
• Container Security Status
• Seal Identifier
• Height
• Weight (empty)
• Handling Instructions (empty)

What other data belongs in this category?
Details - Ancillary Data
38
Proposed Ancillary Data about the Seal

• Type
• Seal Identifier
• Security Status
• Container Identifier

What other data belongs in this category?
Details - Ancillary Data
39
Proposed Ancillary Data about the Route

• Origin
• Destination
• Route Plan
• Actual Route

What other data belongs in this category?
Details - Ancillary Data
40
Proposed Ancillary Data about the Cargo

• Type
• Identifier
• Contents
• Weight
• Handling Requirements

What other data belongs in this category?
Details - Ancillary Data
41
Questions to be addressed
New Topic

• Is the statement of the problem (and the role of
  a chain of possession in improving security)
  clear?
• Does the working definition of the term chain of
  possession capture the key ideas?
• Is the goal complete and correct?
• Are the benefits complete and correct?
• Is the overview shown on pages 9-10 correct?
• Are the key concepts correct and complete?
• Can the term manifest be used?
• What kinds of custodians are there?
• Is custodian the correct term?

Wrap-Up
42
Questions to be addressed (continued)
New Topic

• Who are the users of chain of possession data?
• What data do they need?
• Are there different chain of possession data
  requirements for different kinds of cargo?
  Examples?
• Are the chain of possession data requirements
  essentially the same for the same kinds of cargo?
• What ancillary data should be accessible to
  investigate a problem? How does it vary based on
  the cargo type?
• Where should the ancillary data be stored?
• How are queries related to the supply chain
  manifest?
• Others?

Wrap-Up
43
Next Steps
New Topic

• Present to US DOT/FHWA management
• Present to stakeholder groups
• Present high-level version at IFTWG meeting be
  clear about expansion of meaning of chain of
  possession
• Present high-level version to other OSC projects,
  CHCP, etc.
• Present to standards groups
• Refine the scenario based on comments received
• Fill in any remaining blanks review data lists
  in detail
• Recommend allocation of requirements to the seal,
  the modal operations systems, and infrastructure
  systems
• Coordinate with Washington State DOT Electronic
  Container Seal Operational Test
• Coordinate with HazMat evaluation project

Is this list of next steps complete and correct?
Wrap-Up
44
Backup MaterialData Users and Data
Providers(redlined at 24 October working group
meeting)

• Note We want the data to be generic across
  modes. Focus on business case needs.
  Eventually, will need to translate to terms and
  data elements each mode uses.

45
Chain of Possession Data Users
Originator/Shipper
Query Type Status Where is the container now? Is
there a problem?

• Data Requested
• Last set of event data

What types of queries will this user make? Can we
complete the description of each data set needed
by this type of user?
Details - Queries
46
Chain of Possession Data Users Final Recipient
Query Type Status Is my cargo intact? Has the
container been tampered with or damaged?

• Data Requested
• Last set of event data

What types of queries will this user make? Can we
complete the description of each data set needed
by this type of user?
Details - Queries
47
Chain of Possession Data Users Customs
Query Type Where did the container
originate? Has the container been tampered with
or damaged? Is there a valid match between
container ID and seal ID? Do the contents match
what is expected?

• Data Requested

What types of queries will this user make? Can we
complete the description of each data set needed
by this type of user?
Details - Queries
48
Chain of Possession Data Users Enforcement
Query Type Is this a container of interest? Is
the container legal?

• Data Requested

What types of queries will this user make? Can we
complete the description of each data set needed
by this type of user?
Details - Queries
49
Chain of Possession Data Users Weigh Station
Query Type Is the container safe and legal?

• Data Requested

What types of queries will this user make? Can we
complete the description of each data set needed
by this type of user?
Details - Queries
50
Chain of Possession Data Users Toll Booth
Query Type ?

• Data Requested

What types of queries will this user make? Can we
complete the description of each data set needed
by this type of user?
Details - Queries
51
Chain of Possession Data Users Gate Controller
Query Type Access, Entrance, Exit What
container(s) are on this vehicle? Should the
container(s) be entering or exiting the yard? Is
the driver authorized to carry the container(s)?

• Data Requested

What types of queries will this user make? Is
this user more complex than a single entity
(access, exit, entrance)? Can we complete the
description of each data set needed by this type
of user?
Details - Queries
52
Chain of Possession Data Users Mode Operators
Query Type What should I do with this container?

• Data Requested
• Container ID
• Container Type
• Bill of Lading (including destination)
• Weight

What types of queries will this user make? Can
we complete the description of each data set
needed by this type of user?
Details - Queries
53
Chain of Possession Data Users Others?
Query Type

• Data Requested

Are there any other data users? Can we complete
the description of each data set needed by this
type of user?
Details - Queries
54
So, what Ancillary Custodian Data should the
Originator/Shipper provide?
Originator/Shipper Container Container
Type Bill of Lading Originator Seal
Number Weight Handling Requirements
Should the custodian data be stored with the
primary event data? Can we complete the
description of data for this type of custodian?
Details - Ancillary Data
55
So, what Ancillary Custodian Data should the
Rail Operator provide?
Rail Operator

• Data to be recorded for each mode type should be
  specified.
• Question Should data parameters for a mode vary
  based on adjacent or preceding modes? Example
  Does it matter if the rail operator receives the
  container from a port or from an over-the-road
  motor carrier?

Should the custodian data be stored with the
primary event data? Can we complete the
description of data for this type of custodian?
Details - Ancillary Data
56
So, what Ancillary Custodian Data should the
Over-the-Road Motor Carrier provide?
Over-the-Road Motor Carrier Carrier ID Vehicle
ID Type Transport Driver ID Transport
Operator Transponder ID Planned Route Pick-Up
and Drop-Off Locations En Route Tracking
Information Cargo type (EDIFACT element 7085)

• Use this as the starting point for generic
  ancillary data

Should the custodian data be stored with the
primary event data? Can we complete the
description of data for this type of custodian?
Details - Ancillary Data
57
So, what Ancillary Custodian Data should the
Drayage Operator provide?
Drayage
Should the custodian data be stored with the
primary event data? Can we complete the
description of data for this type of custodian?
Details - Ancillary Data
58
So, what Ancillary Custodian Data should the
Vessel Operator provide?
Vessel
Should the custodian data be stored with the
primary event data? Can we complete the
description of data for this type of custodian?
Details - Ancillary Data
59
So, what Ancillary Custodian Data should the
Recipient provide?
Recipient Container Integrity Seal
Integrity Cargo Integrity
Should the custodian data be stored with the
primary event data? Can we complete the
description of data for this type of custodian?
Details - Ancillary Data
60
Should Air Operators be included as custodians?
Air
When cargo is moved to an air carrier, the
original container is opened and the cargo is
repackaged into an air container. Does this
represent a terminus for the trip?
Details - Ancillary Data
61
So, what Ancillary Custodian Data should the
Others provide?
?
Should the custodian data be stored with the
primary event data? Can we complete the
description of data for this type of custodian?
Details - Ancillary Data
62
Backup MaterialDraft Seal Performance Standards

• From The North River Consulting Group,
  Commercial Electronic Cargo Seals Standards,
  Marketplace, and Security Requirements,
  Container Shipping Security Workshop, 19 August
  2002.

63
Performance Categories

• Chain of custody audit trail
• Detection and reporting
• Range
• Speed

• Global access
• Physical security
• Electronic Security
• Validity
• Data stream management

• Power
• Variation by commodity
• Conditions that trigger default to greater
  scrutiny

From The North River Consulting Group,
Commercial Electronic Cargo Seals Standards,
Marketplace, and Security Requirements,
Container Shipping Security Workshop, 19 August
2002.
64
Container Seal Performance StandardsA Strawman
to Stimulate Discussion
From The North River Consulting Group,
Commercial Electronic Cargo Seals Standards,
Marketplace, and Security Requirements,
Container Shipping Security Workshop, 19 August
2002.
65
Container Seal Performance StandardsA Strawman
to Stimulate Discussion (contd)
From The North River Consulting Group,
Commercial Electronic Cargo Seals Standards,
Marketplace, and Security Requirements,
Container Shipping Security Workshop, 19 August
2002.
66
Container Seal Performance StandardsA Strawman
to Stimulate Discussion (contd)
From The North River Consulting Group,
Commercial Electronic Cargo Seals Standards,
Marketplace, and Security Requirements,
Container Shipping Security Workshop, 19 August
2002.
67
Container Seal Performance StandardsA Strawman
to Stimulate Discussion (contd)
From The North River Consulting Group,
Commercial Electronic Cargo Seals Standards,
Marketplace, and Security Requirements,
Container Shipping Security Workshop, 19 August
2002.