New
collection (Request for a new OMB Control Number)
No
Regular
02/12/2025
Requested
Previously Approved
36 Months From Approved
288
0
1,152
0
0
0
Currently, for pipelines, it takes
days for a batch of crude oil to cross the United States border
from Canada and eventually travel to the entry point within the
United States, leaving no easily identifiable starting point for
monitoring timely entry and entry summary filings. Moreover,
Canadian crude oil is actively traded as a commodity while in
transit though the North American pipeline network, so ownership
(and thus the right to make entry) may not be known to CBP until
after the commodity crosses the U.S. border. Further, the need for
confidentiality of transactional data among private parties, means
there are limitations on CBP’s, and the trade’s, visibility into
product origin traceability through the supply chain to establish
Free Trade Agreement (FTA) eligibility. The current absence of a
technology capable of tracking changes in ownership and destination
of pipeline-borne goods, from wellhead to refinery, has resulted in
CBP creating a patchwork of local policies for data collection from
carriers and importers over the course of five decades. Under the
auspices of the Department of Homeland Security (DHS) Science and
Technology Directorate’s (S&T) Silicon Valley Innovation
Program (SVIP), with the endorsement of the Commercial Customs
Operations Advisory Committee (COAC), and at the suggestion of the
COAC's Pipeline Working Group (PWG), industry and CBP Subject
Matter Experts conducted three and a half years of joint
development with a cohort of SVIP software companies. They
determined that entry summary data derived from private party
transactions using a common platform of emergent technologies,
which passes this data to CBP using the same platform, represents a
viable means of regulating continuous flow commodities on a
pipeline network. The new platform will consist of decentralized
Identifiers (DIDs) and verifiable credentials (VCs), secured,
exchanged and rendered to CBP’s Automated Commercial Environment
(ACE) in accordance with Global Interoperability Standards (GIS).
In CBP’s first operational use of GIS data, an SVIP cohort company
will identify legitimate products and associated companies to build
a transparent supply chain for pipeline-borne crude oil imported
from Canada. This will enable recordation of bi-lateral transaction
data at each step in a supply chain, secure it from disclosure to
unauthorized parties, allow dynamic updates of ownership and
destination information, and render these data to CBP in real time
while creating an immutable chain of custody from wellhead to
refinery. In addition to potentially eliminating all port level
paper processes, adoption of these technologies could create a
revolutionary automation environment in which pre-arrival data
collection, in-bond tracking, and Free Trade Agreement compliance
traceability – the business process goals of the PWG – are achieved
as a matter of course. Therefore, the purpose of the requested
pilot is to test the usefulness of supplying GIS data to ACE
technology with a view toward resolving existing and anticipated
issues, and by eventually, if the pilot is successful, changing
existing policy and regulations to implement the new policies and
regulations. This collection of information is authorized by 19 USC
1411 National Customs Automation Program.
US Code:
19
USC 1411 Name of Law: National Customs Automation Program
This is a new collection of
information to conduct the oil pipeline test with Neoflow.
$702
No
Yes
Yes
No
No
No
No
Shade Williams 202 365-3691
shade.williams@cbp.dhs.gov
No
On behalf of this Federal agency, I certify that
the collection of information encompassed by this request complies
with 5 CFR 1320.9 and the related provisions of 5 CFR
1320.8(b)(3).
The following is a summary of the topics, regarding
the proposed collection of information, that the certification
covers:
(i) Why the information is being collected;
(ii) Use of information;
(iii) Burden estimate;
(iv) Nature of response (voluntary, required for a
benefit, or mandatory);
(v) Nature and extent of confidentiality; and
(vi) Need to display currently valid OMB control
number;
If you are unable to certify compliance with any of
these provisions, identify the item by leaving the box unchecked
and explain the reason in the Supporting Statement.