![](media/image1.emf){width="4.416666666666667in"
height="1.2777777777777777in"}

**RECOMMENDATION FOR SPACE**

**DATA SYSTEMS STANDARDS**

+-----------------------------------------------------------------------+
| **CCSDS GLOBAL**                                                      |
|                                                                       |
| **SPACECRAFT IDENTIFICATION FIELD:**                                  |
|                                                                       |
| **CODE ASSIGNMENT CONTROL PROCEDURES**                                |
+-----------------------------------------------------------------------+

> ![](media/image2.emf){width="1.976388888888889in"
> height="1.5833333333333333in"}**CCSDS 320.0-B-1.1**
>
> **BLUE BOOK**
>
> October 1993

![](media/image3.emf)

**AUTHORITY**

  ---- -------------------- ------------------------------------------ ----
                                                                       

       Issue:               Blue Book, Issue 1                         

       Date:                October 1993                               

       Location:            Vienna, Austria                            

                                                                       
  ---- -------------------- ------------------------------------------ ----

This Recommendation reflects the consensus technical agreement of the
following member Agencies of the Consultative Committee for Space Data
Systems (CCSDS):

o British National Space Centre (BNSC)/United Kingdom.

o Canadian Space Agency (CSA)/Canada.

o Central Research Institute of Machine Building (TsNIIMash)/Russian
Federation.

o Centre National d\'Etudes Spatiales (CNES)/France.

o Deutsche Forschungsanstalt fŸr Luft- und Raumfahrt e.V. (DLR)/Germany.

o European Space Agency (ESA)/Europe.

o Instituto Nacional de Pesquisas Espaciais (INPE)/Brazil.

o National Aeronautics and Space Administration (NASA)/USA.

o National Space Development Agency of Japan (NASDA)/Japan.

This Recommendation is published and maintained by:

CCSDS Secretariat

Program Integration Division (Code OI)

National Aeronautics and Space Administration

Washington, DC 20546, USA

**STATEMENT OF INTENT**

The Consultative Committee for Space Data Systems (CCSDS) is an
organization officially established by the management of member space
Agencies. The Committee meets periodically to address data systems
problems that are common to all participants, and to formulate sound
technical solutions to these problems. Inasmuch as participation in the
CCSDS is completely voluntary, the results of Committee actions are
termed **RECOMMENDATIONS** and are not considered binding on any Agency.

This RECOMMENDATION is issued by, and represents the consensus of, the
CCSDS Plenary body. Agency endorsement of this RECOMMENDATION is
entirely voluntary. Endorsement, however, indicates the following
understandings:

o Whenever an Agency establishes a CCSDS-related STANDARD, this STANDARD
will be in accord with the relevant RECOMMENDATION. Establishing such a
STANDARD does not preclude other provisions which an Agency may develop.

o Whenever an Agency establishes a CCSDS-related STANDARD, the Agency
will provide other CCSDS member Agencies with the following information:

Ð The STANDARD itself.

Ð The anticipated date of initial operational capability.

Ð The anticipated duration of operational service.

o Specific service arrangements shall be made via memoranda of
agreement. Neither this RECOMMENDATION nor any ensuing STANDARD is a
substitute for a memorandum of agreement.

No later than five years from its date of issuance, this Recommendation
will be reviewed by the CCSDS to determine whether it should: (1) remain
in effect without change; (2) be changed to reflect the impact of new
technologies, new requirements, or new directions; or (3) be retired or
canceled

In those instances when a new version of a RECOMMENDATION is issued,
existing CCSDS-related Agency standards and implementations are not
negated or deemed to be non-CCSDS compatible. It is the responsibility
of each Agency to determine when such standards or implementations are
to be modified. Each Agency is, however, strongly encouraged to direct
planning for its new standards and implementations towards the later
version of the Recommendation.

# FOREWORD {#foreword .centered-heading-1}

This document is a procedural Recommendation which establishes control
procedures for Spacecraft Identification (SCID) codes. As such, it
defines the procedure governing assignment, use, relinquishment, and
management of SCIDs.

To make the most efficient use of the available identification (ID)
space in the several CCSDS-recommended data structures that contain a
SCID field, all CCSDS-compatible missions will be assigned SCIDs by a
single central authority, the World Data Center A for Rockets and
Satellites (WDC-A-R&S), located at the Goddard Space Flight Center in
Greenbelt, Maryland, USA.

As specified in this Recommendation, WDC-A-R&S will accept only requests
from designated Agency Representatives and only when received on
approved Request Forms.

This Recommendation also provides:

Ð a list of the CCSDS Agencies\' Representatives as of the date of this
document;

Ð a form for requesting and relinquishing SCIDs.

Through the process of normal evolution, it is expected that expansion,
deletion or modification to this Recommendation may occur. This
Recommendation is therefore subject to CCSDS document management and
change control procedures which are defined in ReferenceÊ\[1\].

# DOCUMENT CONTROL {#document-control .centered-heading-1}

  -------------- --------------------------- ---------- ------------------------
  **Document**   **Title**                   **Date**   **Status**

  CCSDS 320-B-1  CCSDS Global Spacecraft     October    Original Issue
                 Identification Field: Code  1993       
                 Assignment Control                     
                 Procedure                              

  CCSDS\         CCSDS Global Spacecraft     October    Current Issue. Includes
  320-B-1.1      Identification Field: Code  1993       Corrigendum 1 dated
                 Assignment Control                     November 1996 which
                 Procedure                              replaces the SCID
                                                        Request form in Annex B.

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        
  -------------- --------------------------- ---------- ------------------------

# CONTENTS {#contents .centered-heading-1}

**Sections Page**

**REFERENCES** **vi**

**1 INTRODUCTION** **1-1**

1.1 PURPOSE 1-1

1.2 BACKGROUND 1-2

1.3 GLOBAL SPACECRAFT IDENTIFIER (GSCID) 1-2

1.4 APPLICABILITY 1-3

**2 SCID CODE ASSIGNMENT CONTROL PROCEDURES** **2-1**

2.1 CCSDS SCID MANAGEMENT SYSTEM DUTIES AND RESPONSIBILITIES 2-1

2.2 SCID ASSIGNMENT REQUEST PROCEDURES 2-2

2.3 SCID CODE ASSIGNMENT PROCEDURES 2-3

2.4 SCID RELINQUISHING PROCEDURES 2-3

**ANNEX A LIST OF AGENCY REPRESENTATIVES** **A-1**

**ANNEX B SCID REQUEST FORM** **B-1**

**ANNEX C ACRONYMS AND ABBREVIATIONS** **C-1**

**Table**

1 Bit Structure of Currently Defined VN Fields 1-2

# REFERENCES {#references .centered-heading-1}

\[1\] *Procedures Manual for the Consultative Committee for Space Data
Systems*. CCSDS A00.0-Y-5. Yellow Book. Issue 5. Washington, D.C.:
CCSDS, May 1992 or later issue.

\[2\] *Telecommand Part 1ÑChannel Service*. Recommendation for Space
Data Systems Standards, CCSDS 201.0-B-1. Blue Book. Issue 1. Washington,
D.C.: CCSDS, January 1987 or later issue.

\[3\] *Packet Telemetry*. Recommendation for Space Data Systems
Standards, CCSDS 102.0-B-3. Blue Book. Issue 3. Washington, D.C.: CCSDS,
November 1992 or later issue.

\[4\] *Advanced Orbiting Systems, Networks and Data Links: Architectural
Specification*. Recommendation for Space Data Systems Standards, CCSDS
701.0-B-2. Blue Book. Issue 2. Washington, D.C.: CCSDS, November 1992 or
later issue.

\[5\] *CCSDS Global Spacecraft Identification Field: Technical
Specification for Code Assignment*. Recommendation for Space Data
Systems Standards, CCSDS 321.0-B-1. Blue Book. Issue 1. Washington,
D.C.: CCSDS, most recent issue[^1].

The latest issue of CCSDS documents may be obtained from the CCSDS
Secretariat.

# 1 INTRODUCTION

## 1.1 Purpose

This Recommendation establishes the procedures governing CCSDS
Spacecraft Identification (SCID) field codes which are contained in the
data unit formats specified in references \[2\], \[3\], and \[4\]. As
such it addresses the requesting, assigning, using, relinquishing, and
managing of SCIDs.

The purpose of the CCSDS SCID is to serve as a mechanism for the
identification of:

Ð a simple spacecraft having only one logical space-ground link; or

Ð an association between space-based and ground-based application
processes with complex spacecraft having more than one logical
space-ground link. Therefore, a single spacecraft may be assigned more
that one SCID. Rules governing the use of SCIDs in this case are
addressed in Reference \[5\].

This identification may be used only throughout a spacecraftÕs active
phases, e.g., simulations, prelaunch testing, and in-orbit operations.
As quickly as practical after reception of telemetry data, the SCID
should be replaced with a globally unique, unambiguous, permanent, and
SCID-independent label for the spacecraft and/or payload data set(s).
Thereafter, access to and identification of these data sets shall be by
means of this label rather than the SCID field described in this
document.

These procedures are intended to eliminate the possibility that data
from any given CCSDS-compatible vehicle will be falsely interpreted as
being from another CCSDS-compatible vehicle during the periods of
simulation, testing, or mission operations. Since the data structure
(synchronization code and virtual channel data unit/transfer
frame/telecommand frame) are common to many missions, misinterpretation
of the identity of space vehicle or ground-based simulator assemblies is
possible unless procedures are developed and followed to identify
uniquely each vehicle or assembly during its active phases. Because the
SCID field is only eight or ten bits long for virtual channel data units
and transfer frames respectively, the SCID is not intended to provide
unique identification for all times. It is inevitable that the SCIDs
will have to be reused; however, at any one time, the number of vehicles
under simulation, test, or active operational control is not anticipated
to exceed the available numbering domains.

As used throughout this document, the term SCID shall be construed to be
limited in scope to the CCSDS-defined data fields. Other
nonÐCCSDS-compatible data structures may also use this term; however,
this document does not apply to the assignment and use of identification
codes for nonÐCCSDS-compatible data structures. In such cases the
potential for misinterpretation is negligible because of differences in
the overall data structures.

## 1.2 Background

SCID codes appear in many of the CCSDS-recommended data structures used
for the space-ground links and other purposes. Typical of the
space-ground data structures that incorporate the SCID are:

Ð the Conventional Mission Telemetry Frame (Reference \[3\]);

Ð the Conventional Mission Telecommand Transfer Frame (Reference \[2\]);

Ð the Advanced Orbiting Systems Virtual Channel Data Unit (Reference
\[4\]).

Inasmuch as there are numerous technical and administrative
considerations attendant to SCID management and control, i.e.,
requesting, assigning, using, and relinquishing SCIDs, this document
hereby establishes procedures and guidance for SCID management and
control.

## 1.3 Global Spacecraft Identifier (GSCID)

The GSCID is defined to be the concatenation of the 2-bit Version Number
(VN) and the Spacecraft Identifier (SCID). Thus,

GSCID = VN **.** SCID

> Where Ò**.**Ó refers to the concatenation operator.

The valid range of the currently defined VN field is shown in Table 1.

Table 1: Bit Structure of Currently Defined VN Fields

+----------+------------+--------------+--------------+--------------+
| **V      | **Binary** | **Range of   | **No. of     | **Relevant** |
| ersion** |            | SCID**       | Bits**       |              |
|          | *          |              |              | **CCSDS**    |
|          | *Encoded** |              | **in SCID**  |              |
|          |            |              |              | *            |
|          | **VN**     |              | **Encoded**  | *Documents** |
+----------+------------+--------------+--------------+--------------+
| 1        | 00         | 0Ð1,023      | 10           | Ref. \[2\] & |
|          |            |              |              | \[3\]        |
+----------+------------+--------------+--------------+--------------+
| 2        | 01         | 0Ð255        | 8            | Ref. \[4\]   |
+----------+------------+--------------+--------------+--------------+
| NOTE Ð   |            |              |              |              |
| The      |            |              |              |              |
| binary   |            |              |              |              |
| encoded  |            |              |              |              |
| VN       |            |              |              |              |
| values   |            |              |              |              |
| of Ò10Ó  |            |              |              |              |
| and Ò11Ó |            |              |              |              |
| are      |            |              |              |              |
| reserved |            |              |              |              |
| for      |            |              |              |              |
| possible |            |              |              |              |
| future   |            |              |              |              |
| use and  |            |              |              |              |
| should   |            |              |              |              |
| not be   |            |              |              |              |
| used for |            |              |              |              |
| projec   |            |              |              |              |
| t-unique |            |              |              |              |
| purposes |            |              |              |              |
| prior to |            |              |              |              |
| formal   |            |              |              |              |
| a        |            |              |              |              |
| greement |            |              |              |              |
| within   |            |              |              |              |
| CCSDS    |            |              |              |              |
| for such |            |              |              |              |
| use.     |            |              |              |              |
+----------+------------+--------------+--------------+--------------+

The CCSDS Recommendations on telemetry and telecommand protocols
(references \[2\], \[3\], and \[4\]) provide a mechanism for
establishing an ASSOCIATION (either temporary or permanent) between
space-based application process(es) and corresponding ground-based
application process(es).

The data streams transmitted between space and ground processes will
contain IDENTIFIERS which will specify the relevant association. These
identifiers are MANAGED parameters (i.e., the specific association
implied by a given identifier must have been previously established).
The utilization of the SCID field on a global scale necessitates its
concatenation with other fields in the References and, therefore, the
name Global SCID or GSCID.

This document addresses the procedures related to the SCID only; the
technical considerations attending the use of the GSCID are detailed in
Reference \[5\].

## 1.4 Applicability

This Recommendation applies to all spacecraft that are compatible with
CCSDS protocols contained in those documents listed in the References
section of this Recommendation.

# 2 SCID CODE ASSIGNMENT CONTROL PROCEDURES

## 2.1 CCSDS SCID Management System Duties and Responsibilities

CCSDS SCID assignment and management, on an international basis, must be
viewed as a cooperative effort among the CCSDS Agencies, with each
constituent acting as agent for the users under its cognizance. The
management system comprises four elements:

**2.1.1** **CCSDS Secretariat** shall

2.1.1

Ð serve as the focal point for the resolution of any issues not
adequately covered by these procedures;

Ð request that CCSDS Member Agencies appoint, maintain, and replace as
necessary an official Agency Representative (AR) to handle all SCID
requests from that Agency.

**2.1.2** **CCSDS Head of Delegation** shall

Ð provide the CCSDS Secretariat and the WDC-A-R&S with the name and
address of the person authorized to be the Agency Representative (AR) as
needed to keep this information current.

NOTE Ð A list of ARs as of the date of this Recommendation is included
as Annex A.

**2.1.3** **Agency Representative (AR)** shall

Ð submit SCID requests in accordance with the provisions of this
Recommendation;

Ð interact directly with WDC-A-R&S with regard to any issues relating to
a specific SCID assignment request;

Ð monitor the life of those CCSDS missions within his/her Agency and
relinquish all SCIDs at the earliest practical time, which shall not in
any event be longer than two months after receipt of the last expected
telemetry signal;

Ð inform the applicable Agency personnel of any relevant actions (i.e.,
SCID assignment, relinquishment) taken by WDC-A-R&S relating to that
Agency.

**2.1.4** **World Data Center A for Rockets and Satellites (WDC-A-R&S)**
shall

Ð serve as the assignment manager;

Ð accept, from authorized ARs, requests for SCID assignments;

Ð review and log SCID assignment requests;

Ð assign one or more SCIDs in response to the request and notify the
appropriate AR of the assignment(s);

Ð interact directly with the appropriate AR in matters dealing with a
particular SCID assignment request;

Ð maintain complete and independent catalogs of SCID assignments for
each version number and periodically provide the catalog of currently
assigned SCIDs to the CCSDS Secretariat, CCSDS Heads of Delegation, and
Member/Observing Agency ARs;

Ð work with the respective ARs to recover all SCIDs, corresponding to
those spacecraft whose operational phases have been completed, for
subsequent reassignment.

## 2.2 SCID Assignment Request Procedures

**2.2.1** All SCID Assignment Requests by an Agency shall be submitted
by the designated AR.

**2.2.2** All SCID Assignment Requests shall be submitted on the
approved request form as contained in Annex B.

**2.2.3** A separate form shall be used for each SCID requested.

**2.2.4** All SCID Assignment Requests are to be submitted in writing
to:

> World Data Center A for Rockets and Satellites
>
> Code 633.2
>
> NASA Goddard Space Flight Center
>
> Greenbelt, MD 20771
>
> United States of America
>
> TELEX: 248496 or 197640 NASCOM GBLT
>
> TWX: 710 828 9716
>
> NSI/DECnet: NSSDC: Request
>
> TELEPHONE: +1 301 286 6695

NOTE Ð Telephone communications can be used only to request information.
They cannot be used to request SCIDs.

## 2.3 SCID Code Assignment Procedures

**2.3.1** All CCSDS SCID Assignments shall be made by the WDC-A-R&S.

**2.3.2** Each SCID Code Assignment shall be globally unique during its
assignment period.

**2.3.3** SCID Code Assignments will be made on a
spacecraft-by-spacecraft basis. User requests for reservation of a
sequence of ID numbers for unspecified spacecraft will not be accepted.
However, multiple SCIDs may be assigned for those missions which have
multiple spacecraft or which require separate designations for
protoflight spacecraft or simulations.

**2.3.4** User requests for assignment of specific numerical codes will
be accepted. However, the user should refer to the catalog of existing
SCID assignments (see 2.1.4) to avoid requesting assignments that could
result in duplication, and, therefore, denial of a request.

**2.3.5** The SCIDs that are relinquished by an Agency will not be
immediately reassigned. Rather, the relinquished SCIDs will be placed at
the bottom of the stack of unassigned SCIDs, thereby maximizing the
period of time before the relinquished number is reassigned.

## 2.4 SCID Relinquishing Procedures

**2.4.1** The AR shall determine, in conjunction with the mission
manager, exactly when the operational phase of a mission is complete and
when the related SCIDs can be relinquished.

**2.4.2** The AR will submit to WDC-A-R&S a copy of the original
Assignment Request/ Relinquishment form with the section entitled,
ÒRELINQUISHMENT AUTHORIZATIONÓ completed and signed. If the original
Assignment Request/Relinquishment form cannot be located, a simple
letter relinquishing the SCID will be acceptable.

**2.4.3** WDC-A-R&S will place that SCID code number at the bottom of
the stack of SCIDs available for assignment.

#          ANNEX A {#annex-a .centered-heading-1}

# LIST OF AGENCY REPRESENTATIVES {#list-of-agency-representatives .centered-heading-1}

(THIS ANNEX **IS NOT** PART OF THE RECOMMENDATION)

**Purpose:**

This annex contains complete address information, as of the date of this
Recommendation, for the official CCSDS Agency Representatives. The
authorization and functions of Agency Representatives are defined in
2.1.2 and 2.1.3.

The following is the list of Agency Representatives who are authorized
to officially request Spacecraft Identification Code Assignments (these
are not the same individuals in every instance as the Heads of
Delegation listed in the CCSDS Procedures Manual, reference \[1\]):

[Member Agencies]{.underline}

British National Space Centre (BNSC)/UK

Mr. Peter A. Vaughan

British National Space Centre

Rutherford Appleton Laboratory

Building R68

Chilton, Didcot

Oxfordshire OX11 OQX

United Kingdom

TEL: +44 0235 44 6269

FAX: +44 0235 44 6667

TELEX: 83159

E-Mail: (c:usa, admd:telemail, prmd:nasamail, o:nasa, un:jplral) with
attention line; Internet: pav@sdel.bnsc.rl.ac.uk *or*
ccsds@sdel.bnsc.rl.ac.uk

Canadian Space Agency (CSA)/ Canada

Dr. Arvind Bastikar

Canadian Space Agency

3701 Carling Avenue

P.O. Box 11490, Station H

Ottawa, Ontario K2H 8S2

Canada

TEL: +1 613 990 8953

FAX: +1 613 990 9155

TELEX: 053 4143 COMRESCEN OTT

E-mail: (c:canada, pub:telecom.canada, id:chambers.jg, o:gemdes)
Attention CSA: Please forward to A. Bastikar

Central Research Institute of Machine Building (TsNIIMash)/Russian
Federation

Mr. O. D. Sokolov

Division Director, TsNIIMash

141070 Kaliningrad

Pionerskaya Ulica 4

Moscovskaya oblast

Russian Federation

TEL: +7 095 581 92 66

FAX: +7 095 274 00 25

TELEX: 411952 MCC SU

E-mail:

Centre National DÕEtudes Spatiales (CNES)/France

Mr. Richard Simo-Pons

Sous Directeur de l\'Exploitation des Systems Operationnels

CNES/Centre Spatial de Toulouse (EO/D)

18, Avenue Edouard Belin

31055 Toulouse Cedex

France

TEL: +33 61 27 45 13 or +33 61 27 44 45 (G. Cales)

FAX: +33 61 27 31 35

TELEX: 531 081 F

E-mail: (o:j.p.l., sn:spatiales, fn:centre, i:n, site:telemail) with
attention line

Deutsche Forschungsanstalt fŸr Luft- und Raumfahrt e.V. (DLR)/Germany

Mr. Hubertus Wanke, Head

Mission Operations Department

DLR/German Space Operations Centre

DLR/GSOC/MB

MŸnchner Stra§e 20, Oberpfaffenhofen

D-82234 Wessling

Germany

TEL: +49 8153 282 755

FAX: +49 8153 281 455

TELEX:

E-mail: (c:usa, admd:telemail, o:j.p.l., un:jplgsoc) with attention line

European Space Agency (ESA)/Europe

Dr. Hans Uhrig

Robert Bosch Stra§e 5

D-64293 Darmstadt

Germany

TEL: +49 6151 902 352

FAX: +49 6151 90495

TELEX:

E-mail: (c:usa, admd:telemail, o:esa, un:esa.huhrig)

Instituto Nacional de Pesquisas Espaciais (INPE)/Brazil

Dr. Eduardo W. Bergamini, Responsible

Activity of Application Services in Space Missions

Instituto Nacional de Pesquisas Espaciais

Avenida dos Astronautas, 1758

Caixa Postal 515

Sao Jose dos Campos, SP

12.201-970 Brazil

TEL: +55 123 41 89 77 x385

FAX: +55 123 21 87 43

TELEX: 011 33530

E-mail: ( sn:bergamini, fn:eduardo, i:w, site:j.p.l. )\
Internet: inpecomp@fpsp.fapesp.br

National Aeronautics and Space Administration (NASA)/USA

Mr. Joseph Deskevich

NASA/Goddard Space Flight Center (Code 502)

Greenbelt, MD 20771

U.S.A.

TEL: +1 301 286 8371

FAX: +1 301 286 1725

TELEX:

E-mail: (c:usa, a:telemail, p:gsfc, o:gsfcmail, un:jdeskevich)

National Space Development Agency of Japan (NASDA)/Japan

Mr. Masaru Oyama, Director

Tracking and Data Acquisition Department

National Space Development Agency of Japan

2-4-1 Hamamatsucho

Minato-ku, Tokyo 105

Japan

TEL: +81 3 5470 4302

FAX: +81 3 5470 4327

TELEX: J28424(AAB:NASDAJ28424)

E-mail: (sn:nasda, fn:ccsds, prmd:nasdass, admd:ati, c:japan) with
attention line

[Observer Agencies]{.underline}

Australian Space Office (ASO)/Australia

Mr. Peter N. Churchill

Australian Space Office

Department of Industry, Technology, and Commerce

P.O. Box 269

Civic Square, ACT 2608

Australia

TEL: +61 6 276 1340

FAX: +61 6 276 1942

TELEX: AA 62654

E-mail:

Austrian Space Agency (ASA)/Austria

Professor Johannes Ortner

Managing Director

Austrian Space Agency

Garnisongasse 7

A-1090 Wien

Austria

TEL: +43 1 403 81 77

FAX: +43 1 42 82 28

TELEX: 116560 ASA A

E-mail:

Belgian Science Policy Office (SPO)/Belgium

Mr. G. Thibaut

Belgian Science Policy Office

Rue de la Science, 8

B-1040 Bruxelles

Belgium

TEL: +32 2 238 34 11

FAX: +32 2 230 59 12

TELEX: 24501 prosci b

E-mail:

Centro Tecnico Aeroespacial/Instituto de Aeronautica e Espaco
(CTA/IAE)/Brazil

Diretor do CTA/IAE

Avenida: Dr. Nelson D\'Avila, S/N

12.228-904 Sao Jose dos Campos, SP

Brazil

TEL: +55 0123 41 46 11 x3409

FAX: +55 0123 41 25 22

TELEX: 0123 3393 CTAE BR

E-mail:

Chinese Academy of Space Technology (CAST)/People\'s Republic of China

Professor Chen Daoming

Vice President, Committee of Science & Technology

No. 31, Baishiqiao Lu

P.O. Box 2417

Beijing 100081

Peoples Republic of China

TEL: +86 1 837 8233

FAX: +86 1 8378237

TELEX: 22473 CCSC CN

E-mail:

Communications Research Laboratory (CRL)/Japan

Dr. Takashi Iida

Director of Space Communications Division

Communications Research Laboratory

4-2-1 Nukuikita-machi, Koganei-shi

Tokyo 184

Japan

TEL: +81 423 27 7501

FAX: +81 423 27 6698

TELEX: 2832611 DEMPAJ

E-mail:

Danish Space Research Institute (DSRI)/Denmark

Dr. Allan Hornstrup

Danish Space Research Institute

Gl. Lundtoftevej 7

DK-2800 Lyngby

Denmark

TEL: +45 42 88 22 77

FAX: +45 45 93 02 83

TELEX: 37198

E-mail: allan@danru.dk

European Organization for the Exploitation of Meteorological Satellites
(EUMETSAT)/Europe

Mr. R. Wolf

EUMETSAT

Am Elfengrund 45

D-6100 Darmstadt-Eberstadt

Germany

TEL: +49 61 51 53 92 0

FAX: +49 61 51 53 92 25

TELEX: 4 197 335 emet d

E-mail:

European Telecommunications Satellite Organization (EUTELSAT)/Europe

Mr. Manual Calvo

Head of TCR Section, EUTELSAT

33, Avenue de Maine

Tour Maine-Moniparnasse

75755 Paris Cedex 15

France

TEL: +33 1 40 47 34 51

FAX: +33 1 43 22 07 08

TELEX: 203 823 EUSAT

E-mail:

Hellenic National Space Committee (HNSC)/Greece

Dr. L. N. Mavridis, President

NCSR \"Demokritos\"

Agia Paraskevi, Attikis

GR-15310

Athens

Greece

TEL: +30 1 6524965

FAX: +30 1 6532122

TELEX:

E-mail:

Indian Space Research Organization (ISRO)/India

Mr. P. Soma

SOCG Manager

Indian Space Research Organization

ISRO Telemetry, Tracking and Command Network (ISTRAC)

1st Cross, Peenya Industrial Estate

Bangalore 56058

India

TEL:

FAX:

TELEX:

E-mail:

Industry Canada/Communications Research Center (CRC)

Mr. J. D. Andean

Satellite Communications Directorate

Industry Canada/Communications Research Center

3701 Carling Avenue

P.O. Box 11490, Station H

Ottawa, Ontario, K2H 8S2

Canada

TEL: +1 613 998 2535

FAX: +1 613 990 6339

TELEX: 053 3342 COMTEL OTT

E-mail: (c:canada, a:telecom.canada, o:gemdes, id:andean.d)

Institute for Space Astronautics and Science (ISAS)/Japan

Professor Ichiro Nakatani

Spacecraft Engineering Division

Institute for Space Astronautics and Science

3-1-1 Yoshinodai

Sagamihara-shi 229

Japan

TEL: +81 427 51 3911

FAX: +81 427 59 4251

TELEX:

E-mail: (c:usa, admd:telemail, o:intec, sn:isas, fn:nakatani)

Institute of Space Research (IKI)/Russian Federation

Dr. R. Nazirov

IKI - Space Research Institute

Profsojusnaya 84/32

117810 Moscow

Russian Federation

TEL: +7 095 333 50 89

FAX: +7 095 310 70 23

TELEX: 411498 STAR SU

E-mail: RNAZ1ROV@ESOC1.BITNET

KFKI Research Institute for Particle & Nuclear Physics (KFKI)/Hungary

Dr. Andras Varga, Head

Dept. of Space Physics

POB 49

H-1525 Budapest

Hungary

TEL: +36 1 155 1682 or +36 1 155 3494

FAX: +36 1 169 6567 or +36 1 155 3894

TELEX: AA 62654

E-mail: Y6010NE1@AWIIEZZ11.BITNET via EARN (BITNET)\
(please include \"A. Varga\" in subject line)

MIKOMTEK: CSIR (CSIR)/Republic of South Africa

Mr. W. J. Botha

Programme Manager, Satellite Applications

MIKOMTEK: CSIR

P.O. Box 395

Pretoria 0001

Republic of South Africa

TEL: +27 11 642 4692

FAX: +27 11 642 2446

TELEX: 3-21005 SAC SA

E-mail:

Ministry of Communications (MOC)/Israel

Mr. S. Klepner

Director of Engineering and Licensing

Ministry of Communications

P.O. Box 29107

61290 Tel Aviv

Israel

TEL: +972 3 5126276

FAX: +872 3 5126244

TELEX: 371565 DRENG IL

E-mail:

National Oceanic and Atmospheric Administration (NOAA)/USA

Mr. George W. Saxton

NESDIS/Data Management Division (Code OSD5)

National Oceanic & Atmospheric Administration

FOB 4, Room 3316

Suitland, MD 20233

USA

TEL: +1 301 763 4640

FAX: +1 301 420 0932

TELEX:

E-mail: (c:usa, pub:telemail, pvt:telemail, o:nesdis, un:gsaxton)

Swedish Space Corporation (SSC)/Sweden

Mr. Lennart Marcus

Director of Engineering

Swedish Space Corporation

Box 802

S-981 28 Kiruna

Sweden

TEL: +46 980 72000

FAX: +46 980 21331

TELEX: 8744 Esrange S

E-mail:

United States Geological Survey (USGS)/USA

Mr. Tom Kalvelage

EROS Data Center

United States Geological Survey

Sioux Fall, SD 57198

USA

TEL: +1 605 594 6556

FAX:

TELEX:

E-mail:

#            ANNEX B {#annex-b .centered-heading-1}

# SCID REQUEST FORM {#scid-request-form .centered-heading-1}

(THIS ANNEX **IS** PART OF THE RECOMMENDATION)

**Purpose:**

This annex provides the official form to be used by Agency
Representatives for requesting and relinquishing SCIDs.

**TO:** World Data Center A for Rockets & Satellites (WDC-A-R&S), Code
633,

NASA/Goddard Space Flight Center, Greenbelt, Maryland 20771, USA.

**FROM:** (Name & Address of Agency Representative)

> E-MAIL
>
> Telephone Facsimile TELEX\
> (Include Country & City/Area Codes

**SPACECRAFT INFORMATION:**

> Pre-Launch Name of Spacecraft:
>
> Transmitting Frequencies:
>
> Expected Launch Date (or Year):
>
> Version ID (see table 1): Version-1 Version-2
>
> Intended Use: TLM only TC only Both TLM & TC
>
> (TLM = telemetry; TC = telecommand)

**SPECIAL INSTRUCTIONS/REQUEST:**

**AUTHORIZATION:** (to assign or to relinquish GSCID assignment)

> ASSIGN new GSCID:
>
> Signature of Agency Representative Date
>
> RELINQUISH current GSCID:
>
> Signature of Agency Representative Date

#          ANNEX C {#annex-c .centered-heading-1}

#  {#section .centered-heading-1}

#  {#section-1 .centered-heading-1}

# ACRONYMS AND ABBREVIATIONS {#acronyms-and-abbreviations .centered-heading-1}

(THIS ANNEX **IS NOT** PART OF THE RECOMMENDATION)

**Purpose:**

This annex defines acronyms and abbreviations used in this
Recommendation.

For the purposes of this Recommendation, the following definitions
apply.

[Term]{.underline} [Meaning]{.underline}

AR Agency Representative

CCSDS Consultative Committee for Space Data Systems

GSCID Global SCID

Hex Hexadecimal

NSSDC National Space Science Data Center

TC Telecommand

TLM Telemetry

S/C Spacecraft

SCID Spacecraft Identification

VN Version Number

WDC-A-R&S World Data Center A for Rockets and Satellites

[^1]: At time of publishing, this document was under development.