ANNEX 6
PROCEDURES RELATING TO UNIQUE IDENTIFIERS
1. A unique identifier is a non-repeating alpha-numeric production number,
or a copy thereof, that has been applied by the inspected Party, using
its own technology, to an ICBM for mobile launchers of ICBMs, as provided
for in paragraph 3 or 4 of this Annex.
2. Each Party shall provide the other Party with unique identifier data
for each ICBM for mobile launchers of ICBMs in accordance with paragraph
3 or 13 of Section I of the Notification Protocol.
3. For ICBMs for mobile launchers of ICBMs that are maintained, stored,
and transported in launch canisters, unique identifiers shall be applied:
(a) for ICBMs existing as of Treaty signature, on each launch canister
of such ICBMs for mobile launchers of ICBMs;
(b) for ICBMs leaving the production facility after Treaty signature,
on each launch canister and on each first stage of such ICBMs for mobile
launchers of ICBMs. The data from such unique identifiers shall be provided
in a form that establishes the "one-to-one" relationship between the data
from the unique identifier applied on the first stage of an ICBM for mobile
launchers of ICBMs and the data from the unique identifier applied on the
launch canister associated with such an ICBM. Such unique identifiers may
not be changed.
4. For ICBMs for mobile launchers of ICBMs that are maintained, stored,
and transported as a unit without launch canisters or in stages, the unique
identifiers shall be applied on each first stage of such ICBMs for mobile
launchers of ICBMs.
5. During baseline data inspections, data update inspections, new
facility inspections, post-dispersal inspections of mobile launchers of
ICBMs and their associated missiles, and conversion or elimination inspections,
as well as during the conduct of continuous monitoring, inspectors or monitors
shall have the right to read the data from the unique identifiers on deployed
and non-deployed ICBMs for mobile launchers of ICBMs. Exceptions to the
right to read the data from such unique identifiers are set forth in paragraph
9 of Section VII and paragraph 11 of Section X of this Protocol.
The data from a unique identifier shall be read: (1 JCIC Agreement No.
2, Article 1, Paragraph 7.)
(a) for ICBMs specified in subparagraph 3(a) of this Annex, from the
launch canister associated with ICBMs for mobile launchers of ICBMs;
(b) for ICBMs specified in subparagraph 3(b) of this Annex, from the
launch canister associated with ICBMs for mobile launchers of ICBMs, and
if the unique identifier applied on the first stage of such a missile is
accessible for external viewing and reading without opening the launch
canister, or if during the process of elimination of such an ICBM the missile
is removed from its launch canister, from the first stage of ICBMs for
mobile launchers of ICBMs;
(c) for ICBMs specified in paragraph 4 of this Annex, from the first
stage of such ICBMs for mobile launchers of ICBMs.
6. The place from which inspectors or monitors are allowed to read data
from the unique identifier applied on each launch canister for ICBMs for
mobile launchers of ICBMs or each first stage of such an ICBM shall be
specified by a member of the in-country escort in such a manner as to ensure
an accurate reading of such data. If a unique identifier applied on a launch
canister or a first stage of an ICBM for mobile launchers of ICBMs is not
accessible for reading as provided for in paragraph 5 of this Annex, such
a unique identifier shall be duplicated on the portion of the surface of
the launch canister or the first stage of an ICBM for mobile launchers
of ICBMs that is accessible for reading its data by inspectors or monitors
during viewing.
7. For a newly-produced ICBM for mobile launchers of ICBMs, the inspected
Party shall inform the monitors of the data from the unique identifier
applied to such an ICBM, as provided for in paragraph 3 or 4 of this Annex,
before such an item exits through the portal of the monitored facility
and shall provide to the inspecting Party such data in accordance with
paragraph 3 of Section I of the Notification Protocol.
BITS
Homepage
|