CONSOLIDATED REPORT

of the

ARGOS OPERATIONS COMMITTEE MEETINGS

JUNE 2006

(Revision 13)

A Cooperative Project:

Centre National d\'Etudes Spatiales (CNES, France)

National Oceanic & Atmospheric Administration (NOAA, USA)

National Aeronautics & Space Administration (NASA, USA)

TABLE OF CONTENTS

[Section 0. INTRODUCTION 1](#introduction)

[Section 1. MEMORANDUMS OF UNDERSTANDING
2](#memorandums-of-understanding)

[1.1 INITIAL MEMORANDUM OF UNDERSTANDING
2](#initial-memorandum-of-understanding)

[1.1.1 PURPOSE 2](#purpose)

[1.1.2 CHANGES / AMENDMENTS 2](#changes-amendments)

[1.1.3 FINAL DRAFT APPROVAL 4](#final-draft-approval)

[1.2 NEW MEMORANDUM OF UNDERSTANDING
4](#new-memorandum-of-understanding)

[1.2.1 INCEPTION 4](#inception)

[1.2.2 BASIC AGREEMENT 4](#basic-agreement)

[1.2.3 STATUS, CHANGES & AMENDMENTS 4](#status-changes-amendments)

[1.3 JOINT PROJECT PLAN 8](#joint-project-plan)

[1.3.1 WORKING LEVEL DOCUMENT 8](#working-level-document)

[1.3.2 STATUS, CHANGES & AMENDMENTS 8](#status-changes-amendments-1)

[Section 2. OPERATIONS COMMITTEE & MEETINGS
9](#operations-committee-meetings)

[2.1 CHARTER & RESPONSIBILITIES 9](#charter-responsibilities)

[2.1.1 REPRESENTATION 9](#representation)

[2.1.2 RESPONSIBILITIES 9](#responsibilities)

[2.2 FREQUENCY & FORMAT OF MEETINGS 10](#frequency-format-of-meetings)

[2.2.1 MEETING FREQUENCY (AMENDMENTS) 10](#meeting-frequency-amendments)

[2.2.2 MEETING FORMAT 10](#meeting-format)

[2.3 MEETING ATTENDEES 11](#meeting-attendees)

[2.3.1 POLICY 11](#policy)

[2.3.2 MEETINGS AND CO-CHAIRS 11](#meetings-and-co-chairs)

[2.4 MEETING MINUTES 12](#meeting-minutes)

[2.4.1 Distribution of Meeting Minutes
12](#distribution-of-meeting-minutes)

[2.4.2 Special Requirements 12](#special-requirements)

[2.5 CONSOLIDATED REPORT 12](#consolidated-report)

[2.5.1 PURPOSE 12](#purpose-1)

[2.5.2 STATUS, CHANGES & AMENDMENTS 12](#status-changes-amendments-2)

[2.6 ORGANIZATIONAL ISSUES 14](#organizational-issues)

[2.6.1 CNES (ARGOS) ORGANIZATION 14](#cnes-argos-organization)

[2.6.2 U.S. Argos Representative 14](#u.s.-argos-representative)

[2.6.3 CNES Subsidiaries 15](#cnes-subsidiaries)

[2.6.4 CLS Organization 15](#cls-organization)

[2.7 GEOSTAR AND CNES 16](#geostar-and-cnes)

[2.7.1 GEOSTAR DEVELOPMENT 16](#geostar-development)

[2.8 FISHING VESSEL MONITORING (IN U.S. WATERS)
16](#fishing-vessel-monitoring-in-u.s.-waters)

[2.8.1 Project Development 16](#project-development)

[2.8.2 Impact on System 16](#impact-on-system)

[2.9 METEOSAT AND GOES AND CLS 16](#meteosat-and-goes-and-cls)

[2.9.1 MAEDS 16](#maeds)

[2.10 Global Learning and Observations to Benefit the Environment
(GLOBE)
17](#global-learning-and-observations-to-benefit-the-environment-globe)

[2.11 CONFIDENTIAL TREATMENT OF DATA FROM THE ARGOS SYSTEM
17](#confidential-treatment-of-data-from-the-argos-system)

[2.11.1 Terms and Conditions 17](#terms-and-conditions-1)

[2.12 Joint Working Group 17](#joint-working-group)

[2.12.1 MEMBERSHIP 17](#membership)

[2.12.2 RESPONSIBILITIES 17](#responsibilities-1)

[2.12.3 O/C RELATIONSHIP 17](#oc-relationship)

[2.13 STATUS, CHANGES & AMENDMENTS 17](#status-changes-amendments-3)

[2.13.1 CNES/NOAA WORKING GROUP 17](#cnesnoaa-working-group)

[2.13.2 TECHNICAL ADVISORY GROUP 18](#technical-advisory-group)

[2.14 CANSAT 18](#cansat)

[2.15 Review of other systems 18](#review-of-other-systems)

[2.15.1 ORBCOMM: 18](#orbcomm)

[2.15.2 GSP: 18](#gsp)

[Section 3. Terms of Reference 19](#terms-of-reference)

[3.1 Terms of Reference 19](#terms-of-reference-1)

[3.1.1 Operations Committee 19](#operations-committee)

[3.1.2 Objectives of the Operations Committee
19](#objectives-of-the-operations-committee)

[3.1.3 Membership 20](#membership-1)

[3.1.4 Organization 20](#organization)

[3.1.5 Procedures 20](#procedures)

[3.1.6 Decision-making 21](#decision-making)

[3.1.7 Amendment 21](#amendment)

[3.1.8 Effective Date and Duration 21](#effective-date-and-duration)

[3.1.9 Procedures for System Use Agreement Approval
21](#procedures-for-system-use-agreement-approval)

[3.2 Terms of Reference for Expanded Operations Committee
22](#terms-of-reference-for-expanded-operations-committee)

[Section 4. Global System Use Policy 23](#__RefHeading___Toc137347027)

[4.1 Background 23](#__RefHeading___Toc137347028)

[4.2 Argos System Use Policy 23](#__RefHeading___Toc137347029)

[4.2.1 Scope 23](#__RefHeading___Toc137347030)

[4.2.2 Definitions 23](#__RefHeading___Toc137347031)

[4.2.3 Use of Argos Data Collection System
25](#__RefHeading___Toc137347032)

[4.2.4 Argos Data Collection System Use Agreements
25](#__RefHeading___Toc137347033)

[4.2.5 Treatment of Data 26](#__RefHeading___Toc137347034)

[4.3 Understandings 27](#__RefHeading___Toc137347035)

[4.4 Specific Responsibilities of the User
27](#__RefHeading___Toc137347036)

[4.5 Specific Responsibilities of Operator
28](#__RefHeading___Toc137347037)

[4.6 Disclaimers 28](#__RefHeading___Toc137347038)

[4.7 Period of Use/Termination 28](#__RefHeading___Toc137347039)

[4.8 Dispute Settlement 29](#__RefHeading___Toc137347040)

[Section 5. SPACE Segment 30](#space-segment)

[5.1 SPACECRAFT Issues 30](#spacecraft-issues)

[5.1.1 TIROS-N TYPE SPACECRAFT 30](#tiros-n-type-spacecraft)

[5.1.2 SPACECRAFT CALLUP 30](#spacecraft-callup)

[5.1.3 ADVANCED TIROS-N TYPE SPACECRAFT
30](#advanced-tiros-n-type-spacecraft)

[5.1.4 NOAA-D SPACECRAFT 31](#noaa-d-spacecraft)

[5.1.5 NOAA-F, G SPACECRAFT 32](#noaa-f-g-spacecraft)

[5.1.6 NOAA-H, I and J SPACECRAFT 33](#noaa-h-i-and-j-spacecraft)

[5.1.7 NOAA-K, L and M SPACECRAFT 34](#noaa-k-l-and-m-spacecraft)

[5.1.8 POST NOAA-M ERA 36](#post-noaa-m-era)

[5.1.9 NPOESS : 41](#npoess)

[5.2 SYSTEM CONFIGURATION 44](#system-configuration)

[5.2.1 ORBIT CONFIGURATION 44](#orbit-configuration)

[5.2.2 ONE SPACECRAFT SYSTEM (One or Two Instruments in Orbit)
44](#one-spacecraft-system-one-or-two-instruments-in-orbit)

[5.2.3 Argos Study: 45](#argos-study)

[5.2.4 TWO SPACECRAFT SYSTEM 45](#two-spacecraft-system)

[5.2.5 THIRD SPACECRAFT DATA 45](#third-spacecraft-data)

[5.2.6 Alternate operational scenarios
45](#alternate-operational-scenarios)

[5.3 INSTRUMENTATION 46](#instrumentation)

[5.3.1 INSTRUMENTS FOR NOAA-H, I AND J
46](#instruments-for-noaa-h-i-and-j)

[5.3.2 INSTRUMENTS FOR NOAA-K,L,M 47](#instruments-for-noaa-klm)

[5.3.3 INSTRUMENTS FOR POST-NOAA-M 48](#instruments-for-post-noaa-m)

[5.3.4 SHUTTLE COMPATIBILITY 56](#shuttle-compatibility)

[5.3.5 INTERCHANGEABILITY OF INSTRUMENTS
57](#interchangeability-of-instruments)

[5.3.6 INSTRUMENTS ON SPARE SATELLITES IN STORAGE
57](#instruments-on-spare-satellites-in-storage)

[5.3.7 EXPERIMENTS WITH SPACECRAFT THAT HAVE EXPERIENCED MAJOR SYSTEM
FAILURES
57](#experiments-with-spacecraft-that-have-experienced-major-system-failures)

[5.4 PROCEDURES 58](#procedures-1)

[5.4.1 LAUNCH AND POST-LAUNCH 58](#launch-and-post-launch)

[5.4.2 SPACECRAFT INSTRUMENT RECONFIGURATION
58](#spacecraft-instrument-reconfiguration)

[5.5 FREQUENCIES 59](#frequencies)

[5.5.1 Non-Environmental DATA 59](#non-environmental-data)

[5.5.2 Wind Profiler Radar (WPR) 59](#wind-profiler-radar-wpr)

[5.5.3 FCC LICENSING REQUIREMENTS 59](#fcc-licensing-requirements)

[5.6 ARGOS-2 and NOAA-Next 59](#argos-2-and-noaa-next)

[5.7 BRAZILIAN DCS 59](#brazilian-dcs)

[Section 6. GROUND SYSTEM 64](#ground-system)

[6.1 NESDIS PROCESSING CENTER (DPSS) 64](#nesdis-processing-center-dpss)

[6.1.1 DATA FRAGMENTATION 64](#data-fragmentation)

[6.1.2 DATA TRANSMISSION DELAYS 64](#data-transmission-delays)

[6.1.3 INTERFACE FOR SYSTEM PROBLEMS 65](#interface-for-system-problems)

[6.1.4 DATA-GAPS 65](#data-gaps)

[6.1.5 DATA PROCESSING PROBLEMS 65](#data-processing-problems)

[6.1.6 OPERATIONAL REPORTS 66](#operational-reports)

[6.1.7 ENHANCEMENTS 66](#enhancements)

[6.1.8 Performance 68](#performance)

[6.2 ARGOS PROCESSING CENTER (APC) 69](#argos-processing-center-apc)

[6.2.1 DATA TRANSMISSION DELAYS 69](#data-transmission-delays-1)

[6.2.2 DATA-GAP REPORTS 70](#data-gap-reports)

[6.2.3 OPERATIONAL REPORTS 70](#operational-reports-1)

[6.2.4 ENHANCEMENTS 70](#enhancements-1)

[6.3 COMMUNICATIONS 79](#communications)

[6.3.1 SUITLAND/NEW YORK/MAINE PROBLEMS
79](#suitlandnew-yorkmaine-problems)

[6.3.2 TELETYPE PROBLEMS 79](#teletype-problems)

[6.3.3 PROCEDURES FOR PROBLEMS 80](#procedures-for-problems)

[6.3.4 New communications means 80](#new-communications-means)

[6.4 DATA TRANSFER 81](#data-transfer)

[6.4.1 PROCESSED DATA TRANSFER 81](#processed-data-transfer)

[6.4.2 UNPROCESSED DATA TRANSFER, POLICY
82](#unprocessed-data-transfer-policy)

[6.4.3 DIRECT READOUT STATIONS 82](#direct-readout-stations)

[6.5 DATA DISSEMINATION & COMMUNICATION
83](#data-dissemination-communication)

[6.5.1 Global Telecommunications System (GTS)
83](#global-telecommunications-system-gts)

[6.5.2 Constant Level Balloon & Drifting Buoy Codes
84](#constant-level-balloon-drifting-buoy-codes)

[6.5.3 HYDRA Code 84](#hydra-code)

[6.5.4 Data Format Standardization 84](#data-format-standardization)

[6.5.5 Data Format Dissemination 84](#data-format-dissemination)

[6.6 ORBITOGRAPHY 84](#orbitography)

[6.6.1 Orbitography Platform Location
84](#orbitography-platform-location)

[6.6.2 Proposed Relocation of Orroral Platform
85](#proposed-relocation-of-orroral-platform)

[6.6.3 Spare Parts and Test Equipment Procedures
85](#spare-parts-and-test-equipment-procedures)

[6.7 SYSTEM PERFORMANCE EVALUATION 85](#system-performance-evaluation)

[6.7.1 System Location Accuracy Evaluation
85](#system-location-accuracy-evaluation)

[6.7.2 System Monitoring Requirements
85](#system-monitoring-requirements)

[6.8 TRANSMISSION CONSTRAINTS 85](#transmission-constraints)

[6.8.1 System Saturation Determination
85](#system-saturation-determination)

[6.8.2 Performance Management Tools 86](#performance-management-tools)

[6.9 Data Collection Platforms 86](#__RefHeading___Toc137347116)

[6.9.1 CERTIFICATION 86](#__RefHeading___Toc137347117)

[6.9.2 Certification Proposal 86](#__RefHeading___Toc137347118)

[6.9.3 Platform Certification 86](#__RefHeading___Toc137347119)

[6.9.4 Certification Withdrawal 86](#__RefHeading___Toc137347120)

[6.9.5 Certification Specifications 86](#__RefHeading___Toc137347121)

[6.10 PROBLEMS 87](#__RefHeading___Toc137347122)

[6.10.1 INDIAN SPACECRAFT 87](#__RefHeading___Toc137347123)

[6.10.2 USER PROBLEM DOCUMENTATION 87](#__RefHeading___Toc137347124)

[6.10.3 PLATFORM COSTS 87](#__RefHeading___Toc137347125)

[6.11 IDENTIFICATION CODES 87](#__RefHeading___Toc137347126)

[6.11.1 ISSUANCE & DURATION 87](#__RefHeading___Toc137347127)

[6.11.2 ELIMINATION PROCEDURE 87](#__RefHeading___Toc137347128)

[6.12 REGISTRATION 88](#__RefHeading___Toc137347129)

[6.12.1 PROCEDURE & POLICY 88](#__RefHeading___Toc137347130)

[Section 7. User Services and System Use
90](#user-services-and-system-use)

[7.1 SYSTEM PROMOTION & PUBLICITY 90](#system-promotion-publicity)

[7.1.1 POLICY 90](#policy-1)

[7.1.2 RELEASE OF TECHNICAL INFORMATION
94](#release-of-technical-information)

[7.1.3 ARGOS NEWSLETTER 94](#argos-newsletter)

[7.1.4 MONTHLY REPORTS 95](#monthly-reports)

[7.1.5 CONFERENCES AND WORKSHOPS 95](#conferences-and-workshops)

[7.2 APPLICATION FOR SYSTEM USE 96](#application-for-system-use)

[7.2.1 ADMISSION CATEGORIES 96](#admission-categories)

[7.2.2 ADMISSION POLICIES 96](#admission-policies)

[7.2.3 GOVERNMENT SPONSOR LIST 99](#government-sponsor-list)

[7.2.4 RENEWAL OF PROGRAMS 99](#renewal-of-programs)

[7.2.5 USERS MEMORANDUM OF AGREEMENT 99](#users-memorandum-of-agreement)

[7.2.6 ACCESS PROCEDURE 99](#access-procedure)

[7.2.7 NEW ADMISSION PROCEDURE 100](#new-admission-procedure)

[7.2.8 PROGRAMS USING DIRECT READOUT STATIONS
102](#programs-using-direct-readout-stations)

[7.2.9 CHANGING PLATFORM USE WITHOUT NOTIFICATION
102](#changing-platform-use-without-notification)

[7.2.10 SUA Renewal Letter and Data Denial Policy
102](#sua-renewal-letter-and-data-denial-policy)

[7.2.11 USER INTERFACE 103](#user-interface)

[7.2.12 USER GUIDANCE OFFICE 103](#user-guidance-office)

[7.3 Electronic SUA submission Process
104](#electronic-sua-submission-process)

[7.3.1 Electronic SUA structure (Submitted 37th O/C)
104](#electronic-sua-structure-submitted-37th-oc)

[7.3.2 System Operation 104](#system-operation)

[7.3.3 Assigned Approvers 104](#assigned-approvers)

[7.3.4 Review Strategies 104](#review-strategies)

[7.3.5 Processing Steps 105](#processing-steps)

[7.3.6 Summary 106](#summary)

[7.3.7 Electronic SUA Implementation
106](#electronic-sua-implementation)

[7.4 SYSTEM USE 106](#system-use)

[7.4.1 Initial System Activity 106](#initial-system-activity)

[7.4.2 Operational Activity 106](#operational-activity)

[7.5 EVOLUTION OF THE ARGOS PROGRAM
115](#evolution-of-the-argos-program)

[Section 8. Joint TARIFF Agreement 119](#joint-tariff-agreement)

[8.1 POLICY 119](#policy-2)

[8.1.1 GENERAL 119](#general-1)

[8.2 TARIFF PRICE STRUCTURE 119](#tariff-price-structure)

[8.2.1 GUIDELINES 119](#guidelines)

[8.2.2 DETERMINING TARIFF CHANGES 120](#determining-tariff-changes)

[8.2.3 DATA PROCESSING COSTS 120](#data-processing-costs)

[8.3 PROCESSING AGREEMENT 121](#processing-agreement)

[8.3.1 GENERAL 121](#general-2)

[8.3.2 PRICING STRUCTURE, CHANGE PROPOSALS
121](#pricing-structure-change-proposals)

[8.4 Joint TAriff agreement meetings
123](#joint-tariff-agreement-meetings)

[8.4.1 Annual meeting, reports 123](#annual-meeting-reports)

[8.5 Status of U.S. processing agreement
126](#status-of-u.s.-processing-agreement)

[8.6 Financial status of Service Argos
128](#financial-status-of-service-argos)

[Section 9. O/C MEETING Action Items 131](#oc-meeting-action-items)

[Section 10. O/C MEETING Open Actions 160](#oc-meeting-open-actions)

[Section 11. ANNEX 1](#annex)

[11.1 Argos DCS Program and Policy Documents
1](#argos-dcs-program-and-policy-documents)

# INTRODUCTION

This Consolidated Report of the Argos Operations Committee (O/C)
Meetings is designed to provide highlights from past meetings. Included
are both decisions made and the rationale behind them. Entries are
identified by applicable meeting number. For more detail please refer to
specific meeting minutes.

During the 28th O/C Meeting , it was recognized that specific items for
inclusion in the Report had not been identified at each meeting since
the last update (1989). Thus, it was decided that a draft would be
prepared by assigned authors for review by the Committee. The Committee
then would decide on what was to be retained or subsequently added.
Guidelines for this Report include.

1\. All pages that contain additions or changes from the last version
will be indicated in the upper right-hand corner with the revision
number.

2\. The paragraphs added or changed will be identified by a vertical
line in the left-hand margin opposite the paragraph.

3\. The title page will be replaced with each revision and will contain
the revision number and date.

4\. Pages affected by revisions on previous pages, but containing no new
material, (i.e., due to re-pagination) will not be identified as
revised.

# MEMORANDUMS OF UNDERSTANDING

## INITIAL MEMORANDUM OF UNDERSTANDING

### PURPOSE

The initial Memorandum of Understanding (MOU) was prepared and signed in
1974. It reflected the desire to conduct a space applications project of
mutual interest and for peaceful purposes by the National Aeronautics
and Space Administration (NASA) and the National Oceanic and Atmospheric
Administration (NOAA) of the United States of America, and the Centre
National d\'Etudes Spatiales (CNES) of France.

#### Access to Users Data

The MOU adequately covers the access to operational and experimental
users\' data. Although an industrial user\'s data are not covered in the
MOU, Service Argos will refer any industrial user\'s request to the O/C
for evaluation. See System Use Admission Policies. (7th O/C Meeting)

#### Data Availability

Users have expressed the feeling that if they pay for the data
collection then their data should be only available to them. This is
contrary to the policy of U.S. satellite data availability which is that
data are considered in the public domain. The MOU clearly states this in
paragraph 7b(4). (6th O/C Meeting)

NOAA reaffirmed this policy at the 13th O/C Meeting.

### CHANGES / AMENDMENTS

#### Paragraph 2a(6)

Change from \"NASA providing CNES ephemeris data\" to \"NESDIS providing
CNES ephemeris data.\" (1st O/C)

#### Paragraph 5

Change from \"assignment of call letters\" to assignment of
identification codes.\" (1st O/C)

#### General

\"National Environmental Satellite Service\" to be changed to \"National
Earth Satellite Service\" wherever it appears in the MOU. (14th O/C)

#### Additional Spacecraft

To properly reflect the additional spacecraft in the series, several
changes were made to the MOU of 1974. (14th O/C)

#### Proprietary Data

NOAA has agreed that private users may request and be authorized the
proprietary treatment of their data provided they qualify under the
specified circumstances. This policy will be valid for 3 years and, at
the end of that time, it will be reviewed in the light of use and
applicability. (15th O/C)

#### Proprietary Data Requests

Proposals involving provision for intellectual property rights of
principle investigators will be considered on a case-by-case basis.
(15th O/C)

##### Terms and Conditions:

The specific terms and conditions are:

a\. Only private users can request proprietary treatment of data.

b\. Data considered for proprietary treatment must be confidential
commercial information or trade secrets.

c\. There must be identified both a U.S. and French government agency
need for some or all of these data.

d\. Data required to protect life and property will not be considered
for proprietary treatment.

e\. NOAA and CNES will not release conversion information for data
collected on a proprietary basis. However, NOAA and CNES cannot
guarantee confidentiality of data that is received at direct readout
facilities. (15th O/C)

##### Information Required:

The following information shall be required on the application form
submitted by users applying for privileged or confidential treatment of
data:

1\) The names of government agencies in France and the U.S. interested
in obtaining these data.

2\) Identification of the precise portion(s) of these data that are
requested to be treated as confidential.

3\) Statement that release of these data would be likely to cause
substantial harm to the user\'s competitive position.

4\) Statement concerning when these data may be publicly disclosed.

5\) Statement reflecting agreement with interested government agencies
as to ways they may combine and disclose these data in such format as
general studies, environmental warnings and forecasts, or aggregate
reports or summaries in order to protect life and property.

6\) Identification of data required by the government agencies or
programs and any requirements for transfer of these data which have been
agreed upon by the user and the interested government agencies. (16th
O/C)

### FINAL DRAFT APPROVAL

A final draft was agreed upon. This and the modifications agreed to at
the 15th O/C Meeting were submitted for approval by the member agencies.
(18th O/C)

## NEW MEMORANDUM OF UNDERSTANDING

### INCEPTION

Since January 1984, NOAA and CNES have discussed continuing Argos
cooperation after the flight of NOAA-J. These discussions continued
through 1985 and resulted in a new Argos MOU that superseded the 1974
MOU. The new MOU was signed by CNES on March 11, 1986, and by NOAA on
March 25, 1986. (20th O/C)

### BASIC AGREEMENT

The basic agreement is consistent with the 1974 MOU as amended. CNES
will continue to provide the Argos Data Collection and Platform Location
instruments for the Polar-orbiting Environmental Satellite (POES),
process data received from the satellite, and distribute these processed
data to U.S. and other users. NOAA will be responsible for the overall
design, integration, and operation of the spacecraft. NOAA will provide
CNES the raw global data from the Argos instruments onboard the POES.
Specific mention of the U.S. Argos Processing Center and CNES\'s cost
recovery objectives are included. The new MOU clarifies liabilities and
provides for the Joint Tariff Agreement. (20th O/C)

### STATUS, CHANGES & AMENDMENTS

#### Status of MOU, (22nd O/C)

The MOU between NOAA and CNES for the continuation of the Argos Data
Collection and Platform Location System was signed March 1986. A summary
of changes effected by the 1986 MOU will be contained in the
Consolidated Report (See Appendix A)

#### Environmental Protection Programs

In an effort to adapt the Argos program to growing requirements of the
U.S. and French Governments, the U.S. and French Co-chairs recommended
that NOAA and CNES amend the 1986 MOU to include protecting the
environment in addition to monitoring the environment. The U.S.
Department of State is expected to provide final clearance to enable
NOAA to proceed in formally proposing to CNES that the 1986 MOU be
amended. (24th O/C)

NOAA and CNES amended the MOU in 1990 expanding traditional system use
of monitoring the environment to include protection of the Earth and its
environment. (25th O/C)

#### Future Agreements

C. Wooldridge presented plans for the modification or drafting of future
agreements to govern the post NOAA M era. For NOAA-N, NOAA proposes an
exchange of letters to amend the current Argos MOU. For post NOAA-N, it
is envisioned that future agreements for polar-orbiting meteorological
satellites will be comprised of two levels of agreements; memoranda of
understanding and implementation arrangements. (24th O/C)

In 1991, NOAA and CNES amended the MOU to cover the NOAA-N program.
(25th O/C)

#### Post-NOAA-N MOU Planning

Discussions on a post NOAA-N Argos agreement began prior to the 25th
Argos O/C Meeting in July 1991. NOAA and CNES agreed that the current
Argos Memorandum of Understanding (MOU) would serve as a basis for a new
agreement. The Argos MOU will be a subsidiary agreement to a
NOAA-EUMETSAT Memorandum of Agreement (MOA). NOAA proposed that a new
NOAA-CNES Argos MOU be signed Spring 1993. To this end, NOAA and CNES
will resume internal discussions on this topic with the goal of
presenting a draft for discussion in October 1992. (26th O/C)

#### Post-NOAA-N MOU (1994 Status)

The NOAA-EUMETSAT Polar Memorandum of Agreement (MOA) is anticipated in
mid-1995 following EUMETSAT Council approval of the full polar program.
As an interim measure, NOAA and EUMETSAT signed an exchange of letters
indicating intent to cooperate in polar-orbiting satellites, pending
funding authority and completion of a formal agreement. Negotiation,
conclusion, and signature, or preferably amendment, of the current Argos
MOU covering NOAA N\', METOP-1, and 2, should be conducted in the same
time frame as the NOAA-EUMETSAT Memorandum of Agreement, thus signature
by mid-1995. CNES cannot formally commit to provision of Argos on post
NOAA-N platforms until a decision is made in Europe on full funding of
METOP-1 and 2 which could come as late as early 1996. As an interim
measure, the French Co-Chair recommended that the NOAA/NESDIS Assistant
Administrator send a letter to the CNES Director General to facilitate
timely conclusion of agreements. (28th O/C)

#### Post-NOAA-N MOU (1995 Status)

The NOAA-EUMETSAT MOA on cooperation in the Initial Joint Polar-orbiting
Operational Satellite System (IJPS) is in the final stages of
negotiation. EUMETSAT intends to provide the final text to the EUMETSAT
Council June 26-27, 1995. The Council will be asked to approve the text
with the exception of the data policy section which is still under
discussion. The data policy article must be approved at the November
1995 EUMETSAT Council Meeting. NOAA obtained a second C-175 approval
from the Department of State in June 1994 due to the new convergence
consideration. NOAA will request final approval from the Department of
State once the data policy issue is resolved.

In April 1995, CNES and EUMETSAT began discussions on a direct agreement
between CNES and EUMETSAT for Argos on METOP. Since discussions in IPOMS
in 1988, CNES, EUMETSAT and NOAA had planned to have the NOAA-CNES Argos
MOU cover commitment for flight of Argos on METOP. During meetings on
April 26-27, 1995 in Washington, NOAA, CNES and EUMETSAT agreed to
proceed according to CNES \'desire to have a direct MOU with EUMETSAT
subject to EUMETSAT accepting the basic policies and procedures already
in place for the Argos programs.

Based on the assumption that CNES and EUMETSAT would negotiate a direct
agreement, NOAA presented a first draft of a revised NOAA-CNES Argos
MOU. The major modification was to provide the appropriate background
and linkages to EUMETSAT participation in the IJPS and a reference to
the CNES-EUMETSAT MOU. Operations Committee attendees took the action to
provide comments on the draft MOU language to C. Wooldridge and L. Ruiz
by end of July 1995.

In addition, the meeting focused on options for the future structure of
the Argos Program Management as currently exercised by the Operations
Committee. The options included an expanded Operations Committee with
new members and a two level structure with a council/steering committee
and separate bilateral Operations Committees. The consensus of the
Operations Committee was to pursue the expanded Operations Committee
option. Once agreement has been reached on this language, NOAA and CNES
will jointly develop a Terms of Reference for an expanded Operations.
Committee providing guidelines on participation, membership, conduct of
meeting, etc. (29th O/C)

#### POST NOAA-N MOU (1997 Status)

C. Wooldridge reported that NOAA and CNES have agreed to amend the
current Argos MOU to cover NOAA-N'. NOAA and CNES will coordinate a
draft exchange of letters to accomplish this amendment in the same
timeframe as the completion of the NOAA-EUMETSAT MOU which is expected
by December 1996. (30^th^ O/C)

The current 1986 NOAA-CNES Argos MOU covers flight of the Argos DCS
through NOAA N. Since NOAA N\' will be the last satellite in the current
NOAA series before NPOESS begins, NOAA and CNES have agreed to a simple
amendment to extend the current MOU to cover NOAA N\'. After
coordination with CNES, NOAA forwarded the proposed MOU amendment
package to the Department of State in May 1997, for approval. After
which an exchange of letters with CNES will implement the amendment.
NOAA and CNES expect this to be completed by the end of 1997. In June
1996 the EUMETSAT Council approved the text of the Initial Joint
Polar‑Orbiting Operational Satellite System (NOAA N and N\', METOP 1 and
2) Memorandum of Understanding. Both ESA and EUMETSAT subscriptions are
still open for Member state funding commitments. NOAA has submitted the
MOU for internal USG Circular‑175 authority to conclude the agreement.
All agencies have cleared on the text with the exception of the
Department of State which has requested an additional legal review by
the Treaty Affairs Office. NOAA hopes to gain State clearance by end of
the summer. (31st O/C)

C. Marzin informed the Operation Committee that on July 7, 1998, NOAA
sent to CNES the letter proposing the amendment of the NOAA-CNES Argos
MOU. The amendment will update the liability section and extend the
current MOU to cover NOAA N'. CNES is expected to reply to the NOAA
letter within the month. Upon signature of the reply, the amendment will
be implemented. (32^nd^ O/C)

C. Marzin presented the status of Memorandum of Understanding (MOU)
governing the Argos DCS. In particular, the 1986 NOAA-CNES MOU governing
Argos on the NOAA polar satellites was amended by an exchange of letter
to include the NOAA-N' satellite. The new agreement became effective in
July 1998. In addition, the NASDA-CNES MOU governing Argos on ADEOS-II
was signed on August 15, 1996. The EUMETSAT-CNES MOU governing Argos on
the METOP serie has been approved by the EUMETSAT council in November
1997. The CNES-DG has confirmed approval on April 1998, and signature of
the MOU is expected by end of 1999. Finally, the Initial Joint
Polar-Orbiting Satellite System (NOAA N and N', METOP 1 and 2) Agreement
between NOAA and EUMETSAT was signed in November 19, 1998, in Washington
DC. (33^rd^ O/C)

C. Marzin presented the status of Memorandum of Understanding (MOU)
governing the use of the Argos DCS. The CNES-EUMETSAT MOU governing
Argos on the METOP series has been approved by the EUMETSAT Council and
the CNES Board of Directors. The MOU is planned to be signed by end
2000. The NOAA-CNES MOU covers the Argos system on NOAA-N'. The OPSCOM
discussed the necessary steps to prepare for an MOU to provide Argos in
the NPOESS era. Argos is considered a national instrument on the NPOESS
satellites. The first NPOESS satellite is planned to be launched at the
end of 2008/early 2009. As such, the instruments should be developed to
meet the delivery date by 2006. Considering a three-year time line to
develop the first instrument, the MOU covering this cooperation should
be signed by late 2002/beginning 2003. (34^th^ O/C)

It is the current understanding of NOAA that the data collection system
will fly on both the morning and afternoon orbits of the NPOESS system.
NOAA and CNES will use their best efforts to negotiate a new memorandum
of understanding that should specify more precisely requirements for DCS
on NPOESS spacecraft. (35^th^ O/C)

M. Beckman recognized that the existing CNES/NOAA MOU provides for
cooperation through the NOAA-N' satellite which has a launch planning
date of March, 2008. He also provided an update on discussions held
among CNES, NOAA, and the NPOESS Integrated Program Office (IPO)
regarding cooperation on the NPOESS series of satellites. Agreement in
principle exists for cooperation ; appropriate contacts have been
established on the program and technical sides for all parties. A
planning timeline has been established for agreeing on a new MOU, taking
into account both the NPOESS and CNES budget and development
requirements. (36^th^ O/C)

Emilie Bruchon from NOAA presented the status of the NPOESS MOU. A draft
agreed to by key NOAA program offices (Satellite Data Processing and
Distribution; Integrated Program Office) is currently under review by
NOAA General Counsel. Following legal review, the revised draft will be
reviewed again by key program offices and by other interested offices
within NOAA/Department of Commerce. The NOAA-agreed draft will then be
sent to the U.S. Department of State for authorization to negotiate.
When that authorization is granted, NOAA will then be able to provide
CNES with a draft and discuss specifics of the text. NOAA is required to
send the negotiated text back to the State Department for authorization
to sign. It is anticipated that this process will be completed by the
end of 2003.(37^th^ O/C)

A draft of the Argos DCS NPOESS MOU has been provided to CNES last
February 2004. The negotiation is in progress and a signature is
expected before the end of this year. (38^th^ O/C)

#### Instrument Delivery Dates

In response to the NOAA request to provide an additional instrument
(NOAA-N'), CNES is coordinating its response internally. The French
Co-Chair explained that for CNES there is no question in principle of
providing the instrument, but rather how soon a formal commitment is
required by NOAA.

Currently Argos instruments are available well in advance of NOAA
instrument delivery dates. Participants discussed an approach whereby
CNES would send a letter of intent to NOAA as an interim measure, thus
delaying an amendment to the Argos MOU. NOAA and CNES agreed to
investigate if this approach is acceptable. (27th O/C)

## JOINT PROJECT PLAN

### WORKING LEVEL DOCUMENT

As part of the cooperation under the new MOU, a working level document
called the Joint Project Plan (JPP) was written. The JPP confirms
technical arrangements made for spacecraft through NOAA-J, and describes
arrangements for NOAA-K, L, and M. The JPP is expected to be signed by
NOAA, NASA, and CNES as soon as possible. A JPP implementation group
will be formed consisting of members from NOAA, NASA, and CNES. (20th
O/C)

### STATUS, CHANGES & AMENDMENTS

#### Liability & Patent Indemnification.

NASA has requested that a letter to CNES from NASA be included as an
annex to the JPP. The letter will deal with STS liability and patent
indemnification. (20th O/C)

#### Joint Project Plan Approved

The Joint Project Plan for ARGOS-2 was approved by CNES, NOAA, and NASA
August 24, 1987. (22nd O/C)

# OPERATIONS COMMITTEE & MEETINGS

## CHARTER & RESPONSIBILITIES

### REPRESENTATION

Paragraph 6 of the MOU provides the basic charter for the O/C. The O/C
will have equal representation from France and U.S and will be chaired
alternatively by persons from NOAA and CNES. (1st O/C)

### RESPONSIBILITIES

#### System Design and Development

The O/C, as part of its charter, is responsible for the design and
development of satellite data collection systems. In order to provide
meaningful information to the O/C, it is necessary to obtain detailed
knowledge from the experience gained in operating the present system. A
mechanism is required to document and periodically update this document
for use of the O/C. (17th O/C)

#### Current System.

Since the current system was not designed to measure performance
improvements, it is difficult to quantify these improvements. The O/C
regrets that this capability is not available in the present system and
strongly recommends that this capability be included in the ARGOS-2
system. (18th O/C)

#### Follow-on Systems

In addition to the information contained in the Argos Consolidated
Report, CNES proposed that the monthly operations reports and minutes
from meetings with users and international organizations be reviewed to
identify all users claims and modifications or improvement (either
operational or technical) which have been suggested (whether implemented
or not) as desirable for a benefit to the users or improved operation of
the system. A list of items gleaned from this review would be available
and updated as necessary for the O/C to examine and be used for the
development of the follow-on system. (18th O/C)

#### Other Responsibilities.

Other responsibilities include:

1\) Review development and operation of the Coordination Center (Service
ARGOS) and Processing Centers.

2\) Review the Satellite Data Collection System (Argos System) design
and development.

3\) Review and approve proposals received by Service Argos for use of
the system.

4\) Resolve issues that may arise with respect to the operation of the
system. (1st O/C)

## FREQUENCY & FORMAT OF MEETINGS

### MEETING FREQUENCY (AMENDMENTS)

#### Amendment, 9th O/C

In order to make the meetings more efficient, it was felt that the
meeting should be once each 6 months. (9th O/C)

#### Amendment, 14th O/C

The Co-chairs discussed the need for semi-annual meetings and agreed
that one meeting each year would be sufficient if the Argos program was
a stable on-going operation. However, the Co-chairs noted that impending
events, such as the U.S. Coast Guard proposal to directly tap the NESDIS
data stream as well as potential U.S. budget reductions, may have
serious implications for Service ARGOS. For these reasons, the Co-chairs
agreed to meet again in 6 months. The meeting schedule will be
considered again at that time. (14th O/C)

#### Amendment, 15th O/C

The meeting schedule was reviewed and it was agreed to meet again in 6
or 7 months due to the many uncertainties in the polar orbiter program.
The frequency of meetings will be discussed at the next meeting. (15th
O/C)

#### Amendment, 17th O/C

The Co-chairs agreed that, since there are no-known crucial items and
the O/C Meetings have become more routine, it was not necessary to have
the meetings twice per year. Therefore, the next meeting will be
scheduled in approximately

9 months, repeated at about 9 to 12 month intervals. (17th O/C)

### MEETING FORMAT

The Meeting Format should be as follows:

a\. A proposed agenda will be forwarded by the host organization at
least 90 days in advance of the meeting.

b\. Information concerning each agenda item will be prepared in written
form by the responsible organizations.

c\. This information will be exchanged with the other organizations 30
days in advance of the meeting.

d\. During the meeting a writing group will be appointed for the writing
of the draft minutes each day.

e\. These draft minutes will be distributed to the members on the
following day for review and approval.

f\. The entire draft minutes and action items will be approved before
the meeting adjourns. (9th O/C)

## MEETING ATTENDEES

### POLICY

#### User Invitation

The O/C is a working group of system operators and is not generally open
for attendance by users. If there is a requirement for a user to
personally express a problem, either Co-chair may invite that user to
the O/C Meeting. (7th O/C)

#### WMO Invitation

It was agreed that the host organization would provide, well in advance
of the meeting, a written invitation to the permanent WMO representative
of that country and to WMO Headquarters representatives for attending
the meeting. (17th O/C)

### MEETINGS AND CO-CHAIRS

  ------- ------------- ------------------ --------------- -----------------
  **N**   **Date**      **Place**          **US Co-Chair** **FR Co-Chair**

  1       Jun 17, 1975  Suitland Md        C. Spohn        B. Lago

  2       Dec 8, 1975   Toulouse Fr        G. Ludwig       B. Lago

  3       May 5, 1976   Suitland Md        G. Ludwig       B. Lago

  4       Oct 18, 1976  Cap d\'Agde Fr     G. Ludwig       B. Lago

  5       Apr 25, 1977  Annapolis Md       G. Ludwig       R. Simon de
                                                           Kergunic

  6       Nov 7, 1977   Toulouse Fr        G. Ludwig       R. Simon de
                                                           Kergunic

  7       Mar 29, 1978  Camp Springs Md    G. Ludwig       R. Simon de
                                                           Kergunic

  8       Nov 29, 1978  Toulouse Fr        G. Ludwig       R. Simon de
                                                           Kergunic

  9       Apr 2, 1979   Toulouse Fr        G. Ludwig       R. Simon de
                                                           Kergunic

  10      Sep 17, 1979  Williamsburg Va    G. Ludwig       R. Simon de
                                                           Kergunic

  11      Apr 28, 1980  Antibes Fr         G. Ludwig       R. Simon de
                                                           Kergunic

  12      Oct 6, 1980   Charlottesville Va G. Ludwig       R. Simon de
                                                           Kergunic

  13      May 4, 1981   Ajaccio Fr         D. Winner       R. Simon de
                                                           Kergunic

  14      Oct 21, 1981  Gettysburg Pa      D. Winner       R. Simon de
                                                           Kergunic

  15      Apr 26, 1982  Toulouse Fr        R. Koffler      R. Simon de
                                                           Kergunic

  16      Dec 7, 1982   New Orleans La     R. Koffler      R. Simon de
                                                           Kergunic

  17      Jun 1, 1983   Reston Va          R. Koffler      P. Bescond

  18      Apr 4, 1984   Toulouse Fr        R. Koffler      P. Bescond

  19      Mar 25, 1985  San Francisco Ca   R. Koffler      P. Bescond

  20      Mar 25, 1986  Annapolis Md       R. Koffler      P. Bescond

  21      Apr 14, 1987  Sarlat Fr          R. Koffler      G. Delmas

  22      May 10, 1988  Ocean City Md      R. Koffler      G. Delmas

  23      Jun 16, 1989  Villefranche/mer   H. Wood         G. Delmas
                        Fr                                 

  24      Apr 9, 1990   Orlando Fl         H. Wood         D. Hernandez

  25      Jun 1, 1991   Aix en Provence Fr H. Wood         D. Hernandez

  26      Apr 14, 1992  Boulder Co         H. Wood         D. Hernandez

  27      Jun 2, 1993   Biarritz Fr        H. Wood         D. Hernandez

  28      Jun 7, 1994   Landover Md        H. Wood         C. Gal

  29      Jun 13, 1995  Blois Fr           H. Wood         C. Gal

  30                                       H. Wood         C. Gal

  31      June 24,1997  Arcachon Fr        H. Wood         C. Gal

  32      July 7, 1998  Anchorage Al       H. Wood         C. Gal

  33      June 23, 1999 Saint-Malo Fr      H. Wood         C. Gal

  34      June 27, 2000 Woods Hole Ma      H. Wood         C. Gal

  35      June 5, 2001  Sarlat Fr          H. Wood         C. Gal

  36      June 4, 2002  Kihei Maui Hi      D. Benner       C. Gal

  37      June 11, 2003 Saintes Maries de  D. Benner       C. Gal
                        la Mer Fr                          

  38      June 30, 2004 Monterey CA        D. Robertson    C. Gal

  39      June 21, 2005 Collioure, France  D. Benner       P. Goudy
  ------- ------------- ------------------ --------------- -----------------

## MEETING MINUTES

### Distribution of Meeting Minutes

It was agreed that the minutes of the O/C meetings will be furnished
only on request to persons who genuinely need to know what was decided.
This would always include members of the O/C and JWG. Service Argos will
provide the WMO a short summary of the meeting giving the status of the
system and the main decisions of that particular meeting. (6th O/C)

### Special Requirements 

The requirement for Service Argos to forward O/C Meeting Minutes was
only necessary during the FGGE period. (15th O/C)

## CONSOLIDATED REPORT

### PURPOSE

To assure continuity, NOAA and CNES agreed that the Consolidated Argos
O/C Meeting Minutes (Consolidated Report) would serve as the basis for
operating under the MOU. NOAA, NASA and CNES agreed to review the
Consolidated Report to ensure that all relevant elements of NOAA, NASA
and CNES cooperation are included under the new MOU. (20th O/C)

### STATUS, CHANGES & AMENDMENTS

It was agreed that no structural changes to the Consolidated Report are
necessary. It was also agreed that revisions and additions be made as
necessary to reflect decisions made by the O/C, or to reflect changes
made by signature of the \"New\" MOU. (22nd O/C)

A working group composed of R. Bassett, L. Mesnier, C. Marzin and L.
Ruiz was tasked at the 32 OPSCOM meeting to update the consolidated
report. R. Bassett presented the proposal from the working group for
developing a functional reference document covering the entire Argos
program rather than an archive of the past OPSCOM meetings. This draft
table of content is included as 33^rd^ O/C Exhibit \# 17.

The 33rd OPSCOM approved the proposed framework and mandated the working
group to move forward with the drafting of the new Consolidated Report.
The Working Group is to distribute a draft Consolidated Report for
review by early 2000, so that the Consolidated Report can be approved at
the 34th OPSCOM meeting in Spring-Summer 2000.

The priority will be given to core documents, in particular the current
mode of operations, and the definition of the roles, responsibilities
and relationships of all parties. Although the working group remains
responsible for the delivery of the Consolidated Report, OPSCOM members
will contribute their expertise in the drafting of appropriate documents
upon request and validation of the draft documents before inclusion in
the report. (33^rd^ O/C)

R. Bassett reported on the status of updating the Consolidated Report
(CR) and delivered the rough draft of the Consolidated Report for review
and comment by the OPSCOM members. The tentative work plan for the
update, developed during the CNES/NOAA meetings in November 1999, was
reviewed. R. Bassett noted that while the update was behind schedule,
good progress has been made as evidenced by the delivery of the rough
draft. A revised schedule for completion of the final version was
proposed and approved by the OPSCOM. The OPSCOM principals provided
initial comments on the Introduction section of the rough draft.
Comments from all the OPSCOM members and in particular, the NASDA and
EUMETSAT representatives, were requested by September 2000. Comments
should be submitted to R. Bassett for distribution to the writing task
group. The task group will consolidate and incorporate all
comments/changes to produce a final version by May 2001 for review and
approval at the 35^th^ OPSCOM meeting. The Writing Group for that and
each subsequent OPSCOM meeting will be tasked with identifying items to
be added and/or removed from the CR, subject to the approval of the
OPSCOM principals. (34^th^ O/C)

R. Bassett reported on the status of updating the Consolidated Report
(CR). R. Bassett noted that while the update was behind schedule, good
progress has been made and requested an extension of the delivery date
of the edited draft to CNES to September 2001. Input from OPSCOM 34 had
been incorporated and reviewed. CNES agreed to maintain the CR as the
Argos instrument provider and manager of the program. NOAA offered to
post the CR and associated appendices on the NOAA Argos web-site. All
participants were encouraged to provide applicable appendices in
electronic format for inclusion in an electronic library.(35^th^ O/C)

R. Bassett provided an update on the status of the Consolidated Report.
He stated that the original sections require editing and the minutes
from prior Opscom meetings need to be reviewed for the inclusion of
applicable OC decisions. Contract support will be established to assist
in finalizing the document and tap the "corporate knowledge' of the
Opscom members (36^th^ O/C).

Rob Bassett of NOAA provided a history and update on the status of the
Consolidated Report (CR). He stated that the contract support will be
established to assist in finalizing the document and tap the "corporate
knowledge" of the OC members (37^th^ O/C)

C. O'Connors provided a plan to revise the Consolidated Report to
contain the operational documents and procedures and policies of the
OPSCOM. NOAA proposed that the maintenance of the document rotate
between the host chair representatives and be published each year after
the OPSCOM with the current meeting minutes. Proposed Chapters :

-   MOU

-   OPSCOM / Terms of Reference (TOR)

-   Global System Use Policy

-   Space Segment Project Plan

-   Ground Segment Project Management Operation and Implementation Plan
    (PMOIP)

-   User Letter Procedure

-   Data Denial Policy

-   Agent (CLS/SAI) Responsibilities

-   Electronic SUA Procedure

-   Joint Tariff Agreement

-   OPSCOM Minutes (38^th^ O/C)

At O/C 39 NOAA proposed a work plan and responsibilities for the update
and management of the updated ConRep.

-   OPSCOM host agency to publish an updated document with latest OPSCOM
    minutes

-   OPSCOM host agency will maintain the document during the
    intercessional

-   The outgoing custodian of the document will brief the changes to the
    report at the OPSCOM (39^th^ O/C)

## ORGANIZATIONAL ISSUES

### CNES (ARGOS) ORGANIZATION

#### Technical and Organizational Aspect:

The increase in use of the Argos system and technical progress in data
processing and transmission led CNES to re-examine technical and
organizational aspects of Service Argos. In particular, CNES considered:

1\) Increased user requirements for both the quantity and quality of
data.

2\) Methods by which CNES can meet these needs through system upgrade,
reorganization, and expansion of Argos data processing facilities. (20th
O/C)

### U.S. Argos Representative

#### Selection Consideration:

Service Argos is considering hiring a U.S. citizen to serve as the Argos
representative in the U.S. (13th O/C)

#### NESDIS Support:

Service Argos requests NESDIS to consider what support can be provided
for an Argos representative in the U.S. (14th O/C)

#### Selection Criteria:

NESDIS has agreed in principle with the plan to have a Service Argos
representative in the U.S.. NESDIS desires that the following conditions
be observed:

1\) The representative be a Service Argos employee or contractor.

2\) NESDIS desires to participate in the selection of the
representative.

3\) Service Argos prepares a draft position description (15th O/C)

#### Representative Selection:

The U.S. Representative for Service Argos has been selected. (17th O/C)

### CNES Subsidiaries

Various solutions have been assessed (technically, economically, and
legally) in order to adapt the Argos system to users\' requirements.
CNES has decided to create a separate body, which will be a subsidiary
corporation of CNES and will be responsible for all promotional and
operational activities of the Argos system. In addition, a subsidiary
will be established in the U.S. These two organizations will share the
operational system workload. These subsidiaries will remain under full
control of CNES, which will ensure that the conditions of the MOU are
satisfied. Official creation of these subsidiaries will be April 1986
for the French-based organization and May 1986 for the U.S.
organization. (20th O/C)

### CLS Organization

CLS/Service Argos added an oceanography group to the organization. Also
of interest was CLS\' discussion of participation in the DORIS and
Topex/Poseidon projects. (24th O/C)

Concerning Service Argos Inc.\'s move out of the NOAA Seattle facility,
the U.S. Co-chair stressed the need for close communication between NOAA
and North American CLS (NACLS). Continued care should be taken to
differentiate between the activities of NACLS and the activities of
Service Argos, Inc. (24th O/C)

#### Differentiation of Activities

NACLS was relocated to a new separate facility in Landover, Maryland,
and a new manager has been named. The Organization of Service Argos,
Inc. and NACLS is now consistent with the exchange of letters between
the Co-chairs completed in February 1991. (25th O/C)

## GEOSTAR AND CNES

### GEOSTAR DEVELOPMENT 

The activity of the Geostar program concerning \"truck tracking\" during
1988 and 1989 was presented. The GEOSTAR - CLS studies concerning the
satellite radiolocalization demonstrations in different countries
(Australia, China, etc.) and the development of a hybrid GEOSTAR/Argos
terminal has been suspended since February 1989. (23rd O/C)

## FISHING VESSEL MONITORING (IN U.S. WATERS)

### Project Development

NOAA is conducting an experiment to determine the technical and economic
feasibility of tracking fishing vessels in the Pacific Ocean for treaty
enforcement and resource management. NOAA and CNES will establish a
Working Group to study and develop recommended guidelines for
applications concerning the tracking of fishing vessels. (23rd O/C) It
should be noted that the MOU was amended to permit environmental
protection applications including those related to fishing vessel
tracking (See 1.2.3.2).

### Impact on System

Results of simulations by CLS to determine the possible number of PTT\'s
within the \"instantaneous field of view\" showed that transmissions
from the proposed number of fishing vessels operating in the north
Pacific can be received and processed (without difficulty) by the Argos
on-board system. (24th O/C)

Argos activity to track fishing vessels declined with the United Nations
Treaty banning high seas driftnet fishing. However, there are a number
of individual countries and international organizations (e.g., the
European Economic Community) which are considering and/or implementing
vessel tracking programs for regulatory enforcement purposes. In some
cases, Argos has been declared acceptable for this purpose but has yet
to be implemented. There are several marketing efforts underway which
could lead to an increase in this activity beginning in late 1994. (28th
O/C)

## METEOSAT AND GOES AND CLS

### MAEDS

CLS presented the MAEDS project, the object of which is the creation of
a new service offering data collection, value added processing and
dissemination to users of all satellite-based environmental data
collection systems (drifting and stationary satellite). The first step
of the project is to provide the Meteosat user with the possibility to
receive their data through the Argos data dissemination system with
value added services like data bank, sensors processing. The second step
will be the interfacing of the MAEDS with the GOES system. NOAA noted
that under such an arrangement, CLS would appear to be no different than
any other user of GOES DCS. (23rd O/C)

## Global Learning and Observations to Benefit the Environment (GLOBE)

The U.S. Co-chair briefed the O/C about this new international program,
which may involve Argos. GLOBE\'s goals are to enhance the environmental
awareness around the world and to increase the scientific understanding
of the environment by using a worldwide network of schools to collect
environmental observations. Mr. Tom Pyke, former NESDIS Assistant
Administrator, is director of GLOBE. Realizing that Argos may be well
suited to support GLOBE, Mr. Pyke has begun discussions with SAI and
several manufacturers of Argos transmitters. The U.S. Co-chair
encouraged CNES participants to share their thoughts and relevant
experiences with Mr. Pyke. (28th O/C)

## CONFIDENTIAL TREATMENT OF DATA FROM THE ARGOS SYSTEM

### Terms and Conditions

The terms and conditions for confidential treatment of data obtained
from the Argos Data Collection System expired on March 11, 1989. The
Annex required NOAA and CNES to review the policy of restricting
dissemination of Argos data and to determine whether such provisions
should be extended. The O/C recommended that the Annex not be renewed at
this time since no requests for confidential treatment of data had been
received in the three years that the Annex was in effect. The O/C will
reconsider renewal of the Annex should Service Argos receive such
requests in the future. (23rd O/C)

## Joint Working Group

### MEMBERSHIP

The three DCS Project Managers may include technical advisors as
required. (2nd O/C)

### RESPONSIBILITIES

Each Project Manager is responsible to his agency. (2nd O/C)

### O/C RELATIONSHIP

The JWG functions as a consultant group and will inform the O/C about
their activities and decisions. (2nd O/C)

## STATUS, CHANGES & AMENDMENTS

### CNES/NOAA WORKING GROUP

The Joint Working Group proposes that its activities should cease since
the major development of the spacecraft and ground system has been
completed. It is suggested that a CNES/NOAA Working Group could
accomplish the necessary activities for the remaining ground system
enhancement work. (11th O/C)

### TECHNICAL ADVISORY GROUP

It was agreed that there be no change in the JWG functions. Also, it was
proposed to create a Technical Advisory Group (TAG) of 3 members to
provide technical consultation to the O/C. The specific functions and
membership of this group will be determined (12th O/C)

#### TAG Deferred

Since there has been no progress within CNES, NASA and NOAA for the
approval of a possible extension of the functions and responsibilities
of the O/C, there is no requirement at the present time for the TAG.
(13th O/C)

## CANSAT

L. Ruiz informed the meeting that a Low Earth Orbit Mobile Satellite
System (LEO MSS), known as CANSAT, has been declared to the ITU by
Canada. According to available information, the CANSAT system would use
several frequency bands, some of which are used by the Argos System
(401-406 MHZ). The meeting agreed to check whether there may be a risk
for the Argos system to incur interference from the CANSAT system. NOAA,
NASDA, EUMETSAT, and CNES are invited to request their respective
regulatory authorities to undertake the appropriate coordination
measures. (32^nd^ O/C)

## Review of other systems

### ORBCOMM:

The main concern seems to be the financial difficulties faced by this
commercial space-based system in spite of its technical achievements,
the number of active transmitters being presently far under the break
even. (34^th^ O/C)

### GSP:

The suppression of the selective availability effective May 1, 2000
opens interesting possibilities to some Argos users and will lead them
to request more resolution in location accuracy and time coding. (34^th^
O/C)

# Terms of Reference

## Terms of Reference

### Operations Committee

#### History 

The Argos Operations Committee (OPSCOM) was formed in 1978, in
recognition of the cooperative effort by the Centre National d'Etudes
Spatiales (CNES) and the National Oceanic Atmospheric Administration
(NOAA) governing the implementation and use of the global Argos Data
Collection and Location System (DCS). The cooperation was first defined
under the 1974 NASA-NOAA-CNES Memorandum of Understanding (MOU) and its
1984 amendments governing the TIROS-N Satellite Data Collection System.
The 1986 NOAA-CNES MOU for the Argos DCS and its 1991 and 1998
amendments contained in Appendix A superseded the 1974 NASA-NOAA-CNES
MOU to cover the Argos DCS operations on the POES satellites.

Agencies contributing to the Argos DCS space segment are referred to as
\"Participating Agencies\".

### Objectives of the Operations Committee 

-   to review the Argos DCS development, implementation and operations
    activities, and make recommendations to the Participating Agencies
    on appropriate measures for accomplishing the objectives as defined
    in section 4.1 of the 1986 NOAA-CNES MOU, namely, to provide a
    system for the location, acquisition, and dissemination of
    environmental data, thereby improving and expanding the capabilities
    of the global operational weather system, and supporting research
    and development in ocean, weather, and other environmental
    disciplines;

-   to review and approve applications for System Use Agreements and
    formulate criteria for approval of such applications received from
    prospective users for the use of the Argos DCS. It is understood
    that in exercising its right to approve applications, each
    Participating Agency will take into account the principles of the
    Argos system use policy as defined on the System Use Agreements;

-   to review and concur with the tariff structure based upon a review
    of the Joint Tariff Agreement (JTA) and CNES recommendations
    applicable to the processing of the data by the Argos DCS data
    processing system. Such tariff structure proposals will be developed
    in light of the guidelines agreed by the Participating Agencies in
    the Argos OPSCOM Consolidated Report, and updated as appropriate;

-   to coordinate to resolve issues that may arise with respect to the
    implementation and operations of the Argos DCS. Issues having a
    financial impact shall be submitted to the proper management level
    of each Participating Agency for decision according to their own
    internal procedures.

### Membership

The Argos OPSCOM will have equal representation from Participating
Agencies. Each Participating Agency will designate a Lead
Representative. The Lead Representatives will co-chair the OPSCOM.

Other entities participating in the OPSCOM will be:

-   The representatives of the Agent (CLS and SAI);

-   The chair of the JTA;

-   Other invitees proposed by a Lead Representative, when relevant to
    the agenda of the OPSCOM meeting.

In addition, countries or space consortia that provide flight
opportunities for the Argos instrument may partner with existing
Participating Agencies, and become new Participating Agencies in the
OPSCOM. Countries or space consortia can gain official Observer status
on the Argos OPSCOM upon signing separate MOUs with CNES governing the
Argos DCS operations. They will gain status as Participating Agencies in
the Argos OPSCOM when an Argos instrument becomes operational on their
spacecraft, and retain that status throughout the instrument\'s
operational lifetime.

### Organization

The Argos OPSCOM will meet in session, in principle, annually. Ad hoc
working groups may be convened at the request of any Participating
Agency to consider specific issues in detail. Such working groups will
report at the next Argos OPSCOM meeting. The Argos OPSCOM meeting will
be hosted alternately by the Participating Agencies, except as otherwise
decided.

The Consolidated Report will serve as a record of the decisions made by
the Argos OPSCOM, and the policies and procedures of the system, but
will be subsidiary to the MOUs that govern the Argos system.

### Procedures

The format for the annual Argos OPSCOM meeting should be as follows:

A proposed agenda will be forwarded by the host organization at least 90
days in advance of the meeting. The agenda shall address at a minimum
the following items:

-   Adoption of the agenda

-   Selection of the writing group

-   Review of past action items

-   Review of spacecraft system performance

-   Review of future Argos systems

-   Review of the ground processing system

-   Review of the Argos program, admissions and promotion activities

-   Status of agreements

-   Revision and approval of the draft minutes

-   Guidance for revision of Consolidated Report

-   Establishment of the date and location of the next meeting

Information concerning each agenda item will be prepared in written form
as a "working paper" by the responsible organization. This information
will be exchanged with the other organizations at least 30 days in
advance of the meeting.

During the meeting a writing group will be appointed for the writing of
the draft minutes each day. These draft minutes will be distributed to
the members on the following day for review and approval. The final
draft minutes and action items will be approved before the meeting
adjourns, and appropriate sections of the minutes will be designated for
inclusion in the Consolidated Report.

The host organization will be responsible for producing the final
minutes of the meeting, and for making the appropriate revisions to the
Consolidated Report as directed by the OPSCOM at the meeting. The
completed final minutes and revised Consolidated Report will be
distributed to all attendees within 90 days after the meeting.

### Decision-making

Decisions will be made by consensus of the Lead Representatives of the
Participating Agencies, either during the OPSCOM meeting or in the time
frame between the meetings, as necessary. Any decision that can not be
reached by consensus will be referred to the signatories of the MOUs
that govern the Argos system, with each Participating Agency having
equal weight.

### Amendment 

These Terms of Reference may be amended or modified by consensus of the
Lead Representatives of the Participating Agencies.

### Effective Date and Duration 

#########  {#section .unnumbered}

The Participating Agencies agreed to adopt these Terms of Reference for
the Argos Operations Committee on July 2, 2004. The Terms of Reference
will remain in effect unless or until revised or terminated by consensus
of the Lead Representatives of the Participating Agencies.

### Procedures for System Use Agreement Approval

##### These procedures and principles will be applied: {#these-procedures-and-principles-will-be-applied .unnumbered}

-   Electronic mailing is used as much as possible;

-   All SUAs are sent to all Lead Representatives;

-   Receipt of SUAs is confirmed;

-   If no objections are raised by any of the Lead Representatives
    within two weeks, then the CNES Lead Representative signs the SUA
    and distributes it to the other Lead Representatives;

-   If an objection is raised by any of the Lead Representatives, that
    Lead Representative is to provide the rationale behind the objection
    at the same time.

## Terms of Reference for Expanded Operations Committee

At the March 18 1997 NOAA-CNES Bilateral Meeting held in Paris CNES and
NOAA agreed to a draft Terms of Reference (TOR) for an Expanded
Operations Committee. The Operations Committee Co-chairs approved the
draft TOR which will be formally submitted as part of the Consolidated
Report. CNES will address this with NASDA in a future meeting. NOAA and
CNES also agreed that it is not necessary at this time to amend the
current MOU to reflect an expanded Operations Committee and its TOR. It
is desirable to modify the relevant program management positions of the
MOU to more closely harmonize with the texts of the ADEOS and METOP
MOU's. This should be accomplished before NASDA and EUMETSAT become
Participating Agencies and the TOR enter into effect. CNES briefed on
the status of cooperation with EUMETSAT for flight of Argos on the METOP
series of satellites. CNES provided the draft March 3, 1997 version of a
CNES-EUMETSAT Memorandum of Understanding (MOU). NOAA provided comments
to CNES on April 9 1997. Helen Wood also participated in the April 28,
1997, annual NOAA-EUMETSAT Bilateral meeting and addressed data
collection system and search and rescue program statue and requirements.
NOAA discussions with EUMETSAT representatives signaled that there may
be issues delaying negotiation and conclusion of the CNES‑EUMETSAT MOU.
CNES clarified that EUMETSAT and CNES will submit the text of the MOU
for the December 1997 EUMETSAT Council meeting for approval.

Rob Bassett of NOAA reported on the TOR for the Argos system outlining
its contents and provided a copy for the minutes. He highlighted that
the current TOR were adopted at OPSCOM 31 in June 1997 and included
proposed modifications for expanded OPSCOM participation. The OPSCOM
co-chairs expressed a major concern that procedures for SUA approval be
documented and disseminated that reflect NASDA role as a Participating
Agency. Four Action Items were taken. (37^th^ O/C)

Emilie Bruchon of NOAA presented a proposed revision of the Operations
Committee Terms of Reference. The base text was the 1998 version of the
Terms of Reference, with comments from the NOAA-CNES intersessional
meeting held in March 2004, and with some additional revisions proposed
by NOAA (David Benner and Emilie Bruchon). The revisions were discussed
and further revisions agreed to. The final revision of the TOR, dated
July 2, 2004, is appended to the minutes. In accordance with the revise
TOR, JAXA changed its position from participating agency to observer.
Accordingly, leaving from the position of co-chair, because of the loss
of their satellite ADEOS II. (38^th^ O/C)

# Global System Use Policy

## Background

The Argos Data Collection System (Argos DCS) is operated through a
cooperative program between the United States'National Oceanic and
Atmospheric Administration (NOAA) and France's Centre National d'Etudes
Spatiales (CNES). The Argos DCS is managed by NOAA and CNES jointly
through the Argos Operations Committee. The system consists of:
instruments provided by CNES, which are flown aboard NOAA polar-orbiting
satellites; user supplied platform transmitter terminals (PTTs); and
global data processing centers. Argos instruments are also scheduled to
fly on Japanese and European polar-orbiting satellites, when the system
on these satellites are operational, Nasda and Eumetsat, respectively,
will become members of the Argos Operations Committee as well.

NOAA is authorized to enter this agreement under the authority granted
to it in 15 USC 313 and 49 USC 44720.

CNES is authorized to enter this agreement under the authority granted
to it by Act 61-1382 of 19 December 1961.

## Argos System Use Policy

### Scope

a\) This policy applies to any person who operates or proposes to
operate data collection platforms to be used with the Argos DCS either
directly or through an affiliate or subsidiary.

b\) These policies apply to all existing Argos DCS users as well as all
future agreements for use of the Argos DCS.

### Definitions

For purposes of this agreement and policy:

a\) Approving Authority means the Argos participating agencies, via the
Argos Operations Committee.

b\) Argos DCS means the system which collects data from fixed and moving
platforms and provides platform location data. This system consists of
platforms, the Argos French instrument on the Polar-orbiting Operational
Environmental Satellites (poes) and planned to fly aboard the Adeos 2
Japanese spacecraft and the eumetsat metop spacecraft; a ground
processing system; and telemetry ground stations.

c\) Argos participating agencies means those agencies that participate
in the management of the Argos DCS; currently this includes NOAA and
CNES, but it will also include the European Organization for the
Exploitation of Meteorological Satellites (Eumetsat) once the Argos
instruments commence operations from their satellites systems.

d\) Environmental data means environmental measurement and environmental
protection data.

e\) Environmental measurement data means data that relate to the
characteristics of the Earth and its natural phenomena by helping to
better understand, evaluate, or monitor its natural resources.

f\) Environmental protection data means data that relate to the
characteristics of the Earth and its environment (including its
ecosystems and the species which inhabit them) by helping to protect
against any unreasonable adverse effects thereto.

g\) Environmental Use means the use of the Argos DCS for the collection
of environmental data.

h\) Episodic use means the use of the Argos DCS for short events where
there is a significant possibility of loss of life, such as for Arctic
expeditions or scientific campaigns into remote areas.

i\) Government interest means that the use is determined in advance to
be of interest to one or more governmental entities of the United
States, France or, once Eumetsat becomes an Argos participating agency,
Eumetsat .

j\) Government user means agencies of international governmental
organizations, national government or any subdivision thereof, or any of
those agencies' contractors or grantees, so long as the contractor is
using the data collected by the Argos DCS to fulfill its contractual
obligations to the government agency or in the case of a grantee that
these data are being used in accordance with the statement of work for
the award.

k\) Non-profit user means a not-for-profit academic, research, or other
non-governmental organization, which is using these data, for education
and/or scientific, non-commercial purposes.

l\) Operational use means the use of data in a situation where the
utility of the data are significantly reduced if not collected or
delivered in a specific time window. This includes situations where
extensive preparation work is in place and a delay in acquisition of
data would jeopardize the project.

m\) Operator means the Argos Operation Committee members elected to
represent participating agencies for Argos users.

n\) Platform compatibility means the compatibility of the platform with
the space segment of the system, and includes elements such as message
length and composition, signal strength, and transmission protocol
(e.g., continuous versus event driven).

o\) Testing use means the use of the Argos DCS by manufacturers of
platforms for use in conjunction with the Argos DCS, for the limited
purpose of testing and certifying the compatibility of new platforms
with the technical requirements of the Argos DCS.

p\) Sensitive Use means the use of the Argos DCS where the users'
requirements dictate the use of a governmental system such as national
security, homeland security, law enforcement, and humanitarian
operations.

q\) User means the entity and/or organization which owns or operates
user platforms for the purpose of collecting and transmitting data
through the Argos DCS, or the organization requiring the collection of
the data.

r\) User platform means devices, designed in accordance with the
specifications delineated and approved by the Approving Authority, used
for the in-situ collection and subsequent transmission of data via the
Argos DCS. Those devices which are used in conjunction with the Argos
DCS are referred to as platform transmitter terminals (PTTs). For the
purpose of this policy, the terms user platform, PTT and Platform
Terminal Transceiver (PMT) are interchangeable.

s\) User requirement means the requirement expressed and explained in
the System Use Agreement.

### Use of Argos Data Collection System

a\) Use of the Argos DCS will only be authorized in accordance with the
conditions and requirements set forth in paragraphs (b), (c), and (d) of
this section.

b\) (1) Use of the Argos DCS will only be authorized where it is
determined that there are no commercial space-based services available
that meet the user's requirements.

\(2\) A determination under (b)(1), above, must be based on such factors
as satellite coverage, accuracy, data throughput, platform power
consumption, size and weight, service continuity and reliability,
platform compatibility, system access mode, and, in the case of
government agencies, cost-effectiveness.

c\) (1) Except as provided in paragraphs (2), (3), (4), and (5) of this
section, Argos DCS shall only be used for the collection of
environmental data by governmental and/or non-profit users.

\(2\) Non-governmental, environmental use of the Argos DCS is only
authorized where there is a Government interest in the collection and/or
receipt of the data.

\(3\) Except as provided in paragraph (c)(4) of this section,
non-environmental use of the Argos DCS is only authorized for government
use and non-profit users where there is a government interest. The Argos
DCS will continue to be predominantly used for environmental
applications. Non-environmental use of the system shall be limited to
sensitive use. And to episodic use as defined below in (c) (4) of this
section.

\(4\) Episodic use of the Argos DCS may also be authorized where
specific instances when there is a significant possibility for loss of
life. Such use shall be closely monitored.

\(5\) Testing use of the Argos DCS will only be authorized for
manufacturers of Argos DCS platforms, that require access to the system
in order to test and certify prototype and production models.

d\) In the event that Argos DCS capacity limitations require that
priority determinations be made, priority will be given to those
platforms that provide environmental data of broad international
interest, especially of an operational nature, and to those requiring
the unique capabilities of the Argos DCS, such as platform location or
polar coverage.

### Argos Data Collection System Use Agreements

a\) In order to use the Argos DCS, each user must have an agreement with
the approving authority for that system.

b\) These agreements will address, but may not be limited to, the
following matters:

\(1\) The period of time the agreement is valid and procedures for its
termination,

\(2\) The authorized use(s), and its priorities for use,

\(3\) The extent of the availability of commercial space-based services
which meet the user's requirements and the reasons for necessitating the
use of the Argos DCS,

\(4\) Any applicable government interest in the data,

\(5\) Required equipment standards,

\(6\) Standards of operation,

\(7\) Conformance with applicable ITU and national agency radio
frequency ­agreements and regulations,

\(8\) Reporting time and frequencies,

\(9\) Data formats,

\(10\) Data delivery systems and schedules, and

\(11\) User-borne costs.

c\) The Approving Authority shall evaluate user requests and conclude
agreements for use of the Argos DCS.

d\) (1) Agreements for the collection, via the Argos DCS, of
environmental data by government agencies or non-profit institutions
shall be valid for 3 years from the date of initial in-situ deployment
of the platforms, and may be renewed for additional 3-year periods.

\(2\) Agreements for the collection of environmental data, via the Argos
DCS, by non-government users shall be valid for 1 year from the date of
initial in-situ deployment of the platforms, and may be renewed for
additional 1-year periods, but only for so long as there exists a
governmental interest in the receipt of these data.

\(3\) Agreements for the collection of non-environmental data, via the
Argos DCS, by government agencies, or non-profit institutions where
there is a government interest, shall be valid for 1 year from the date
of initial in-situ deployment of the platforms, and may be renewed for
additional 1-year periods.

\(4\) Agreements for the episodic collection of non-environmental data,
via the Argos DCS, shall be of short, finite duration not to exceed 1
year without exception, and usually shall not exceed 6 months. These
agreements shall be closely monitored and shall not be renewed.

\(5\) Agreements for the testing use of the Argos DCS by equipment
manufacturers shall be valid for 1 year from the date of initial
testing, and may be renewed for additional 1-year periods.

### Treatment of Data

a\) All Argos DCS users must agree to permit Argos Participating
Agencies, and their governments' agencies the full, open, timely, and
appropriate use as determine by the Participating Agencies of all
environmental data collected from their platforms; this may include the
international distribution of environmental data under the auspices of
the World Meteorological Organization.

b\) Raw data from the Argos DCS space segment is openly transmitted and
accessible.

c\) Accessibility of the Argos DCS processed data from the ground
segment is handled in accordance with the users specifications and
system design limitations, subject to the provisions stated in Data
Treatment Section (a) of this policy.

4.2.6 Technical requirements

a\) All platform operators of the Argos DCS must use a data collection
platform radio set whose technical and design characteristics are
certified to conform to applicable specifications and regulations.

b\) All platform operators are responsible for all costs associated with
the procurement and operation of the platforms, and for the acquisition
of data from those platforms, either directly from the satellite or from
the applicable data processing center.

## Understandings

a\) The Argos Operations Committee reserves the right to terminate or
suspend the user's participation in this program in the event of
spacecraft or ground equipment limitations requiring curtailment or
elimination of services.

b\) PTTs which the user plans to implement as part of the Argos DCS are
subject to type-certification by the operator before deployment.
However, such certification does not imply any judgment or endorsement
as to the PTT's performance.

## Specific Responsibilities of the User

The user shall:

a\) Notify the Operator, within a reasonable time, of any changes to the
program.

b\) Obtain and utilize PTTs manufactured and type-certified in
accordance with the specifications and rules stipulated in the "Argos
Platform Transmitter Terminal General Specifications and Certification"
document available from the operator upon request.

c\) Obtain authorization from the appropriate national authorities to
transmit on the frequency specified in the "General Specifications and
Certification" document.

d\) Comply with all applicable laws and regulations, and the terms and
conditions for operation of the system which have been agreed to by the
Argos participating agencies (and which shall be available upon
request).

e\) Provide periodic reports, upon request by the operator, on the uses
of location and sensor data.

f\) Make all reasonable efforts to deactivate platforms which are either
performing outside the system specifications; malfunctioning in a manner
that interferes with the other platforms or with general system
operations, or are in a program which has been terminated.

## Specific Responsibilities of Operator

The operator shall:

a\) Oversee the collection, processing , and transmission of Argos data.

b\) Notify the user, through the agent, of changes to the established
operational plan. Notification will normally be prior to initiation of
such changes, except when sudden abnormal spacecraft or operational
conditions preclude such prior notification. In any event, notification
will be made as soon as possible.

c\) Notify the user, through the agent, by the most efficient means
available, whenever Argos system monitoring indicates that a platform is
performing outside system specifications or is malfunctioning in a
manner that interferes with the other platforms or with general system
operation; and require the user to make every reasonable effort to
deactivate such a platform.

## Disclaimers

a\) The operator will make every effort to maintain the Argos DCS in
full operation at all times subject to the availability of
appropriations. The operator will bear no responsibility for any losses
as a result of the non-availability of the DCS.

b\) The operator can not guarantee the timeliness of data dissemination,
the accuracy of the data provided or their suitability for any
application whatsoever, and cannot be held responsible for any damage,
including loss of life, resulting from defective operation of the Argos
DCS.

c\) In the event of damage being suffered by the goods or personnel of
the user or third parties, and insofar as such damage arises out of the
use of the equipment, the Operator shall not be liable.

d\) The user agrees not to make any claim or bring any action against
the operators, or any of their employees or agents and the user agrees
to indemnify and hold each such entity and individual harmless against
any such claim or action brought by any third party and any award of
damages, loss, or other expense incurred in connection therewith
(including attorneys' fees) where such claim or action is based,
directly or indirectly in whole or in part on the use of the Argos
system. Indemnification shall not be applicable in those instances where
the user is not allowed by applicable law to indemnify.

## Period of Use/Termination

a\) Either party to the System Use Agreement may request amendments by
letter to the signatories of this System Use Agreement and such
amendments will take effect upon the consent of all parties.

b\) Within 30 days of the expiration of the approved period of use,
users may request to renew the system use agreement. These agreements
will be renewed in accordance with all applicable laws and regulations.
Renewal is not automatic, however, and there may be instances when the
agreements will not be renewed.

## Dispute Settlement

In the case of any disputes arising out of the terms of this agreement,
the matter will be referred to the Argos Operations Committee for
settlement.

# SPACE Segment

Details on the operation and agreed upon roles of the Participants of
the Program are outlined for each launch in the Joint Project Plan. A
copy of the most recent Joint Project Plan can be found on NOAA Argos
DCS information web site http://noaasis.noaa.gov/ARGOS.

## SPACECRAFT Issues

A chart depicting the drift rates of the NOAA Polar Satellites
demonstrates the need for NOAA to control the drift of the \"afternoon\"
missions. Currently, the afternoon satellites drift approximately 1 hour
from their designated equator crossing nodes (orbiter) in a 2.5 year
period. As a result of this drift, NOAA has implemented a procedure to
inject the afternoon satellites, starting with NOAA-L, into a more
stable orbit. It is projected that these satellites will drift only 2
hours in an 8 year period. (31^st^ O/C)

### TIROS-N TYPE SPACECRAFT

TIROS-N was successfully launched on October 13, 1978. Some problems
were encountered with attitude control, due to the loss of hydrazine,
but this was corrected. The Argos instruments functioned satisfactorily.
(8th O/C)

### SPACECRAFT CALLUP

#### Current Callup Conditions

Current conditions for spacecraft callup are:

a\. If the thermal vacuum tests have successfully been completed, callup
may occur within 120 days.

b\. If the thermal vacuum tests have not been successfully completed,
then 150 days are required.

The above apply only to launches with expendable launch vehicles. (12th
O/C)

#### Single Spacecraft System

With the advent of the single spacecraft system, the launch schedule
will reflect launches at 18 month intervals. Therefore, the spacecraft
callup criteria previously used will no longer be valid. (15th O/C)

### ADVANCED TIROS-N TYPE SPACECRAFT

#### NOAA-E, Search & Rescue

NOAA-E will be the first spacecraft that will contain the Search and
Rescue package and will require ground system changes for its operation.
The decision to launch NOAA-E before NOAA-D will not be made until
sometime in 1981. (12th O/C)

#### NOAA-E, Launch

NOAA-E is now planned to be launched in June 1982, instead of March 1982
as was planned earlier, due to conflicts at the Western Test Range.
(14th O/C)

##### NOAA-E, Launch Reschedule

NOAA-E has been rescheduled for launch during February 1993. (15th O/C)

### NOAA-D SPACECRAFT

#### NOAA-D Launch Callup

NOAA-D is ready for launch callup and will remain so until NOAA-E is
ready for launch callup. If NOAA-E is launched before NOAA-D, the NOAA-D
spacecraft will be stored and maintained as a backup for NOAA-E. (13th
O/C)

#### NOAA-D Launch

NOAA-D is in storage but is now in queue for launch after NOAA-H. It is
not required by the U.S. Navy. (19th O/C)

#### NOAA-D Status

The spacecraft was launched on May 14, 1991 and replaced NOAA-10 as the
operational morning spacecraft. This satellite is based upon the
original Tiros-N bus. All instruments and subsystems are operating
normally; the SARP is not flown on this spacecraft (now NOAA 12). (28th
O/C)

The DCS system is operational using Receiver 1 and Data Recovery Units
1, 2, 3 and 4. Data are used by CLS and SAI. (29^th^ and 31^st^ O/C)

NOAA-12 is the primary \"morning\" satellite. All instruments are
operating without problems. (30^th^ O/C)

The NOAA-12 satellite continues to be the operational missions in the
morning orbit. The primary sounding instrument on NOAA-12, the HIRS/2,
has demonstrated a filter wheel problem since May 30 . The temperature
sounding data from the instrument is noisy and as of late June, 1997
NOAA is evaluating the impact the data is having on the production of
numerical weather forecasts. It is possible that NOAA will process
NOAA-11 sounding data on a semi-operational basis (taking all 14 orbits
of data in 3 contacts with the satellite on a daily basis) if the HIRS/2
on NOAA-12 is deemed as a non-operational instrument (i.e. the
instrument data is too noisy or the filter wheel fails). The Argos
instrument continues to provide useful data to the user community. The
NESDIS Assistant Administrator has decided not to launch NOAA-K earlier
than February, 1998 (31^st^ O/C)

NOAA-12 is now the secondary AM satellite and will back up to NOAA-15
when needed. The HIRS instrument has failed and NOAA-11 HIRS will be
used for sounding products. Tape recorder 5A has failed, 2B has problems
and is used in a limited role. The DCS system is operational and using
Receiver 1 along with DRU 1, 2, 3, and 4. All units are fully
operational. (32^nd^ and 33^rd^ O/C)

The NOAA-12 satellite is being used to supplement NOAA-15's LAC and HRTP
transmissions. (37^th^ O/C).

The DCS is fully operational (34^th^, 35^th^ , 36^th^, 37th and 38th
O/C)

### NOAA-F, G SPACECRAFT

#### NOAA-F Status

The spacecraft was launched on December 12, 1984 into an equator
crossing time of 14:30 ascending node and drifted to 20:45 in the last
9.5 years. The spacecraft (now NOAA-9) is currently in a standby status
and is planned to be deactivated following successful launch and
activation of NOAA-I. (27th O/C)

NOAA-9 will likely be \"decommissioned\" following the launch of NOAA-J
later in 1994. NOAA acquires NOAA-9 data 4 times daily, which is
sufficient to provide 24 hour global coverage. (28th O/C)

The Data Collection System is operating on Receiver 2. DRU1 was kept on
to allow the DCS to be used to maintain an accurate measurement of the
orbital elements. On December 20, 1993 all DRUs were commanded \"on\" to
fill global data coverage gaps from other satellites. However, the
transmission of the data to the Argos Processing Center is in delayed
mode. Data are processed by CLS and SAI as available. (29^th^ O/C)

NOAA-9 has experienced a number of anomalies in 1996 which caused
several data outages. It may be necessary for NOAA to reassess the need
to continue collecting data from this 11 1/2 year-old satellite and
perhaps collect Argos data from NOAA-11 instead. An evaluation of the
equator crossing nodes of the polar satellites reveals that NOAA-9 has
drifted 7 1/2 hrs since launch in late 1984. NOAA-14, launched in
December 1994. has only drifted 14 minutes since launch. (30^th^ O/C)

NOAA-9 is the most important stand‑by satellite since it provides SBUV/2
and Search & Rescue data to the user community four times per day. The
ERBE non‑scanner was deactivated in early 1997 after the satellite
suffered a power system anomaly. If the HIRS instrument on NOAA‑12 is
deemed non-operational, the NOAA-9 satellite will be de‑activated to
allow NOAA\'s satellite Operations Control Center to collect HIRS/2 data
from NOAA‑11 four times per day. This will allow the Argos data users to
collect an additional source of data from a third NOAA satellite.
(31^st^ O/C)

NOAA-9 was decommissioned February 20, 1998 (32^nd^ O/C)

#### NOAA-G Status

The spacecraft was launched September 17, 1986 and remained in operation
as the morning satellite until September 1991, when NOAA-12 became the
operational morning satellite. The satellite (now NOAA-10) is in standby
status. Following launch of NOAA-I, NOAA is unable to sustain operations
of both 9 and 10; NOAA-10 will remain in active standby and NOAA-9 will
be deactivated. (27th O/C)

The Data Collection System is operating on Receiver 1 and Data Recovery
Units 1, 2, 3 and 4. However, data are not available to CLS and SAI.
(29^th^ O/C)

NOAA-10 is in \"standby\" status and as such NOAA/SOCC makes only one
contact per week with this satellite. (30^th^, 31^st^, 32^nd^ O/C)

N-10 is in stand-by status supporting search and rescue (34^th^ O/C)

### NOAA-H, I and J SPACECRAFT

#### NOAA-H Status

The spacecraft was launched in September, 1988 and drifted from 13:40
ascending node orbit to the current 16:30 ascending node. Y and Z gyros
failed and reduced gyro software has been controlling the spacecraft in
a nominal mode since May 1990. The spacecraft orbit is experiencing
significant drift due to orbit launch bias. Argos DRU \# 4 has been
deactivated (failed right after launch). This spacecraft (now NOAA-11)
will become a standby after the successful launch of NOAA-J later in
1994. (28th O/C)

The Data Collection System is fully operational on its single receiver.
Data Recovery Unit 4, which had a low throughput, has been turned off
and is considered failed. The three remaining DRUs are operating
normally. Analog telemetry channel 95, DCS receiver gain, showed a 6dB
drop in gain on March 19, 1992. Data are not available to CLS and SAI.
(29^th^ and 31^st^ O/C)

NOAA-11 is in \"standby\" status and as such NOAA/SOCC makes only one
contact per week with this satellite. (30^th^ and 31^st^ O/C)

NOAA-11 is providing sounding data with its HIRS instrument. The DCS is
fully operational with DRU 4 turned off. The three remaining DRUs are
operating nominally. The SARP instrument is fully operational. (32^nd^,
33^rd^, 34^th^ , 35^th^ and 36^th^ O/C)

N-11 is in stand-by status supporting search and rescue (34^th^ O/C)

NOAA-11 is in standby mode and recorded data from DCS is downloaded only
several times per day. It is not clear whether real time data can be
received from this satellite (36^th^ O/C)

The NOAA-11 was de-activated in mid-June 2004. (38^th^ O/C)

#### NOAA-I Failure

NASA presented a summary of the NOAA-13 power system failure which
occurred on August 21, 1993. A failure Review Board, established at the
NASA/GSFC, investigated the NOAA-13 anomaly through analysis of
satellite telemetry and inspection of NOAA-J hardware.

The failure, isolated to a short in the unregulated 28 volt power bus,
prevented charging of the batteries. Review of drawings and flight
hardware indicated significant mechanical tolerance issues and poor
packaging design that supported the conclusion of a catastrophic short
in the Battery Charge Assembly (BCX). The NOAA-J BCX was modified to a
more robust design, thoroughly tested, and performed flawlessly during
the recent thermal vacuum test. In addition, the flight software has
been modified to recognize a similar BCX short and take autonomous
corrective action.

The final failure review report, now in signature cycle, was provided to
the O/C. (29th O/C)

#### NOAA-J -- Launch

Scheduled for November, 1994 (28th O/C)

The DCS on NOAA-14, launched in December 1994, has four DRUs in
operation. Data are used by CLS and SAI. (29th O/C)

The primary \"afternoon\" satellite is NOAA-14. All instruments are
operating nominally except for the SARP, which failed in March 1995.
(30^th^ and 31^st^ O/C)

The NOAA-14 continues to be the operational missions in the afternoon
orbit. The ozone profiler on NOAA-14, SBUV/2, has experienced grating
drive problems late in 1996 which affect the calibration of the data.
The Argos on NOAA‑14 continues to operate nominally. The Search & Rescue
Processor is the only instrument to have failed on the satellite. (31st
O/C)

NOAA-14 is the primary PM satellite. One of two CPU's have failed, the
SARP has failed, and Tape Recorder \# 4 is inoperable. The ozone
capability is marginal because the SBUV/2 is experiencing a grating
drive anomaly (32nd O/C)

The N-14 blind orbit STIP data that normally is down-linked over the
Lannion CDA is being temporarily discontinued since Lannion has stated
an inability to process the data due to Y2K equipment problems and due
to a lack of tape resources on N-14. The tape recorder used to down-link
STIP will now be used to down-link LAC data. NOAA-14 is drifting
severely and the environmental products are in danger of becoming
useless due to the drift problem. (34^th^ O/C)

NOAA-14 orbital plane is drifting at a rate of 5 minutes per month, or
one hour per year. During the past year NOAA-14 crossed the orbital
plane of NOAA-12. The data of both satellites were somewhat redundant.
At the date of the 37^th^ OPSCOM meeting NOAA-14 will cross NOAA-15
orbital plane. At the same time NOAA-12 will fill the gap between
NOAA-15 and 16 and its data will be more important than those of
NOAA-14. R. Bassett requested guidance as to the desired changes in the
NOAA Satellite constellation upon the launch of NOAA-M and an action
item was opened for CNES/CLS to report the utility of data from NOAA
back-up satellites. (36th O/C)

The DCS instrument and all DRU's are operating nominally. (32^nd^,
33^rd^, 34^th^, 35^th^ , 36^th^ ,37^th^ and 38^th^ O/C)

### NOAA-K, L and M SPACECRAFT

#### NOAA K, L, M Slowdown

Work on the NOAA K, L, M spacecraft was essentially terminated with a
NOAA-directed funding cap during 1991. Contractor has continued a low
level of effort so that NOAA K bus integration can begin as soon as
possible after funding is restored. Work continued on instruments and
recorders.

Since March 31, 1992, funding guidelines provided by NOAA may allow a
more beneficial schedule. NOAA K bus integration may now begin January
1, 1993, with a satellite launch availability of October 1994. Schedules
will become evident soon after the Metsat project and Contractor can
review the guidelines and a new program baseline proposal can be
presented by Contractor. (26th O/C)

#### NOAA-K, L, M Schedules

The NOAA-K, L, and M spacecraft were scheduled to be launched on the
following dates (28th O/C):

-   NOAA-K - June , 1996

-   NOAA-L - May, 1997

-   NOAA-M - June, 1999

#### NOAA-K

The NOAA-K integration and test schedule is proceeding on schedule. EMI
testing has been completed and thermal/vacuum testing will take place in
late July. The usual number of problems have been found but none of
these will seriously affect the scheduled launch. The planned launch
date is January 30, 1996. (29^th^ O/C)

Starting with NOAA-K, the new microwave instruments will replace the
MSU. These are AMSU-A1, AMSU-A2 and AMSU-B. (29th O/C)

The latest POES schedule indicates NOAA-K may be launched in either the
Spring or Fall of 1997, depending on the need to replace failed assets
in orbit, launch pad availability, and spacecraft development schedules.
(30^th^ O/C)

The launch date for NOAA-K is scheduled for February 1998. (31^st^ O/C)

NOAA-K is now NOAA-15 and is undergoing a 60-day on-orbit verification
checkout which is scheduled to end mid-July. NOAA-15 will replace
NOAA-12 as the primary morning satellite. All instruments on NOAA-15 are
operating nominally with the exception of AMSU-B. The AMSU-B has a scan
position dependant warm bias on channels 17 and 19. (32^nd^ O/C).

A Wade informed the OPSCOM members that N-15, S-Band down link
communications, consists of two channels and not the normal three
channel configuration due to antenna degradation. The HIRS instrument on
N-15 is behaving erratically. One of the gyros on N-15 has be turned off
leaving N-15 with only two gyros. (34^th^ O/C)

The Data Collection System (DCS) Instrument and all Data Recovery Units
(DRU) are fully operational (32^nd^, 33^rd^, 34^th^, 35^th^ , 36^th^
,37^th^ and 38^th^ O/C)

#### NOAA-L

NOAA-L has been shipped from East Windsor, NJ, to Sunnyvale, CA. NOAA-L
will undergo post-shipment testing and then be placed in storage. NOAA-L
completed vibration testing prior to shipment. EMI testing and thermal
vacuum will be done in Sunnyvale, CA. (32^nd^ O/C)

Lockheed Martin Missiles and Space (LMMS) has moved its spacecraft
operations from the East to the West Coast of the US. Resulting from
this move is a projected significant cost over-run in the NOAA budget.
This may make it difficult to accommodate the Argos-3 down-link
transmitter on NOAA-N'. The launch of NOAA-L into a 2:00 PM orbit is
planned for late February 2000. NOAA-M will be launched approximately 1
year later in March 2001. (33^rd^ O/C)

NOAA-L is scheduled to be launched from Vandernberg Air Force Base on
August 29, 2000. (34^th^ O/C)Launched September 2000, NOAA-L is now
NOAA-16. He reported on the various anomalies of NOAA-16 such as
spacecraft pointing, satellite computer, and VHF communications (APT).
NOAA-16 is now operational. It became operational March 20 after an
extensive early on-orbit evaluation. The instrument was successfully
activated and is now fully operational. (35^th^ , 36^th^ , 37^th^ and
38^th^ O/C)

#### NOAA-M

After testing of NOAA-M is completed, the LMMS plant in East Windsor NJ
will be closed and all work transferred to Sunnyvale, Cal. This is
expected to begin in April, 1998. (31^st^ O/C)

The NOAA-M satellite has completed EMI testing and Thermal vacuum
testing will occur in Sunnyvale, CA, in 1999. NOAA-M has been shipped
from East Windsor, NJ, to Sunnyvale, CA. (32^nd^ O/C)

NOAA-M is currently in storage. The launch of NOAA-M is likely to occur
following a much shorter interval than normal after the NOAA-L launch
(the current planned launch date is May 2001). This is because the
NOAA-K spacecraft has several significant problems and the Titan II
launch pad is scheduled to be closed in 2002. (34^th^ O/C)

The launch of NOAA-M is now scheduled for 28 March 2002. (35 O/C)

.NOAA-M is ready for launch into a 10 A.M. equatorial crossing orbit.
The scheduled launch date is 24 June 2002. R. Bassett noted that there
are several actions such as handbook updates and constellation charges
that should be completed prior to launch of a new satellite. C. Gal
noted that some of the Argos instrument information in the NOAA-M
handbook was incorrect. (36^th^ O/C)

NOAA-M is now NOAA-17. The current on-orbit operational satellite
constellation maintained by NOAA consists of the NOAA-17, 16, 15, 14,
and 12 satellites. NOAA-17 was launched June 24, 2002 and deemed the
operational \'morning\' (daylight equator crossing is around 1030 local)
satellite in October 2002 replacing NOAA-15. With the AMSU A1 instrument
failing on NOAA-17 in October 2003, NOAA-15 has been re-tasked to
provide the operational sounding data using its AMSU A1 instrument. This
event is significant to the Argos community in that the data from
NOAA-15 is recovered in its entirety with an operational priority
equivalent to NOAA-17 and NOAA-16. When NOAA-16 was launched on
September 21, 2000 it eventually replaced NOAA-14 as the primary
afternoon satellite (daylight equator crossing is around 1330 local).
NOAA-16 has had various on-orbit anomalies that prevent the satellite
from operating at its full capability in providing data for user
community. These anomalies have necessitated the call-up of NOAA-N in
February 2005. The NOAA-14 satellite\'s orbit has drifted to an almost
7:00 pm (local) equator crossing node (ECN). It is considered a backup
satellite both operationally and in science data recovery. With
\'backup\' status, any conflicts with NOAA-17, NOAA-16, or NOAA-15 data
recovery efforts will be mitigated with NOAA-14 receiving a lower
priority (i.e., less timely data retrieval). NOAA-12 is currently in
standby mode and transmitting APT and HRPT data real-time, and
\'dumping\' STIP (2-4 orbits of recorded low rate data which includes
Argos DCS) once per day. (38^th^ O/C)

### POST NOAA-M ERA

#### NOAA-N \"Gap Filler\" 

Contingent on obtaining necessary budgetary and programmatic approval,
NOAA plans to procure a new series of free-flyers to continue afternoon
services for the operational payload. NOAA would procure one additional
spacecraft in the NOAA-K, L, M series as a gap filler (NOAA N). (23rd
O/C)

To begin planning for an instrument for NOAA N, CNES asked NOAA to
provide in writing a firm assurance that it plans to procure a NOAA N in
the NOAA K, L, M series. (24th O/C)

The spacecraft launch \"need date\" for NOAA-N is late 2003 to be ready
to replace a failed launch of NOAA-N. (31^st^ O/C)

Manufacturing of NOAA N spacecraft and spares was suspended in East
Windsor, NJ, in April 1998. Sixty of 90 subsystems were completed.
Assembly of the NOAA-N spacecraft has not yet started (32^nd^ O/C)

The Argos-2 Joint Project Plan was amended to include the NOAA-N
satellite. The letter was signed by NESDIS Deputy Assistant
Administrator, Mary Glackin and sent to Mr. Marc Pircher of CNES and Al
Diaz of NASA. Mr. Pircher is Director for orbital systems and Al Diaz is
the Center Director for NASA/GSFC. The NOAA-N satellite has completed
modal testing and the SARP-2 and DCS-2 are on the spacecraft. (34^th^
O/C)

The Receiving and Power Unit (RPU) of the DCS installed on NOAA-N
exhibited an anomaly and has been returned to the contractor for
investigation and repair. These operations are currently being
performed. (35^th^ O/C)

Testing of NOAA-N will be completed in the last quarter of this year and
will go into storage. The Argos-2 DCS installed on NOAA-N experienced an
anomaly due to a Ultra Stable Oscillator (USO) bad start resulting in
blowing the satellite bus line fuse. The instrument was returned to
France and the USO malfunction was fixed. The instrument is back on the
satellite since February 2002, ready to continue the satellite test
sequence: thermal vacuum in August/September 2002. (36^th^ O/C)

Launch of NOAA-N is planned for late June 2004 but several significant
technical problems need to be solved first. After the launch testing
will resume with work being completed by the end of 2004. (37^th^ O/C)

Launch of NOAA-N is planned for February 2005 The instrument is ready
for flight. It is the last of the four Argos.2 DCS. Compared to the
three already in operation, there is nothing new in terms of
performances. (38^th^ O/C)

#### U.S. - European Cooperation

NOAA and NASA are working with ESA and EUMETSAT to secure a commitment
to fly platforms for the morning operational service. EUMETSAT would
provide the European Polar Platform (EPOP) communications and data
handling system and a European Ground System (CDA and DPC). (23rd O/C)

NOAA\'s future ground system would receive NOAA free-flyer and EPOP
operational data in near real-time at the USGPC, as well as selected
global data sets from the prototype operational instruments that will be
flown on the NASA polar platform (NPOP). NOAA will also relay global
operational level 0 data sets back and forth in near real-time between a
U.S. DPC and a European DPC. (23rd O/C)

#### Post NOAA-M Funding

The U.S. FY 1993 budget included \$47 million for post NOAA-M. The FY
1994 and 1995 budgets submitted to Congress included \$45 million and
\$165 million respectively for the post NOAA-M program. (27th O/C)

On the European side, in November 1992, the European Space Agency
meeting at the Ministerial level agreed to fund a METOP-1 morning polar
operational meteorological mission planned for launch in 2000. EUMETSAT
for its part resolved in September 1992 to provide a financial
contribution to ESA for the METOP program. Further, EUMETSAT agreed in
November 1992 to provide \$35.4 million for the EUMETSAT polar satellite
preparatory program (in parallel with the METOP-1 preparatory program)
as a first step in the development of a series of satellites to provide
continuous observation from the morning polar orbit. (27th O/C)

#### Polar-satellite Convergence

L. Heacock, NOAA Transition Team Leader for Convergence, briefed the O/C
on the May 5, 1994, decision by the U.S. Government to converge the NOAA
polar satellite program, the Department of Defense Meteorological
Satellite Program (DMSP), and the NASA Earth Observing System (P.M.
platform). The U.S. has emphasized the continued importance of
international cooperation and continued open distribution of
environmental data worldwide from a converged system. Mr. Heacock
emphasized the invitation to ESA and EUMETSAT to be part of the
converged system with METOP in the 09:30 node orbit. NOAA will work with
ESA and EUMETSAT on a method whereby METOP could satisfy U.S. mission
requirements. (28th O/C)

C. Wooldridge presented the status report on planning for NOAA N\' and
METOP cooperation. For the U.S. polar mission, C. Wooldridge reviewed
the May 1994 Presidential Decision Directive to establish a National
Polar-orbiting Operational Environmental Satellite System (NPOESS).
Since the last Operation Committee meeting, an Integrated Program Office
was established within NOAA and is headed by Mr. Mennan. Also in May
1995, a Memorandum of Understanding on NPOESS cooperation was signed by
the Department of Commerce, NASA and the Department of Defense. The
converged system is being implemented in a manner that encourages
international cooperation such as the long-standing NOAA-European
cooperation. The establishment of requirements for the NPOESS spacecraft
has begun. (29th O/C)

An overview of the changes made to NOAA-N and N' reveals significant
differences between the NOAA-K, K, M series and NOAA-N and N'. The
changes include: replace digital recorders with solid state recorders;
reducing the field of view of the HIRS measurements from 20km to 10km;
new adapters for the Microwave Humidity Sounder and the Delta II launch
vehicle; and a change to the transmit frequencies for APT Direct
Broadcast Services. The new frequencies are 137.1 and 137.9125 Mhz.

A new launch policy has been established by NOAA as a result of the
study to review the operational lifetimes of NOAA\'s in-orbit assets. A
\"launch on failure\" policy was established to save considerable
near-term funds for the polar program. It was found that the NPOESS-1
launch availability date can be delayed from 2004 to 2007/8 without too
many risks to the current program. In order to ensure that NOAA assets
will last until 2007/8, several enhancements are being considered.

The candidate enhancements for NOAA-N' will be evaluated by an Executive
Committee of NOAA, DoD, and NASA managers at the end of July 1996. It is
possible that NOAA will request that funding for the accommodation of
the new Argos-III instrument on NOAA-N' be provided by the Integrated
Program Office as part of the list of enhancements being considered for
NOAA-N.

The result of the Argos-III accommodation study reveals that there are
no technical difficulties in incorporating the new downlink messaging on
NOAA-N'. However, the cost is not significant. Meeting the July 1999
need date for instrument integration on NOAA-N' is the most vital issue
to NOAA. Once NOAA has received assurances from CNES that this new
capability can be delivered by this date, NOAA will locate the necessary
funds to proceed with this accommodation. (30^th^ O/C)

The future of the NOAA Polar-orbiting Operational Environmental
Satellite (POES) program\'s support of the Argos community currently
consists of the successful launch and activation of the NOAA N and N\'
satellites. While the NOAA N satellite (planned launch February 2005)
will provide coverage for the Argos community from a 2 pm, afternoon
orbit, the METOP satellites will provide coverage from the 930 am
morning orbit (planned launch December 2005). The METOP satellites are
being provided as part of an Initial Joint Polar System (IJPS) agreement
between NOAA and the European Organization for the Exploitation of
Meteorological Satellites (EUMETSAT). Under the IJPS, each group (NOAA
and EUMETSAT) will operate their respective satellites and ground
segments while exchanging and sharing the data collected by all
satellites. This data sharing agreement will greatly benefit the Argos
community by eliminating the current \'blind orbit\' data recovery
delay. After the launch of the first METOP satellite, the National
Polar-orbiting Operational Environmental Satellite System (NPOESS) is
scheduled to begin deployment in 2010. NPOESS is designed to meet the
operational satellite needs of both the civilian and national security
communities and plans to provide data coverage from the 530 and 1330
orbit planes. The NOAA Integrated Program Office (IPO) develops,
manages, procures, acquires and operates the NPOESS satellites. (38^th^
O/C)

#### NOAA-N'

In April, 1997, the Integrated Program Office released an invitation to
tender for five new instruments designated for NPOESS. The IPO plans to
award two contracts per instrument development study during the summer
of 1997. Three of these instruments are designated by the IPO as
potential candidate sensors for NOAA-N\'. These are:

1\. The Ozone Mapper / Profiler Suite

2\. Cross‑track Infrared Temperature Sounder, and

3\. Global Positioning System Occultation sensor.

NASA is conducting a spacecraft data handling study that will examine
the components on the NOAA‑N + N\' satellites that need to be upgraded.
In order to be ready to accommodate the three sensors proposed by IPO
for NOAA‑N\', NASA has been directed by NOAA to assess the impacts
associated with NOAA\'s ground and data processing and archive systems.
The study will also reveal the modifications which are necessary to
ingest the Metop \"packetized\" data in 2003. The full system study and
implementation cost estimates will include impacts on the NESDIS
communications, telemetry, command and data processing systems.

NOAA has requested that NASA also evaluate several enhancements to the
NOAA‑N\' mission. Included in the list is the accommodation of the
Argos-3 instrument with the forward messaging capability.

A chart depicting the schedule of the NASA reveals the ground system
analysis will be completed in December 1997. The spacecraft data
handling study will be completed in October of 1997. At that point NOAA
will select which instruments will be accommodated on NOAA-N\'. (31st
O/C)

Manufacturing of NOAA N' spacecraft and spares was suspended in East
Windsor, NJ, in April 1998. Sixty of 90 subsystems were completed.

A. Wade reported on the NPOESS accommodation study conducted by NASA
under the direction of NOAA. Lockheed Martin is performing a study which
will culminate in a cost estimate by August 1998. The cost estimate will
include costs associated with the accommodation of NPOESS instruments
and NESDIS study items. The NPOESS instruments studied are CrIS, GPSOS,
and OMPS. NESDIS study items included Full Time 6-channel AVHRR data,
processing global 1 Km AVHRR, adding CrIS sounder data to Direct
Broadcast, changing the C and DH system to CCSDS format, and
accommodating Argos-3 on NOAA-N'. (32^nd^ O/C)

Three A-DCS accommodation issues are reviewed by NOAA:

Option 1, separate receive and transmit antennas for up and down-link
transmission of Argos data,

Option 2, a single receive/transmit antenna and,

Option 3, a baseline accommodation with receive only capability.

A. Wade presented the risks of each option. Option 2 is considered the
higher risk of the three options because it presents EMI risks to search
and rescue as well as other instruments. C.Gal stated that the
requirements for the A-DCS transmit antenna pattern/gain should be
reviewed if the solution of a deployable antenna is not feasible. A
smaller fixed antenna (the METOP solution) or at the extreme a unique
transmit/receive wide-band antenna (the ADEOS-II solution) may be
considered and closely coordinated between NOAA and CNES. H. Wood stated
that the presentation was an overview of the current issues regarding
the A-DCS accommodation and a more comprehensive exchange of information
should follow. H. Wood commented that there are significant increases in
the POES budget and the accommodation of A-DCS on NOAA-N' was the single
biggest item. (33^rd^ O/C)

Jim Mentall discussed why it is imperative that the Argos-3 instrument
be delivered to Lockheed Martin by mid-2001 if it is to receive adequate
testing. J. Mentall also reported that the Lockheed Martin design for
accommodating Argos-3 on NOAA-N' is proceeding smoothly and on schedule.
The new down-link antenna is likely to exceed the CNES requirements. It
is important, however, that the Interface Document have its final review
is signed by all parties. (34^th^ O/C)

A final design review for the A-DCS and SARP-3 instruments was held on
April 25, 2000. The spacecraft contractor has stepped-up its effort on
the accommodation of these two instruments on the NOAA-N' satellite. The
location of the antenna for the new transmit capability has been chosen
on the spacecraft. The Argos-3 JPP space segment draft has been reviewed
by CNES and comments sent to NOAA. NOAA has acquired a full time person
to act as liaison between IPO, NESDIS and CNES. (34^th^ O/C)

The delivery date of the A-DCS for NOAA-N' is critical. The instrument
PFM-1 will be delivered to NOAA in 2001. NOAA/NASA will check if a date,
at the earliest by the end of July 2001 is acceptable. At this date CNES
could deliver a functional proto flight model, but with software not
fully validated, implying that at some point in time one unit of the
instrument (the RPU) should be made available to CNES for final software
uploading at LMMS. If two or three more months would become available
i.e. a delivery in October/November 2001 the instrument could be final.
NOAA and CNES will closely monitor the schedule situation. (34^th^ O/C)

Late delivery of the A-DCS has created a problem for integrating this
instrument on NOAA-N'. The development of FM2 to be installed is going
on with the delivery of the FM2 to NOAA planned in February 2002 and the
opportunity will hopefully arise allowing it to be mounted on the
spacecraft prior to vibration testing. (35^th^ O/C)

It was noted that the SARSAT/3 and ARGOS/3 Flight Models have not yet
been delivered to Lockheed Martin. Delivery prior to the start of
preparation for Thermal/Vacuum Testing is critical. These preparations
are scheduled to start in February 2003 but could start several months
earlier. The NOAA co-chair recognized that while technical
considerations may affect instruments delivery dates, every effort must
be made to minimize the impact on the integration costs and schedule to
ensure the full viability of the Argos Program. The FM-3 should be ready
end of September 2002 for a delivery to NOAA/LMSSC for NOAA-N\' in
October 2002. As there is no possibility to load a new software after
delivery, the later the delivery, the better. Consequently, NASA and
CNES are presently working to find ways to make progress on the NAGE
software before delivery. A Technical Interface Meeting (TIM) is being
planned early September 2002 on this question (among others). (36^th^
O/C)

Thermal-Vacuum testing has been completed on NOAA N-prime. This
spacecraft is going into temporary storage until after the launch of
NOAA-N. NASA reported that the A-DCS was successfully integrated onto
the NOAA N-prime spacecraft. Unfortunately during satellite
thermal-vacuum testing a significant number of test messages were not
correctly processed. Some "failures" were just a mater of definition but
others were real failures of the A-DCS processing messages. The most
significant anomaly was that 6 times the times the instrument stopped
processing messages entirely and a "restart" command had to be sent.
After N-prime goes into storage A-DCS will be sent back to CNES for
trouble shooting. (37^th^ O/C)

On September 6, 2003, an unfortunate handling accident occurred during
the integration and testing of the NOAA N\' satellite. As a result of
the accident, the satellite was completely disassembled and a re-build
decision has not been made. NOAA N\' would be the first NOAA provided
satellite with the Advanced Data Collection System (A-DCS) instrument
The Argos 3 NOAA-N' A-DCS was returned to CNES for testing. So far
tests: functional and environment are successful and should be completed
by the end of June. After results review the instrument should be
declared flight worthy and stored at CNES before eventual delivery to
LMSSC. (38^th^ O/C)

### NPOESS :

NOAA and CNES will identify the necessary steps to develop and deliver
the instrument consistent with the required delivery dates. NOAA and
CNES will also initiate discussions toward a bilateral MOU. The DCS
NPOESS instruments should be compliant with the users requirements as
foreseen in the next decade era (34^th^ O/C)

CNES/CLS will coordinate a joint NOAA/CNES/CLS action (35-8-C/S) with
the objective to combine and integrate Argos users requirements and to
tentatively translate them into preliminary specifications. The
following sources of information will be used: CNES/CLS study about
Argos user's requirements for future Argos missions ; DBCP/JTA
participants' requirements ; Animal trackers' requirements, not
available today. The objective date to submit a preliminary report is
September 2001. This report will be circulated among participating
agencies. CNES and NOAA will set up a joint meeting by December 2001
with the view to compile the users and system requirements for the
NPOESS era. NOAA and CNES discussed the results of consultations NOAA
held with the integrated program office regarding requirements for DCS
on NPOESS spacecraft. NOAA indicated that current plans are to carry DCS
on both the morning and afternoon missions. The possibility also exists
to fly the DCS on "NPOESS-LIGHT" if the requirement exists. However, it
was generally felt that Metop-3 would fulfill that requirement. (35^th^
O/C)

The eventual launch of NOAA-N' will signal the end of the TIROS series
of polar orbiting satellites. This program will be continued into the
new millennium by a combination of the METOP and NPOESS Programs. The
NPOESS Program has successfully completed the concept definitions phase
and proposals submitted by the two competing prime contractors, TRW and
LMSSC, are being evaluated. An award of this contract is expected in
mid-August. D. Benner described the evolution from the present day
(2002) four orbit Polar Operational Environmental Satellite (POES)
constellation, tomorrow's (2005) four orbit constellation with METOP and
the future (2008 and beyond) 3 orbit constellation with NPOESS "lite"
and METOP in same 0930 orbital plane. CNES/CLS noted that there was no
operational benefit to the carriage of the Argos A-DCS on the NPOESS
"lite" satellite. C. Gal reported that as agreed at OC 35, CNES provided
LMSSC and TRW with a preliminary definition of the instrument interfaces
which was found sufficient by both competitors for their purpose. A key
input provided in return by LMSSC and TRW is the instruments delivery
schedule which was taken into account in the agenda item E-3 preparation
(DCS requirements for NOAA Future Polar Missions). An IPO/NOAA/CNES
meeting was held on March 1, 2002 during which information was exchanged
also for helping E-3 preparation. More detailed discussions will start
presumably in the fall of 2002, involving the winning contractor
(through IPO) and taking into account the OC 36 decisions. CNES provided
a preliminary Interface Control Document which was considered sufficient
by both contractors for preparing their bids. The user driven
requirements are compatible with the preliminary interfaces given to
LMSSC and TRW. Contacts will resume after IPO selects the winning
contractor (36^th^ O/C)

Chris O'Connors provided an NPOESS overview of the infrastructure and
handling of DCS data. A discussion on the status of safety net was
raised by Bill Woodward. Bill inquired what progress Northrop Grumman
has made in making Safety Net a reality. It was reported that the
contractor is required to build this infrastructure by contract, but
what the current state of the network is today is unknown. Also of note,
the slide containing the payload for the three NPOESS satellites and the
METOP satellite contains an error in the placement of the CRIS
instrument. The payload slide should be consulted for DCS information
only as the NPOESS system continues to evolve. Chris O'Connors presented
a summary of a two day meeting held in the end of January that focused
on coordination between NOAA, NASA, IPO, CNES, and NOAA /NESDIS/IA. The
first day's agenda addressed issues with the SARSAT program and the SARP
instrument planned for the NPOESS era of satellites. Day two of the
meeting centered on ADCS instrument for the Argos program on NPOESS. A
draft meeting report for the second day of the meeting is available with
detailed information on discussions and participants at NOAA/DSD. The
main topics of discussion were HRD/LRD requirements to carry Argos data,
proposing to place an existing Argos instrument on the 2130 NPOESS orbit
currently not scheduled to carry Argos, and MOU creation and timeline
for approval. It was reported that the request for DCS data on LRD data
stream and the possibility of a DCS instrument on the 2130 orbit of
NPOESS were no longer in consideration. The MOU will be updated.
Withdrawal of the LARD and 2130 requests. IPO and NASA settled an
antenna pattern discrepancy. IPO is requested to investigate liability
of handling the CNES DCS instrument while in the U.S. (37^th^ O/C)

#### Satellite :

NPOESS is the National Polar-orbiting Operational Environmental
Satellite System built by Northrop Grumman Space Technology (NGST) for
the United States Integrated Program Office (IPO). NPOESS will acquire,
store and disseminate to processing centers and field terminals, global
and regional environmental imagery and specialized meteorological,
climatic, terrestrial, oceanographic and solar-geophysical and other
data in support of DoC mission requirements, and DoD peacetime and
wartime missions. In this way NPOESS combines the resources of the
military and civilian satellite programs and its international partners
to minimize duplication of efforts and expand the environmental
capability. It will deliver data faster to Centrals (95% data delivery
in 30 minutes), is more reliable (7 year design life) and provides
greater earth coverage (15 globally distributed receptors linked to
centrals via fiber) than predecessors. The NPOESS payload is composed of
14 sensors including:

-   Visible/IR Imager Radiometer Suite (VIIRS)

-   Cross-track IR Sounder (CrIS)

-   Ozone Mapper/Profiler Suite (OMPS)

-   GPS Occultation Sensor (GPSOS)

-   Space Environmental Sensor Suite (SESS)

-   Aerosol Polarimetry Sensor (APS)

-   Advanced Technology Microwave Sounder (ATMS)

-   ARGOS Data Collection System (A-DCS)

-   Search And Rescue (SARSAT)

-   Earth Radiation Budget Sensor (ERBS)

-   Total Solar Irradiance Sensor (TSIS)

-   Radar Altimeter (ALT)

The responsibilities for the NPOESS program extend from design,
development, and acquisition of the next generation operational
environmental satellites, through launch, on orbit operation, and
delivery of raw data and derived products and applications to end users
to improve operational meteorological and environmental forecasting and
global climate monitoring services. NOAA, in cooperation with its other
U.S. partners, will ensure that the voluminous data acquired from these
new space-based sensors are archived and made available to support
long-term global environmental monitoring. (38^th^ O/C)

#### A-DCS on NPOESS

A-DCS is planned to fly on the NPOESS 1330 (C2, C5) and 1730 (C3, C6)
orbits. The engineering development phase of NPOESS extends through C2.
CNES has an instrument already built and on the shelf to support C2.
They presently do not have allocated budget for C3, C5 and C6
instruments, however, the spacecraft need date for the earliest, C3, is
not until 2012. To prepare for that delivery, CNES would need to
finalize budget commitment and begin development around 2007. The A-DCS
comes to NGST as Government Furnished Equipment (GFE). It will have
TIROS-like interfaces, and it is assumed that no modifications will be
done by the instrument provider. Since the technology is different from
that used by NPOESS, the NPOESS spacecraft is making custom
accommodations.

The instrument planned to be installed on NPOESS C2 is available at
CNES. Discussion on interfaces with and accommodation on NPOESS are in
progress. Next meeting will be in Toulouse during the week starting
November 15 2004. It will involve IPO, NGST, NOAA and CNES.

A-DCS Coordination continues between NOAA/CNES/NGST C. O'Connors
provided minutes from the September 2003 meeting as well as action items
from the June 2-4 2004. Greg Barber in attendance at the meeting is the
new representative for NGST in this process. In addition to the
instrument effort NESDIS is reviewing the ground segment between the
NPOESS infrastructure to the delivery of products to the users. The
NPOESS Data Exploration Team has identified several questions related to
A-DCS data. C. O'Connors provided these questions in his brief and call
the committees attention to two specific items. First, NDE is reviewing
the other Centrals for a potential back up to NESDIS to ensure
continuity of operations if the NESDIS central fails. Second, NOAA has
an action to identify the granules size that best fits the needs of
CLS/SAI in the NPOESS and IJPS (METOP) era. Granules are the smallest
time length that data can be ordered on the NPOESS system. Granules will
be collected into packets and delivered to the USGPC at set time
intervals per the user requests. Currently 1 complete orbit (102
minutes) is the granule and packet size for delivering POES data.
(38^th^ O/C)

#### DCS Acquisition Status

The ITAR Technical Assistance Agreement (TAA) between NGST and CNES has
been completed. It covers interface related material transfer,
discussion and support. Also included is exchange of materials related
to instrument-to-satellite integration, test, Ground Support Equipment
(GSE), and functional verification.

A Technical Interchange Meeting (TIM)/ Quarterly was held in Washington
June 2-4, 2004. It was very productive. CNES had reviewed the NPOESS
General Instrument Interface Document (NGIID) and the group was able to
step through and process their comments in real time. NGST is updating
the NPOESS ICD to reflect the comments and resolutions. (38^th^ O/C)

#### A-DCS/NPOESS Interface Issues

The following A-DCS/NPOESS interface issues have been or are presently
being worked:

-   TIROS provided power regulation which is different from NPOESS

-   The Command and Data Handling interface will need a custom
    application

-   A-DCS requires a +10V power source

-   The RF front end is in design and will be common to 2 other
    instruments

-   NPOESS will have the same Power Flux Density concerns as TIROs

```{=html}
<!-- -->
```
-   Making mass and power preparations for future A-DCS modifications

-   Current ripple was found to be within NPOESS tolerances(38^th^ O/C)

## SYSTEM CONFIGURATION

### ORBIT CONFIGURATION

#### Early Orbit Investigation

In order to enable NOAA to deliver more timely sounding data for use in
the N.M.C. forecast models, NOAA is investigating an earlier orbit for
NOAA-B. CNES and NESDIS will investigate the effect of this earlier
orbit on their respective operations.

#### Early Orbit Determination.

CNES and NESDIS have investigated the effect that an earlier orbit for
NO M -B and follow-on afternoon satellites would have on their
respective operations. CNES has determined there would be no significant
effect of an earlier orbit on Argos System performance. NESDIS has
determined that an earlier orbit would improve the data ingest schedule.
(11th O/C)

### ONE SPACECRAFT SYSTEM (One or Two Instruments in Orbit)

#### One Spacecraft System

At the 10th O/C it was stated by NOAA that additional spacecraft are
planned (NOAA-H and I). Service Argos will assess the extent to which
the Argos objectives would be met with only one Argos instrumented
spacecraft.

#### O/C Recommendations

The result of the study was presented at the 11th O/C. This study led
the O/C to recommend the construction of additional Argos instruments.

#### One Spacecraft Potential

NESDIS stated there is a possibility to change to a one-spacecraft
operational system. Service Argos was requested to reassess
probabilities of continuing Argos Service after considering a single
spacecraft system including 18 month launch schedule. (15th O/C)

### Argos Study:

The conclusion of the Service Argos study indicated two major drawbacks
compared to the normal system:

1\) A loss of performance.

2\) A greater risk of total system breakdown.

##### Impact Assessment:

It was felt that the impact of these drawbacks would result in:

1\) A gradual disappearance of meteorological applications.

2\) No increase of major scientific programs in the system resulting in
the number of platforms remaining at the present level. (16th O/C)

### TWO SPACECRAFT SYSTEM

NESDIS examined the possibility of maintaining a two spacecraft Argos
capability even though one spacecraft might have a complete METSAT
sensor failure and has agreed to operate a 2nd Argos capable spacecraft
unless it conflicts with SARSAT operations (SARSAT would have priority).
(19th O/C)

### THIRD SPACECRAFT DATA

The O/C agreed to form a working group to discuss ways to improve the
availability of Argos data from three satellites. NOAA-9, launched in
December 1984, operates with four Data Recovery Units. The data are
transmitted to Service Argos only twice a day which is not satisfactory.
A letter from the United States Air Force requesting NOAA-9 data was
presented in support of the importance of NOAA-9 telemetry. (28th O/C)

### Alternate operational scenarios

M. Cazenave stated that the satisfaction of the large diversity of Argos
users requires non only reliability of data collection but also regular
updating of the data collected with short delays in reception and
distribution. The most optimal scenario should then require the maximum
utilization of all existing payloads. More than 20 years of experience
in operations have demonstrated that the average lifetime of the
satellites is approximately 7 years.

Assuming this is likely to continue and including ADEOS-11 and METOP
satellites, a constellation of 5 to 6 satellites could be available in
the future.

Reception of all data collected by these satellites, even in slightly
delayed mode as it has been the case throughout 1999, will allow to
improve Argos contribution to worldwide science and governmental
requirements. (33^rd^ O/C)

## INSTRUMENTATION

### INSTRUMENTS FOR NOAA-H, I AND J

#### Receivers

Following the recommendation of the O/C CNES proposes an Argos
instrument option for NOAA-H and I that only uses one receiver per
spacecraft versus the two receivers in the instruments for earlier
spacecraft. CNES feels that the reliability of the receivers warrants
this change. (11th O/C. This change was approved at the 15th O/C (see
4.3.3).

#### Polar-orbiter Mission

In order to continue the polar-orbiter mission in the 1988-1989 time
period, NESDIS is planning to procure an additional spacecraft, NOAA-J.
CNES reported that funds have already been requested for instrumenting
NOAA-H and I with an option for NOAA-J. (12th O/C)

#### Data Rate Change Request

It was agreed to have NASA submit a formal Change Configuration Request
(CCR) to increase the data rate from the DCS instrument to the TIP from
the current 720 bps to 880 bps. This will allow more platforms to be
accommodated in the system. Also, NOAA and CNES are to evaluate the
impact of this increase data rate on ground processing. (16th O/C)

#### Data Rate Change Approval

The CCR has been approved by the Change Configuration Board at NASA and
a Request for Proposal has been requested from the spacecraft contractor
to increase the data rate for the Argos instrument. After further
investigation into this task it was discovered that the DCS data rate
can only be increased in multiples of three 8-bit TIP words since the
DCS data output word is 24 bits. The information will be furnished to
NOAA for a final decision as to implementation. (17th O/C)

#### Data Rate Change Impact

Since there will be an increase in data rate (720 to 960 bps) for the
Argos instruments carried on these spacecraft, the NESDIS METSAT DPSS
will have to be modified to accommodate this increase. (20th O/C)

#### DCS Instrument Components

NASA will provide periodic reports to CNES on the results of the TIROS
Orbital Anomaly Review Board pertaining to the DCS instrument components
of the spacecraft bus which will affect the commanding or retrieval of
data from the DCS, or failures which may impact the lifetime of the
spacecraft. (15th O/C)

### INSTRUMENTS FOR NOAA-K,L,M

R. Peavler presented the schedule and status for the future spacecraft
and also indicated the activities that would take place at the Lockheed
Martin Marietta facilities at East Windsor, NJ, and Sunnyvale, CA. It
was also pointed out that the MHS instrument would replace the AMSU-B on
the N and N' spacecraft.

The IMU that is to be used on all NOAA spacecraft is being reevaluated
because of an anomaly that was discovered during 3-axis vibration of the
spacecraft structure. This analysis and recommendation for potential
solution are due November 1996.

A summary of the five most pressing problems that have occurred during a
week of design and test at LMMS were presented. (30^th^ O/C)

#### NOAA-K,L,M Planning

NESDIS has decided to delay introducing a new block of polar orbiting
spacecraft until the 1990\'s and this new block series will be called
NOAA-Next. However, to ensure continuity of the polar orbiting system
additional ATN spacecraft are planned (NOAA-K, L, and M). CNES has
agreed to provide Argos and SARSAT instruments for these additional
spacecraft. During a meeting between Dr. McElroy of NESDIS and Mr.
d\'Allest of CNES, this information was exchanged. Also, discussed at
this meeting was the need to maintain the environmental nature of data
transmitted by the system. (19th O/C)

#### Argos-2 Instrument

CNES is developing an advanced instrument to be carried on NOAA K, L,
and M spacecraft. (21st O/C). This instrument (DCS 2) will carry eight
DRUs instead of four. The engineering model of this new instrument was
delivered to CNES in June 1989. The specified performances have been
achieved. The protoflight model is due September of 1990. (24th O/C)

#### Argos-2 Instrument Delivery

The three DCS 2 instruments to be installed on the NOAA-K, L, M
satellites were delivered to CNES. After the flight readiness review
held by NOAA / NASA in October 1991, the DCS 2 protoflight was shipped
to the Martin Marietta Astro Space facility for integration on the
NOAA-K platform. Integration operations are in process. The DCS 2 to be
installed on the NOAA-L and NOAA-M platforms are stored at the Toulouse
Space Center. (27th O/C)

The first model has been installed on the NOAA-K satellite. The results
of the electrical tests of the integrated satellite have been so far
satisfactory. These tests are continuing with EMI testing and later
thermal vacuum testing. As agreed, CNES is providing technical
assistance to NASA by reviewing the Argos DCS test results. (29^th^ O/C)

NOAA L and M : ARGOS-2 instruments have been delivered to NOAA for
integration.

NOAA-N: Argos --2 instrument is stored at CNES. To be delivered to NOAA
in 1999.

#### Argos-2 instrument performance

C. Gal reported that the new Argos-2 instrument was operating well and
highlighted the additional capacity in the increased bandwidth as
illustrated by the graphs. (32^nd^ O/C)

### INSTRUMENTS FOR POST-NOAA-M

#### Future Cooperation

Letters were exchanged by NOAA and CNES exploring possibilities for
cooperation in future polar missions. NOAA letter signed B. Smith
(January 16, 1990) to CNES (Ph. Guerit) proposing to move ahead with MOU
modifications both for NOAA N and post NOAA N missions (NOAA O, P, Q and
EPOP-1). Various modifications/improvements are presently being studied
by CNES and CLS as part of the post NOAA N DCLS mission definition.

Principal improvements being considered are:

1\) Implementation of a repeater mode.

2\) Implementation of a two way system. (24th O/C)

#### Transparent Repeater Proposal

It is planned to develop an improved version of the DCS receiver
processor by adding a repeater to the Argos band. The objective is
two-fold :

1\) Improve reliability of the receiver processor in the coverage of
local ground stations ;

2\) Allow development of new applications by improving flexibility of
the ground system processing. (25th O/C)

NOAA explained the rationale behind its negative answer to the CNES
proposal. It was agreed that consideration of the concept must be given
to the mission definition and policy aspects during the CNES/NOAA
discussions on the configuration of the POEM 1 and NOAA O payloads.
(26th O/C)

#### NOAA-N\' Instrument Request

CNES is considering a NOAA request for the provision of an extra DCS 2
to be installed on NOAA-N'. In view of the requested delivery by end of
1998 (meaning funding in 1996 at the earliest), CNES will use its best
efforts to inform NOAA of its plans to provide a formal commitment for
NOAA-N'. (27th O/C)

In reply to THE NOAA/NESDIS Assistant Administrator\'s letter that
requested CNES to provide the NOAA/N\' DCS, the CNES President will
inform NOAA (Administrator) that :

-   CNES confirms it will supply an improved ARGOS instrument for the
    NOAA-N\' satellite.

```{=html}
<!-- -->
```
-   CNES supports the METOP/DCS since it will meet the requirement for
    coverage of the morning orbit. However it is CNES intention to
    provide directly the METOPs/DCS instruments to EUMETSAT. (29th O/C)

#### Instrument Configuration

The decision to use identical Argos instruments (K-L-M-N clones) on N\'
and METOP was welcomed by CNES as cost-effective. However, two factors
have to be considered which require more work on the evolution of the
Argos mission:

1\) Manufacturing of N\' and METOP instruments will start after 1995,
i.e., 10 years after the K-L-M-N instruments design. Technological
changes will be necessary to address electronic parts obsolescence and
take advantage of new technologies.

2\) CNES proposed to consider the following instrument configuration
which, while departing as little as possible from the \"clone\"
principle, would allow the improvement of service offered to the Argos
users.

Configuration description:

a\) Mechanical interfaces unchanged.

b\) Electrical interfaces: increase in power consumption (5/10 watts on
the 28 volt bus).

Otherwise essentially unchanged, except:

i)Increased sensitivity

ii)Introduction of programmable capabilities to the in flight
instruments to allow some flexibility in the bit rate, the message
length, etc.

iii)Implementation of a space-to-earth UHF (460-470 MHz) 50/100 bps link
designed to command/control some platforms (down-link messaging). This
link implies connecting one of the Signal Processing Units to a transmit
antenna (under study, to be defined). There would be no acknowledgment
from the platforms which will operate in the present random access mode.
The command link may be used to increase the efficiency of the system,
e.g., to start or stop some platforms, modify configuration of the
sensors, change repetition period, cycle of operation, etc. The command
link would be global. Uploading memory would be done from a ground
station installed at the processing center. The uplink would be through
the DCS antenna and receiver. (28th O/C)

An accommodation study for Argos-III on N and N' has been completed by
LMMS. It was determined that the instrument could be integrated onto the
N' spacecraft without a high risk to the program if the assumptions as
stated in the report were followed completely. It was made clear that
NOAA requires all instruments designated for NOAA-N' by July 1999 in
order to meet the contracted need date for the NOAA-N' launch. In
relation to the enhanced Argos for NOAA-N', NOAA will accept a working
engineering model in July 1999 if the flight model is not available.
(30^th^ O/C)

Due to contractual obligations with the spacecraft manufacturer, all
instruments designated for NOAA-N\' must be delivered to Lockheed Martin
by October 2000 for integration and testing. The new Argos-3 Flight
Model, if selected as a payload for NOAA‑N\', is required at this time.
The engineering model of Argos-3 will be required in February 2000 at
Lockheed Martin for initial check out. (31^st^ O/C)

#### ADEOS II/DCS

After discussion with NOAA, CNES is pursuing cooperation with the
Japanese space agency, NASDA, to carry an Argos DCS on board the
polar-orbiting satellite, ADEOS II.

##### Formal agreements

CNES provided supplemental information to that given in a meeting with
NOAA in Washington (April 26, 1995). Since then, CNES and NASDA have
exchanged formal letters of agreement (June, 1995) to carry out
cooperation while the MOU is being negotiated. A first draft of the MOU
should be available at next NASDA/CNES meeting (Paris, June 19-21,
1995).

While the agreement is limited at this stage to one satellite (ADEOS
II), both parties have expressed their hope to jointly develop long term
cooperation.

Following the NOAA/NASDA/CNES meeting held in Paris on April 19, 1996, a
new version of the CNES/NASDA ARGOS MOU was drafted and submitted to
NOAA, NASDA, and CNES for comment.

The last revised version, dated July 4, 1996, is available. Some issues
were identified for further coordination with NOAA and were discussed
during a separate session.

A draft letter from CNES to NOAA was reviewed requesting that the
ADEOS-II/Argos DCS data received by the NOAA ground stations be
transmitted (Level 0) to Service Argos, Inc. in Largo, MD. NOAA provided
CNES a draft copy of the NASDA/NASA/NOAA ADEOS-II MOU for comment.
(30^th^ O/C)

##### Development activities

Space segment : both CNES and NASDA have already started hardware
development under industrial contracts. Flight model should be delivered
by CNES to NASDA in May \'97.

Ground segment : the tentative schedule has been established as follows
:

\- critical design : end \'96

\- manufacturing : end \'97

\- integration : end \'98

The operations were scheduled at the beginning of \'99 but some delay is
now expected (launch date of ADEOS II is likely to be delayed to second
half of \'99). (29th O/C)

Space segment: engineering model of the CNES components will be
delivered to NASDA September 29, 1996 and the protoflight model in
November 1997.

Ground segment: development by CLS of the evolution of the Argos
processing system to include the ADEOS-II/Argos DCS data will start in
1999 to be ready for the launch now planned in August 1999.

[Project status of the space segment]{.underline}

The integration of the Engineering Model of the CNES Components (RPU,
two SPUs and an interface box called DIU) in the NASDA/NEC DCS unit
subsystem has been successfully completed between the end of 1996 and
the beginning of 1997 (the DCS Unit subsystem is composed of the four
CNES boxes completed by a transmitter, \~ 466Mhz, a diplexer, a
deployable transmit / receive antenna and a thermal control system.

The delivery of the flight model is planned in December 1997 at NEC
Yokohama after post-transportation test performed by CNES. As for the
EM, NEC with CNES support, will integrate the CNES components with the
NASDA components in the FM of the DCS Units.

Then NEC will deliver the tested DCS Unit subsystem to the satellite
contractor (MECO) in May 1998. The tests at the spacecraft lever will be
performed in the NASDA space center at Tsukuba.

The launch of ADEOS‑II is currently planned for August 1999.

C. Gal presented the status of the Argos-Next program based on an Argos
instrument integrated on NASDA's ADEOS II satellite: the proto flight
model was delivered to NEC for integration within a single box with the
Japanese UHF transmitter and antenna. This subsystem will then be
delivered in October 1998 to NASDA for integration on the ADEOS-II
satellite proto flight at the beginning of 1999. Concerning the ground
segment, M. Cazenave stated that 1) the Japanese distribution center was
recently (June 1998) upgraded to become a regional processing center;
and 2) the development of software for 2-way communication is ongoing
and scheduled for completion at the end of 1999. Connection with EOC at
Hatoyama for the ADEOS-II/Argos DCS level 0 data delivery will be tested
at the end of 1999. It was agreed that CNES will send a letter to NOAA
and EUMETSAT (Action Item 32-7-C) about the possible implementation of a
master beacon at the Fairbanks and the planned EUMETSAT CDA's. It should
be noted that this master beacon will later be upgraded for use with the
Argos-3 system on METOP 1-3 and NOAA-N'. (32^nd^ O/C)

N. Matsuura made a presentation of ADEOS-II satellite status which is in
the proto Flight Test started in May 1999. The Initial Electrical
Performance Test (IEPT) was started in May 1999 and the IEPT for mission
instruments including Argos DCS will be finished in July 1999. Satellite
level testing will then continue (vibration, thermal vacuum...) by July
2000. The launch date of ADEOS-II will be in November 2000. Y. Ishido
and T. Sasada described the status of ADEOS-II ground segment which were
in the manufacturing phase and would be integrated by the end of 1999.
(33^rd^ O/C)

Instrument status :The complete PFM subsystem i.e. including the NASDA
transmitter and antenna was installed on the satellite in June 1999.
Beginning of July, NASDA and CNES will perform the Initial Electrical
Performance Test (IEPT). During these tests, a CNES team will upload the
flight software and test the compatibility between the instrument and
the user ground segment (transmit and receive). (33^rd^ O/C)

The complete DCS subsystem is installed on the satellite. Thermal vacuum
test at satellite level was successfully completed. Acoustic, vibration
and shock tests are underway. Final Electrical Performance Test (FEPT)
is planned for October 2000 after which the satellite will be stored
until its preparation for the launch in November 2001. (34^th^ O/C)

The ADEOS II Proto Flight Test was finished in last December and the
pre-shipment test is on going. ADEOS II will be shipped to the launch
site in August and be launched in February 2002. (35^th^ O/C)

ADEOS-II satellite is stored at Tanegashima Space Center, which is the
Japanese launch site. The launch schedule is no earlier than November,
2002. ADEOS-II Ground system successfully performed End-to-End test
(from spacecraft to end-user community) for mission operation planning
and data delivery at September, 2001.The Mission Readiness Review (MRR)
to confirm overall launch readiness is scheduled around late July. A
final Argos-Next DCS performance test will be performed in August 2002
by a CNES team, after which the instrument will be considered ready for
flight in November 2002. (36^th^ O/C)

[Status of ground segment redundancy]{.underline}

Concerning the global and regional DCS data received by ADEOS II ground
stations in both modes 1 and 2 the meeting concluded that there is an
operational interest to have these data transmitted to both the NESDIS
and NASDA ground systems for redundancy purposes. CNES took the action
to inform officially NASDA and NOAA about this requirement. NOAA took
the action to assess, together with NASA and NASDA, the technical
feasibility of implementing such possibility. (31^st^ O/C)

Overall conclusion is that the ADEOS-II and DCS check out results are
good and that the routine operation is working well since April 14, date
of a NASDA internal review. The instrument in operational use since May
2003 (37^th^ O/C)

Mr. Kojima from JAXA explained about the investigation status of
ADEOS-II anomaly happened on 24^th^ October 2003. As a result of ground
test and analysis of telemetry, it is estimated that the discharge in
harness of solar array is the most possible scenario. JAXA is going to
conclude the report soon, and reflects the lessons learned to the
following programs. (38^th^ O/C)

##### Adeos follow-on :

N. Matsuura provided an overview of ADEOS-II follow-on named as « Global
Change Observation Mission (GCOM) ». The GCOM has two missions ; one is
for monitoring for ozone and greenhouse gases, and the other is for
monitoring for material and energy cycles. To implement the GCOM, the
GCOM-A1 and B1 spacecraft will be launched in 2005, and NASDA will start
developing an ozone instrument for GCOM-A1 in 2000. NASDA is inviting
mission instruments for GCOM-A1 and B1 coordinating with other space
agencies.

CNES expressed a strong desire to fly an A-DCS instrument on board
GCOM-A or GCOM-B because an analysis indicated a significant improvement
in the overall performance of the global Argos system, most notably by:

-   ensuring the down-link messaging capability from single point of
    satellite failure ;

-   increasing the data throughput rate, by 50% ;

-   decreasing the average waiting time between satellite passes by 50%.

CNES also reported that the Japanese Governmental Users (JGU) confirm
their requirements for these capabilities. JGU have also decided to send
a letter to NASDA requesting the Japanese Space Agency to continue their
cooperation to provide these Advanced Argos capabilities by flying an
Argos A-DCS on board GCOM-A or GCOM-B. (33^rd^ O/C)

There is official statement for DCS on GCOM platforms in the presented
material (No Argos on GCOM-A1, studying possibility on GCOM-B1). (34^th^
O/C)

GCOM-B is to observe material and energy cycles and needs many ocean
in-situ data. The potential benefits of DCS missions on board Japanese
environmental satellites were reviewed in Tokyo on May 24, 2001, with
the participation of Japanese users and representatives from NASDA,
NOAA, NASA and CNES agencies. The cooperation with NASDA on DCS missions
is considered to be a major contribution to future in-situ observations
and is required by Japanese users as a continuation of the ADEOS-II/DCS
mission. The possibility to fly a DCS instrument on board the GCOM-B1
satellite is under discussion between NASDA and CNES; The final
instrument configuration for GCOM-B1 is expected to be decided by mid
2002. (35^th^ O/C)

NASDA continues the phase-A conceptual study during JFY 2002. The
decision of phase-up will be discussed by August 2002 (36^th^ O/C)

Mr. Ishido from JAXA presented a preliminary JAXA long rang Earth
Observation Plan from the view point of DCS program. JAXA studies
ADEOS-II follow-on that includes Greenhouse Gasses Observing Satellite
(GOSAT) and Global Coverage Observing Mission (GCOM). GCOM consists of
two kinds of satellite, GCOM-W and GCOM-C. GCOM-W will carry Microwave
sensors such as AMSR and SeaWinds, and GCOM-C for optical sensors
including GLI follow-on. This preliminary plan will be refined in
accordance with the result from the current failure analysis about
satellites and H-IIA rocket.(38^th^ O/C)

#### Down-link messaging and NOAA-N\'

Recognizing the evolution of the users needs, the Operations Committee
agreed to pursue implementation of a down-link messaging function on
NOAA-N\' and approved the study that was previously completed by CLS and
SAI.

In that context, CNES presented a preliminary mission proposed for the
improved Argos instrument to be flown on NOAA-N\', METOP-1 and METOP-2 :

\- Functional compatibility with ARGOS-2 (K,L,M,N).

\- Addition of the Argos down-link messaging capability developed and
tested on ADEOS-II.

\- Increased output data rate.

\- Addition of new capabilities (TBD).

From the above preliminary definition, an improved instrument baseline
has been determined to be used for the NOAA-N\' (and METOP)
accommodation studies.

\- Compatibility with the NOAA-K,L,M mechanical interfaces.

\- Increased power consumption on the 28V line (up to 60 watts).

\- New transmit antenna (or combined receive/transmit antenna).

\- New EMC requirements (5W RF narrow band transmission at 465 or 468
MHz).

\- Increased data rate at the instrument/satellite interface (TBD).

Other interfaces should be essentially unchanged.

It was decided to carry out an evaluation on the technical feasibility
of implementing such improvements on the NOAA-N\'/DCS using data
provided by CNES.

It was recognized that, due to the NOAA-N\' satellite schedule, this
evaluation should be completed before the end of 1995. (29th O/C)

Argos-3 (A-DCS) instrument (flight-model) can be delivered to NOAA in
March 2001. If an early delivery is needed, workaround may be possible
using the simplified EM. Integration of the A-DCS on NOAA-N' is being
formalized by the UIIS. (33^rd^ O/C)

H. Wood provided all members with a copy of the NOAA letter to IPO and
response outlining the U.S. Government (USG) requirements for Argos-3 on
NPOESS. She also provided copies of a NOAA memo outlining USG
requirements for Argos-3 on NOAA-N'. C. Gal stated that information on
Argos-3 interfaces is available in the NOAA N' UIIS and proposed that
NASA and NOAA provide the information to the NPOESS Technical Point of
Contact as a starting point for planning. However, the NPOESS instrument
may include new capabilities and require more power and data throughput.
(33^rd^ O/C)

#### METOP

##### Formal agreements

A preliminary draft CNES/EUMETSAT/MOU was prepared in Spring 1996.

It is foreseen that a consolidated version will be finalized during the
third quarter of 1996. (30^th^ O/C)

##### Development activities

The METOP/Argos DCS mission will be specified before the end of 1996.
However, EUMETSAT and CNES have already agreed that the METOP/Argos DCS
mission will be compatible with Argos-II and that, in addition to
existing functions, it will provide:

-   \- downlinkan increased data collection capacity

CNES is already involved in the METOP-1 phase-B and will participate in
the definition of the satellite interfaces. The satellite phase-B will
end at the end of 1996.

The METOP -1 launch is scheduled for March 2002. (30^th^ O/C)

The status of the Advanced-DCS (Argos 3) instrument accommodations on
the METOP-1 satellite was presented . Reference document is the data
package from the Eumetsat/ ESA design review held on November 15, 1996.
The main relevant document: the A-DCS ICD and SARP ICD were reviewed at
a meeting between Eumetsat, ESA, NASA (for Sarsat) and CNES on May 13
and 14, 1997. The main outcome of the meeting is that the A-DCS ICD is
at this stage too detailed and that ESA will prepare a new issue based
on the confirmed requirements e.g. EMC, mass, power, volume, etc.
Leaving open what is undefined e.g. center of gravity position, momentum
of inertia, detailed corrector pins assignments, etc. CNES intends to
have identical instruments for METOP satellites and NOAA-N\'. It is
urgent for CNES and NOAA/NASA to coordinate to ensure that the
interfaces are compatible. (31^st^ O/C)

Response to an RFQ for development and manufacturing of 4 Argos-3
instruments has been received and is being evaluated by CNES. Interface
control documents with the METOP satellite are ready for approval after
final review by Single Space Segment Team (SSST), ESA/EUMETSAT, and
CNES. They should be approved before the end of September 1998. A
quasi-final draft was sent to NASA and it was agreed that NOAA/NASA will
review and comment on the documents with the purpose of verifying its
compatibility with the future NOAA-N' Instrument Unique Instrument
Interface Specification (UIIS). (32^nd^ O/C)

M. Cohen reported on the status of the EUMETSAT POLAR SYSTEM (EPS) and
METOP programs. One of the major events was approval of the EPS program
by its Council. The last member state who did not yet lift its
ad-referendum vote, indicated recently that it would be in a position
soon to do it during the Summer 1999. Regarding the development status
of the METOP satellite, the Service module (SVM) Hardware Design Review
was held successfully. The Payload Module Preliminary Design Review
(PDR) was also held. The overall Satellite PDR is on going and Board
conclusions are expected to be available during the month of July 1999.
In particular, great care was put towards the RF compatibility of
instruments with the satellite. Major milestones dates are maintained
i.e. a critical design Review in February 2001, a Qualification Review
in April 2002, a Flight acceptance Review in February 2003 leading to a
baseline launch date mid 2003. On the Ground Segment side, the
requirements for the Core Ground Segment, its interfaces, and
specifications for products are being finalized. A formal review is on
going and the plan is to release an ITT to industry early August 1999.
The kick-off meeting for the contract is scheduled in April 2000 with a
development time of about 25-30 months. The selection of the CDA site is
done in parallel to the selection of the prime contractor. The final
location of the site will be communicated to the ground segment
contractor at the kick-off meeting. In addition, EUMETSAT reinforces its
teams in particular in the area of system engineering and operational
preparation. Emphasis will be put on the future on the overall system
verification and validation prior to METOP launch and also during the in
orbit commissioning phase which is scheduled to last 6 months after the
launch / LEOP phase. (33^rd^ O/C)

Argos-3 (A-DCS) instruments are under development since September 1998:

-   The PDR was held in April 1999and the board authorized to start the
    c/d phase of the project.

-   Simplified Engineering Model (EM) delivery: December 1999.

-   EM delivery: September 2000

-   PFM delivery: March 2001

Integration of the A-DCS on METOP is now defined by an approved
Interface Control Document. (33^rd^ O/C)

The integration of the METOP engineering model is well underway. In
particular, CNES has delivered the A-DCS and SARP-3 (reduced EM) to
Alenia for integration on the Metop EM panels. This integration is now
completed and Alenia will deliver the integrated panels to Dornier (DSS)
in July 2000. Engineering model will be delivered to EUMETSAT in
November 2000. However, this model will not include the final software
and will have to be returned to the CNES contractor for finalization.
Flight model No. 2 will be delivered to Eumetsat in November 2001 at the
earliest. It will be a full flight model. Flight models No. 3 and 4 will
follow in 2002 and 2003. (34^th^ O/C)

Graeme Mason presented the status of the future Metop (Meteorological
Operational) satellites, which will replace the "morning orbit",
polar-orbiting meteorological service currently provided by NOAA
following NOAA-M. As part of a Co-operation Agreement between EUMETSAT
and CNES (formally signed in February 2001), these satellites will also
embark the A-DCS instrument. The Metop satellites will be launched by
Soyuz ST launch vehicles from Baikonur, Kazakhstan, with the first
launch planned for July 2005. The Metop satellite activities are
currently well advanced, with testing of the satellite Structural Model
due to be completed by the end of June 2001 and the Engineering Model
programme due to complete in August 2001. The satellite Critical Design
Review is planned for September / October 2001. Data from A-DCS will be
stored on-board the Metop satellites for downlink every orbit, and will
also be included in the HRPT (1700 MHz) direct broadcast available to
regional users.

C. Gal reported that the test at satellite level (METOP-EM and METOP-1)
of the instrument reduced EM and EM installed on these satellites are
progressing normally under Eumetsat/ESA responsibility. The development
of the Proto-flight Model (PFM1) to be installed on METOP-1 or 2
satellite is going on with the delivery of the PFM1 to Eumetsat planned
in December 2001 (35^th^ O/C)

The EUMETSAT document EUM/C/50/02/DOC/36 was submitted for review and
discussion. The satellite CDR was successfully completed in October
2001. C. Gal noted the "Need for an early convergence on the SAR antenna
design". This antenna is common to SAR and A-DCS and CNES will
investigate if the A-DCS performances could be impaired. Soyouz is now
the EUMETSAT launcher baseline. The PFM-1 was delivered to EUMETSAT
early March 2002 at ALENIA (Italy) in spite of some non conformances
being open. It was pre-integrated by ALENIA on the satellite panels and
it is now ready to be delivered to ASTRIUM GmbH for integration on
METOP-1 (swap with the EM panels used until now). It will be upgraded to
become spare model. The A-DCS EM will be returned to CNES in the fall of
2002, it will upgraded to become spare model. As METOP-2 will be the
first satellite to fly, the A-DCS PFM-1 will be returned to CNES for
fixing the non conformances at the end of the METOP-1 test sequence in
2004 (date TBC). It will be replaced on METOP-1 by the refurbished EM,
and will become the spare model. The A-DCS FM-2 should be ready end of
July for delivery to EUMETSAT in spite of some persisting software
difficulties. Delivery is planned early September. The possibility to
load a new software version at ALENIA until the end of October
consolidates this schedule. The FM-2 will be installed on METOP-2, which
will be the first METOP satellite to fly in 2005. (36^th^ O/C)

Marc Cohen from EUMETSAT presented the overall status of the EPS
Programme and of the associated Metop Space Segment. The launch of the
first satellite (Metop 2) is confirmed to be in 2005. The IASI
instrument is nearing completion of its environmental testing and
subsequent delivery to Metop (planned in July 2003). All Argos related
space hardware have been delivered by CNES to Metop. The first 2 flight
models were successfully integrated on the Metop 1 and 2 satellites. The
last model is being integrated on the Metop 3 satellite. It was pointed
out that the current anomalies detected on the NOAA N´ satellite
regarding the A-DCS instrument may have some relevance to Metop although
similar problems have not been found out on Metop. Close cooperation
between CNES and EUMETSAT was confirmed about this topic. (37^th^ O/C)

Most salient point is that METOP-2 will be launched first at the end of
2005. The A-DCS installed on this satellite is ready for flight.
However, the test sequence of the satellite is not yet completed. The
three A-DCS Argos 3 instruments have been delivered to EUMETSAT and are
installed on METOP-1-2 and 3. METOP-2 will be the first satellite to be
launched end of 2005. The METOP-2 payload module (PLM) assembled and
tested by ASTRIUM GmbH will be delivered in July 2004 to ASTRIUM France
in Toulouse for assembly with the service module and mechanical tests.
(38^th^ O/C)

### SHUTTLE COMPATIBILITY

#### Instrument Requirements

It was requested at the 12th O/C that instruments for NOAA-H, I and J
must be designed to be compatible with a launch by either the shuttle or
an expendable vehicle. The JWG reported at the 13th O/C that vibration
level compatibility remained the area of main technical uncertainty with
shuttle launches.

#### Vibration Specifications

At the 14th O/C NASA intends to launch NOAA-H, I and J with expendable
vehicles and that vibration specifications remain unchanged.

##### Vibration Specification Update:

Although the shuttle vibration specifications are no longer applicable
to NOAA-H, I and J there may be a future requirement to use a shuttle
launch for other CNES instruments. NASA (TIROS Project) has minimal
dialogue with organizations responsible for updating information
concerning shuttle vibration specifications but will forward as
information only, to CNES, any information that becomes available. (15th
O/C)

### INTERCHANGEABILITY OF INSTRUMENTS

#### Interchangeability

NASA desires to have the Argos instruments interchangeable between those
designed for the NOAA-A through G spacecraft and those designed for the
NOAA-H, I and J spacecraft. NASA will investigate the impact of using
the different instruments in regards to weight and different commands,
etc. (14th O/C)

#### Spacecraft Interface

A Change Configuration Request has been approved that will make the
spacecraft interfaces for NOAA-H, I and J spacecraft the same as NOAA-G.
CNES has agreed to ground all unused telemetry points in the DCS
instruments for NOAA-H, I and J thereby making the DCS instruments from
NOAA-H, I and J interchangeable with NOAA-G and vice versa. (15th O/C)

### INSTRUMENTS ON SPARE SATELLITES IN STORAGE

#### Instrument Removal

CNES will determine their desires as to whether or not the Argos
instrument should be removed from NOAA-D spacecraft prior to its
storage. (14th O/C)

It was stated by CNES that it is preferable to remove the DCS prior to
storage. (15th O/C)

### EXPERIMENTS WITH SPACECRAFT THAT HAVE EXPERIENCED MAJOR SYSTEM FAILURES

#### Additional Testing

NESDIS and NASA will consider performing additional tests designed by
the JWG, on the Argos instruments on spacecraft that have experienced
major system failures and are no longer operational. Ground system
availability is critical for most of these tests and must be considered
in the planning. (14th O/C)

#### Test Duration

Depending upon the nature of the spacecraft failure and the availability
of the NESDIS ground system, NASA and NOAA will attempt to provide a
minimum of 21 days of testing as proposed by the JWG. (15th O/C)

## PROCEDURES

### LAUNCH AND POST-LAUNCH

#### Agency Coordination

Coordination is required between all involved agencies in developing
launch and post-launch procedures. Operational checkout plans must be
coordinated before spacecraft launches and any changes after launch must
be disseminated immediately in order to complete the checkout of the
Argos System. (7th O/C)

#### Post-launch Task Procedure Review

The O/C agrees that the JWG review the post-launch task procedures and
make appropriate change in sufficient time for each spacecraft launch.
(14th O/C)

### SPACECRAFT INSTRUMENT RECONFIGURATION

#### Reconfiguration Procedures

NESDIS and CNES will develop a written set of procedures for spacecraft
instrument reconfiguration. These procedures will cover emergency and
routine changes, and will be tested periodically. The test will not
actually change the spacecraft instrument configuration. (9th O/C)

#### Approved Procedures

The approved procedures for spacecraft instrument reconfiguration are
described in the document \"TIROS-N ARGOS

Subsystem Command Management\". (10th O/C)

#### Operator Procedures

NESDIS and CNES will revise the \"TIROS-N Argos Subsystem Command
Management\" procedures to include procedures for both the NESDIS and
Service Argos operators to handle the Argos instrument reconfiguration
command requests initiated by Service ARGOS. These procedures should
ensure the command message is transmitted both by teletype and console
message due to the problems caused by the narrow bandwidth for the
teletype link. (11th O/C)

##### Argos Instrument Reconfiguration, Updated Procedures:

Updated procedures were developed to handle the Argos instrument
reconfiguration command requests initiated by Service ARGOS. The O/C
requests these procedures be exercised at least once every month. (12th
O/C)

##### Procedure Exercises:

Procedures were exercised for requesting the commanding of the Argos
power and instrument reconfiguration. However, the quality of the
NESDIS-CNES data link was not reliable and all parties were forewarned
of the exercise. The O/C recommends that these exercises be conducted
without prior warning. (13th O/C)

## FREQUENCIES

### Non-Environmental DATA

NOAA has formally requested NASA to recommend frequencies that could be
used for other than environmental data for future spacecraft systems in
the late 1980\'s or 1990\'s. (11th O/C)

### Wind Profiler Radar (WPR)

The potential threat of this system to interfering with transmissions on
the 401.65 frequency was a topic of discussion at several O/C Meetings.
See Action Items 22-6 AND 23-2. (23rd O/C)

### FCC LICENSING REQUIREMENTS

The O/C discussed recent communication between the U.S. Federal
Communications Commission (FCC) and the Department of Commerce\'s Radio
Frequency Branch. The discussion focused on the FCC licensing process
required for radio stations (including Argos PTTs) operating in the U.S.
and use of the 401.65 Mhz frequency. Item 27-5 was developed. (27th O/C)

The O/C reviewed a proposed insert to the Argos Application pertaining
to FCC licenses, and recommended clarification for exactly which users
will be impacted. Service Argos and NOAA will work together to complete
a notification to the users (Item 28-1). (28th O/C).

## ARGOS-2 and NOAA-Next

Officials from CNES, NOAA, and NASA met to discuss Argos cooperation in
the context of NOAA-Next, the follow-on U.S. polar-orbiter to the
TIROS-N series of spacecraft. NASA presented the NOAA-Next spacecraft
constraints while CNES explained scenarios for the space and ground
segments as well as payload configuration according to project user
demands. A baseline set of design limits on weight, power and volume
were established. Discussions based on these presentations resulted in
progress towards the identification of a mutually acceptable program for
cooperation in future meetings concerning the new ARGOS-2 instrument and
its possible mating with the NOAA-Next spacecraft. (18th O/C)

##  BRAZILIAN DCS

Coordination between the Brazilian DCS and Argos DCS :

From an operations point of view, the need for coordination between the
two systems can be summarized as follows :

-   Brazil has already 100 DCPs in the field ;

```{=html}
<!-- -->
```
-   250 DCPS are being manufactured ;

```{=html}
<!-- -->
```
-   Future needs range to 2000 ID numbers.

CNES suggested that Brazil send CLS the list of IDs used for these 100
DCPs. CNES will check which are already allocated to Argos users and
need to be re-assigned. As they are in the field, this operation may
take time. NOAA-K is scheduled for launch in April 1996.

250 new Argos IDs will be provided to Brazil for their own use.

These 2000 ID numbers will be provided later because the DCS management
of ID numbers is going to be critical (up to 24000 IDs have already been
distributed out of 32000 available ones). (29th O/C)

In order to distinguish Brazilian SCD-1 platforms from Argos platforms,
CLS has assigned 200 ID\'s for SCD-1 users. Beginning with NOAA-K, SCD-1
and Argos uplink frequencies will be the same. (30^th^ O/C)

L. Ruiz presented the status of CNES/INPE (Brazil) discussions. Because
the Brazilian DCS is using a frequency band which overlaps with the
frequency band used by Argos-2, there is an urgent need to coordinate
both systems in order to avoid any interference. Practical coordination
measures have been identified and will be aggressively pursued. In
addition, INPE has proposed to fly an Argos DCS instrument on board the
SCD3 satellite that is planned for launch around 2001. CNES and INPE are
currently studying the possibility to accommodate the Argos instrument
on board SCD3. Results of this study are expected at the beginning of
1999. CNES will send a letter providing NOAA with the status of
discussions between CNES and INPE on this issue (32^nd^ O/C)

L. Ruiz reported that INPE and CNES/CLS have agreed to take appropriate
measures to coordinate the operations between the Brazilian DCS and the
Argos system.

As a first step, CLS has accepted to provide INPE with 2000 DCP
identification numbers. Other tasks currently being carried out are:

-   assessment of the complementarity of coverage between the Brazilian
    HRPT stations and the CLS station planned for installation in French
    Guyana ;

-   comparison of location and data collection performance between
    Brazilian DCS and Argos system, on a set of selected platforms from
    the Amazonian hydrological network.

Preliminary discussions have started between CNES and INPE on a possible
Argos-3 instrument to be flown on the SCD3 Brazilian satellite. (33^rd^
O/C)

C . Gal made a brief presentation on the on-going discussions with the
Brazilian space agency, INPE, regarding possible co-operation between
the Brazilian DCS and the Argos DCS. The Argos Operations Committee
confirmed its interest in continuing these discussions. The Operations
Committee proposes to take the opportunity of the next CEOS meeting to
review the progress made in the discussions. In order to inform INPE of
this proposal, the OPSCOM co-chairs will send a letter to the INPE
Director, Mr. Barbosa (34^th^ O/C)

Today SCD1, SCD2 and CBERS-1 are operational, 5 more satellites are
planned for launch in the future: CBERS-2 (2002), SSR-1 (2005), CBERS-3
(2005), SCD-3 (2007) and CBERS-4 (2007). The ground processing segment
is fully operational with one receiving S-band station in Cuiaba and
another one in Alcantara. Three more receiving S-band antennas are
planned in the near future. An average of 850 DCPS is received per
satellite and per day. Tests were performed between CLS and INPE to
evaluate the interest of integrating Argos data received through the
Brazilian network in the Argos global network. The preliminary results
are very encouraging: the Brazilian DCS and Argos DCS prove to be
compatible. The Brazilian DCS offers improved coverage and reduced
latency times within equatorial regions. The quantity of usable Argos
data collected by the Brazilian DCS would be estimated at about 30 % to
50 % of that of the Argos system without too much technical work having
being done so far. CLS, CNES and INPE are willing to perform a more
detailed technical evaluation, in particular regarding the ground based
message decoding equipment. To give a framework to this cooperation, the
parties will plan to develop the basis of a future Agreement. (35^th^
O/C)

Three satellites are actually operational: SCD-1, SCD-2 and CBERS-1.
Five more are planned in the future: CBERS-2 (2002), SSR-1 (2005),
CBERS-3 (2005), SCD-3 (2007) and CBERS-4 (2007). DCP message processing
is done at Data Collection Mission center located in Cachoeira Paulista
and users access their data at most 30 min after the pass above a
receiver station by FTP. At present:

-   470 DCPs are installed,

-   3 satellites are operational (SCD-1, SCD-2 and CBERS-1),

-   2 receiving antennas (Cuiaba and Alcantara),

-   Users access via Internet (FTP).

C. Vassal then reported about the follow-on experiments performed
between CLS and INPE since July 2001. The processing and distribution of
Brazilian DCS data is feasible through the Argos processing centers
based upon recent experiments and the use of the Brazilian DCS data
tremendously improves the latency for data collection PTTs within the
coverage of the Cuiaba station. It is observed that no more mid-day
holes are seen at low latitude in Southern hemisphere and that an
additional 40% of data information was delivered by the Brazilian DCS.
CLS's principal customer in Latin America is more satisfied with system
performance qualified as "near real-time". Next step for the technical
cooperation would be the development and implementation of a dedicated
stand alone Brazilian DCS station including S-Band antenna and enhanced
procod 3 receiver. Cost and performance to be assessed by December 2002.
In view of the above results, the Operations Committee recommends that
CNES / CLS and INPE formalize a framework for this cooperation through
an agreement. 36^th^ O/C)

CNES and CLS did a very preliminary study which demonstrates that the
integration of a stand alone Brazilian station is feasible. The antenna
sub-system is available off-the --shelf from manufacturer involved in
the Jason program. The processor (procod) is upgraded presently by a
Brazilian manufacturer and should be ready by the middle of 2005. Any
decision to finalize a cost analysis and to present it to OPSCOM/JTA is
dependant upon two factors:

-   A strong users'requirement for enhanced latency time in any
    equatorial region of the world

-   The confirmation from INPE that their actual constellation is going
    to be replaced within the expected timeframe.

Wilson Yamaguti presented the Brazilian Data Collection System. Its
continuity is assured by the following plan for the space segment:

-   The Launch of the CBERS-2 satellite by Sep. 2003.

-   The discussion of two additional scientific satellites (FBM, EQUARS)
    to carry on a DCS transponder. The FBM is a 6 degrees inclination
    and 750 km altitude orbit to be launched by 2005/2006. The EQUARS is
    a 20 degrees inclination and 750 km altitude orbit to be launched by
    2006.

-   The addition of two new small satellites (SCD-3, SCD-4) in the
    2004-2007 National Space Activities Program to replace the SCD-1 and
    SCD-2 satellites by 2006 and 2008.

-   The approval of the China and Brazil cooperative program to build
    and to launch the CBERS-3 and CBERS-4 by 2008 and 2010.

```{=html}
<!-- -->
```
-   A possible cooperative program between Argentina and Brazil to build
    and to launch the SSR-1 by 2007.

-   The launch of the SSR-2 with a Synthetic Aperture Radar and a DCS
    transponder by 2010.

Related to the data exchange between CNES and INPE the status is the
following: CNES/CLS is receiving raw data transmitted from INPE. INPE is
doing the technical evaluation of data transmitted from CLS and is
analyzing ways to formalize the data exchange. (37^th^ O/C)

W. Yamaguti presented the Brazilian Data Collection System report. The
presentation shows the efforts to assure the Space Segment as well as
actions to improve the ground reception and processing. The space
segment is based on the SCD-1, SCD-2, and CBERS-2 satellites. CBERS-2
satellite was launched successfully in Oct, 2003 to substitute the
CBERS-1 that failed in Aug. 2003. The following satellites are
considered in the system:

-   The FBM satellite is being redefined in terms of mission objectives
    and participating space agencies.

-   The DCS payload will be installed on EQUARS (20º inclination, 750
    km, 2007). Budget for DCS transponder implementation is being
    discussed.

-   The strategies to implement the SCD-3 and SCD-4 for SCD-1 or SCD-2
    replacement are under analysis.

-   A possible Brazil-Argentina Cooperation is under discussion to
    implement SSR-1 with an optic payload for remote sensing and data
    collection. A polar orbit with 900km altitude is considered, as well
    as launch date planned by 2007. This satellite will use the
    Multimission Platform (MMP) under development by a contract managed
    by the Brazilian Space Agency (AEB).

-   The cooperation between China and Brazil for CBERS-3 (Polar Orbit,
    778 km, 2007) and CBERS-4 (Polar Orbit, 778 km, 2011) were signed
    and payload characteristics specification are under discussion.

-   SSR-2 or MAPSAR is planned to use the Multimission Platform in a
    polar orbit with 606 km altitude and launch date by 2011.

Other planned actions to improve Brazilian Data Collection System are:

-   To improve the data collection processor performance with addition
    of a second PROCOD-2 in the Cuiabá and Alcântara Station.

-   To develop the PROCOD-3 by 2005.

-   To improve the Alcântara G/T by changing LNA and some RF equipments.

-   To enable the Natal TT&C Station to receive data collection
    satellites. Budget is allocated for 2004.

-   A Receiving Station operating in S Band will be installed in
    Mozambique (Beira)( Brazil-Mozambique cooperation in Data
    Collection).

-   a Data Collection and Applications Section at Brazilian Remote
    Sensing Symposium (April, 2005) was proposed to exchange experience
    and to explore new applications.

Related to the data exchange between CNES and INPE the status is the
following:

-   CNES/CLS is receiving raw data transmitted from INPE.

-   The formalization procedure is under INPE/MCT analysis. INPE plans
    to create an organization or to assign services to an existing
    organization to process, to store and to disseminate the acquired
    data to the users in a similar fashion as CLS Argos. A definitive
    position was not obtained yet. (38^th^ O/C)

# GROUND SYSTEM

## NESDIS PROCESSING CENTER (DPSS)

### DATA FRAGMENTATION

#### GAC & LAC Data

The fragmentation, or breaking into smaller data sets, of the large
Global Area Coverage (GAC) and Local Area Coverage (LAC) data sets has
caused many problems. The DPSS has trouble saving, retrieving,
processing, and archiving these data since the algorithms used to
temporarily stage these data were designed to accept only single, large
data sets from each wide-band readout of the spacecraft recorders. (8th
C/C)

#### Stored TIP Data

There are problems with the processing, transmitting and monitoring of
the Stored TIP (STIP) data from Lannion to Suitland. NESDIS will design
and conduct tests to determine the nature of these problems. (13th O/C)

#### STIP Test

A limited test was conducted by NESDIS in an attempt to solve the
fragmentation of STIP data from Lannion. This test was inconclusive and
it is believed that an extended test period will be required to
determine the causes. (14th O/C)

### DATA TRANSMISSION DELAYS

#### Suitland to Toulouse

Delay in transmitting data from Suitland to Toulouse. Service Argos has
noticed that there are many large delays in receiving the Argos data
from Suitland. NESDIS will study means of minimizing these data
transmission delays. (10th O/C)

#### Action Plan

NESDIS reported on current and planned efforts being made to minimize
Argos data transmission delays. This will be a continuing item as
required. (11th O/C)

#### Reported Improvement

These data delays have improved over the past few months. In August
1981, 66% of these data were delivered in less than 3 hours and average
monthly delays have also improved. However, the average yearly delay is
nearly constant. (14th O/C)

### INTERFACE FOR SYSTEM PROBLEMS

#### Agency Interfaces

It was agreed to maintain a current table, listing agency interfaces, to
be used when system problems occur. (9th O/C)

#### DPSS Operator Responsibility

The DPSS operator will prepare the operational messages for coordination
between NESDIS and Service ARGOS. (7th O/C)

### DATA-GAPS

#### Missing Data

Service Argos will compare their missing data with the future NESDIS
data-gap (\>4 minutes) messages and transmission delays. After comparing
information, Service Argos will notify NESDIS of any data-gaps not
contained in the NESDIS messages. NESDIS will investigate to determine
the cause. (8th O/C)

#### Missing Data Notification

NESDIS is now accounting for data-gaps equal to or greater than 4
minutes and 30 seconds, instead of gaps lasting more than 4-minutes. It
was agreed not to change from the 4-minutes and 30 seconds gap
notification. Service Argos will provide to NESDIS on a weekly basis
information on data not received at Toulouse and not reported as missing
in the NESDIS data-gap messages. In addition, Service Argos will notify
NESDIS of any processing difficulties. (10th O/C)

#### Missing Data, NOAA-6

Data gaps on NOAA-6 data have apparently increased since March 1981.
NESDIS will attempt to determine the cause. (14th O/C)

#### Data Gap Investigation

NESDIS to ensure that data gap messages are routinely being sent and
that investigation of data gaps are being made. Explanations, when
known, will be included in the message. (14th O/C)

### DATA PROCESSING PROBLEMS

Problems with Argos data received from NESDIS that affect processing
are:

1\) A pause of Å10 minutes is necessary after each data set transmission
in order to forward this data set from the acquisition computer to the
main processing computer.

2\) Occasional data set headers that have incorrect orbit numbers,
non-sequential progression of data set numbers or no time for the
beginning of the data set.

3\) Stored TIP data from Lannion that is routed through Suitland at
times are difficult to transmit, monitor and process. (13th O/C )

### OPERATIONAL REPORTS

#### Monthly Report

A monthly operational report for Argos System Processing was received
and some modifications were requested. It was agreed that NESDIS would
develop a monthly report on the DPSS that would complement this report.
(12th O/C)

#### Monthly Report Format

Service Argos accepted the format of the proposed NESDIS monthly reports
with the understanding that changes may be necessary in the future as
conditions dictate. (13th O/C)

### ENHANCEMENTS

#### Transmission Delay Improvement

Scheduled NESDIS enhancements and or modifications to the DPSS are
expected to reduce the data transmission delays by approximately 35
minutes per orbit after July 1981. It was noted that further
improvements will be necessary to reach the goal of a 45 minute
transmission delay to Service ARGOS. (13th O/C)

#### DPSS Enhancements, 1983-84

Future enhancement of the DPSS include the acquisition of another ingest
computer, upgrade of the existing computers, disc replacement, and
improvement tape transport backup. These are scheduled for the 1983-84
time frame and are subject to budget approval. (14th O/C)

#### DPSS Enhancement Requests, 1986

Three enhancements to the METSAT DPSS have been requested by Service
Argos and agreed to by NESDIS. These are:

1\) A second data port and associated software to provide an identical
data flow to both Toulouse and the U.S. Processing Center.

2\) Extract Argos data from the HRPT data stream.

3\) Additional data compression

Due to severe restrictions on resources, NESDIS may be delayed in
completing all of these enhancements during this calendar year. (20th
O/C)

#### Data Compression Software

Data compression software was implemented in December 1983. (18th O/C)

#### DPSS Improvement/Status 1989

A number of METSAT DPSS system improvements which benefit the Argos
Processing Centers and the overall user community were made. The
improvements and services addressed included system configuration,
operating procedures and the support of special tests. In addition data
processing goals were established as a performance reference, and future
improvement plans were discussed. (23rd O/C)

#### NOAA 9, 10 Monitoring

By agreement between NASA and NOAA, one month prior to launch of NOAA D,
NASA will begin to acquire 100% of the global STIP data recorded on NOAA
9. The data will be acquired through one contact/day at Fairbanks and
two contacts/day at NASA Wallops. Multiple playbacks will be relayed
post pass to a new TIROS capture and processing capability which has
been developed at the Goddard Space Flight Center (GSFC). NOAA will
monitor the satellite for health and safety and load the stored table
and ephemeris, as required, during the Fairbanks contact. NOAA/DPSS
plans to ingest only one STIP/day. The NOAA 9 satellite will revert to
the current operation approximately two months after launch of NOAA D.
(24th O/C)

#### CEMSCS to Replace DPSS

A new Central Environmental Satellite Computer System (CEMSCS) will
replace the current DPSS. No changes or problems with Argos data
processing are anticipated during the phase over period. (24th O/C)

All NESDIS software applications will be removed from the NOAA/NWS HDS
computers by the end of 1992. The second CEMSCS mainframe will be in
place by mid-summer 1992. This new computer will run the jobs previously
processed on the HDS machines. NESDIS expects increased reliability and
speed from the new configuration. (26th O/C)

#### New Uninterruptible Power Supply

A new UPS was installed in the NESDIS facilities. (25th O/C)

#### New Polar Acquisition and Command System (PACS)

The PACS represents a change to the computer hardware and software at
SOCC and the CDAs. Improvements:

-Expansion to handle management of four satellites

-Greater data storage capability

-Improved man-machine interface capability

-Provides a realistic spacecraft simulator. (25th O/C)

The PACS is nearing completion of acceptance testing. One problem is
prominent; the interface between PACS and CEMSCS. The interface may need
to be replaced but the system is still expected to be operational by
late Summer, 1992. (26th O/C)

The PACS has been successfully integrated with the polar satellite
ground system configuration. The interface between PACS and CEMSCS has
been solved. PACS systems are now in place at Wallops CDA, Fairbanks
CDA, and SOCC Suitland, ready for the launch of NOAA-I. (27th O/C)

### Performance 

R. Bassett reported that for the period of January 1, 1998 -- April 30,
1999, the DCS data that were successfully processed through the Central
Environmental Satellite Computer System (CEMSCS) and made available to
the Argos Processing Centers averaged 99.1 % for NOAA 14 and 99.5 % for
NOAA 12/NOAA 15. NOAA defined this statistic as a measurement of the
global data delivered versus the absolute maximum amount of data capable
of being collected regardless of delivery time. NOAA also reported that
the amount of data delivered to CLS/Service Argos within 2 hours
averaged 73.5% for NOAA 14 and 70.9 % for NOAA 12/NOAA 15. NOAA defined
this statistic as a measurement of the global data delivered within 2
hours of receipt onboard the spacecraft. It was noted that this
statistic includes data from blind orbits, which accounts for much of
the delay and therefore the statistic can be viewed as a lower limit.
These two statistics are the current metrics for the U.S. processing
system. NOAA proposed that these metrics serve as a starting point to
identify a common approach to measure system performance utilizing well
defined parameters such as processing thresholds, performance
objectives, etc. and adopt common metrics to report end to end system
performance including processing statistics (33^rd^ O/C)

R. Bassett reported that for the period of January 1, 1999 -- May 31,
2000 the DCS data that were successfully processed through the Central
Environmental Satellite Computer System (CEMSCS) and made available to
the Argos Processing Centers averaged 99.6 % for NOAA 14 and 99.5 % for
NOAA 15. NOAA also reported that the amount of data delivered to
CLS/Service Argos within 2 hours averaged 75.9% for NOAA 14 and 71.5 %
for NOAA 15. (34^th^ O/C)

R. Bassett reported that for the period of January 1, 2000 -- April 30,
2001 the DCS data that were successfully processed through the Central
Environmental Satellite Computer System (CEMSCS) and made available to
the Argos Processing Centers averaged 99.04 % for NOAA 14 / NOAA 16 and
99.14 % for NOAA 15. NOAA defined this statistic as a measurement of the
global data delivered versus the absolute maximum amount of data capable
of being collected regardless of delivery time. NOAA also reported that
the amount of data delivered to CLS/Service Argos within 2 hours
averaged 68.64% for NOAA 14 / NOAA 16 and 67.74 % for NOAA 15. The
significant differences between each of the processing systems, however,
may require a much broader, high-level metric for comparison. (35^th^
O/C)

David Benner reported that for the period of January 1, 2001 to April
30, 2002 the global stored DCS data that were successfully processed by
the Central Environmental Satellite Computer System (CEMSCS) and made
available to the Argos Processing Centers averaged 99.6% for NOAA-16 and
99.8% for NOAA-15. NOAA defined this statistic as a measurement of
global data delivered versus the absolute maximum amount of data capable
of being delivered regardless of delivery time. NOAA reported that the
amount of data delivered to SAI and CLS within 2 hours averaged 69.6%
and 67.9% for NOAA-16 and 67.4% and 65.8% for NOAA-15, respectively.
NOAA defined this statistic of data throughput as a measurement of
global stored data delivered the data processing center within 2 hours
of receipt onboard the spacecraft. All blind orbits were considered late
thus adversely impacting this measurement of performance. It was also
reported that a total of 9,188 or 100% of available regional data sets
were delivered in real-time to SAI/CLS from NOAA-15 And NOAA-16. It was
noted that significant differences exist in the communication
architectures of the four Argos data processing systems (NOAA, NASDA,
EUMETSAT, CLS/SAI) and that establishing and implementing common
performance metrics that are meaningful may be difficult. An Action Item
assigns task to CNES/CLS and NOAA to investigate feasibility of
measuring data processing using following performance metrics: a) the
number of data sets delivered per day, b) time required to deliver data
to the user and c) bit error rate. (36^th^ O/C)

Chris O'Connors NOAA/DSD provided the Information Processing Division
(IPD) of NESDIS POES statistics on the data delivery to CLS and SAI.
99.2% percent of global stored data (DCSX) was delivered from NOAA 16
and 99.5% from NOAA 15 and 17 to CLS/SAI over the course of January 2002
to March 2003. In addition 18432 regional datasets were delivered of
real-time DCSH/HRPT data from NOAA 14, 15, 16, and 17 from three ground
station, Monterey, Fairbanks, and Wallops Island. Statistics were also
provided to show the percentage of data deliver to CLS and SAI within 2
hours. The 2 hours is an IPD metrics for data delivery of DCS and is
calculated from the time of a completed orbit (recorder stop time) to
the time of delivery to CLS or SAI. In both graphs NOAA 15 and 17
percentages are equal to or less then the percentages for NOAA 16. The
lower percentages of data delivered within 2 hours by NOAA 15 and 17 are
caused by conflicts in the downlink of POES data. The Satellite
Operations Command Center (SOCC) will downlink NOAA 16 data before NOAA
17 data thus causing the delivery differences to occur. (37^th^ O/C)

C. O'Connors provided the NESDIS processing statistics for the POES
spacecraft NOAA 16 and 17. 99.5% of NOAA 17 and 98.9% of NOAA 16 stored
data was delivered to USGPC. Discussion was held on the usefulness of
the 2 hour metric used by NESDIS processing division with no action
other then to consider further options. The Information Processing
Division (IPD) of NESDIS provided statistics on the data delivery to CLS
and SAI. The Argos global stored (DCSX) data that was successfully
processed through the Central Environmental Satellite Computer System
(CEMSCS) and made available to the Argos processing centers averaged
98.9 (99.2 2002-3) percent for NOAA-16 and 99.3 (99.5 2002-3) percent
for NOAA-17. In addition to the DCSX data sets (Data set equal to one
orbit), a total of 19058 regional (increase from 2002-3 18432 )
real-time (DCSH/HRPT) data sets from NOAA-14, NOAA-15, NOAA-16 and
NOAA-17 were provided. The delivery rate of available data sets was
100%. (38^th^ O/C)

The National Oceanic and Atmospheric Administration's (NOAA's) National
Environmental Satellite Data and Information Service (NESDIS) currently
receives and processes 98.7% of NOAA-16 and 99.1% of NOAA-17 global data
for the 2004-2005 reporting period. In addition to global data recovery
and processing, the receipt and processing of real-time, regional
datasets increased from 19058 in 2003-2004 to 19566 in 2004-2005 and was
delivered 100% of the time (pretty good!). The problem of "blind orbits"
in NOAA's system still limits the 2 hour timeliness of delivery
requirement for global data recovery and processing to 69-77% (4 blind
orbits/3 blind orbits out of 14 per day). With this fact, the delivery
of global data within 2 hours for NOAA 16 was 75.2% and 71.1% for NOAA
17. While these numbers fall within the NOAA ground systems' limits, the
rationale for NOAA-17's lower number is due to instrument anomalies (not
DCS) that require NOAA-15 data to also be recovered and delaying
NOAA-17's data recovery a small percentage of the time. (39th O/C)

## ARGOS PROCESSING CENTER (APC)

### DATA TRANSMISSION DELAYS

#### Data Retransmission

It was agreed that the APC would request retransmissions of data by
block-time rather than orbit number. (10th O/C)

#### Improved Throughput Time

Mean throughput time of the system decreased significantly in 1989. This
is primarily due to the processing of all real-time data from Fairbanks,
Wallops Island and Lannion. The access of real-time data through other
country host agencies is the new Service Argos direction (24th O/C)

### DATA-GAP REPORTS

#### Weekly Reports

The Argos Processing Center is now sending a weekly report to the NESDIS
Production Section indicating data gaps not reported in the NESDIS data
gap messages and any processing difficulties. (11th O/C)

### OPERATIONAL REPORTS

#### Monthly APC Reports

It was agreed that a monthly APC report will be forwarded to the U.S.
This report will contain the number of platforms on a weekly basis and
processing information. (9th O/C)

#### Report Format

The monthly report from the APC was reviewed and a few additions were
requested. It was recommended that information concerning platform
improvements, such as improved oscillators, more powerful
micro-processors and other platform technological improvements be
included in the APC monthly reports. (12th O/C)

### ENHANCEMENTS

#### Duplication of Data

Stored TIP data only will be recovered through Lannion. The primary
Argos data will be routinely recovered on all Gilmore and Wallops
interrogations via the wide-band down links. If the APC receives both
the stored TIP and the Gilmore/Wallops wide-band data there will be
periods when there is extensive duplication of Argos data being sent
from the DPSS to the APC. The DPSS has no provision for eliminating
these duplicate data. The APC will have to have the capability for
accommodating these duplicate data. (5th O/C)

#### Interface Document, TIROS-N

The document \"Argos Project: NESDIS-CNES Interface for Tiros-N\" dated
March 23, 1977, and identified as 77/CT/EMT/MT/EDP/#194 was approved. An
amendment to this document will reflect the APC\'s ability to accept the
duplicate Argos data from the DPSS that occur when both the Stored TIP
data received at Lannion and the wide-band Argos data received at
Gilmore/Wallops are transmitted. (6th O/C)

#### Orbit Interpolation Determination

The interpolation method for orbit determination has been suggested but
investigation has revealed that there is considerable doubt that this
method would provide the location accuracy desired. No other work will
be done in this area until after the system becomes operations. (6th
O/C)

#### APC Design Life

The original design life of the APC equipment was to last through 1985.
Studies are underway to determine the most cost-effective method to
extend the life of the APC equipment through 1990. (13th O/C)

#### APC Improvements/Enhancements.

Improvements/enhancements to the APC include the addition of rough
estimates of daily orbits available in the orbital files, connection to
the French Transpac Data Transmission Network, and changes to the
distribution computer that will reduce response delays. Also, an
improvement to the distribution computer has been approved that will
allow the management of a larger number of files. (14th O/C)

#### European Meteorological Data

CNES is planning to directly link their VHF direct readout station to
the APC. This will allow rapid processing and dissemination of data in
Europe of meteorological information obtained through the system (data
collection processing only - no location processing in less than 30
minutes). Development began in July 1982, and final acceptance is
anticipated in January 1983. (16th O/C)

#### Data Compression Software

The implementation of the data compression software in December 1983,
has permitted a forty percent gain in time for the acquisition function.
(18th O/C)

#### U.S. Processing Center

CNES is currently conducting a study for the establishment of a U.S.
Processing Center. CNES plans to send NOAA a formal proposal for the
center after the completion of the study later in 1985. (19th (O/C)

So that both current and future global users of the Argos system will be
better served, CNES/Service Argos has decided to locate their U.S.
Processing Center in the Washington D.C. area. This decision was reached
after an extensive evaluation of candidate locations, each of which
offered the opportunity to locate the processing center near a major
NOAA facility. (20th O/C)

##### Scheduled Operation:

The Joint Project Plan ground system managers are to establish a
schedule of activities to ensure that the U.S. Argos Processing Center
is operational by March 1987. (20th O/C)

##### Design evolution

A major upgrade to Alpha computer was made during 1996 with
significantly improved performance. Associated storage devices,
infrastructure were also improved. The USGPC interior space is being
reconfigured in light of the reduced space requirements of the computer
center. (31^st^ O/C)

#### Toulouse Improvements (1985)

The primary improvements made at Toulouse in 1985 were:

1\) New distribution system

2\) New acquisition system

3\) Modification of the DRIBU coding software to include subsurface
temperatures and surface atmospheric pressure tendency. (20th O/C)

#### Filtering Software

Because of the redundancy of data from the three (3) ground receiving
stations at Fairbanks, Wallops Island and Lannion, filtering software
was implemented in September 1990 to eliminate redundant processing,
thus reducing processing time considerably. (25th O/C)

#### French/U.S. GPC Improvements (1991)

CLS took action to reverse declining hardware performance trends and to
solve resource problems by improving management of computers and disks.
CLS is also improving their data backup system. The U.S. processing
center installed a new DEC VAX 6000 computer system in mid-1991, which
resulted in a significant increase in CPU and I/O efficiency (data
throughput times improved by about 10%). An Automatic Data Distribution
System was installed in October. This enables users to receive their
data automatically through multiple communication or media sources.
(26th O/C)

#### Regional Center in Australia

The Argos Regional Center in Australia became operational in November
1989. Service Argos is studying the possibility of implementing a
similar center in Japan. (24th O/C)

#### Regional Center in Japan

The Regional Center in Japan became operational in August, 1991. (26th
O/C)

#### Location Algorithms

CLS reported that a new location processing was successfully developed
and would be installed in mid-1994. (28th O/C)

#### Argos-GPS Processing

CLS reported that software which would process data from receivers
providing locations from the Global Positioning System (GPS) was now
installed at the Processing Centers. (28th O/C)

#### Operations and further improvements

Hardware: The main improvement was the completed move onto Alpha
computers which not only gives better performance to the processing. but
also improves redundancy between US and French center.

Ground segment: New S-band antenna in South Africa and New Zealand are
now collecting real-time data and another in La Réunion island is
planned to be connected before the end of 1997.

Software: Both centers are ready to process NOAA K data and the software
development for ADEOS II data processing will stars in 1997. (31^st^
O/C)

Hardware : Primary upgrades involved storage and communication; high
capacity disks are being installed along with multi-protocol routers
which provide more secure data storage and faster data access. SAI
implemented an Internet server to distribute data through fax, FTP and
E-mail. This capability will exist in CLS by the end of the year.

Regional Processing Centers : The number of regional centers has grown
to 14 with the addition of Cape Town, South Africa; Halifax, Nova
Scotia; Edmonton, Alberta; and Tokyo, Japan. Reunion Island, France,
will be added in 1998, along with Monterey, California, and Baton Rouge,
Louisiana, in the United States.

Software : Software was developed and installed to process the new
telemetry format from NOAA-K.

A new accounting system (ROSS Systems) to manage business development,
accounting and invoicing, is now fully operational.

Future Projects : There are 2 major projects coming in the years 2000
and 2001. CNES and NASDA (the Japanese Space Agency, have agreed to fly
an advanced Argos instrument on ADEOS-II. The NASDA satellite is
scheduled for launch in November 2000. The Argos instrument will provide
a satellite-to-transmitter downlink, thus giving Argos a 2-way
capability. In 2001, Argos will upgrade the entire processing system.
This project, called Argos 2001, will result in an open architecture
system which will allow fast and easy response to changes requested by
Argos' users. (32^nd^ O/C)

In the French APC, two technical problems occurred in February 1998 and
April 1999. One was caused by a failure in power supply and the other by
a computer. No data were lost but data distribution was seriously
disturbed. The availability of the Argos System remained over 99.9% from
an user point of view. In January 1999, the number of real-time data
sets processed per day in each Global Processing Center was about 5
times the number of stored data sets which was nearly 80. The number of
locations calculated per day (\~ 30.000) was between one third and one
fourth the number of distinct messages received by each center in a day
(\~ 100.000). (33^rd^ O/C)

M. Taillade presented the improvements made in both US and French
Processing Centers : Concerning hardware, the efforts mainly focused on
disk storage, Internet access and Intranet architecture. The software
upgrades have concerned the changes in formats to acquire data from
Argos-2 instruments and also to replace X25 by FTP in the link with
NOAA.

*Argos 2001:* This project aims at renewing the whole processing system
within the next 2 or 3 years. The first phase will be implemented by the
end of 1999 and concerns mainly the user interface including the new
system use agreements database. (33^rd^ O/C)

The operation of down-link messaging capability on ADEOS-II request the
addition of two important parts in the ground segment:

-   DMMC (Down-link Message Management Center) to collect and manage
    requests from user to be transmitted to platforms ;

-   4 Master beacons installed in Fairbanks, Kiruna, Hatoyama and
    Toulouse.

After completion, the network of receiving stations and processing
centers will be fully interconnected via NOAA and NASDA with adequate
redundancy. (33^rd^ O/C)

M. Taillade presented the improvements made in the system since last
year meeting :

-   Concerning hardware, the main improvement concerns the installation
    of new HRPT stations in Russia and the connection to new HRPT
    stations in the US.

-   Concerning software, much work was dedicated to Y2K compliance and
    new services development for data distribution.

-   Two major projects are on their way for the near future : Argos 2001
    and Argos-Next. (34^th^ O/C)

Concerning hardware, the main improvements concern the upgrade of the
computer systems architecture to host the new Argos 2001 Oracle
database, the installation of a centralized data back-up system and the
increase in performance of our internal and external communication
links. Concerning the ground segment, the connection or installation of
4 new HRPT stations in 2001 will be followed by the installation of 3
new stations in Europe (Helsinki, Las Palmas and Athens) and Buenos
Aires is already connected. (35^th^ O/C)

Concerning hardware, the main improvements concern the continuing
enhancement of the computer systems architecture with the upgrade of 2
computers, the implementation of an Oracle database management system
and a replication mechanism between global processing centers. For the
Argos 2001 project, a web data distribution server and a validation
configuration were also installed. Concerning the ground segment, the
connection or installation of 6 new HRPT stations in 2001 (Buenos Aires,
Miami, Las Palmas, Noumea, La Reunion and Helsinki) will be followed by
the connection of 3 new stations in Asia and Europe (Singapore, Oslo and
Hatoyama). Presently, the real-time data flows from 28 stations are
processed, most of them receiving up to 4 satellites. Concerning
software, much work was dedicated to the maintenance and upgrade of the
operational software while the Argos 2001 and Argos Next software
developments have continued. It should be noted that due to performance
problems detected during tests in the Argos 2001 data distribution
system, it will become operational only in September 2002. (36^th^ O/C)

Bill Woodward reviewed the Argos system operations for year 2002 in the
categories of Ground Stations, Processing Centers, Communications Links
and data Throughput Times. He reported that Fairbanks and Wallops
continue to be the ground stations receiving the STIP telemetry from
NOAA- 11, 12, 14, 15, 16, & 17 and that the Lannion station is still not
in service to receive STIP data. Five new regional stations were brought
on line in 2002 (Oslo, Hatoyama, Singapore, Las Palmas, Santiago)
bringing the total number of regional stations to 33. The Argos
constellation now includes 7 satellites with the basic Argos service
being provided by NOAA-15 and 16 as well as ADEOS II. During 2002 the 2
Global Processing Centers (Toulouse and Largo) and the 3 Regional
Processing Centers (Lima, Tokyo, Melbourne) operated without a hitch.
The Toulouse Center now has double Internet access which improves the
performance and reliability of the communication links. Data throughput
times for 2002 were approximately the same as for the previous year. For
NOAA 15, 16, 17, 64% of the stored data arrived within 3 hours. 86% of
the real-time data from all the satellites arrives within 30 mins.
(37^th^ O/C)

Argos System Improvements for 2002 included upgrades to the hardware and
software configurations, the ground segment architecture and the
regional processing centers. A fourth Argos operational computer was
added to improve the performance of the Oracle database service, and a
second internet access at 2 Mbits/sec was added to enhance the bandwidth
and reliability of the communication links. In addition, the capability
for total redundancy between Toulouse and Largo was successfully
achieved in 2002 and 5 new HRPT stations were added to the regional
network bringing the total number to 33. Phase I of the Argos 2001
project was completed and opened to users in May 2003, and Phase II,
improvements in added-value services, began in December 2002 with a
target completion date of December 2003. A new project called SSA3 was
started which will address all changes needed in the current ground
segment for Argos 3. The main improvements at the regional processing
centers involved upgrading versions of their software. (37^th^ O/C)

Bill Woodward reported on the status of Argos operations. The two global
ground stations at Gilmore Creek and Wallops Island continue to deliver
STIP data from NOAA-12, NOAA-14, NOAA-15, NOAA-16, NOAA17. Only two
orbits/day are delivered from NOAA-12 which is just enough to collect
the minimum amount from the Orbitography beacons and enable the location
calculation to be done. TIP or real-time data are delivered to CLS/SAI
immediately on reception from now 40 regional stations around the globe.
The two global processing centers process more than 600 datasets per day
and they are now fully redundant. All three regional centers continue to
process data received by their antennas and they all operated
continuously without any problems during 2003. The main communication
link is via the internet and parallel capability has been established
with each link at 2 Mbits/sec. Data encryption now exists as an option
for those users selecting ADS as the mechanism to receive their data.
During 2003 96% of real-time data was delivered to users within 30
minutes of it arriving at the satellite. 81% of the stored data is
delivered to the users in 3 hours. (38^th^ O/C)

Bill Woodward reported that hardware improvements for 2003 were
dedicated to the Argos 2001 project and included primarily the addition
of 4 new Linux processors and significantly increased disk storage
capability. The level of redundancy between the two global centers was
also increased. Substantial efforts were applied to the Argos 2001,
Phase II project which addresses improvements in value-added services
and which will become operational in the 4Q 2004. A substantial amount
of work was performed in support of the SSA3 Project which addresses all
changes needed in the ground segment for Argos 3. This includes software
upgrades of the relevant processing sub-systems in the Argos processing
center, addition of a new time reference beacon in Toulouse, additions
to the Master Beacon Network and development on new hardware for PTT/PMT
type acceptance by CLS. A new regional processing center in Jakarta,
Indonesia was prepared for installation and operation during 2003 and
the new Argos Visualization System (AVS) was installed at the NOAA
Office of Climate Observations to support their climate monitoring
center. (38^th^ O/C)

##### ADEOS II ground segment

> K Oshimura explained the status of NASDA ADEOS II ground system. There
> is no significant news regarding ground system development. Detailed
> test plan involved with CLS during early 2001 time frame is being
> coordinated between CNES and NASDA. (34^th^ O/C)

Yoshio Ishido, Eiichi Sakata and Tomoaki Endo presented the status of
ADEOS II ground system and mission operation base line including DCS
data acquisition of ADEOS II as follows.

-   Ground system at NASDA/EOC including CNES/CLS interface.

-   The Information System and Network (Earth Observation Information
    System: EOIS) of NASDA/EOC

-   Acquisition of ARGOS of NOAA satellite

-   The status of ADEOS II Mission Simulation Test (MST)

-   Schedule for ADEOS II operation and its preparation

-   Operation Organization for ADEOS II

To insure operational readiness, the ADEOS II ground system development
and test will be completed in summer 2001, and operations training will
be done by ADEOS II launch. (35^th^ O/C)

For ADEOS-II ground segment NASDA completed Mission simulation test
including NASA/NOAA/CNES in CY2001. The activity in CY2002 focuses on
rehearsal activities as pre-launch phase. At April 1st, 2002, NASDA
started test operation to acquiring NOAA ARGOS regional data started at
Hatoyama station and it works well so far. (36^th^ O/C)

Yoshio Ishido from NASDA EOC presented the status of the ADEOS-II ground
system. He explained the mission operations scenario: 24 hours and 7
days with global data acquisition and Argos/DCS level delivery in Near
Real time for both global and regional data. Dosho Hirohiko from NASDA
EOC presented the ADEOS-II initial operations and evaluation. In
conclusion, NASDA confirmed that the requirements were met and that the
EOC interface for the Argos DCS system could start the routine
operations. (37^th^ O/C)

ADEOS-II mission operation was done successfully, but was terminated due
to ADEOS-II anomaly occurred in October, 2003. The DCS data delivered to
CNES/CLS was about 3,700 downlink segment that include regional and
global data. He mentioned the DCS application regarding Calibration and
Validation (CAL/VAL) of ADEOS-II on-boarded sensor, AMSR and GLI. This
activity was not performed due to budget restriction unfortunately. JAXA
intends to keep NOAA regional reception at EOC under ADEOS-II project by
the end of March 2006. The Master beacon at EOC was closed due to
ADEOS-II termination in conjunction with RF license regulation in Japan.
(38^th^ O/C)

##### Argos-Next ground segment

C. Gal reported that the Argos-Next ground segment will undergo
acceptance testing in July 2000.

It is ready to participate in the NASDA managed Mission Simulation Tests
(MST) the objective of which is to validate the Argos next ground
segment interfaces with the overall ADEOS-II ground segment. In that
context the interface between NESDIS and SAI for the transfer of the
ADEOS II/Argos DCS data (back up link) has to be defined (formats and
transmission line) (34^th^ O/C)

The development of the DMMC (Downlink Message Management Center) the
role of which is to centralize, validate and schedule downlink message
requests from users was completed by mid-2000 and test accepted. A
redundant (and identical) DMMC is to be installed in Largo next year.
The network of Master Beacons will be installed in 4 locations :
Toulouse, Hatoyama, Fairbanks and Spitsberg (Svalbard). Toulouse and
Hatoyama master beacons were installed in September 2000 and the
installation of Fairbanks master beacon is planned for September 2001. A
Mission simulation test consisting of interface tests between NASDA
/ADEOS II ground segment and CLS was conducted since mid-2000 to confirm
compatibility of mission data and interface, and is to be continued
until launch presently scheduled for February 2002. (35^th^ O/C)

The development of the DMMC (Downlink Message Management Center) the
role of which is to centralize, validate and schedule downlink message
requests from users was completed by mid-2000 and test accepted. A
symmetrical (and identical) DMMC is to be installed in Largo after the
deployment of the Argos2001 has been completed. The network of Master
Beacons is planned to be installed in 4 locations: Toulouse, Hatoyama,
Fairbanks and Spitsberg (Svalbard). Toulouse and Hatoyama master beacons
were installed in September 2000. The installation of Fairbanks master
beacon was completed in October 2001. The last one will be installed
when the Argos Next system will become fully operational. A Mission
simulation test consisting of interface tests between NASDA /ADEOS II
ground segment and CLS was conducted since mid-2000 to confirm
compatibility of mission data and interface, and is to be continued
until launch presently scheduled for November 2002. Two other elements
of the Argos Next ground segment are being developed :

-   An Argos Next demonstrator (DAN) which simulates the on-board
    instrument and will be used to qualify the instrument during the
    in-flight acceptance test phase. It will also be used to demonstrate
    the downlink capabilities to potential users and to train Argos
    staff and users.

-   A PMT (Platform Message Transceiver) including a certified
    transmitter plus a receiver with appropriate antennae and a logical
    unit. The receiver was developed by a CNES

sub contractor and CLS ordered 200 units so that a first series of PMTs
be available by the end of the year 2002. (36^th^ O/C)

Elements of the Argos Next ground segment were reviewed including the
Processing Centers, the DMMC, the Master Beacons and the Platform
Messaging Transceiver (PMT). All of the necessary modifications to the
Processing Centers were made and successfully tested during the ADEOS II
on-orbit test phase. The DMMC was installed in Toulouse in late 2002 (to
be installed in Largo in mid-2004). Testing of the DMMC is nearly
complete and and it will be available to Beta testers in the 3Q of 2003
and to everyone else soon thereafter. Three Master Beacons have been
installed (Hatoyama, Toulouse and Fairbanks). Installation of a fourth
beacon is pending. The Fairbanks beacon is currently not operating and a
repair visit is scheduled for late June. The PMT development is nearly
complete. Two prototypes will be delivered by early summer and 50 units
are scheduled to be available in early September for initial
applications of the Argos 2-way. (37^th^ O/C)

Elements of the Argos Next ground segment were reviewed including the
Processing Centers, the DMMC, the Master Beacons and the Platform
Messaging Transceiver (PMT). All of the necessary modifications to the
Processing Centers were made and successfully tested during the ADEOS II
on-orbit test phase until the failure of ADEOS II in October 2003. The
DMMC was installed in Toulouse in late 2002 and was planned to be
installed in Largo in mid-2004. Testing of the DMMC was completed and
made available to Beta testers in the third quarter of 2003. Three
Master Beacons have been installed (Hatoyama, Toulouse and Fairbanks).
The Fairbanks beacon is currently not operating. The PMT development has
been completed and 50 units were available in early September for
initial applications of the Argos 2-way. A live demonstration was
successfully made at Oceans 2003 in San Diego by using the interactive
mode to push up to 18 messages per satellite pass. The development of
the Argos 3 PMT which will begin in October 2003 will certainly take
advantage of the Argos Next accomplishments. (38^th^ O/C)

##### METOP DCS ground segment

C. Gal reported that the development of the METOP overall ground segment
is starting. Interface with the Toulouse CLS APC is defined. Impact of
the METOP data distribution procedure on the APC will be evaluated in
preparation of the necessary modifications. (34^th^ O/C)

Graeme Mason presented an overview of the EUMETSAT Polar System (EPS)
ground segment and the interfaces to the ARGOS ground segment. The
Command and Data Acquisition stations will be located at 78°N in
Svalbard, Norway, which will acquire stored data from on-board Metop for
all orbits (i.e. no "blind orbits" exist). These data will be forwarded
to the EPS ground segment in Darmstadt, Germany via a satellite link
using a so-called "pipeline processing" scheme. It is foreseen to
possibly install an ARGOS Master Beacon at this site in Svalbard.
Monitoring and control of the A-DCS instrument will be performed as part
of the overall Metop satellite control facility. A-DCS data will not be
processed by EUMETSAT, but will be transferred to CLS-ARGOS within 135
minutes of the time of acquisition by A-DCS ([not]{.underline} 135
minutes from Metop stored data dump). Data transfer to CLS-ARGOS will be
performed via a so-called "Near Real Time" (NRT) terminal based on
commercial satellite communication services. EUMETSAT will be
responsible for installing the necessary NRT hardware at CLS-ARGOS.
(35^th^ O/C)

The European Polar System (EPS) core ground segment (CGS) PDR started in
June 2001, but could not be closed out successfully before December
2001. Overall the CGS schedule is now: CGS CDR in June 2002 and
Provisional Acceptance Review in May 2004. C. Gal highlighted the
information of concern to the ADCS is that the installation of the NRT
terminals at User premises is planned between May and August 2003. A
letter will be sent by EUMETSAT requesting from each user the nomination
of a point of contact to deal with these matters. (36^th^ O/C)

The status of the EPS Ground segment was presented leading to a phased
delivery of the EPS CGS from May 2004 onwards. The Polar Site site
(Svalbard) is now available and all antennas are installed with a
planned acceptance in Summer 2003. This site has the advantage of having
no blind orbits. EUMETSAT confirmed that it will exercise the option for
the installation of the Master Beacon in Svalbard. The likely
installation period will be in the summer 2004. (37^th^ O/C)

Christophe Vassal presented a chart with the foot prints of a minimum of
10 METOP Receiving antennas to optimize real time data acquisition for
Argos transmitters.

Those foot prints should ideally be centered at:

-   Wallops Island CDA VA

-   Gilmore Creek CDA in Fairbanks AK

-   Anchorage AK

-   Honolulu Hawaii

-   Tahiti

-   Lima

-   Canaries Islands

-   Tokyo

-   Jakarta

-   Capetown

-   Svalbard.

NOAA plans to upgrade its two CDA sites (Wallops Island and Fairbanks
AK) to accommodate real time IJPS data. Decisions on the NOAA/NWS
Honolulu and Anchorage sites are pending. We hope that the BOM in
Australia is going to update its network of 5 receiving antennas to
maximize the real time coverage in the area. (38^th^ O/C)

## COMMUNICATIONS

### SUITLAND/NEW YORK/MAINE PROBLEMS

#### Second Suitland/New York Link

The second Suitland to New York link became available in May 1979. An
evaluation of the efficiency resulting from this redundant line will be
made by NESDIS and CNES. (10th O/C)

##### Data Link Failure Evaluation:

The NESDIS evaluation of the NESDIS-CNES Data Link failures between
Suitland and New York indicates that the number of required changes to
the backup link has decreased and the reliability has improved. (11th
O/C)

##### Data Link Problem Resolution:

Many problems have been encountered in the NESDIS-CNES Data Link due to
the unreliability of the line between Suitland and New York. CNES plans
to double this portion of the link to improve reliability. (18th O/C)

#### New York/Maine Link

Some long outages still occur in the NESDIS-CNES Data Link. Most of
these problems occur between New York and Andover, Maine. Andover is the
site of the communications satellite earth station. (14th O/C)

### TELETYPE PROBLEMS

#### NESDIS-CNES Data Link

Teletype problems have been encountered since the Installation of the
telephone concentrator that uses the NESDIS-CNES Data link. Service
Argos will analyze the problem to see if the design can be improved and
along with NESDIS, will review operational procedures in order to
alleviate the problem. (11th O/C)

#### Software & Procedural Changes

Software and procedural changes have been made to alleviate the teletype
interference problem on the NESDIS-CNES Data Link. Service Argos feels
the present arrangements are satisfactory. (12th O/C)

#### Lower Bandwidth Teletype

Service Argos proposes to use a lower bandwidth teletype to improve the
teletype circuit on the NESDIS-CNES Data Link. (13th O/C)

### PROCEDURES FOR PROBLEMS

#### Procedure Development

Formalized procedures need to be developed to determine cause of
NESDIS-CNES Data Link problems. Also, these procedures will identify who
is responsible to notify the proper organizations of the problems in
different portions of the link. (7th O/C)

#### Procedure Handbook

Procedures to solve problems in the NESDIS-CNES Data Link have been
expanded and included in the joint operational procedures handbook. (9th
O/C)

Action to solve NESDIS-CNES Data Link problems should be initiated by
the APC. (13th O/C)

#### Problems, action responsibility

Action to solve NESDIS-CNES Data link problems should be initiated by
the APC. (13^th^ O/C)

### New communications means

Internet has become the first mean to collect data sets from regional
stations and also to distribute the results to the users (54%). But
eased lines are still in use to secure communications between NOAA, SAI
and CLS. Concerning throughput times, 68% of the results from stored
data are available within 3 hours for the operational satellites (NK,
NJ) while this figure is only 49% for the back-up satellites (ND,NH).
80% of the real-time data are available within 30 minutes. The
performance varies from one station to the other. (33^rd^ O/C)

Internet is now the primary means to collect data sets from regional
stations and to distribute the results (60% compared to 55% last year).
Concerning throughput times, 68,4% of the results from stored data are
available within 3 hours for the two operational satellites 30% for the
other satellites. With the 20 HRPT receiving station network, 85% of the
data are available within 30 minutes. (34^th^ O/C)

Internet is definitely the first means to collect data sets from
regional stations and to distribute the results to users. X25 is only
used to send data. Concerning throughput times, 70% of the results from
stored data are available within 3 hours for the two operational
satellites 30% for the other satellites, which represents no improvement
since last year. With the network of HRPT receiving station network,
more than 85% of the data from platforms inside the visibility circle of
stations are available within 30 minutes. (35^th^ O/C)

The primary communication link is via internet. This link has been
upgraded from 512 kbit/s to 1 Mbit/s. The X.25 protocol continues at CLS
to send GTS bulletins to Meteo France. This is scheduled to be replaced
with ftp transfer during this year. The transatlantic link between
Touloluse and Largo was terminated in July, 2001. The data throughput
times represent the time elapsed between the recording of the message
on-board the satellite and processing of the same message by the global
processing center. For the two operational satellites, NOAA-16 and
NOAA-15, 33% of the data were available within two hours while 64% were
available within three hours. For the network of the regional receiving
stations, 86% of the data from platforms within the visibility circles
of those stations were available within 30 minutes. (36^th^ O/C)

## DATA TRANSFER

### PROCESSED DATA TRANSFER

#### GOES DCS Data Link Proposal

It was proposed to transmit processed Argos data for U.S. users from the
APC through the GOES DCS. The APC design has made provision for such a
data link. NESDIS will review this proposal and notify CNES. (5th O/C)

#### DCS Data Link Alternatives

NESDIS has no plan to use the GOES DCS to transfer processed Argos data
to the U.S. Several other suggestions were made for providing processed
Argos data to North American users. These included:

1\) Providing the full Argos data stream to the users.

2\) Writing computer digital tapes on the NOAA IBM 360/195 for delivery
of the raw data to the user. (6th O/C)

#### NESDIS-CNES Data Link Proposal

CNES proposed to transfer the processed data from the APC via NESDIS on
the backside of the existing NESDIS-CNES Data Link. CNES will expand on
this proposal at the next meeting. (7th O/C)

#### Data Transmission Proposal

CNES proposes to use the backside of the NESDIS-CNES Data Link to access
the computer files in the APC. North American users would dial a number
in Suitland where a concentrator is installed to handle the data
transmitted at a higher data rate for dissemination at a lower data rate
to the users. NESDIS agreed to a test of this proposal. (9th O/C)

#### Telephone Concentrator Installation

A 300 baud telephone concentrator has been installed at Suitland that
uses the backside of the NESDIS-CNES Data Link to allow North American
users to access their data files in the APC. This eliminates the expense
of a trans-Atlantic telephone call for the user. A two-month test will
be conducted to evaluate its feasibility. The operational phase will
depend upon the results of this test and the final location of the
concentrator equipment in the NESDIS facility as well as the completion
of instructions for operators, maintenance personnel and the users.
Future capabilities such as telex or higher data rates will be deferred
pending the outcome of the above. (10th O/C)

##### Telephone Concentrator Test:

The initial testing of telephone concentrator in Suitland has been
favorable. NESDIS has decided that the concentrator equipment will
remain in FB-4 adjacent to the DPSS. (11th O/C)

#### Connection to Lannion

A connection to Lannion for receiving \"blind\" orbit datasets became
fully operational in February 1989. CLS requested that:

1\) NOAA continue to read out the STIP data over Lannion until another
way of avoiding blind orbits is found.

2\) NOAA maintain the necessary hardware belonging to NOAA and operated
at the Lannion HRPT station. (23rd O/C)

#### STIP from Lannion

NESDIS requested Argos study a way of providing them with STIP from
Lannion. It was discovered that transmitting data from Lannion to
Toulouse entails a significant increase in cost. The only way to avoid
this would be to install an HRPT station in Toulouse. NESDIS will
clarify its needs in this respect. An earlier Service Argos request has
not been clearly answered concerning NOAA\'s continuing to readout STIP
data over Lannion until another way of avoiding blind orbit is found.
This concerns operational data when S/C are declared operational and is
quite different from Lannion launch support previously requested by
NASA. (24th O/C)

#### Connection to SOCC

For HRPT data received at SOCC, the DCS would be decommutated at SOCC
and automatically be put on a dedicated circuit from SOCC to CLS and
USGPC. The DPSS would continue to transmit GAC/DCS data to CLS and USGPC
as they are currently doing. (23rd O/C)

### UNPROCESSED DATA TRANSFER, POLICY

It was agreed that, at this time, NESDIS would not provide data taps
into the NESDIS processing system. NESDIS views Argos as a cooperative
effort among NASA, NOAA, and CNES and, although the MOU allows data to
be processed in the U.S., it is not in the best interest of the system
to allow a data tap in the DPSS. (15th O/C)

### DIRECT READOUT STATIONS

#### New S-Band Stations

An S-band station in Hawaii is feeding data to the U.S. Global
Processing Center. The Melbourne, Perth, Darwin, Casey S-band stations
are connected to the Australian Regional Processing Center. (27th O/C)

#### Ground receiving stations

No major problems were noted. Nevertheless, Lannion does not yet deliver
stored data from NOAA-K directly to CLS. These data are received via the
Wallops station and it will reduce throughput times by nearly 2 hours
when an agreement is signed with METEO-France. The date flows of stored
data from the two operational satellites (NK, NJ) are regularly spread
in time during the day while up to 4 data flows of stored data from the
back-up satellites (ND, NH) can be received together which means 4 to 8
hours delay for some of the data sets. The number of regional receiving
stations collecting real-time data is now 18 with 4 new stations
connected to both GPC during the past year. Most of them are collecting
data from 3 to 4 satellites. (33^rd^ O/C)

##### Global stations:

During the course of the year, Fairbanks stopped sending STIP data from
NOAA-12 and Wallops only delivered two STIP orbits a day for this
satellite: three hours is not sufficient for an accurate orbit
determination. In addition after the change of NOAA-15's frequency,
Lannion is no longer able to provide STIP for this satellite. (34^th^
O/C)

Lannion is no more downloading STIP data from any satellite. This means
that the \"blind orbits\" are now received with more delay than before.
Concerning Wallops and Fairbanks, all orbits of STIP data from NOAA 12
were sent from July 2000 to March 2001 but now again, two orbits only
are received per day. We continue to receive STIP data from NOAA 11,
which is essential as HRPT was shut down in October 2000 and NOAA 11
fills the «midnight hole», but throughput times are still very long. For
NOAA 15 and 16, overall performance is good, but some delays are
systematically experienced. (35^th^ O/C)

Fairbanks and Wallops Island continue to be the two stations receiving
the global Argos data from the NOAA satellites. Both stations
operationally deliver the global or STIP data from NOAA-11, NOAA-12,
NOAA-14, NOAA-15 and NOAA-16. Only two orbits per day are delivered to
CLS/Argos from NOAA-12 and from NOAA-11 it is only the STIP, not
real-time TIP data, that is delivered -- in groups of 3 or 4 orbits. The
global data from NOAA-11 continues to be critical because that satellite
fills the "midnight hole" for satellite coverage. NOAA-M (17) will be
launched in late June 2002 and ADEOS-II in November 2002. Both of these
satellites will be placed in orbits that are very close to NOAA-11 and
will provide real-time data from that time slot. (36^th^ O/C)

##### Regional stations:

Persuing the effort, CLS-Service Argos developed new cooperation
agreements able to deliver the regional data sets. 20 stations are now
connected, but many do not receive NOAA 11 and other can no longer
receive NOAA 15 since the HRPT channel frequency was changed. However in
certain regions (North America, Australia, Europe) throughput times are
less than 20 minutes, 80% of the time. (34^th^ O/C) . In 2000, Miami,
Cayenne, Hawaï, and Toulouse were connected to the Argos network.
(35^th^ O/C)

CLS and Service Argos continued to pursue efforts to increase the number
of regional receiving stations able to provide real-time or TIP data
sets from the NOAA satellites. Five new stations joined the Argos
network during the year -- Buenos Aires (Argentina, INTA), St. Denis de
la Reunion (Reunion Island, IRD), Noumea (New Caledonia, IRD), Las
Palmas (Canary Islands, IRD), and Miami (U.S., NOAA/AOML). Currently 28
regional stations are delivering TIP datasets to CLS and Service Argos.
Plans for year 2002 include adding stations from Singapore, Oslo, and
Hatoyama (Japan, NASDA). A new tool is now in place to enable the daily
monitoring of the arrival of TIP and STIP data sets from all satellites
and all stations and to illustrate trends in these numbers. (36^th^ O/C)

## DATA DISSEMINATION & COMMUNICATION

### Global Telecommunications System (GTS)

Access to the GTS will require that the user make arrangements through
their national weather service who, in turn, will make necessary
arrangements with the French National Weather Service to send the data
on the GTS. These data will be forwarded directly from the APC to Paris
where it will be inserted in the GTS. All data disseminated via the GTS
must be in an approved World Meteorological Organization (WMO) code.

#### GTS Software

A new GTS processing chain became fully operational in February, 1993.
It will separate the processing of GTS sensor data from the Argos sensor
processing system. Additional quality control is a part of the new
system. New equipment was installed at the U.S. GPC to accommodate this
system. (27th O/C)

### Constant Level Balloon & Drifting Buoy Codes

The Constant Level Balloon (COLBA) and the Drifting Buoy (DRIBU) codes
were used during the FGGE operational year. After coordination with WMO,
a limited amount of housekeeping information (battery voltage, etc.) may
be included in the DRIBU coded messages disseminated over the GTS. If it
appears that this additional information may cause saturation of the
GTS, WMO will require that the housekeeping information be deleted. (4th
O/C)

### HYDRA Code

The HYDRA code has been implemented to allow the transmission of the
water level and rainfall automatically from hydrological stations. SHIP
code (FM21) had been used in the system. WMO replaced the SHIP code on
January 1, 1982, with the new SYNOP/SHIP code (FM12/13). The
corresponding software changes have been made in the APC. (16th O/C)

### Data Format Standardization

There is a great need for additional information on the GTS to aid the
computation of Sea Surface Temperatures (SST) from satellite data. There
are only a few buoys in the U.S. processing agreement that have their
data transmissions in a format that is not compatible with the WMO SST
code used on the GTS. Data format standardization will be difficult to
implement due to the variety of users. It was agreed that an education
program was needed for both the users and PTT manufacturers. In order to
accomplish this, NOAA will provide background information for CNES to
notify manufacturers and users of the need for using a WMO code
compatible data format. Also, CNES will urge users to make their data
available for transmission on the GTS. (16th O/C)

### Data Format Dissemination

Service Argos has included an article in the latest issue of the Argos
Newsletter concerning the data format standardization for dissemination
via the GTS. This information based on a draft letter provided by NOAA,
also will be sent to every system applicant. An increase in the number
of DRIBU and ship messages acquired through the Argos DCLS has been
noted. (17th O/C)

## ORBITOGRAPHY

### Orbitography Platform Location

The primary reference or orbitography platforms will be at Kerguelen
Island, Gilmore Creek, Alaska, and Toulouse, France. These sites will be
equipped with redundant sets of equipment. The other sites will be
considered secondary as an outage at a secondary site will not have a
major impact on the system. (5th O/C)

### Proposed Relocation of Orroral Platform

The orbitography platform located at Orroral, Australia, is turned off
many times during the day to avoid interference with another system.
This platform is useful for orbit determination in that part of the
world and must be moved to a site where it can operate continuously.
Proposed new locations are at either Canberra or Melbourne. (8th O/C)

The Orroral platform has been moved to Canberra and is operating as
required. (9th O/C)

### Spare Parts and Test Equipment Procedures

The Joint Working Group recommends that certain procedures be used to
handle the exchange of spare parts and the test-set for all U.S.
operated orbitography platforms. (9th O/C)

The procedures recommended by the Joint Working Group for handling the
exchange of spare parts and the test-set for all U.S. operated
orbitography platforms were approved with some modification. (10th O/C)

## SYSTEM PERFORMANCE EVALUATION

### System Location Accuracy Evaluation

To evaluate the system location accuracy, both orbitography and test
platforms were used. Assuming a medium term stability of the platform
oscillator to be 10-8, the accuracy averages 390m. The maximum error
among 2767 position computations was 2.8m. The difference between
one-pass and two-pass location accuracy is about 35m. During the
evaluation period, it was noted that many of the passes to the east of
Toulouse contained a considerable amount of radio frequency noise. The
spacecraft antenna pattern was estimated by using data from the
Kerguelen Island platform (which is free of most radio frequency noise)
and is very close to the pattern that was measured in pre-launch tests.
(9th 0/C)

### System Monitoring Requirements

Service Argos will determine their system monitoring requirements for
evaluating Argos System performance in the future. These requirements
should consider using the monitoring equipment available at both the
Goddard and Toulouse Space Flight Centers. (10th O/C)

#### Goddard Monitoring Equipment

Service Argos has determined that there will be no requirement to use
the monitoring equipment at the Goddard Space Flight Center for future
system tests. (11th O/C)

## TRANSMISSION CONSTRAINTS

### System Saturation Determination

Service Argos uses a half-global depiction (10û latitude-longitude
sectors) of the average number of messages received per-second to
determine potential saturation areas. The estimated number of messages
received per second to cause saturation is 5 (there are only 4
DRU\'s/spacecraft). Up to that number, the probability of successfully
receiving a message is 0.84. (12th O/C)

There are no areas where the system is nearing saturation. The maximum
of 1.6 transmissions per second is located off the east coast of Canada.
(14th O/C)

### Performance Management Tools

CLS presented some tools used for performance management and the results
of actions taken in order to increase the efficient use of the system.
These results show that the decisions taken at the 22nd O/C Meeting were
applied without major problems, i.e. increasing overall efficiency
without major user complaints. The Committee confirmed the decision
taken during the 22nd Meeting. Nevertheless, the Committee authorized
CLS to grant waivers on a case by case basis if needed by the user
constraints.

Taking into account the projected launch delays associated with
increased Argos capacity on NOAA-I, J, K spacecraft and the expected
increase of the number of platforms in some critical areas, the O/C
authorized CLS to negotiate on a case by case basis with the users for
more efficient use of the system. This approach will remain compatible
with user needs in the framework of CLS\' performance management
responsibilities. (23rd O/C)

## Data Collection Platforms

### CERTIFICATION

### Certification Proposal 

The Joint Working Group presented their platform certification proposal,
after a number of changes and additions, Service Argos was directed to
publish the information.

### Platform Certification

NESDIS was not able to identify a company which would become a
certification laboratory and will not fund the establishment of such a
laboratory. Therefore, NESDIS will not certify platforms. Service Argos
will be the only organization that certifies platforms for use in the
system. (5th O/C)

### Certification Withdrawal 

In the event that a type or series of platforms does not work properly,
then:

1\) The O/C can withdraw the platform certification if the integrity of
the system operation is threatened.

2\) In order to improve the system, reports provided by the users will
be released for general information on the performance of different
platforms. (4th O/C)

### Certification Specifications

Certification specifications for equivalent isotropic radiated power
(EIRP) limits, etc., are contained in the certification specifications
for Argos Platform Transmitting Terminals. This document can be obtained
from Service ARGOS. (5th O/C)

## PROBLEMS

### INDIAN SPACECRAFT

#### Potential System Interference

The Indian Space Research Organization (ISRO) plans to develop a DCS
that will use frequencies at about the 401.5 MHz range. The use of these
frequencies might interfere with the Argos System - CNES will
investigate. (6th O/C)

#### Interference Determination

Additional information has been obtained and it appears that there will
no longer be any interference from ISRO in the 401.5 MHz band. (8th O/C)

### USER PROBLEM DOCUMENTATION

#### Operator and User Problems

The list of identified operator and user problems has been established
at Service Argos and will be continuously updated with responses, as
available, reported to the next O/C meeting. (19th O/C)

### PLATFORM COSTS

#### Oscillator Costs

NASA is supporting oceanographic research and buoy experiments. These
experiments have been data limited due to the lack of buoys and the lack
of buoys is directly related to the cost of buoys. Specifically; the
oscillator has been identified as a possible high cost item. NASA and
Service Argos will coordinate a series of tests to determine the range
of oscillator performance acceptable for use in the platforms that will
both insure system integrity and provide the required performance for
the users. (14th O/C)

## IDENTIFICATION CODES

### ISSUANCE & DURATION

It was agreed that all platform identification codes (ID\'S) would be
issued for a one-year period. Those ID\'s not in use at the end of the
year may be withdrawn after Service Argos notifies the user. (8th O/C)

### ELIMINATION PROCEDURE

#### Procedure Development

Service Argos will develop procedures (similar to the admission
procedures) to eliminate (from the Argos Processing System), user
platform transmitter terminal (PTT) ID\'s that are no longer used. (11th
O/C)

#### Procedure Implementation

Satisfactory procedures have been developed to eliminate from the Argos
Processing System those user PTT ID\'s that are no longer being used.
(12th O/C)

## REGISTRATION

### PROCEDURE & POLICY

#### Frequency Assignment

A new procedure for user PTT registration was reviewed. Since the main
purpose of the registration form currently used is to provide the
oscillator frequency of these PTT\'s that require location and new
software is being developed to compute this frequency automatically, it
was decided not to change the procedure. After the software is developed
and implemented, the registration form will no longer be used. (12th
O/C)

The new software has been developed and implemented that eliminates the
requirement to register the frequency of each PTT prior to deployment.
(13th O/C)

Following Action Item 32-2-C, CLS sent a letter to each transmitter
manufacturer, followed by visits in order to collect their
recommendations on implementing the move away from the Central
Frequency. The general attitude of all the manufacturers was
constructive and none were openly opposed to the assignment of
frequencies. A final meeting with all manufacturers is scheduled for
6-10 September in Largo, Maryland. Resulting from a study conducted in
conjunction with CNES for Argos-3, a proposal to optimize the
utilization of the frequency bandwidth allocated to Argos-2 as well as
to Argos-3 was presented. After discussion, this proposal was approved
by the Operations Committee and should be implemented in February 2000
after the launch of NOAA-L. (33^rd^ O/C)

The situation with the platforms operating in the Argos-1 frequency
bandwidth slightly improved over one year. The percentage of the total
number of platforms operating in the central channel (S11) decreased
from 65% to 60%. The activity of manufacturers were not very sucessful
except with the main French manufacturer which is supplying platforms to
CLS. This leads to the result that the action should be reoriented
toward the users by two means: financial incentive and allocation of
channel with id numbers and possible degradation. The US ROC and the JTA
chairman commented that a financial incentive could complicate the
tariff structure unnecessarily, but agreed that the idea had merit. The
meeting recommended that a proposal be prepared by CLS in cooperation
with the JTA chairman to be discussed at JTA 20 (34^th^ O/C)

Michel Cazenave reported that the situation with the platforms operating
in the Argos1 frequency bandwidth slightly improved over one year. The
percentage of the total number of platforms in the central channel
remains around 60 %. All along the year, comparative measurements were
realized by CLS to demonstrate the benefits of shifting the transmission
frequency that can be obtained by users as a function of power, message
length, number of locations required,...(35^th^ O/C)

M. Cazenave reviewed the evolution, along the past five years, of the
use of the ARGOS 1 -- ARGOS 2 bandwidth. It is going in the good
direction but it seems necessary --for the future- to organize the
bandwidth use with mandatory constraints. The OPSCOM recognizes the need
for more stringent framework to allocate frequency bands to ARGOS
beacons manufacturers. (36^th^ O/C)

Louis Mesnier of CLS reviewed the five year evolution of the use of the
Argos-1 and Argos-2 bandwidth. It was noted that still over 35% of
active platforms are clustered  in the central part of the Argos 1
frequency band (401,650 Khz +/- 2 Khz). CLS/SAI continued promotional
activities to educate users and ask manufacturers to voluntarily utilize
all of the available bandwidth. The OPSCOM recognized the need to more
encourage ARGOS beacon manufacturers to utilize the entire Argos
frequency band since now four Argos 2 instruments are now in flight.
Nevertheless, it seems that the assignment of frequency channels is not
optimal to better use the Argos 2 band and the meeting decided not to
take any coercitive decision as long as the situation continues to
improve. A recommendation should be added to the program review letters
sent to users to allocate username and password, together with the list
of ID numbers. (37^th^ O/C)

Louis Mesnier of CLS reviewed the five year evolution of the use of the
Argos-1 and Argos-2 bandwidth. It was noted that still over 30% of
active platforms are clustered  in the central part of the Argos 1
frequency band (401,650 Khz +/- 3 Khz). CLS/SAI continued promotional
activities to educate users and ask manufacturers to voluntarily utilize
all of the available bandwidth but it does not seem appropriate to
enforce the use of the entire Argos2 bandwith by allocating channels as
it was initially planned. The reason for most of users to not leave the
Argos1 band is that they can get more data from their platforms with
less throughput time as three Argos 1 flying instruments were still
transmitting real-time data until N11 was recently deactivated. As
proposed at the 37^th^ meeting, a recommendation will be added to the
program review, which is sent to users to allocate username and
password, together with the list of ID numbers (38^th^ O/C)

# User Services and System Use

## SYSTEM PROMOTION & PUBLICITY

### POLICY

During the 30^th^ O/C two main issues were raised :

1 Application Forms: CNES raised the following two issues concerning
consistency

the draft NASDA/CNES ADEOS-II MOU and the Argos Program Application,

A.  CNES discussed the issue of a NASDA reference to Argos Program
    Application as \"Argos Access Agreement.\" In order to clarify this
    ambiguity, the Operations Committee agreed that future additions of
    the Argos Program Application will include the following insert:
    \"UPON SIGNATURE BY ALL PARTIES THIS APPLICATION CONSTITUTES AN
    ACCESS AGREEMENT\". Although the NOAA-CNES Argos MOU does not use
    the term \"Access Agreement,\" Article 5.5.4 and Article 6 are
    interpreted to refer to \"Access Agreements.\"

B.  Another issue pertaining to the Argos Program Application raised
    during review of the ADEOS-II MOU relates to Intellectual Property
    Rights (IPR). The Operations Committee agreed to change the current
    wording of the Argos Program Application to change memorandum\" to
    \"document\" specifically \"Except for such provision as may be
    established elsewhere in this DOCUMENT, data collected for users may
    by made available by the Operator to other interested parties.\" C.
    Wooldridge (NOAA) noted it was necessary to distinguish between
    environmental data and processing techniques and value added
    activities when discussing IPR. In general, IPR does not apply to
    environmental or Earth observations data and consequently IPR cannot
    be claimed as a basis for requesting proprietary or confidential
    treatment of Argos data. Other national laws and regulations may
    apply to a request for confidential treatment of data itself such as
    the U.S. Freedom of Information Act. H. Wood (NOAA) noted the
    commitment to full and open dissemination of environmental data for
    meteorological forecast and research purposes adopted by
    international coordination groups such s the World Meteorological
    Organization and the Committee on Earth Observation Satellites.

2\. Commercial Use Policy: H. Wood (NOAA) discussed the status of
activities to respond to emerging commercial data collection and
location services which impact Argos system use policy. NOAA outlined a
number of transitional steps under consideration to address the issue of
the role of these new systems and NOAA and CNES responsibilities to
ensure continuity of environmental data collection and location
services. NOAA and CNES had agreed previously to assess and monitor
developments in their governments and in the commercial sector with
regard to user requirements and to factor these considerations into
future planning efforts. (30^th^ O/C)

Ms. Alvarez reported on the statue of the U.S. regulations which
implement the system use policy which was proposed by NOAA in March. The
new policy, as illustrated by the flow chart.

31^st^ O/C Exhibit #27 sets as a prerequisite in reviewing applications
for use that there be no commercial space based services available which
meet the users requirements in terms of satellite coverage, accuracy,
data throughput, platform, platform power consumption, size, weight,
service continuity and reliability, platform compatibility and, in the
case of Government agencies, cost-effectiveness. The new policy would
reaffirm that non-environmental use of the system is primarily
authorized for government users, for use in such applications as
humanitarian cargo tracking, or for national security purposes. Non
governmental use of the system would be curtailed and a prerequisite
that there be a government interest in the collection of the data has
been added. Moreover, only non-profit users would be allowed to use the
Argos System for non-environmental uses, except in cases where there is
a significant possibility for the loss of life. However at no time would
non environmental use of the system exceed five percent of the system\'s
total use.

Before the Operations Committee meeting, in early June, NOAA provided
CNES with a draft of these regulations. CNES sent their comments. These
comments were discussed here. Most relevant was the clarification from
previous discussions about the quantity of non-environmental use that
would be allowed. It was agreed that 5% of total system use would be the
maximum allowable amount as opposed to 2% of system capacity. This was
done because of the need to keep the prevailing use of the system as
environmental , so as not to lose access to the meteorological frequency
which is used by the system. (31^st^ O/C)

K. Alvarez presented a draft of the System Use Policy Statement for
adoption into the Argos Consolidated Report. After review of the
document and brief discussion, the Operations Committee adopted the
system use policy which is detailed in the document: "Policies and
Procedures Concerning Use of the Argos Data Collection System". This
document (32^nd^ O/C exhibit 22) will be incorporated into the
Consolidated Report. H. Wood commended and thanked the task team working
on this new system use policy for all their hard work over the past 2
years which made this possible. (32^nd^ O/C)

R. Bassett presented the current status in implementing the system use
policy enacted in July 1998. He stated that over the past year many
lessons have been learned in applying the new policy. He noted that most
of the cases requiring clarification were resolved through close
coordination with CLS which was greatly appreciated. There have been
some cases, however, where the current statement of policy was not as
clear as intended. A NOAA/CNES working Group was tasked with reviewing
the current policy statement to identify areas for clarification and
propose future revisions to the policy where appropriate. (33^rd^ O/C)

R. Bassett presented an overview of the administrative processing of the
Argos System Use Agreements (SUA). He stated that the user is advised by
the CLS/SAI Customer Service Departments to nominally allow six weeks
for the process and estimated that on average the processing time is
less, however, NOAA did not maintain any statistics on the end to end
process. In order to gauge the level of success in meeting this six-week
target, the OPSCOM requested an annual report on such statistics which
is available from the CLS/SAI Customer Service Departments. For NOAA's
administrative purposes, R. Bassett stated that the processing time
averaged two weeks, although a "Rush" SUA can be processed in a few
days. The OPSCOM noted that a two-week processing period for the OPSCOM
principals was reasonable in light of the manual handling of SUAs. The
OPSCOM requested an annual report on the number of SUAs not approved
each year to monitor the SUA review process. R. Bassett reported that
there is an ongoing effort to further streamline and improve the
timeliness of the SUA administrative process through "a priori" approval
and electronic submission. R. Bassett recommended that a redesign of the
SUA being reviewed by the SU Policy Clarification Working Group would
provide the opportunity for an electronic submission design. L. Mesnier
reported that the "a priori" approval agreed to at the 33^rd^ OPSCOM
meeting has been implemented for Bird Tracking applications that
resulted in a modest reduction in administrative processing. During this
first annual review of this "a priori" approval policy, the OPSCOM
agreed to expand "a priori" approval to all wildlife applications where
the user requirements for using the Argos System are low power
transmitters where there is no commercial space-based service that can
meet the user requirement.

R. Bassett reported the status of efforts to identify areas of the Argos
System Use Policy that may require clarification and outlined several
possible methods such as Frequently Asked Questions (FAQ), fact sheets
and revisions to the SUA. He identified several policy areas that appear
to require clarification such as proprietary data handling, hazardous
material monitoring and JTA membership. The OPSCOM endorsed preliminary
efforts to revise the SUA and directed the drafting of a fully revised
SUA by September 2000 for approval by the OPSCOM principals (34^th^ O/C)

Rob Bassett presented a report on the SUA processing statistics as
requested by OPSCOM 34. He reported that based on the SUAs received
since January 1, 2001, NOAA's processing time for SUAs (with complete
information) averaged 8 working days. Rob Bassett also stated that 25%
of the SUAs were delayed in processing due to missing or incomplete
information. He proposed that these delays could be significantly
reduced through the electronic submission and tracking of SUAs. As
requested at OPSCOM 34, the number of SUAs withdrawn and/or resubmitted
with modifications was approximately 1-2% of the total received. Rob
Bassett reported that there is Electronic Processing Initiative to
process the SUA that will begin in September 2001. The initiative is
driven by the U.S. Government Paperwork Elimination to be implemented by
2003. Rob Bassett stated that CNES/CLS participation is critical to the
success of the initiative. The OPSCOM directed that a plan be developed
for the implementation of electronic submission of SUAs. (Action Item
35-13-C/S). Louis Mesnier reported that the "a priori" approval agreed
to at OPSCOM 34 meeting has been implemented for all wildlife
applications that resulted in a reduction of 83 SUAs in administrative
processing. (35^th^ O/C)

R. Bassett presented three topics concerning System Use Administration.

-   NOAA's SUA processing statistics were discussed and it was noted
    that the average processing time was eight calendar days for SUA's
    with complete information.

-   The main reasons for pending SUA's was presented and NOAA offered to
    assist CLS / SAI in the implementation of some proposed solutions
    including the provision of "sample" SUA's and Frequently Asked
    Questions.

-   An update was provided of NOAA's SUA electronic processing
    initiative (35-13-C/S). NOAA thanked CLS for their assistance in
    supporting the initiative to date and estimated a completion date of
    September 2002.

D. Benner reported that NOAA and NACLS had discussions regarding
acceptable promotion practices for Argos DCS services. It was noted that
proposed changes in Code of Federal Regulations (15 CFR 911) to allow
increased use of Argos DCS for non-environmental and "sensitive use"
applications has not been finalized and should not be advertised until
completion. Acceptable practices include referencing only previously
published material, highlighting agency roles/partnerships and promoting
Argos processing and value-added services. (36^th^ O/C)

Chris O'Connors reported on the NOAA Argos SUA administration. He
submitted three draft user letters for approval by the OPSCOM. The user
letters serve as notification from CLS/SAI to the users of their
requirement to renew their SUA, 30 days prior to renewal, on the renewal
date and 30 days after renewal date. The letters were accepted by the
co-chairs. With the pending regulation changes opening the Argos system
up to more sensitive use users it's an appropriate time to coordinate
what information should be included and how users should be grouped in
the SUA process. NOAA reported the categories to separate users into for
sensitive as law enforcement, homeland security, national defense, and
humanitarian. (37^th^ O/C)

NOAA provided its SUA management statistics to the OPSCOM. Over the
course of the last year 244 SUA were processed with 39 held for pending.
The average processing time for an SUA with no questions was 5.4 days
down from 6 days in 2002-2003 and the average processing time for
pending SUA was 13 days. NOAA gave a review of the Chilean VMS situation
and proposed a possible compromise. Discussions were held off line about
the NOAA proposal with some agreement how to move forward. In summary
the NOAA proposal is to follow the Alaskan NMFS Model of a three year
SUA in which time to further resolve the remaining coordination issue on
transition. NOAA requested to review the sensitive use program at NACLS
and CLS to ensure missing information has been updated and answer any
remaining questions the agents may have. Argos SUA administration at
NOAA processed 244 System Use Agreements (SUA) with 39 SUAs held pending
for questions over the course of May 2003- May 2004. NOAA uses an
internal metrics of 14 days to process completed SUAs. For 2003 the SUAs
processing time averaged 5.4 days down from 6 days in 2002-2003, with a
decrease in the number of pending SUAs received for processing (15% from
28%). As of June 16^th^ 2004 there were 4 Pending SUAs not associated
with the review of Vessel Monitoring Systems usage and 7 SUAs for the
Fishing Vessel monitoring application. The Electronic processing system
contractor has continued to run into problems installing the development
system. During trails conducted in January and February of 2004 issues
where identified with the software coding compatibility with the
resident hardware and software. There were several issues with the
performance of the system that could not be overcome. The contract
funding ran out at the end of March 2004 with no delivered system. NOAA
negotiation with the contractor to resolve the issues remaining and
complete the instillation by the beginning of July 2004. NOAA is
submitting a procedure for implementing the user letters approved by the
OPSCOM. The user letters serve as notification from CLS/SAI to the users
of their requirement to renew their SUA, 30 days prior to renewal, on
the renewal date and 30 days after renewal date. The letters also
reference data denial for non compliant programs. NOAA is also
submitting a draft data denial policy for review of the OPSCOM. Both
documents have been shared with CLS/SAI with no comment generated. NOAA
requests an action to have the two documents reviewed before acceptance
in the Consolidated Report. In October 2003 NOAA work with NACLS on how
sensitive use applications need to be filed as was agreed at OPSCOM 37.
Some slight modifications were made from what was brief at last year's
OPSCOM. The Changes were made based on request of NACLS and its users.
Applications for sensitive use will be submitted in entirety to NACLS
and kept secure at their location. NACLS will provide a signed SUA with
the name of the program, contact, organization sponsoring the program, a
brief description of the activity, number of platforms, and program
start date. The type of sensitive use category would be listed under the
other file in Application type section of the SUA. This same procedure
was adopted for CLS. While review the sensitive use application at NACLS
it was discovered that a couple of applications had no record on file.
NOAA would like to request an action to review again NACLS programs have
completed SUA's on file. (38^th^ O/C)

#### Bilateral Agreement.

Either Service Argos or NESDIS will respond to inquiries regardless of
the source of the inquiry. To avoid duplication of effort, NESDIS will
provide copies of such correspondence to Service ARGOS. (3rd O/C)

#### Promotion

NOAA and NASA will help Service Argos in the promotion of the system by
recommending events where the presentation of the system could be useful
for potential users and participating in users conferences whenever
possible. (15th O/C)

#### FOI Requests for Argos User Information

The O/C discussed a request under the U.S. Freedom of Information Act
for access to information on Argos users. The U.S. Co-chair explained
that for the purposes of protecting confidentiality of non-JTA users,
NESDIS only requires information on the characteristics of applications.
An agent could present this information in place of the end user. All
applications covered by the JTA will be forwarded to NOAA for approval
as filed. (24th O/C)

### RELEASE OF TECHNICAL INFORMATION

#### CNES Position

CNES is concerned about the release of system technical information to
other than French or U.S. citizens and will present a position paper on
this point at the next meeting. (9th O/C)

#### Distribution

NASA and NOAA will review the CNES proposal to limit the distribution of
system technical information to non-U.S. or non-French requesters. (10th
O/C)

#### Position of CNES, NASA, & NOAA.

It was agreed by CNES, NASA, and NOAA that, in regards to the release of
detailed Argos System technical information to non-U.S. or non-French
requesters, U.S. participants in the Argos program will not release
technical information about the French portions of the system to
non-U.S. or French requesters without the approval of CNES. CNES is
expected to adopt a similar practice with respect to information about
the U.S. portions of the system. (11th O/C)

##### Policy Dissemination:

Both the U.S. and French agencies have distributed letters outlining
this policy to the appropriate manufacturers and organizations of the
Argos system. (12th O/C)

### ARGOS NEWSLETTER

#### Argos Newsletter

It was decided that information concerning certified manufacturers of
PTT\'s be included in the Argos Newsletter. (4th O/C )

#### Information & Content

An Argos Newsletter will be published periodically by the Coordination
Center (Service Argos). It will inform the users on:

1\) Design Status

2\) Operational Status

3\) System performance

4\) List of Manufacturers of Certified Platforms

5\) Results of Users Experience with the System (4th O/C)

#### Platform Certification Information

The newsletter section on platform certification should include the name
and address of PTT manufacturers and the model numbers that have been
certified. Also, that certification information can be obtained from
Service ARGOS. (7th O/C)

### MONTHLY REPORTS

#### Service Argos Monthly Reports

It was recommended that information concerning PTT improvement be
included in the Service Argos monthly reports. PTT improvements would
include improved oscillators, more powerful micro-processors, and other
PTT technological improvements. (12th O/C)

#### Active Platforms

It was agreed that Service Argos would make a monthly report containing
the number of active platforms on a weekly basis and forward this to
NESDIS. (9th O/C)

### CONFERENCES AND WORKSHOPS

#### Workshop Agenda

The O/C agreed to arrange a workshop in order to exchange information on
the system and to identify user\'s needs. Users, potential users, and
system technical experts will be invited. Service Argos will organize
the workshop with the assistance of NESDIS. The meeting will be
scheduled to take place either just before or after the next O/C in the
U.S. The agenda will include the following:

[First Day]{.underline} Presentation to the Users (Opening Session)

\- Spacecraft

\- On-board DCS

\- Ground Data Processing

\- Platform Certification

\- Admission to the System

\- Delivery of Data

[Second Day]{.underline} Presentation by the Users or potential users of
their programs

\- Open session during the afternoon for completion of detailed
discussions (4th O/C)

#### Workshop Guidance

It was agreed that the guidance provided at the 4th O/C meeting
pertaining to the user\'s workshop or conference is still valid and
should be used as a guide for all user\'s conferences. Minor variations
to the proposed agenda will be necessary from time-to-time and Service
Argos will have the authority to make these changes. However, major
changes to the guidance should be reviewed by the O/C prior to
implementation. (15th O/C)

#### Regional User Seminar:

CLS/Service Argos participated in a variety of conferences and other
promotional meetings during the year. These included a series of
Regional User Seminars designed to better educate users and provide an
effective mechanism for user feedback. (28th O/C)

## APPLICATION FOR SYSTEM USE

### ADMISSION CATEGORIES

#### Priority 1

Admissions will be provided without limitations.

#### Priority 2 and 3

Service Argos will reserve the right to review and terminate the
agreement in the event of system saturation. (4th O/C)

#### Platform Engineering Test

A new admission category has been created called \"Platform Engineering
test.\" All platform identification codes (ID\'s) assigned under this
category are to be used only by the platform manufacturer for
engineering tests and for no other purposes. Eight ID\'s per
manufacturer will cover all possible sensor combinations. Service Argos
will include in any such agreements with platform manufacturers a
provision that the manufacturers must remove the engineering test ID
from all platforms prior to delivering the platforms to the customer.
(10th O/C)

### ADMISSION POLICIES

#### Eligibility

To expedite decision making on the eligibility of a potential user for
entry into the Argos System, it was agreed that:

1\) If a question of eligibility arose, Service Argos would address a
request for determination to the Co-chairs of the O/C.

2\) If the Co-chairs disagreed, they would refer the matter to higher
authority in their respective organizations. (3rd O/C)

#### FGGE Programs

The O/C gave blanket approval for all FGGE programs. (4th O/C)

#### Development programs.

A development program may be considered an environmental platform if it
is intended to develop a future environmental measurement capability and
if the platform transmits at least one environmental measurement. (5th
O/C)

#### Exceptions

A program that results in the O/C having little or no control over the
individual program admissions will not be accepted unless, when each
individual program is proposed, the O/C will review and approve or
disapprove the program as the case may be. For those programs approved,
the MOA must have the ultimate user\'s signature. (7th O/C)

#### North American Applications

A new processing procedure for North American applications has been
proposed. The new procedures will expedite the processing of these
applications and will utilize the U.S. Argos representatives office to
coordinate the processing in the U.S. Formerly, the U.S. Executive
Secretary received the courtesy copy of U.S. applications but had to
wait for the formal application to be mailed from France before
processing the application. Now the courtesy copy will be forwarded
directly to the U.S. Argos representative and processing will commence
immediately. (18th O/C)

#### Programs Not Clearly Defined

Even if a program is approved by the O/C, the technical program review
by Service Argos can indicate that access must be denied due to a lack
of technical information required to determine the compatibility with
the system. (8th O/C)

#### Wildlife Tracking Programs

Since the current Radio Communication Handbook does not authorize Earth
exploration and animal tracking for the 1700-1710 MHz band, France will
propose to the 1979 World Administrative Radio Conference to modify the
appropriate foot notes of the rules to include the use of these
frequencies for Earth exploration and animal tracking. (8th O/C)

##### Tracking Frequencies:

The frequencies used by the Argos System have been approved to support
the entire file of Earth exploration, which includes animal tracking.
Wildlife tracking programs may be accepted in the Argos System using
normal application procedures and assigned standard operational
categories. Service Argos will notify those organizations who had
previously asked to use the system for wildlife programs of this new
policy. (11th O/C), (14th O/C)

#### Fishing Vessels.

The program concerning the surveillance of fishing vessel s in Nigerian
Sea has not been approved. The U.S. Co-chair found that the application
is not consistent with the principle governing use of the system which
was designed for collection of only environmental data. However, the O/C
recognizes that location information obtained during transmission of
environmental data may be used for various purposes which are beyond the
purview of the Committee. The applicant must assure the O/C that their
application does meet the requirements for acquiring environmental data.
(16th O/C)

#### Non-environmental Programs

As a result of actions from the 23rd Argos O/C Meeting, a joint NOAA
CNES Working Group met on several occasions to propose a set of terms
and conditions for the implementation of a 5% non-environmental use of
the Argos System. At the 24th Argos O/C Meeting the U.S. and French
Co-chairs signed the terms and conditions for implementation of the 5%
Non-Environmental Use Proposal. (24th O/C)

It was agreed that it is necessary to closely monitor the impact of
these programs on a local-area and global aspect. CLS will submit a
quarterly report to show the status of non-environmental programs. NOAA
will work with CLS to define the report format. The purpose is to
demonstrate that a reasonable effort is being initiated to monitor
system use to ensure compliance to the terms and conditions for
non-environmental use as established by the O/C Co-chairs at its 24th
session. (26th O/C)

In October 2003 NOAA work with NACLS on how sensitive use applications
need to be filed as was agreed at OPSCOM 37. Some slight modifications
were made from what was brief at last year's OPSCOM. The Changes were
made based on request of NACLS and its users. Applications for sensitive
use will be submitted in entirety to NACLS and kept secure at their
location. NACLS will provide a signed SUA with the name of the program,
contact, organization sponsoring the program, a brief description of the
activity, number of platforms, and program start date. The type of
sensitive use category would be listed under the other file in
Application type section of the SUA. This same procedure was adopted for
CLS. While review the sensitive use application at NACLS it was
discovered that a couple of applications had no record on file. NOAA
would like to request an action to review again NACLS programs have
completed SUA's on file.(38th O/C)

NOAA has coordinated the expansion of non environmental applications
with the NTIA and has come to an agreement on the definition of de
minimis use. The 5% system use cap on non environmental applications has
been redefined as 5% system capacity measured in Erlangs. The OPSCOM
co-chairs were briefed on the success of the coordination at the March
2005 intercessional. In order to manage the new agreed on 5% cap a
change in the OPSCOM Terms of Reference is required. The TOR provides
the OPSCOM greater flexibility in managing its non environmental use as
well as greater responsibility. Therefore NOAA recommends editing
Section 2.2.2 Objectives of the Operations Committee to add the
following: "to review and ensure reports of non-environmental use of
spare capacity does not exceed the de minimis value of 5% of the system
capacity or interfere with environmental use of the system. System
capacity is defined in the paper "The Case for a 5% of Argos System
capacity limits on non environmental applications**"**. (39th O/C)

### GOVERNMENT SPONSOR LIST

Potential private users need to have a list of U.S. and French
government agencies they may contact to determine whether there is a
need for all or a portion of their data. These agencies would act as a
sponsor for the private user in order for the private user to use the
system. A combined list has been compiled and is available for
distribution to future users. These lists are to be expanded in the
future as a routine procedure. (17th O/C)

(Note: Discussions at various subsequent meetings resulted in the
elimination of the sponsorship list)

### RENEWAL OF PROGRAMS

The following restrictions are considered to be necessary for
considering a program for automatic renewal by Service ARGOS:

1\) Must insure that the program has not changed.

2\) Must inform the Co-chairs of all extensions.

3\) Cannot renew experimental programs not involving environmental data.

4\) Must require that experimenters, which have restrictions in their
prior program approval, to submit a new application form for approval by
the Co-chairs. (13th O/C)

### USERS MEMORANDUM OF AGREEMENT

#### Signatories

It was agreed that the signatories of a Memorandum of Agreement (MOA)
would be the user and Service Argos. Agreement for Service Argos to
enter into the MOA must be given by the O/C. (3rd O/C)

### ACCESS PROCEDURE

#### Procedure Format.

The procedures should use the following format:

A. Program Application and Approval

1\) Contact Questionnaire provides:

\(a\) Name of the program

\(b\) Description of the program

\(c\) Name of the principle person

2\) Program approval by O/C Co-chairs

B. Technical Preparation

1\) Platform Certification

2\) Identification of the platform

3\) Data processing selection

C. Agreements

1\) Memorandum of Agreement

2\) Contracts for data processing (if any) (7th O/C)

### NEW ADMISSION PROCEDURE

The O/C agreed to the proposed procedure as it will reduce the number of
documents and save time. Service Argos will prepare a single document
which includes the information presently contained in the MOA and the
application form. This new document will be signed by the user and
Service Argos. (12th O/C)

The Operations Committee approved the concept of separating the current
application form into two parts: a \"System Use Agreement\" and a
\"Program Description\". The System Use Agreement will be signed by the
user as well as NOAA and CNES upon approval. This will be the formal
agreement for use of the system. The Program Description will be a
detailed questionnaire with the information needed by CNES/CLS for
management of the Argos System. (31^st^ O/C)

K. Alvarez presented the new System Use Agreement (SUA) which was
drafted with CLS. The new form will implement the new system use policy
that has now been adopted by the Operations Committee. The Operations
Committee adopted the new form, which will be used from this day forward
for all new and renewing users. (32^nd^ O/C)

L. Mesnier reported on the implementation of the Argos User Agreement
data base. The data base will be implemented in the first phase of the
Argos 2001 project and all the fields requested by NOAA in February 1999
are taken into account.

A breakdown of current programs by applications and categories was
presented. To reduce significantly the administrative burden, the "a
priori" approval should concern the Environmental / Governmental
category. It was suggested that all "Earth Sciences" programs in this
category be eligible for a priori approval. The Operations Committee did
not agree to this proposal but accepted that specific cases such as
"birds" or "high latitude" platforms might be eligible. It was recalled
that the global objective of this action was to streamline the SUA
process and the use of electronic in exchanging information should be
more efficient.

1\. The Operations Committee agreed that all partners have full access
to the Argos SUA data base to meet their management oversight and
reporting requirements.

2\. The Operations Committee agreed to "a priori" approval of wildlife
applications where the user requirements for using the Argos System are
low power transmitters, (e.g. Bird Tracking) where there is no
commercial space-based service that can meet the user requirement

3\. The Operations Committee stated a commitment to improve the
timeliness of the SUA administrative process. (33^rd^ O/C)

Louis Mesnier presented the situation concerning the SUA implementation.
Out of the 372 programs approved between April 2000 and April 2001, less
than 25% were A priori approved (wildlife with low power) while 57% of
them were renewals. Since the last O/C meeting, two mailings were sent
to users requesting the renewal of their expired SUAs. The last mailing
sent in March 2001 concerned mainly SUAs which were approved within the
last 3 years and users seem rather reluctant to renew by themselves. The
process time of SUAs is one month on average including the time spent in
CLS and NOAA/CNES to approve and this time should be reduced. One reason
of the delay is frequently missing information in the form and
misunderstanding by users concerning user requirements. Possible
improvements / solutions to be explored were presented, namely : to
extend "a priori" approval to E/G category when user requirements are
"low power " and/or "global coverage" , to approve for the longest
authorized duration (1 year / 3 years), to review SUA form and open SUA
web site as soon as possible, to request renewal by email with no hand
written document. The OPSCOM agreed to extend a priori approval to low
power transmitters operated in high latitudes above 60 degrees of
latitude, for E/G applications in addition to all E/G wildlife
applications where the user requirements for using the Argos are low
power transmitters that was approved by OPSCOM 34~~.~~ The OPSCOM also
agreed to approve SUAs for the longest duration of use allowed under the
System Use Policy. Rob Bassett presented a revised form for the SUA
(Action Item 33-7-C/S), including improvements that provide the
opportunity for an electronic submission. The revisions were discussed
and adopted with minor changes by the OPSCOM. The OPSCOM also reviewed
section 5 (Treatment of Data) of the System Use Policy and clarified the
application of the policy. Action 35-15-C/S was assigned to prepare the
revised SUA for final OPSCOM approval at an intersessional meeting. The
OPSCOM expressed concern that there continues to be a problem in the
timely renewal of SUAs and took an action item to develop a standard
operating procedure and timetable. The OPSCOM acknowledged that a
simplified renewal form that could be sent electronically (i.e. email)
may facilitate the renewal process. NOAA and CLS were encouraged to
include such a form as they develop electronic forms and tracking
systems. CLS confirmed that the SUA web-site will be operational by the
end of year 2001. (35^th^ O/C)

The SUA and policy modified as approved by OC 35 was reviewed. Some
additional minor modifications were discussed, approved and will be
implemented by CLS immediately. SUA expiration date to be added to the
program review sent back to users. The action plan for SUA renewal was
presented and approved by OC 36. An update on the SUA policy
modifications was presented with an estimated completion in October
2002. R. Bassett noted that a breakdown of Argos usage in the categories
of the proposed policy modifications would support this effort. A new
SUA form was presented by R. Bassett and L. Mesnier. The form includes
all the changes which were discussed at OC 35 plus some minor
improvements which were added during the inter session period. The new
form was submitted to the meeting for approval and will be used in both
paper and electronic form. The a priori approvals which were extended to
programs operating platforms at high latitude (\>60°) or requesting low
power transmitters (\<1 watt) represent now 40% of the approvals.
Concerning the validity status of SUAs, Louis Mesnier presented a
report. The requests for renewal are sent by email and 290 requests were
sent out since the last meeting. Nevertheless, presently approximately
15% of the SUAs still have to be renewed and only 40% of users renew
after the 1^st^ notification which confirms the need to implement a more
efficient renewal procedure (see action item 35-3-C/S). The web site
which should be operational together with the Argos 2001 data
distribution system should help to improve this situation. (36^th^ O/C)

Rob Bassett of NOAA presented the following topics for discussion.

a\) He stated that modifications to the SUA approved by OC 35 (SUA
"electronic" format and modification of "treatment of data" policy) have
been implemented.

b)  Additional SUA modifications, however, will be necessary to: respond
    to a JTA request for clarification of the financial liability of the
    user, to reflect recent SU policy changes i.e. Sensitive Use, and to
    reflect the addition of the Japan Aerospace Exploration Agency
    (JAXA) as an Argos Participating Agency. (37^th^ O/C)

C. O'Connors provided an update to the electronic SUA development at
NOAA. Installation of the system is schedule for this week (June 30^th^
--July 2^nd^ 2004) with acceptance testing in the beginning weeks of
July. An updated version of the Electronic SUA Procedure (see exhibit \#
32) at NOAA was submitted in the working papers. NOAA requested an
action to have the SUA renewal letter procedure and the Data Access
Policy reviewed by CNES/CLS. The electronic SUA process is intended to
reduce the paper and latency of the approval process. It allows for
flexibility in the management of SUAs and a secure transfer route
between the Argos user offices and NOAA. This policy can be change and
adjusted as the implementation and system development continues and
working procedures mature. Louis Mesnier made a short presentation of
the modifications proposed for the SUA form. They mainly concern the new
definitions and changes in the system use policy, which were adopted in
the previous meeting. This new form will be made available to users from
now, mainly on Argos websites. (38^th^ O/C)

### PROGRAMS USING DIRECT READOUT STATIONS

Service Argos proposed a special MOA for these programs. The O/C felt
that this might not be necessary since there would be no problems in
programs using direct readout stations to obtain their data as long as
all platforms adhere to the normal rules for entry and operation. (8th
O/C)

### CHANGING PLATFORM USE WITHOUT NOTIFICATION

#### Control of Offending Users

There are three approaches that can be used to control offenders who
have changed their use of platforms without notification:

1\) Frequency control through the appropriate communications authority
in the U.S., France, and other countries.

2\) WMO to apply pressure on an offending WMO member.

3\) The U.S. STATE DEPARTMENT and/or the French MINISTERE DES AFFAIRS
ENTRAGERES may apply diplomatic pressure on the offender\'s country.
(10th O/C)

#### NOAA Legal Position

The NOAA Legal Office agrees with the above methods. (11th O/C)

### SUA Renewal Letter and Data Denial Policy

NOAA is submitting a procedure for implementing the user letters
approved by the OPSCOM. The user letters serve as notification from
CLS/SAI to the users of their requirement to renew their SUA, 30 days
prior to renewal, on the renewal date and 30 days after renewal date.
The letters also reference data denial for non compliant programs. NOAA
is also submitting a draft data denial policy for review of the OPSCOM.
Both documents have been shared with CLS/SAI with no comment generated.
NOAA requests an action to have the two documents reviewed before
acceptance in the Consolidated Report. (38th O/C)

Service Argos Inc. provided an alternative plan of action at the March
2005 Intercessional meeting for using User letters and Data denial
policy. SAI proposed to reduce the user letter process from three
letters to one and eliminate the data denial options altogether. SAI
feels the renewal process is much improved and the numbers of
applications that fail to renew in the timely manner are minimal. OPSCOM
Co-chairs agreed to amend the O/C 38 accepted plan based on SAI/CLS's
request with one requirement. SAI/CLS will need to report at the OPSCOM
the numbers of unresolved renewals. The OPSCOM will use this information
to ensure there is a minimal amount of active programs with expired
SUAs. (39th O/C)

### USER INTERFACE

#### Direct Readout Facilities

Local User Terminals or Direct Readout Facilities that measure time,
relate time to ephemeris data, and then use it to determine location,
require support. Service Argos will handle this support unless the
number of Direct Readout Facilities with these time platforms becomes
too numerous and saturate the system. (7th O/C)

#### GMT and DCS On-Board Clock Correlation

The O/C has requested Service Argos to determine the best method to
provide time correlation information between GMT and the DCS on-board
clock for users that require this information. (10th O/C)

##### Correlation Procedure:

When a request for time correlation between GMT and the DCS clock is
received by Service ARGOS, a telex response is prepared. This procedure
will be possible for as long as the number of these requests is small.
(11th C/C)

### USER GUIDANCE OFFICE

#### User Inquiry

The O/C requested that Service Argos obtain the opinion of the users on
the value of the Users Guidance Office. (13th O/C)

#### User Questionnaire Response

The initial questionnaire distributed by Service Argos was sent
primarily to program managers and not technicians resulting in the
responses being inconclusive. Another inquiry will be sent to a larger
number of users. (14th O/C)

#### Determination

It was determined that the User Guidance Office is providing a useful
function and should be maintained. (15th O/C)

## Electronic SUA submission Process

### Electronic SUA structure (Submitted 37th O/C)

The Argos SUA Database System provides a web based capability for
tracking pending SUAs and providing a workflow for editing, approving
(or dis-approving) SUAs. This system involves a mix of web pages,
underlying database access, and background Windows NT processes to
monitor/process emails in support of the system. The central structural
element of the AS System is the database, which contains SUA details,
and supporting tables used for supporting operations such as
configuration, logging and the generation of reports and management of
registered users and recipients of email notifications.

### System Operation

The system will import electronic agreements in XML format as e-mail
attachments. The e-mails will be sent from CLS/SAI
<argos-sua-manager@cls.fr> to a set NOAA address <argosua@noaa.gov>.
Agreements will be received on the e-mail router on the SUA system. The
attachments will be picked up by the front end and processes to an SQL
data base. The front end will place a new record on the main web
interface for public viewing. SUAs received will be posted on public web
page with the following information, a unique CLS/SAI data base
reference number, date the application was received, and status of the
approval process. The displayed information is purposely generic to
minimize confidentiality concerns for the users and the agent. The
received date and reference number will not change once they are set.
The status section will update as the SUA move through the approval
process. The status section may read under review N of N+1, where N can
be 1-4 and N+1 can be 2-5. There is a maximum of 5 levels of review in
the system. It is not anticipated that all five levels will be
necessary.

### Assigned Approvers

Level 1 Argos Management Team member -- Initial check in and review on
content

Level 2 Argos Program Manager -- Policy/Regulation review of all SUAs

Level 3 DSD Chief -- review of normal environmental SUAs

Level 4 OSDPD Director - Final Decision level for all SUAs

Level 5 unassigned

Super User Argos Program Manager -- system administration and account
management

### Review Strategies

There are two basic review strategies that will be employed in the
review process. First is the normal review for government environmental
agreements that are initials or renewals and non government
environmental applications with clear program descriptions of government
interest and system use. In these cases the agreements will be sent
through three levels of review for approval. The second strategy is
higher level of review, which covers sensitive use application and uses
that require additional review such as fishing vessel monitoring. In
these cases the SUA will be assigned 4 levels of review and signed by
the OSDPD Director. OSDPD Director will reserve the right to delegate
his authority to sign SUAs.

### Processing Steps

Once an SUA enters the system the following steps will be followed in
the electronic approval process.

1.  Level 1 approver reviews the initial SUA information to ensure the
    application is complete. A valid e-mail address is required to
    replace the user's signature and shows the user understands their
    responsibility under the Global System Use Policy.

2.  Level 1 approver sets the number approval levels

3.  Level 1 approver assigns a recommendation for the agreement, either
    approved, disapprove, pending, or purged to DSD Coordinator. There
    is a comment section to capture pertinent information about the
    recommendation that can be viewed internally in the approval
    process.

4.  The public web site will show an update for the SUA under review
    based on the recommended action taken by the level 1 approver. If
    recommended for approval or disapproval the status will read at
    level 1 of N, where N is the number of level set by the level one
    approver. Regardless of the level 1 recommendation the final
    approval or disapproval will come from the level 3 or level 4
    reviewer.

5.  If questions or information are required the level 1 approver will
    select pending and generate an e-mail to CLS/CLS America and the
    displayed status will update to pending.

6.  If an SUA is withdrawn or resubmitted by the agent CLS/SAI the old
    or withdrawn agreement will be purged to DSD Coordinator for removal
    from the system.

7.  An e-mail is generated to notify the next appropriate reviewer that
    a new SUA is available.

8.  In a 2 level review process the Argos Program Manager approver would
    review the recommendation and comments of the level 1 approver and
    make one of the following options, Approve, disapprove, pending,
    increase the levels of review, or purged to the DSD coordinator. The
    level2 reviewer will then provide a recommendation and comments for
    the level 3 approver.

9.  The level 3 approver will be the final approver unless the SUA calls
    OSDPD level review. The level 3 approver will review the comments
    and recommendations of the first two levels and then make a
    decision.

10. If a level 4 review is necessary then they will follow a similar
    review as step 9 and make the final determination.

11. When an SUA is given the final approval or disapproval an e-mail
    will be generate to the OPSCOM chairs, CLS and CLS America to notify
    the interested parties the review process is complete. The public
    web site will also display the final status of the SUA. The e-mail
    will contain an updated SUA with the approval field populated with
    the approver's name, and e-mail, and date of completion, length of
    time, and comments. Once and SUA is complete the system will not
    allow edits and changes to the SUA fields.

12. The DSD coordinator will function as an administrator and has the
    ability to make recommendations at any level in the process plus
    purge SUA from the database. The coordinator can not move SUA
    backwards in the process only forward. In case of a reviewer absents
    the coordinator can step in to allow the review process continue and
    minimize any process delays.

### Summary

The electronic SUA process is intended to reduce the paper and latency
of the approval process. It allows for flexibility in the management of
SUAs and a secure transfer route between the Argos user offices and
NOAA. This policy can be change and adjusted as the implementation and
system development continues and working procedures mature.

### Electronic SUA Implementation

The Electronic processing system contractor has continued to run into
problems installing the development system. During trails conducted in
January and February of 2004 issues where identified with the software
coding compatibility with the resident hardware and software. There were
several issues with the performance of the system that could not be
overcome. The contract funding ran out at the end of March 2004 with no
delivered system. NOAA negotiation with the contractor to resolve the
issues remaining and complete the instillation by the beginning of July
2004. (38th O/C)

The NOAA Electronic SUA system is Operational as of April 1^st^ 2005.
Since April the system has successfully ingested 30 SUAs. The approval
e-mail is incomplete but otherwise the system is operating as intended.
(39th O/C)

## SYSTEM USE

### Initial System Activity

During the first weeks of Argos System checkout on TIROS-N, about 250
platforms were received. (8th O/C)

### Operational Activity

A slight increase in the number of active DCP\'s is noted. As of October
1, 1981, 2000 individual platforms have been received and processed in
the Argos Processing Center since the start of the operation in 1978.
(14th O/C)

The maximum occupancy of the system was approximately 63% in March 1992.
It is expected that PTT growth projections will be accommodated by an
increase in the data rate beginning with NOAA I, and a doubling of the
onboard Data Record Units beginning with NOAA K. In spite of the
increasing number of platforms, Argos system utilization rate is not
projected to be a problem.

The number of active platforms transmitting daily increased from 2194 to
2373 since the 27th O/C Meeting. The number of platforms whose data were
sent through the GTS increased regularly in the same proportion as the
buoys (from 625 to 704). (28th O/C)

The daily average number of active platforms remained between 2250 and
2400 for the period April 1994 to April 1995. Data from 650 to 700
platforms were distributed over the GTS during the same period. Due to
increasingly efficient use of the system by the users, the difference
between the numbers of active platforms seen daily and those seen
monthly continues to grow. The highest level of occupancy is in the
Northeastern United States and the North Sea area of Europe. (29th O/C)

The daily average number of active platforms increased from 2400 to 2700
since the last Operations Committee Meeting. The data from 931 platforms
are sent on the GTS (671 in June 1995). The difference between the
number of active platforms seen daily and those seen at least once per
month continues to grow. The highest level of occupancy still remains in
the North Sea area. (30^th^ O/C)

The daily average number of active platforms increased slightly from
2734 in April 1996 to 2814 in April 1997 (3%). But during the same
period of time, the number of active platforms seen at least once in a
month continued to increase at an higher rate (6%) and it is now far
above 5000. The data from about 850 platforms are sent onto the GTS.
Concerning the type of platforms in the system, about half of them are
drifting buoys. Under this category, we count \"floats\", which are
subsurface drifters, coming up randomly to transmit data. There are now
more than 600 active floats seen each month. The highest lever of
occupancy is now centered in the North Atlantic Ocean and represents
about 75% of the Argos 1 equipment capacity. (31^st^ O/C)

L. Mesnier reported that the daily average number of active platforms
increased significantly from 2814 in April 1997 to 3264 by April 1998
(16%). During the same period, the number of platforms seen at least
once a month went over 6000 by mid-1997. The data from about 700
platforms are sent onto the GTS. Concerning the type of platforms in the
system, about half of them are buoys, either drifting or moored. Animals
represent 10% of the active platforms. Concerning the category
"miscellaneous," which increased dramatically over the last three years,
it includes mobiles of any type including hazardous goods
transportation. Concerning the geographical distribution of platforms,
the highest level of occupancy is over the North Atlantic Ocean and
represented 85% of the Argos-1 equipment capacity by mid-May. At the
same time, the worldwide average system duty coefficient was only 21.7%
of this capacity. Recently, the average load measured on a 12-hour
period for NOAA 15 represented about 8% of the Argos-2 equipment
capacity. This confirms that the new equipment provides roughly 3 times
the Argos-1 capacity. The references for calculation of the system duty
coefficient will be reviewed accordingly when NOAA-15 will become the
primary AM satellite. (32^nd^ O/C)

L. Mesnier reported that the number of platforms, i.e. the number of
transmitting platforms seen daily, then averaged over one month,
continued to increase significantly from 3264 in April 1998 to 3858 in
April 1999 (+18%). A significant part of the increase concerns fishing
vessel monitoring. During the same period, the number of platforms seen
at least once in a month approached 7000. The data from more than 750
platforms are sent onto the GTS and "Drifters on GTS" represents about
60% of the drifting buoys category. Animal tracking platforms represents
only 11% of the total number while this application concerns more than
30% of the current programs in the system but most of these platforms
are not transmitting continuously. A "Mobiles" category appears now in
the table and curves and it gathers any type of Mobiles not belonging to
other categories. Concerning the geographical distribution of platforms,
the major change is that the highest level of occupancy is no more over
the North Atlantic ocean but along the West Coast of South America. This
is due to the concentration of monitored fishing vessels in that area.
The highest level was still about 85% of the Argos-1 instrument capacity
in April 1999. At the same time, the worldwide averaged system duty
coefficient was at 23%.

Finally, it was decided that the references for calculation of the
system duty coefficient will be reviewed only when NOAA-16 will become
operational. The worldwide distribution of all platforms continues to
show high concentrations at rather low latitudes. (33^rd^ O/C)

M. Taillade reported that the number of transmitting platforms seen
daily increased by 7% over the year (4121 compared to 3858). During the
same period the number of active platforms, i.e seen at least once in
a month, went over 7500. The most important type of platforms in the
system is still drifting buoys with more than 1400, out of them 900
being transmitted onto the GTS. The global system occupation rate is
increasing regularly and is now around 25%, based on the Argos-1
theoretical capacity and reaches a maximum of 85% in Europe and South
America. More than 15,000 different transmitters were received and
processed last year in the Argos processing centers (34^th^ O/C)

Louis Mesnier reported that the number of transmitting platforms seen
daily increased by 6% over the year (4369 compared to 4121). During the
same period the number of active platforms, i.e seen at least once in
a month went over 8500 then back under 8000. The most important type of
platforms in the system is still drifting buoys with about 1400 seen
daily, out of them 800 being transmitted onto the GTS. The meeting
expressed its concern as the number of PTTs transmitted onto the GTS has
decreased since last year. The US co-chair~~man~~ requested that a
specific report concerning the GTS transmission be presented at future
O/C meetings (See action item 35-7-C). The number of wildlife and
fishing platforms in the system continue to grow.The global system
occupation rate is increasing regularly and is now around 30% on
average, based on the Argos 1 capacity. Now the system use calculation
is based on the Argos2 capacity, which is more than 3 times the Argos 1.
The system occupation rate is then around 9% and reaches a maximum of
35% in Europe and South America. More than 15,000 different transmitters
were received and processed last year in the Argos processing centers.
(35^th^ O/C)

Louis Mesnier reported that the number of transmitting platforms seen
daily increased by 13.6% over the year: 4962 in April 2002 compared with
4369 in April 2001. During the same period the number of active
platforms, i.e seen at least once in a month went over 9000 then back
under 8000. The most numerous type of platforms operating in the system
is now fishing vessel monitoring platforms with more than 1500.
Operating means seen daily and averaged over on month. The second type
in number is then the drifting buoys with more than 1400 including the
subsurface drifters and out of them 700 are transmitting onto the GTS
(see below). The number of wildlife and fishing platforms in the system
continue to grow faster than other types. The global system occupation
rate is increasing regularly and is now around 9.5 % of the Argos 2
instrument capacity. It reaches a maximum at more than 40 % in South
America due to important Argos activity in Peru and Brazil. It is around
30 % in Europe and North America. More than 16,000 different id numbers
transmitters were received and processed last year by the Argos
processing centers. B. Woodward of SAI reported on action item 35-7-C in
that concern was expressed at OC 35 regarding the apparent low
percentage of drifting buoy data inserted onto the GTS by certain
countries, and the possibility that certain countries were withholding
data for confidentiality reasons. Consequently, CLS/Argos was asked to
investigate this situation, to explore the possibility of routinely
providing GTS buoy data statistics by country and to report on this
effort at OC 36. Substantial assistance to this effort was provided by
Etienne Charpentier, the DBCP Technical Coordinator. The main
conclusions from this investigation are:

-   the number of drifting buoys reporting through Argos has increased
    substantially since 1991 with some variability during that time;

-   the percentage of these buoys reporting their data onto the GTS has
    in general increased during this time period;

-   recent temporary decreases in numbers of operational drifting buoys
    were due to several short-term buoy deployments ( e.g., YOTO, GDP
    for EPIC);

-   corrections to the DBCP data base were made to ensure only drifting
    buoys and their data were represented;

-   "Confidentiality is really not an issue anymore although there might
    be a few small instances from time to time." The desired buoy and
    GTS statistics are routinely available on the DBCP web site.

O/C co-chairs indicated continued strong support to put platform data on
GTS in accordance with Argos System Use policy. (36^th^ O/C)

Louis Mesnier of CLS reported that the number of "operational"
platforms, i.e. transmitting once daily and averaged over one month,
increased by 8.7% over the past year. It was noted that 5393 operational
platforms reported in April 2002 compared with 4962 platforms in April
2001. During the same period, the number of "active" platforms, i.e.
transmitting at least once in a month, exceeded 9000 to reach 10,000
during May 2003. The 1,700 platforms used in fishing Vessel Monitoring
Systems (VMS) represent the largest number of "operational" platforms
used in any one application. The second largest number of operating
platforms with more than 1,500 platforms are reported to being used on
drifting oceanographic buoys. It was reported that nearly 750 of this
drifting buoys report on GTS and that the totals include the subsurface
drifters. The percentage of Drifting buoys transmitting onto the GTS was
confirmed to have reached again the level of 2001, i.e. 57%. The number
of wildlife and fishing platforms in the system continue to grow faster
than other types. It was noted that the global system occupation rate
(or duty coefficient) continues to increase with usage estimated at
approximately 12% of the Argos 2 instrument capacity in May 2003. System
use reaches a maximum at more than 50% in South America due to Argos VMS
activity in Peru and Brazil. It is estimated to be around 45% in Europe
and North America. It was reported that more than 16,000 individual
(different ID numbered) transmitters were received and processed in the
past year by the Argos processing centers. (37^th^ O/C)

Louis Mesnier of CLS reported that the number of "operating" platforms,
i.e. transmitting daily and averaged over one month, increased by 13.2%
over the past year. It was noted that 6127 operational platforms
reported in April 2004 compared with 5414 platforms in April 2003.
During the same period, the number of "active" platforms, i.e.
transmitting at least once in a month, exceeded 11,000 to finally reach
12,184 in May 2004. The 2,240 platforms used in fishing Vessel
Monitoring Systems (VMS) represent the largest number of "operating"
platforms used in any one application. The second largest number of
operating platforms with more than 1,800 platforms are reported to being
used on drifting and subsurface oceanographic buoys. It was reported
that nearly 900 of this drifting buoys report on GTS and that the totals
include the subsurface drifters. The percentage of Drifting buoys
transmitting onto the GTS was confirmed to have slightly decreased from
57% to 53%. The number of wildlife, fishing platforms but also ocean
subsurface and humanitarian platforms in the system are growing faster
than other types. It was noted that the global system occupation rate
(or duty coefficient) continues to increase with usage estimated at
approximately 15% of the Argos 2 instrument capacity in June 2004.
System use remains at a maximum at more than 50% in South America due to
activity in Peru (VMS) and Brazil (INPE projects). It is estimated to be
around 45% in Europe and North America and growing in Indonesia with 35%
presently. (38^th^ O/C)

#### Status of current programs

One hundred forty-one (141) new programs were approved since the last
Operations Committee Meeting. This is an increase of about 40 percent.
The largest part of these programs are devoted to biological studies.
(30^th^ O/C)

93 new programs were approved since the last Operations Committee
Meeting. There is a decrease in the number of programs but the number of
new platforms remained identical to the last year. As usual the largest
parts of these programs are in oceanography and biology applications.
(31^st^ O/C)

L. Mesnier first explained that the list of current programs is
extracted from the approval files. Current programs are those of which
the approval is valid, thus including some which either are not yet
active or have recently finished. Since the last Operations Committee
meeting, 209 new programs have been approved. Although, wildlife
tracking represents nearly half of them, oceanography remains the
largest application with 47% of the new assigned ID numbers. Almost 3500
ID numbers were assigned in one year while more than 2000 unused ID
numbers have been recovered from the JTA users. The breakdown of current
programs by category shows that 81% of the programs are
Environmental/Governmental and 11% are Environmental/Non-Governmental
with government interest. (32^nd^ O/C)

Louis Mesnier first explained that the list of current programs is an
extract of the approval files. "Current" means either that the approval
is valid even if the program is not yet or no more active, or that the
program was active since the last O/C meeting and should be renewed. The
number of current programs is 851, a 28% increase over one year, but
some of the programs which were renewed produced several different new
ones. Since the last meeting, 210 programs were approved and the renewal
of 360 programs is on going. Fishing vessel monitoring is now the first
application in new programs with one third of the platforms in recently
approved programs. The breakdown by categories shows that 80% of
programs are Environmental / Governmental and 11% are Environmental /
New Governmental with government interest. Looking at the breakdown of
all current programs by field of applications shows that oceanography
and wildlife remain the two most important with more than 70% of all
programs. A breakdown by countries shows the relative importance of some
countries in the use of Argos while the system is used in 57 countries
throughout the world. (33^rd^ O/C)

L Mesnier presented the list of current programs which was completed
with new data fields: I/R (initial/renewal) including a priori (A)
approvals, Initial Deployment date and User Requirements. The number of
programs increased to 960 i.e. a 13% increase over one year. Since the
last meeting, 362 programs were approved and 216 are renewals.
Concerning the number of new programs, wildlife tracking represents 48%
of them with 71 out of 146. Concerning the number of platforms, fishing
monitoring represents the largest application approved in past year with
more than 2200 platforms, i.e. 32% of the total. (34^th^ O/C)

Louis Mesnier presented the list of current programs which is now given
with some specific information such as : I/R (initial or renewal)
including A priori (A) approvals, initial deployment date and user
requirements. The number of programs increased to 992 i.e. a 3.3%
increase over one year. Since the last meeting, 372 programs had their
SUA approved and 214 are renewals. Concerning current programs, wildlife
tracking represents 39% of them with 384 programs. Oceanography comes in
second with 33% and 331 programs. Concerning the number of platforms, ie
the number of ID numbers allocated to programs, oceanography represents
the most important application with more than 11,000 platforms, i.e. 42%
of the total. 26,000 ID numbers are presently distributed to users and
more than 10,000 of them were unused last year. (35^th^ O/C)

L. Mesnier presented the list of current programs which is given with
the same specific information as last year, such as I/R (initial or
renewal) including A priori (A) approvals, initial deployment date and
user requirements. The number of programs increased to 1085 i.e. a 9.4%
increase over one year. Since the last meeting, 388 programs had their
SUA approved of which 185 are renewals. Concerning current programs,
wildlife tracking represents 41% of them with 449 programs. Oceanography
is the second domain of application with 32% and 353 programs.
Concerning the number of platforms in programs, i.e. the number of ID
numbers allocated to programs, oceanography represents the most
important application with more than 11,000 platforms, i.e. 41% of the
total. 27,000 ID numbers are presently distributed to users and more
than 10,000 of them were unused last year. The breakdown of current
programs by granted categories, i.e. Environment/Non Environment,
Governmental/ Non profit /Non governmental, etc did not change
significantly since the last meeting. The environmental programs
represent more than 90% of the total. (36^th^ O/C)

Louis Mesnier of CLS presented the list of current system use agreements
(SUAs) which is replacing the former list of current programs. Apart
from the usual fields, information given included status (approved,
expired, renewed), type (initial or renewal), initial deployment and
expiration dates and user requirements. It was noted that the number of
current agreements was 1029 over the past year from June 2002 to June
2003. Since the last OC meeting, 395 programs had their SUA approved of
which 240 were renewals and approximately 150 were "a priori" approved.
Concerning current programs, wildlife tracking represents 47% of the
overall total with 486 agreements. Oceanography is the second most
dominant application with 349 programs or 34% of the total. In terms of
number of platforms per agreements (i.e. the number of ID numbers
allocated to programs) Oceanography still represents the most important
application with 12,000 distributed ID numbers. This number represents
nearly 31% of the total platforms reporting. The breakdown of current
agreements by recognized categories (i.e. Environment/Non Environment,
Governmental/Non-profit/Non-governmental) did not change significantly
since the last OC meeting. The environmental programs represent more
than 95% of the total number of agreements.(37^th^ O/C)

Louis Mesnier of CLS presented the list of current system use agreements
(SUAs) which now replaces the former list of current programs. Apart
from the usual fields, information given included status (approved,
expired, renewed), type (initial or renewal), initial deployment and
expiration dates and user requirements. It was noted that the number of
current agreements was 1106 over the past year from May 2003 to May
2004. Since the last OC meeting, 506 users had their SUA approved of
which 273 were renewals and approximately 180 were "a priori" approved.
Concerning current programs, wildlife tracking represents 49% of the
overall total with 544 agreements. Oceanography is the second most
dominant application with 351 agreements and 32% of the total. In terms
of number of platforms per agreements (i.e. the number of ID numbers
allocated to users), Oceanography still represents the most important
application with 12,300 distributed ID numbers. This number represents
nearly 31% of the total platforms reporting. The breakdown of current
agreements by recognized categories (i.e. Environment/Non Environment,
Governmental/Non-profit/Non-governmental) did not change significantly
since the last O/C meeting. The environmental agreements represent more
than 92% of the total number of agreements. (38^th^ O/C)

#### Status of non-environmental activity

All along the year, the activity of non-environmental programs remain
well below the allow five percent (0.9 percent in June 1996).(30 O/C)

The activity of the non‑environmental programs remained far below the
allowed level during the second quarter of 1 997.There was only 0.5 % of
the Argos capacity used by non environmental activity. (31^st^ O/C)

L. Mesnier informed the meeting that since the end of 1997, new software
was implemented to accurately monitor the non-environmental activity on
a day-by-day basis. Currently, non-environmental activity represents on
average less than 2% of the total system use, but can vary from 1% to
more than 3% depending on the activity of episodic programs with a
significant potential for loss of life. During the second quarter of
1998, the non-environmental activity was on average 1.75% of the total
system use. It was generated by about 80 active platforms, while in
comparison, the total number of active platforms in the system averaged
3288 during the same period. The OPSCOM requested that in the future the
non-environmental activity continue to be monitored on a quarterly basis
and that all the figures produced be referenced to the total system use
and not to the total system capacity. (32^nd^ O/C)

The non-environmental activity is continuously monitored and a report is
issued every quarter by CLS and sent to NOAA and CNES. Since the last
O/C meeting, a significant increase was noted in the number of
law-enforcement programs (+30%) as well as in the activity itself which
rose from 1.61% of the system use to 2.83%. The averaged value since the
32^nd^ O/C meeting has been 2.45%. The number of daily transmitting
non-environmental platforms was about 95 while the total number of daily
transmitting platforms in the system was 3555 on average during the
first quarter of 1999. The Operations Committee recommends that the
non-environmental activity continues to be monitored as the present
level represents more than half the 5% presently allowed by the system
use policy. (33^rd^ O/C)

K.  Mesnier reported that the non-environmental activity is continuously
    monitored and a quarterly report is sent to NOAA and CNES. Since the
    last O/C meeting, the non-environmental activity continues to
    increase, but less significantly than the previous year. For the
    first quarter of 2000, the percentage of non-environmental activity
    was 3.08% (2.83% in 1999) which represents 113 active platfoms on
    average (95 in 1999). The non-environmental activity will continue
    to be monitored as it represents more than half of the 5% allowed by
    the system use policy. (34^th^ O/C)

Louis Mesnier presented the list of current programs which is now given
with some specific information such as : I/R (initial or renewal)
including A priori (A) approvals, initial deployment date and user
requirements. The number of programs increased to 992 i.e. a 3.3%
increase over one year. Since the last meeting, 372 programs had their
SUA approved and 214 are renewals. Concerning current programs, wildlife
tracking represents 39% of them with 384 programs. Oceanography comes in
second with 33% and 331 programs. Concerning the number of platforms, ie
the number of ID numbers allocated to programs, oceanography represents
the most important application with more than 11,000 platforms, i.e. 42%
of the total. 26,000 ID numbers are presently distributed to users and
more than 10,000 of them were unused last year.

The non-environmental activity is continuously monitored and a quarterly
report is sent to NOAA and CNES. Since the last O/C meeting, the non
environmental activity has continued to increase and the 5% threshold
was trespassed at the end of 2000. For the first quarter of 2000, the
percentage of non-environmental activity was 5.12% which represents 173
active platforms on average (113 in 2000). Over one year, the percentage
was 4.76%. Last year, in addition to the usual NE activity, some
important yacht races were organized to celebrate the millenium : Vendée
Globe, The Race, etc. Also, it was mentioned that the anti-piracy
program of the IMO was growing regularly and faster than the total
activity in the system. Presently more than 1/3 of the non-environmental
activity is by programs with a potential risk of loss of Life. (35^th^
O/C)

The non-environmental activity is regularly monitored on a quarterly
basis and a report is sent to NOAA and CNES. Since the last OC meeting,
the non-environmental activity first came back between 4 and 5% and the
5% limit was only reached again at the end of 2001. For the first
quarter of 2002, the percentage of non-environmental activity was 3.99%
which represents 187 active platforms on average to be compared with 173
in 2001. Over one year, the percentage was 4.75% which is quite the same
as last year. Last year, it was mentioned that the anti-piracy program
of the International Maritime Bureau was increasing regularly and faster
than the overall non-environmental activity in the system. It is now the
most active non-environmental application. It represents more than 2% of
the total activity in the system, while law enforcement programs
represent approximately 1.3% and programs with potential risk of loss of
life are very seasonal with variations between 0.5% and more than 2% of
the total use of the system. As it was proposed at the last OC 35
meeting, it is now recommended that the 5% limit has to be removed
providing that the environmental activity in the system remain
predominant. (36^th^ O/C)

Louis Mesnier of CLS reported that non-environmental use of the Argos
system continues to be regularly monitored. For the first quarter of
2003, the percentage of non-environmental activity was 4.64%, which
represents 235 active platforms on average compared with 187 for the
same period of 2002. Over one year, the percentage was 4.76% which is
similar to last year. It was noted that system usage for
non-environmental applications did exceed 5% in the 3rd quarter of 2002
but subsequently declined in the 4th Q of 2002 due to a decrease in the
episodic use of the system. Last year, it was mentioned that the
anti-piracy program of the International Maritime Bureau was increasing
at a greater rate than the overall non-environmental activity in the
system. Anti-piracy is now the largest non-environmental application. It
represents more than 2.6% of the total activity in the system. In
comparison, law enforcement programs represent approximately 1.1% and
programs with potential risk of loss of life (which are very seasonal)
vary between 0.5% and more than 2% of the total activity in the system.
The meeting decided to adopt a more detailed breakdown concerning the
sensitive use and to identify more specifically national defense,
homeland security, law enforcement and humanitarian operations. Episodic
use will continue to be included in the non-environmental activity
report. (37^th^ O/C)

Louis Mesnier of CLS reported that non-environmental use of the Argos
system is regularly monitored. Further to the request by the O/C meeting
to have a breakdown by sensitive and episodic use applications (homeland
security, law enforcement, humanitarian operations, etc), the unit used
to assess the non environmental activity is now the PTT-days and
PTT-months used in the system for reporting and invoicing the service.
For the whole year 2003, the percentage of non-environmental activity
was 5.36 %, which represents 289 operating platforms on average compared
with 235 for 2002. It was noted that system usage for non-environmental
applications did exceed 6 % in the 1st quarter of 2003 but subsequently
declined during the year due to a decrease in the episodic use of the
system and in the homeland security and law enforcement applications.
Homeland security is now the largest non-environmental application. It
represents more than 3% of the total activity in the system and nearly
60% of the non environmental activity. In comparison, law enforcement
programs represent approximately 1.6% and programs with potential risk
of loss of life (which are very seasonal) vary around 0.5% of the total
activity in the system. The humanitarian operations represents now 0.5%
but is growing fast due to the deployment of platforms by the WFP school
feeding project. The percentage of Non environmental activity is
expected to reach more than 6% in the second quarter of 2004. (38^th^
O/C)

#### Status of US processing agreement

The 1994 Agreement exceeded the guaranted minimum amount of processing
required by 44 platform years, primarily due to a larger than
anticipated drifting buoy program in the Gulf of Mexico. In 1995, the
U.S. requirement is for 725 platform years of processing. Like the JTA,
the U.S. rate was reduced 3.7%. The total value of the 1995 U.S.
Agreement is \$ 2,660,750. (29^th^ O/C)

T. Bryan informed the meeting that the 1996 U.S. JTA costs are nearly
\$3.0M for 805 platforms years. In 1995, the U.S. contracted for 725
platform years and actually used 721.5 platform years. (30^th^ O/C)

R. Bassett informed the meeting that the 1997 U.S. JTA costs are nearly
\$2,5M for 675 platform years. In 1996, the U.S. contracted for 805
platform years and actually used 777 platform years. A report from the
U.S. Government User Group stating Satellite Data Collection and
Location system requirements was entered into the record. (31^st^ O/C)

T. Bryan reported that the United States has committed to 655 platform
years in 1998 and that, with the exception of the Global Drifter
Program, to date there has been minimal interest in taking advantage of
the 35% additional free processing. (32^nd^ O/C)

Steve Auer, the US JTA ROC (Representative Of Country) has implemented a
US JTA website ([www.ogp.noaa.gov/argos](http://www.ogp.noaa.gov/argos))
which is linked to the SAI and NESDIS sites. The US JTA has 500 Argos
programs of which 40% are Non (Federal) Governmental Organizations
(NGO). The US use increased 23% last year; so far, there has been a
negligible increase this year. The US raised its commitment at the 2000
JTA Meeting from 661.6 to 685.0 Ptt/yr in part to help offset the
CLS/SAI income loss expected from the phasing in of Location Plus
service to biologists. The ROC sends invoices to 270 users of which
there are 100 governmental (average 10 Ptt/yr) and 170 NGO (average 1
Ptt/yr). The ROC is concerned that many NGO make payments after service
is rendered which has caused delays in the past for the US in meeting
its quarterly payments to SAI. The ROC suggests it might be advantageous
to all if SAI could collect the actual use JTA fees directly from the
NGO users on their quarterly SAI invoices. Also of concern the ROC only
gets a 50% user response rate in gathering new calendar year
requirements estimates; this presents a problem in making the US
commitment at the annual JTA meeting. Fortunately most of the
non-replies are from small users. A user requirements survey should be
conducted of biologists currently using the Argos system to see what
future system enhancements are desired. So far, no professional
organization has been identied that can speak for biologists like the
DBCP does in gathering and forwarding oceanographer system requirements
to the JTA. The OPSCOM directed NOAA to organize a study of its own
animal applications for future system requirements. The ROC pointed out
that there were JTA Argos user transactions which may have linkage
opportunities for better efficiency and compliance by the users. For
example, the SUA renewal status could perhaps be reported on the annual
JTA Requirements request and, if appropriate, a SUA form could be
attached. Also the JTA invoice could perhaps be linked to the SAI
quarterly invoice for NGO'. (as suggested above). The ROC concluded by
noting that there is significant user frustration with getting good cost
estimates (and the ROC in getting good user estimates). This could
perhaps be mitigated by developing an easy-to-use cost estimating tool
(could be placed on the ROC website) similar to many found on the web
today (e.g., auto.com to purchase and borrow funds for a new car). The
cost tool should provide complete estimates for the CLS/SAI supplemental
costs and the JTA costs. This would bring a level of "no surprises" to
the users to better plan and budget their financial resources. The ROC
will address the items with SAI. (35^th^ O/C)

S. Auer of NOAA, the U.S. Argos JTA ROC, presented the status of the
U.S. JTA. In 2001, the U.S. platform year use increased by 3.7% while
the total number of active platform months only increased by 0.3%. About
75 new users entered the U.S. JTA and these were predominantly
biologists. The ROC paid \$2.7M to SAI for 2001 JTA costs. The ROC
actually collected \$3.2M from users with about \$1M of this amount
comprising advance payments for anticipated 2002 use. About \$0.5M in
user costs remains outstanding (uncollected) primarily from NGO's; this
is becoming more of a concern with the dramatic increase in NGO's over
the past several years and the need to pay SAI promptly and "in full"
each quarter. The ROC is collaborating with SAI to develop creative
techniques to improve collections from this sector. The U.S. signed for
695 platform years in 2002. One expected area of increase is the ARGO
program; it used 11 platform years in 2001 and expects to use 55
platform years in 2002. Biologists have expressed their gratitude for
the phase out of costs for ALP "location Plus service" which will become
part of the basic JTA service for biologists, i.e., "free", in 2003. The
ROC notes that new users are now "by-and-large" better informed about
the JTA procedures and have more realistic expectations of the Argos
system, for example: animal tracking. This change can primarily be
attributed to vast improvements in 24-hour/7-day available website
information at CLS, SAI, NOAA Argos System, and U.S. JTA, and the
implementation of Argos webgroups for biologists. (36^th^ O/C)

The U.S. portion of the Argos Joint Tariff Agreement (JTA) is described.
In 2002, the U.S. used 1402.8 Platform Years (Ptt/yr) and 41,305 Active
Platform Months. For 2003, the U.S. has agreed to purchase 790.0 Ptt/yr
and expects to use 1500 Ptt/yr and 43,400 Active Platform Months.
(37^th^ O/C)

Steve Auer informed the OPSCOM on the status U.S. portion of the Argos
Joint Tariff Agreement (JTA). The total Costs for the U.S. JTA have
risen appreciably increasing 39% the past 3 years (\$2.5M in 2000 to
\$3.5M in 2003); these costs will increase 15% more in 2004 to \$4.0M.
NOAA has borne the biggest JTA cost-growth burden. NOAA costs in 2004
will be 87% more than 3 years ago an additional \$1M! These cost trends
are ominous as total NOAA Argos use could increase by 43% more the next
3 years. In the face of budget reductions and shifting priorities, NOAA
has determined that it must significantly reduce its future JTA cost
participation, and the NOAA cost basis for this must be appreciably less
than its CY 2003 cost. The U.S. ROC and Service Argos Inc. are
continuing their collaboration/partnership toward delivering a
responsive efficient user service. The new JTA invoice collection option
of SAI direct quarterly billing implemented in 2003 is working smoothly.
SAI now handles about 60% of the JTA user invoicing while the ROC still
invoices and collects the vast majority of costs from 100 predominately
Federal users. It is proposed that SAI assume collection responsibility
for all non-NOAA users next year. This will eliminate most of the NOAA
administrative overhead associated with the ROC user invoicing. This
transition in user invoicing/collection responsibility is past due as
NOAA has provided it at no cost to the users or CLS/SAI for over 25
years during which the number of invoice transactions has increased from
4 to over 500. (38^th^ O/C)

## EVOLUTION OF THE ARGOS PROGRAM

As NOAA and CNES move forward with plans to cooperate on Argos for NOAA
N\' and METOP, there will be a number of challenges and opportunities
for expansion and enhancement of the current system to meet users needs.
For instance, CNES and NOAA are beginning to explore international DCS
cooperation with the Japanese National Space Development Agency and
perhaps others in the future. The O/C agreed on the following resolution
regarding this matter:

NOAA and CNES will work together to assess and monitor developments in
their governments and the commercial sector with regard to user
requirements and would take them into account when planning for the
future. (28th O/C)

A presentation on the requirements of Argos system users was given by M.
Taillade (CLS/Service Argos) and A. Shaw (Service Argos, Inc.). It
included results of a comprehensive survey conducted in 1995. The survey
indicated overall satisfaction with Argos and a desire to continue use
of the system. With regard to future scientific and observational
requirements, an evolution in the system is desired in the following
ways:

-   slightly better location accuracy either by improvement in the
    Doppler technique or more widespread integration of GPS.

-   higher data throughput with most users satisfied by 3-5 kilobits per
    pass.

-   continued emphasis on improving on-board satellite receiver
    sensitivity with the primary goals of reducing PTT power
    consumption, size and weight.

-   implementation of a downlink messaging capability to permit sending
    of messages or acknowledgments to user platforms.

-   a slight increase (from 2 to 3 or 4) in the number of operational
    satellites.

The presentation emphasized the role Argos has played in serving as a
catalyst for many international cooperative agreements and formation of
coordinating bodies for data collection.

It also indicated unique Argos capabilities such as global coverage
(store and forward), simple operation (for users), Doppler location, and
highly sensitive receiver enabling small, low-power transmitters.
(30^th^ O/C)

Michel Taillade presented an enthusiastic paper giving an overview of
present and future Argos users requirements (Argos 4). Among Argos
applications, ocean and climate studies represent today the most
important activity (34% of the total). When looking at the medium and
long term evolution of this domain we observe the following significant
points: GOOS (the Global Ocean Observing System) is the framework of the
evolution toward a global system for the study and prediction of the
global climate. There is a significant move in USA for an organization
around the studies of this domain: Interagency organization for ocean,
NOAA climate service proposition for climate. A similar move can be seen
at the global level with the creation of JCOMM, a joint organization of
WMO and IOC. These evolutions of the national and global level are the
beginning of a significant move to set up ocean and climate studies,
services and organization. When looking more precisely at this domain,
we can see a new dimension in the measurements within the study of the
oceans. Subsurface measurements are very promising in the way they are
bringing access to the study of the largest part of ocean. Ocean studies
and subsurface measurements are needing an increased data rate
transmission which represents the main constraint for the evolution of
the Argos onboard equipment and represents the condition for the system
to continue to play an important role within this domain. Initial
results of this study show that a new channel with a data transmission
bit rate up to 40kbits per second might cover the long term needs of
ocean and climate. (35^th^ O/C)

C. Vassal from CLS presented their estimates of the user requirements
for the NPOESS era. To an extent these requirements have been
coordinated with the instrument development constraints. They are
mission requirements for which the feasibility needs to be evaluated
such as :

-   Capacity

-   low power (new generation) PTTs and PMT's: as A-DCS

-   standard PTT's and PMTs : as A-DCS

-   high rate PTTs and PMTs increase of capacity needed, by same bit
    rate.

Timeliness: Installation of an Argos instrument on 0530 and 1330 orbits
; No blind orbits should be allowed. Argos data should be both in the
stored data and in LRD. Some internal enhancements to the Argos
instruments that are proposed are transparent for the satellite. The
OPSCOM discussed a proposal to connect the instrument to the NPOESS On
Board Computer. The NOAA co-chair cautioned that major changes to the
Argos instrument baseline may be difficult due to the advanced stage of
the (see write-up) proposal selection process. The OPSCOM co-chairs
opened an action item to draft a Letter of Intent outlining these
requirements to facilitate discussions with the NOAA/IPO (36-4-C/S). C.
Rob Bassett from NOAA reported on recent efforts to define Argos
requirements for US users in the NPOESS era (see exhibit ). He
highlighted that the law enforcement users expressed great interest in
the down-link message capability while the ocean science community
required data throughput on the order of 40 kbps. (36^th^ O/C)

Rob Bassett reported on NOAA efforts to collect user requirements for
future DCS missions. He highlighted several recent presentations to
various user communities that indicated a need for more accurate Doppler
locations and the capability to transmit large (Mb) data sets. While
efforts continue to solicit user requirements, many of the inputs are
qualitative vice quantitative which makes a technical statement of need
quite difficult. Christophe Vassal presented the preliminary results of
a study performed during the period June 2002 to June 2003 to collect
and analyze users' requirements. These requirements will be used as a
framework to define functional specifications for the next Argos
generation to be flown on NPOESS and GCOM B satellites. It has to be
noted that it is not an easy task to ask Argos users about their
requirements for the future when the third generation of the system is
not even flying. However out of 5 categories of Argos users, namely
oceanographers, biologists, fisheries specialists, government agencies
and humanitarian organizations, we can define two categories of users'
requirements:

-   users' requirements relative to transmitters where users would like
    inexpensive transmitters, lighter, less power drain demanding, and
    with frequency synthesizers for better Doppler positioning.

-   users' requirements relative to system performances where users
    would like reduced latency times principally at the equator, reduced
    throughput times, more capacity to accommodate the regular growth of
    active transmitters that we have been experiencing since 10 years
    and to accommodate high data rate applications.

Also the operator of the system, CNES/CLS anticipates certain technology
driven evolution like the capability to download new software
modifications and/or evolutions directly into the onboard instrument
through the satellite processor, the capability to perform DRUs
maintenance operations from the ground and the capability to change the
frequency of a given transmitter or of a group of transmitters from the
satellite using the downlink. It expected that those preliminary results
will be followed by more precise analysis when phase A studies for the
next Argos generation will have been decided. (37^th^ O/C)

Christophe Vassal presented the Argos constellation as it is today with
3 orbit plans (early morning/NOAA 15, morning/NOAA 16, afternoon/NOAA
17) providing good system performances to the users. Christophe Vassal
indicated that the future planned Argos constellation from 2010 would
provide the same performances with again 3 orbit plans (early morning
NPOESS C3, then NPOESS C6, morning METOP-1 then METOP-2, afternoon
NPOESS C2, then NPOESS C5). Between now and the NPOESS era, there is a
risk on the early morning orbit where there is only one satellite in
orbit (NOAA 15) and no more planned before the launch of NPOESS C3. The
meeting is taking note of the need for a gap filler and has defined an
action item.

C. O'Connors provided an update to the user request for Blind Orbit
Support. NOAA was tracking the development of the Barrow ground station.
In Fall 2003 the Barrow site implemented a T1 line between Barrow and
Fairbanks Alaska to allow for data transfer into the CDA node in
Fairbanks. In recent months Barrow ground station is receiving HRPT data
from the blind orbits in support of the US National Weather Service. The
current Terascan software configuration can only process one data stream
at a time. A request for an upgrade to the software to allow two data
stream simultaneously HRPT, and STIP. The earliest funding may be
available for the upgrade is October 2006. In the mean time NOAA is
interested in testing its equipment in place at Svalbard for risk
reduction for the NPOESS mission. NOAA is considering downloading blind
orbits for one or both of the operational satellites to accomplish this
test. The testing may begin in early 2005. Discussions took place on the
non environmental use of the Argos allocated spectrum. NOAA has been
coordinating the expansion of non environmental applications due the
regulation change in August 2003 with the NTIA the granter of the
frequency bandwidth. In several meetings between NOAA and NTIA and SAI,
NOAA and NTIA risks were identified to the system. NTIA is not in favor
of any non environmental use in the Earth Exploration Satellite Service
(EESS), but recognizes that there are unique capabilities of the Argos
system (small transmitters, low power ...etc.) which Governmental law
enforcement, homeland security, national defense, and humanitarian
application would benefit from. NTIA recommends that NOAA consider
re-establishing a 5% cap on non environmental use. The 5% was de minimis
value on the environmental frequency band and was reported to US
Congress by Secretary of Commerce Ron Brown in the early 1990's. B.
Woodward express their view on the NTIA meetings as a positive process
and recommended that if a cap is re-established that it be based on
system capacity rather then active platforms or IDs. OPSCOM took an
action 38-4 C/S to discuss the definition of 5% system use and how it
should be applied in operation to protect the environmental users. C.
O'Connors submitted an informational matrix (see exhibit \# 14) of space
based data collection system constructed by a third party Aerospace
Corp. for NOAA. The purpose of the study was to help NOAA understand the
viability of commercial providers to make better informed decision and
to fend off commercial challenges of competition. Discussion were held
on whether the matrix should be posted and presented at user meeting in
which strong objection were raised from CNES, CLS, and SAI. There were
concerns that posting the information would promoting these commercial
entities and not to the advantage of the Argos system. NOAA agreed not
to post the matrix and reserve the information per US informational
requests. NOAA made a request to create a customer survey to be included
in the renewal letter procedure. CNES/CLS felt it would be difficult to
gain user responses to both the SUA and a survey. CNES/CLS conducted a
recent survey and delivered it to CNES. M. Hucteau will provide a copy
of the study to NOAA. (38^th^ O/C)

# Joint TARIFF Agreement

## POLICY

### GENERAL

#### Management Responsibility

Operators covered by the 1981 U.S. Processing Agreement are within 3% of
the planned use. NESDIS will not manage the U.S. Processing Agreement
after 1981. The Special Research Office of NOAA will manage the 1982
U.S. Processing Agreement and NESDIS will continue as technical
consultants to that office. (14th O/C)

#### Global Processing Agreement, O/C Participation

The O/C decided that a committee member or their representative would
participate in future negotiations for the Global Processing Agreement.
(16th O/C )

#### O/C Review, Tariff Changes.

At each O/C meeting, Service Argos will inform the O/C of the tariff
structure and prices in effect. If changes to the tariff structure are
anticipated, either for the Joint Tariff Agreement Meeting or the annual
tariff document, Service Argos also will present these changes to the
O/C at this time. The O/C will review these proposed changes and provide
guidance as necessary to ensure that the intent of the MOU is not
violated. (18th O/C)

#### Pricing List

It was agreed that an annual review of processing rates and the pricing
structure is appropriate. (12th O/C)

#### Cost Recovery

The cost recovery principle outlined at the 19th O/C Meeting was part of
the negotiations for the new Memorandum of Understanding. (20th O/C)

## TARIFF PRICE STRUCTURE

### GUIDELINES

#### Annual Pricing Review

The O/C agreed that:

1\) An annual review of rates and pricing structure is appropriate.

2\) The users should be advised that the rates and pricing structure
will be reviewed and may be changed annual. (12th O/C)

#### Future Funding Plan, Service Argos

A future funding plan for Service Argos was discussed. This plan
indicates a near balance of income and expenses for the year 1990. The
figures show a cumulative deficit between 1984 and 1990. This projection
assumes a system usage growth rate of 15%. Under this plan, the tariff
should remain unchanged through 1990. (19th 0/C)

### DETERMINING TARIFF CHANGES

#### Determining Tariff Changes

The rate increase proposed by Service Argos in 1981 only takes into
account the inflation rates during 1980 and some changes in the exchange
rate between French francs and U.S. dollars. Listed below are comments
and guidelines suggested by the O/C for use in determining tariff
changes:

##### Original Basis and Change:

The original basis for the pricing policy in the present MOU was to
provide support to FGGE. Since FGGE is now complete, a change in the MOU
in regards to pricing could now be considered.

##### Pricing Changes:

A major change in the price structure seems appropriate if:

1\) Operating costs become a problem.

2\) There is a change in the U.S. or French policy concerning cost
recovery.

#### Change Justification

It is difficult to change the current price structure, just as a matter
of principle, once it has become well established. There should be some
explainable basis for the change.

#### Change Notification

Any change in price structure should be made with sufficient lead-time
for users to adjust their budgets.

### DATA PROCESSING COSTS

#### Location Processing Costs.

Processing costs for platforms requiring location will be \$20 per day
until 1980. (2nd O/C)

#### User Cost Document

It was agreed that the Users Cost Document would be issued as a CNES
Document. The Argos kit will be issued as a joint CNES/NASA/NOAA
document. (3rd O/C)

#### Revised Charges

The recalculated user charges proposed by Service Argos have been
reviewed and are acceptable to NOAA. (9th O/C)

#### Reduced Tariffs

CNES stated that reduced tariffs are available to all operators of large
numbers of platforms. The present global processing agreement consists
of only government agencies. (16th O/C)

## PROCESSING AGREEMENT

### GENERAL

#### 1981 Agreement

The 1981 Agreement has increased by 15 platform-years over the 1980
Agreement. Ten of these are for the U.S. and 5 are for Australia. NOAA
has no objection to the extension of the agreement to other countries
providing that:

1\) Service Argos and CNES agree

2\) Collected data must be meteorological or oceanographic of broad
operational or experimental use by several countries such as occurred in
the FGGE or WWW Programs. (13th O/C)

### PRICING STRUCTURE, CHANGE PROPOSALS

#### Pricing Structure (1983)

A new pricing structure has been proposed by the members of the Global
Processing Agreement for use in 1983. This new pricing includes prices
for direct readout users and users that require no location computations
(data collection only). These changes were proposed because Service
Argos must process all messages received in order to monitor the system,
regardless of user requirement, and there is a need to help defray these
costs. The pricing structure proposed for the Global Processing
Agreement members could be used for all qualified users in 1984. Of
course, the base price is variable and is based upon the number of
platform years involved. Since the current MOU does not authorize such
charges, the O/C gave tentative approval to the new pricing structure
pending the agencies\' approval of the recommended changes to the MOU
that apply to data processing pricing structure. (16th O/C)

#### New Pricing Structure

The JTA recognizes the need for adjustments or user fee restructuring
based upon system use. The JTA representatives and CLS/Service Argos
will develop a new tariff proposal with consideration given to new and
anticipated programs. (22nd O/C)

CLS presented a proposal which would enable reduction of the accumulated
losses and tariff rate. This proposal was based on anticipated growth
rate and additional revenue being generated by non-environmental users
as provided for in the MOU (up to 5 % of capacity is allowed for this
purpose). NOAA expressed concern that since currently, environmental
applications utilize about 17 % of system capacity, the potential volume
generated by non-environmental users could become a predominate and
highly visible factor, thus bringing into question the environmental
nature of the system and jeopardizing the frequency allocations. NOAA
and CNES agreed to establish a Working Group to propose to the O/C
Co-chairs guidelines for implementing non-environmental use of the
system. (23rd O/C)

#### Basic Service Charge

It was noted that some platforms operate on a reduced duty cycle. While
this reduces users\' processing costs, expense to CLS/Service Argos is
not reduced accordingly. A basic service charge to more equitably
distribute the cost was discussed by the JTA, which then requested CLS
to analyze the idea. J. L. Bessis presented a scenario based on 1989 use
which includes a monthly service charge and applies excess revenue to
reducing the cost per platform year for basic standard services.
Recognizing that applicable percentages may require annual adjustment
and efforts would be made to reflect the expected use during the year
under negotiation, the O/C approved the concept and authorized the JTA
to adopt such a mechanism if they so choose. (24th O/C)

#### Standard Scientific Service

A new class of service, the «Standard Scientific Service», was adopted
by the JTA in agreement with CLS/Argos. Under this service:

1)a platform will transmit no more than eight hours in any 24 hour
period ;

2)a platform will transmit every day (requirement subsequently dropped);

3)standard location or standard location and data processing services
only will be applied (coefficient of x/3);

4)all platforms in a single program must meet these conditions ;

5)separate applications for each unique program must be submitted. (25th
O/C)

The conditions were subsequently modified to include the following

1)a platform will transmit no more than 24 hours in any 72 hour period ;

2)Users will be charged the standard tariff for up to 10 days in a
month. (28th O/C)

#### Division of Operating Costs

At the 13th JTA Meeting, the it was agreed that JTA programs would
supply 50% of the estimated Argos operating costs while the remaining 50
% would be handled by non-JTA programs. The JTA will also be liable for
50 % of allowable losses from 1984 through 1990. (25th O/C)

#### Accumulated Debt and Inflation

The JTA requested the O/C to review and make recommendations on the
CLS/Service Argos intention to apply inflation on the accumulated debt.
CNES representatives noted correspondence with NOAA regarding this issue
and discussed the time period under which the inflation could be
applied. NOAA indicated that it was not clear from the correspondence
under what circumstances and time period inflation could be applied. The
Co-chairs agreed to appoint a working group to make a recommendation to
the Argos O/C regarding JTA contribution to reducing the deficit. (25th
O/C)

#### Value-added Services

Commercially provided value-added services which incorporate processing
fees and their relationship to the JTA were discussed. The O/C accepted,
in principal, that JTA eligible users should be offered a preferential
tariff for the processing portion of these value-added services. The
Committee also recognized that administrative details should be worked
out between CLS / SAI, the commercial provider, and the JTA
Representative Organization for the Country (ROC) (27th O/C)

#### Minimum Use Charge

Noting that the cost to the user should be linked to costs incurred by
CLS/SAI, while still reflecting the services received and perceived by
the user, the JTA Chairman and CLS asked the O/C to consider the
possibility of a minimum use charge(s). The Committee agreed that a
charging change to reflect minimum level of use would be appropriate.
The Committee further agreed to the possible application of two such
charges: 1) a monthly charge for each ID number assigned and 2) a fixed
monthly charge for each ID number used. It was noted that the
implementation of such charge(s) may require some adjustments to be
revenue neutral. (28th O/C)

#### Incentive Tariff

Growth in the number of platform years is inhibited

On behalf of the Data Buoy Cooperation Panel and the JTA, the JTA
Chairman requested that the O/C endorse the concept of incentive
(reduced) tariffs to limited user groups within the JTA to stimulate
cooperative programs. The O/C agreed in principle to this proposal
provided that: 1) there is a demonstrated benefit to the general public,
2) the cost to other JTA participants is not increased, and 3) there is
no loss in total revenue. (28th O/C)

## Joint TAriff agreement meetings

### Annual meeting, reports

The 14^th^ JTA meeting agreed to increase the proportion of the
operating expenses covered by the JTA because of the shortfall in
revenue generated by commercial users. The JTA portion will increase
from 50% to 53.3% in 1995, 56.6% in 1996 and 60% in 1997 provided that
the minimum tariff does not exceed the 1995 rate. The meeting considered
an incentive tariff for cooperative programs and a minimum use charge in
the form of a charge on allocated ID numbers. Both items were deferred,
the former for economic and operational reasons, although a pilot
project may be implemented in 1996, and the latter because the diversity
of applications would cause unacceptable financial penalty to some
users. If the amount of available ID numbers becomes critical, a charge
per ID number may be implemented. It was noted the accumulated loss debt
is being repaid ahead of schedule. (29^th^ O/C)

T. Bryan informed the meeting that the tariff for 1996 was able to be
reduced by about 1 percent to FF25,750 per platform year after applying
the previously adopted rules. This would also allow the remaining
accumulated debt of FF5.0M to be reduced by about FF1.5M. Other
significant issues included the adoption of a charge for ID numbers that
have been inactive for one year, the request for a report on the impact
of potential budget reductions on services provided by CLS/Service
Argos, and the request to the Operations Committee to explore the
possibility of obtaining continuous data from a third satellite. T.
Bryan also informed the meeting of an impending proposal from the Global
Drifter Program for a special tariff rate due to volume and program
consistency. The meeting noted that it had previously approved the
concept of such a special rate providing that the Joint Tariff Agreement
was revenue neutral, there was no additional cost to other users, and
there was a benefit to the community, e.g., data available on the Global
Telecommunications System (GTS). The meeting reaffirmed this decision
and approved implementation of such changes to the tariff structure
should JTA see fit. T. Bryan informed the meeting that the 1996 U.S. JTA
costs are nearly \$3.0M for 805 platforms years. In 1995, the U.S.
contracted for 725 platform years and actually used 721.5 platform
years. (30^th^ O/C)

R. Bassett informed the meeting that the tariff for 1997 increased by
about 1 percent to FF.26,000 per platform year due to a substantial
decrease in system use. Other significant issues included a report that
the adoption of a charge for unused ID numbers was extended from a
period of non‑use from one year to two years. R. Bassett also informed
the meeting that the Argos large International Program (ALIP) was
adopted on a one year interim basis in an attempt to expand
international programs at a substantially reduced rate. (31^st^ O/C)

T. Bryan reported on the results of the JTA XVII meeting, in particular
the adoption of a proposal whereby each country would be allowed a 35%
increase in usage compounded without additional charge in each of the
next 2 years. M. Cazenave pointed out that the impact of this proposal
was not known. In response, the Operations Committee expressed concern
about the future consequences of major tariff changes and reaffirmed its
commitment to maintaining the financial health of the processing system.
M. Cazenave also noted that there is an ongoing problem with late
payments by some countries. T. Bryan also conveyed to the Operations
Committee the recommendation that CLS/Service Argos provide the JTA a
more detailed financial statement of operating and management costs with
a breakout of the promotion and marketing item. The Operations Committee
concurred and requested that this statement be available to them as
well. (32^nd^ O/C)

D. Painting, JTA Chairman, reported on the main results of the 18^th^
meeting of the Argos Joint Tariff Agreement, Marathon, 19-21 October,
1998. He noted that the formulation adopted at JTA 17, La Réunion,
October 1997, to run for two years, had led to a deficit of operating
costs over revenue of some FF. 1.7M for 1998, hence JTA18 decided that
steps should be taken in 1999 and after JTA 19, to achieve a balance of
income and expenditure in the very near future, whilst retaining the
principles established at past meetings. The Operations Committee agreed
that it was essential that the Tariff Agreement be modified, within the
current guiding principles and within the framework of co-operation
between CLS/Service Argos, Inc. and the users, with the objectives of
obtaining a balance of income and operating costs and eliminate the
current deficit as soon as practicable in a period not to exceed five
years. The JTA Chairman agreed to co-operate with CLS in bringing a
suitable proposal to the next JTA session. (33^rd^ O/C)

######## D. Painting, JTA Chairman, reported on the main results of the 19^th^ meeting of the Argos Joint Tariff Agreement (JTA), Wellington, New Zealand, 1-3 November 1999. He drew attention to the discussion on user requirements and in particular two DBCP recommendations supported by the JTA.. These were: {#d.-painting-jta-chairman-reported-on-the-main-results-of-the-19th-meeting-of-the-argos-joint-tariff-agreement-jta-wellington-new-zealand-1-3-november-1999.-he-drew-attention-to-the-discussion-on-user-requirements-and-in-particular-two-dbcp-recommendations-supported-by-the-jta..-these-were .unnumbered}

(i) The need to improve data reception and dissemination within the
    International South Atlantic Buoy Programme (ISABP) by connecting
    existing S-Band stations to the Argos processing centres.

(ii) The potential benefit to DBCP programs that could be realized by
     integrating the planned Brazilian Space Agency (INPE) DCS into the
     Argos global system. The Operations Committee endorsed the CLS in
     response to the recommendations as part of the Argos development
     program.

> Recalling the guidance given by the 32nd Operations Committee meeting,
> the JTA Chairman outlined the plan adopted by JTA 19 to address the
> deficit of income on expenditure that had accrued since the 1998 Joint
> Tariff Agreement. The Operations Committee approved the general
> principles of the plan whilst stressing the need to monitor and adjust
> the variable factors in the light of actual experience. (34^th^ O/C)

The JTA had agreed to maintain the five year plan, agreed at JTA 19,
although it had noted that global operating costs had risen above the 2%
allowed for in the plan. The Operations Committee agreed in principle to
a proposal made jointly by CLS and the JTA Chairman to limit the
increase in operating costs *for the purpose of calculating the actual
share to be met by the JTA* in order to avoid an increase in accumulated
deficit of JTA income over costs. (The details of this limitation to be
decided at the next JTA session). The meeting noted that increases in
operating costs were inevitable during periods of investment in system
improvements and expansion of services that were to the benefit of JTA
and non JTA users, however the meeting stressed the need to maintain a
sound business footing for the Argos Service whilst keeping a fair
balance of contributions of JTA and non JTA users to operating costs.
The Operations Committee concurred with the following proposals agreed
at the JTA meeting : to enhance the GTS subsystem with a BUFR (Binary
Universal Format for the Representation of data) encoder, to phase in
class A/B positions for animal trackers as part of the basic service.
This to be accomplished over a three year period through a 1/3 reduction
of full cost per year. (35^th^ O/C)

Following the direction of the 35^th^ OPSCOM, the JTA had agreed to cap
costs, for the purpose of calculating the JTA share of operating costs,
at the actual 2000 figure to be then increased at the official inflation
rate. A simplified version of the FYP (2000-2004) as adopted by JTA 21
was presented; showing only revised costs and the expected effect on
annual and accumulated losses. The Operations Committee agreed, in
principle, with the user request to enhance the Argos GTS processing
sub-system to accept relevant data from non Argos satellite DCS for
insertion into the GTS. Such data might include, for example, Argo data
relayed by commercial satellites or data from the Brazilian satellite
DCS. In this latter connection the Operations Committee endorsed the
ongoing activity being undertaken by CLS to allow Argos PTTs to operate
on the Brazilian satellite DCS. (36^th^ O/C)

Derek Painting informed the OPSCOM of the main results of the
twenty-second meeting on the Argos Joint Tariff Agreement (La
Martinique, 21 -- 23 October, 2002). It was noted that the 5-year plan
(2000 -- 2004), that provided a systematic framework for JTA cost and
tariff evolutions was operating successfully and should result in
elimination of accumulated losses by 2005. Beyond 2004, the tariff
structure needs to be re-negotiated to reflect the changes in user
community and operational cost basis and also to simplify the rules and
conditions of use, since these have become increasingly complicated over
the years. The OPSCOM concurred with the need to re-address the basis of
tariff determination, especially to return to the original principles of
cost and benefit sharing amongst all JTA participants. It therefore
requested the JTA chairman and CLS to bring this issue to the next
meeting of the JTA with the objective of developing a framework for
future tariff evolution, based on readily understood cost/benefit
principles. This plan, in draft form, should be presented at the next
OPSCOM meeting for approval in principle and further refined for
implementation in 2005 following the twenty-fourth meeting of the JTA in
autumn 2004. On the question of re-activating the Lannion global ground
station to address the "blind orbit" issue, the meeting was informed
that a program to enhance the Barrow ground station was in progress.
This approach would not entirely restore the service provided by Lannion
but was being undertaken in the light of current operational and
technical considerations. Derek Painting presented to the meeting a
graph which was already presented at the last DBCP meeting and shows
clearly the relative effect of Lannion and Barrow ground stations on the
blind orbits. It was noted, however, that the new generation of
satellites carry digital data recorders that might facilitate
downloading of stored data to Lannion (in its current configuration) at
little effect. Also it was noted that the METOP ground segment would
eliminate NOAA/POES blind orbits. (37^th^ O/C)

C.  Painting informed the meeting on the results of the twenty-third
    meeting on the JTA. Following the action proposed by OPSCOM 37 the
    JTA meeting had elaborated some guidelines for a future structure
    and established a small working group tasked with preparing a firm
    proposal to be considered by the twenty-fourth meeting on the JTA
    (to be held October 2004). Bill Woodward presented an initial draft
    of the JTA Proposal as a result of work between CNES/CLS, JTA
    Chairman, and DBCP Chairman. The new structure is proposed to
    include a monthly fee for active platforms (seen at least once in a
    month) and a fee for the PTT day unit. Simulations on actual 2003
    data have been performed to illustrate the effect of this potential
    new structure and a Five Year Plan was presented showing how the new
    structure could seamlessly enable a transition from the previous
    five year plan. The next steps include completion of the simulations
    and drafting of a proposed solution(s) by the JTA working group no
    later then September 14^th^ 2004 for the October 2004 JTA meeting.
    (38^th^ O/C)

During the twenty third JTA meeting in Brazil, the meeting asked CLS to
determine the portion of Argos costs to be attributed to the JTA to be
approved by the Operations Committee. Christophe Vassal presented the
methodology to derive the Argos costs to be attributed to the JTA from
the global CLS costs following a 3 step approach using CLS's analytical
accounting principle and distribution by percentage. The meeting took
good note and agreed in principle with the methodology proposed and that
after some detailed elaboration with the JTA working group it could
provide a satisfactory basis for determination of the future JTA share
of operating costs. (38^th^ O/C)

## Status of U.S. processing agreement

The 1994 Agreement exceeded the guaranteed minimum amount of processing
required by 44 platform years, primarily due to a larger than
anticipated drifting buoy program in the Gulf of Mexico. In 1995, the
U.S. requirement is for 725 platform years of processing. Like the JTA,
the U.S. rate was reduced 3.7%. The total value of the 1995 U.S.
Agreement is \$ 2,660,750. (29^th^ O/C)

T. Bryan informed the meeting that the 1996 U.S. JTA costs are nearly
\$3.0M for 805 platforms years. In 1995, the U.S. contracted for 725
platform years and actually used 721.5 platform years. (30^th^ O/C)

R. Bassett informed the meeting that the 1997 U.S. JTA costs are nearly
\$2,5M for 675 platform years. In 1996, the U.S. contracted for 805
platform years and actually used 777 platform years. A report from the
U.S. Government User Group stating Satellite Data Collection and
Location system requirements was entered into the record. (31^st^ O/C)

T. Bryan reported that the United States has committed to 655 platform
years in 1998 and that, with the exception of the Global Drifter
Program, to date there has been minimal interest in taking advantage of
the 35% additional free processing. (32^nd^ O/C)

Steve Auer, the US JTA ROC (Representative Of Country) has implemented a
US JTA website ([www.ogp.noaa.gov/argos](http://www.ogp.noaa.gov/argos))
which is linked to the SAI and NESDIS sites. The US JTA has 500 Argos
programs of which 40% are Non (Federal) Governmental Organizations
(NGO). The US use increased 23% last year; so far, there has been a
negligible increase this year. The US raised its commitment at the 2000
JTA Meeting from 661.6 to 685.0 Ptt/yr in part to help offset the
CLS/SAI income loss expected from the phasing in of Location Plus
service to biologists. The ROC sends invoices to 270 users of which
there are 100 governmental (average 10 Ptt/yr) and 170 NGO (average 1
Ptt/yr). The ROC is concerned that many NGO make payments after service
is rendered which has caused delays in the past for the US in meeting
its quarterly payments to SAI. The ROC suggests it might be advantageous
to all if SAI could collect the actual use JTA fees directly from the
NGO users on their quarterly SAI invoices. Also of concern the ROC only
gets a 50% user response rate in gathering new calendar year
requirements estimates; this presents a problem in making the US
commitment at the annual JTA meeting. Fortunately most of the
non-replies are from small users. A user requirements survey should be
conducted of biologists currently using the Argos system to see what
future system enhancements are desired. So far, no professional
organization has been identified that can speak for biologists like the
DBCP does in gathering and forwarding oceanographer system requirements
to the JTA. The OPSCOM directed NOAA to organize a study of its own
animal applications for future system requirements. The ROC pointed out
that there were JTA Argos user transactions which may have linkage
opportunities for better efficiency and compliance by the users. For
example, the SUA renewal status could perhaps be reported on the annual
JTA Requirements request and, if appropriate, a SUA form could be
attached. Also the JTA invoice could perhaps be linked to the SAI
quarterly invoice for NGO'. (as suggested above). The ROC concluded by
noting that there is significant user frustration with getting good cost
estimates (and the ROC in getting good user estimates). This could
perhaps be mitigated by developing an easy-to-use cost estimating tool
(could be placed on the ROC website) similar to many found on the web
today (e.g., auto.com to purchase and borrow funds for a new car). The
cost tool should provide complete estimates for the CLS/SAI supplemental
costs and the JTA costs. This would bring a level of "no surprises" to
the users to better plan and budget their financial resources. The ROC
will address the items with SAI. (35^th^ O/C)

S. Auer of NOAA, the U.S. Argos JTA ROC, presented the status of the
U.S. JTA. In 2001, the U.S. platform year use increased by 3.7% while
the total number of active platform months only increased by 0.3%. About
75 new users entered the U.S. JTA and these were predominantly
biologists. The ROC paid \$2.7M to SAI for 2001 JTA costs. The ROC
actually collected \$3.2M from users with about \$1M of this amount
comprising advance payments for anticipated 2002 use. About \$0.5M in
user costs remains outstanding (uncollected) primarily from NGO's; this
is becoming more of a concern with the dramatic increase in NGO's over
the past several years and the need to pay SAI promptly and "in full"
each quarter. The ROC is collaborating with SAI to develop creative
techniques to improve collections from this sector. The U.S. signed for
695 platform years in 2002. One expected area of increase is the ARGO
program; it used 11 platform years in 2001 and expects to use 55
platform years in 2002. Biologists have expressed their gratitude for
the phase out of costs for ALP "location Plus service" which will become
part of the basic JTA service for biologists, i.e., "free", in 2003. The
ROC notes that new users are now "by-and-large" better informed about
the JTA procedures and have more realistic expectations of the Argos
system, for example: animal tracking. This change can primarily be
attributed to vast improvements in 24-hour/7-day available website
information at CLS, SAI, NOAA Argos System, and U.S. JTA, and the
implementation of Argos webgroups for biologists. (36^th^ O/C)

The U.S. portion of the Argos Joint Tariff Agreement (JTA) is described.
In 2002, the U.S. used 1402.8 Platform Years (Ptt/yr) and 41,305 Active
Platform Months. For 2003, the U.S. has agreed to purchase 790.0 Ptt/yr
and expects to use 1500 Ptt/yr and 43,400 Active Platform Months.
(37^th^ O/C)

Steve Auer informed the OPSCOM on the status U.S. portion of the Argos
Joint Tariff Agreement (JTA). The total Costs for the U.S. JTA have
risen appreciably increasing 39% the past 3 years (\$2.5M in 2000 to
\$3.5M in 2003); these costs will increase 15% more in 2004 to \$4.0M.
NOAA has borne the biggest JTA cost-growth burden. NOAA costs in 2004
will be 87% more than 3 years ago an additional \$1M! These cost trends
are ominous as total NOAA Argos use could increase by 43% more the next
3 years. In the face of budget reductions and shifting priorities, NOAA
has determined that it must significantly reduce its future JTA cost
participation, and the NOAA cost basis for this must be appreciably less
than its CY 2003 cost. The U.S. ROC and Service Argos Inc. are
continuing their collaboration/partnership toward delivering a
responsive efficient user service. The new JTA invoice collection option
of SAI direct quarterly billing implemented in 2003 is working smoothly.
SAI now handles about 60% of the JTA user invoicing while the ROC still
invoices and collects the vast majority of costs from 100 predominately
Federal users. It is proposed that SAI assume collection responsibility
for all non-NOAA users next year. This will eliminate most of the NOAA
administrative overhead associated with the ROC user invoicing. This
transition in user invoicing/collection responsibility is past due as
NOAA has provided it at no cost to the users or CLS/SAI for over 25
years during which the number of invoice transactions has increased from
4 to over 500. (38^th^ O/C)

## Financial status of Service Argos

Due to stringent control of the expenses and delays in some investments,
Service Argos has reduced the total amount of expenses from 53.4
(scheduled) to 52.5 MF during 1994. In terms of tariff reduction for
JTA, it is equivalent to :

• about 2% (inflation)

• about 4% (27000 to 26000 FF)

• about 2% (reduction of cost)

which resulted in a total reduction of approximately 8%.

After a decrease of non-JTA revenue, Service Argos has reversed the
tendency, increasing this type of income by 15%. The global balance is
positive by 0.4 MF and now the remaining JTA loss is 9 MF. Depending on
the future JTA activity, this loss repayment will likely occur around
1997-1998. (29^th^ O/C)

Service Argos is continuing its efforts to decrease the operating
expenses. The reduction of the tariff for JTA users led to a decrease of
FF1.0M of JTA income. This decrease was compensated by an increase of
FF1.5M of non-JTA income. It is expected that the remaining JTA losses
will be repaid in 1997. (30^th^ O/C)

Mr Cazenave presented the current financial status of CLS / Service
Argos. He showed how the operating costs of the system have stabilized
and indicated that the JTA portion of the cumulative losses had been
reimbursed ahead of schedule. He expressed hope that the system
operating costs should remain relatively stable, increasing at or below
the inflation rate over the near‑term. Globally, the JTA and non‑JTA
income exceeded the operating costs. (31^st^ O/C)

L. Cazenave reviewed the Argos financial status. A highlight was a
proposal to separate the JTA operating cost obligations from the total
effective operating cost of Argos. This approach would enable the JTA to
maintain more control of their costs during the 5 yr. Plan agreed to at
JTA-19. The committee endorsed the approach and agreed that it should be
proposed at JTA-20. (34^th^ O/C)

Michel Cazenave reviewed the Argos financial status. The proposal made
during the 34^th^ Operations Committee to separate the JTA operating
cost obligations from the total operating cost was considered but not
adopted by JTA 20 meeting. The continued increase in JTA accumulated
losses suggest to make a similar proposal to JTA 21 for year 2000
financial result; the OPSCOM concurred and accordingly asked JTA
chairman and CLS/Service Argos to negotiate a suitable financial
agreement by the next JTA meeting (October 25. 2001). (35^th^ O/C)

M. Cazenave reviewed the Argos financial status. The previous proposal
confirmed during the OC 35 to separate the JTA operating cost
obligations from the total operating cost was adopted by the JTA-21
meeting: the annual Argos basic costs, for the purpose of calculating
the JTA share will be capped at the actual 2000 figure (M€ 9.49) to be
then increased by the annual inflating rate. Globally during year 2001,
the expenses increased by 3.9%, incomes by 5.8%.

-   JTA losses increased by 0.12 M€ (accumulated to 1.52 M€). The five
    year plan contemplates a full reimbursement the first year following
    end of the plan.

-   Non JTA losses reimbursement is 1.17 M€.

-   After calculation Global Non JTA remaining loss is 9.84 M€. (36^th^
    O/C)

Christophe Vassal of CLS reviewed the Argos financial status. The
previous proposal confirmed during the OC 35 to separate the JTA
operating cost obligations from the total operating cost was adopted at
the JTA-21 meeting and reiterated at the JTA-22 meeting. The 2002 annual
Argos basic costs, for the purpose of calculating the JTA share, is
capped at the actual 2000 figure (M€ 9.49) to be then increased by the
annual inflation rates for 2001 and 2002 successively. The percentage of
JTA active PTTs versus the total number of active PTTs is also capped at
55% according to FY plan. Globally during year 2002, the incomes of the
agent increased by 5.5% mainly through JTA use increase. It is also
noted that the 2002 JTA contemplates an excess of 0.5 M€ and the JTA
cumulated loss is now 1.02M€. The five year plan (see exhibit \# 24) may
now contemplate a full reimbursement at the end of the plan which is
2004. Reimbursement of non-JTA losses totals in 2002 was 0.41 M€ while
the remaining Global Non-JTA loss is calculated to be 9.71 M€ at the end
of 2002. (37^th^ O/C)

Christophe Vassal of CLS reviewed the Argos financial status. The
proposal to separate the JTA basic cost obligations from the total
effective basic cost of Argos adopted by the JTA-21 meeting is
maintained for the purpose of calculating the annual 2003 Argos basic
costs. The 2003 Argos basic costs for the purpose of calculating the JTA
share will be capped at the actual 2000 figure of M€ 9,49 to be then
increased by the annual inflation rate of 2001, 2002 and 2003
successively. The 2003 JTA structure shows:

-   A calculated Argos basic cost of M€ 10,13

-   A ratio JTA active PTTs/total active PTTs at 58,3% capped at 53,5%
    according to FYP.

Taking this into account, the 2003 JTA contemplates an excess of 0,63 M€
and the JTA cumulated loss is now M€ 0,39 at the end of 2003. The FYP
contemplates a full reimbursement of the JTA loss in 2004 that is the
last year of the FYP. In conclusion, the Five Year Plan is working
perfectly to help put the JTA back on track. In 2003, non JTA income
barely offset non JTA operating expense share. Consequently, the non JTA
accumulated loss at the end of 2003 is calculated at 9,93 M€. (38^th^
O/C)

# O/C MEETING Action Items

ACTION ITEMS COMPLETED

PAST ACTION ITEMS

A - NASA

C - CNES

S - NESDIS

G - JPP IMPLEMENTATION GROUP

+-----------------------------------------------------------------------+
| [18-2-A/C/S: User Problems]{.underline} A file containing the list of |
| identified operator and user problems has been established.           |
+-----------------------------------------------------------------------+
| [18-5-S: Spacecraft Argos Capability]{.underline} NESDIS will         |
| continue operation of a 2nd spacecraft with Argos capability even     |
| though other METSAT sensors have failed unless it conflicts with      |
| SARSAT operations.                                                    |
+-----------------------------------------------------------------------+
| [18-6-S: Fairbanks Test Platform]{.underline} The Post Launch Test    |
| platform at Fairbanks has been repaired but CNES still wants to know  |
| if moving the platform to Toulouse in the future can be handled by    |
| the NESDIS software.(19th O/C). The post launch test platform at      |
| Fairbanks was repaired but not moved to Toulouse as previously        |
| planned. However, the NESDIS software is capable of supporting a move |
| of the platform to Toulouse (20th O/C)                                |
+-----------------------------------------------------------------------+
| [18-8-S: Communications Protocol]{.underline} NESDIS provided Service |
| Argos with the decision on the new communication protocol prior to    |
| September 1984.                                                       |
+-----------------------------------------------------------------------+
| [19-1-A: NOAA-F Ascent Performance]{.underline} NASA provided         |
| documentation of the ascent performance of NOAA-F which was nominal.  |
+-----------------------------------------------------------------------+
| [19-2-C: System User Information]{.underline} CNES presented a report |
| detailing the use of system operator and user information during the  |
| development of the ARGOS-2 system.                                    |
+-----------------------------------------------------------------------+
| [19-3-S: Operation Reports-1985]{.underline} NESDIS prepared and      |
| submitted monthly Argos Operation-Reports for 1985 in accordance with |
| the content and format previously established.                        |
+-----------------------------------------------------------------------+
| [20-1-S: NOAA-H Data Rate Software]{.underline} NESDIS to ensure that |
| the necessary software changes have been made prior to the launch of  |
| NOAA‑H to accommodate the increased data rate (720 to 960 bps) of the |
| Argos instruments.                                                    |
|                                                                       |
| NESDIS indicated that NOAA H is scheduled for launch October 29,      |
| 1987. NESDIS plans to implement the necessary software changes before |
| launch.                                                               |
+-----------------------------------------------------------------------+
| [20-2-S: OMNISTAR Status]{.underline} NESDIS sent CNES a telex July   |
| 1, 1986 indicating that NOAA-K, L, M studies of OMNISTAR are          |
| continuing in parallel to the planning for the current system and     |
| that if OMNISTAR discussions resulted in a bus other than the ATN,    |
| the bus would be required to match Argos ATN specifications.          |
|                                                                       |
| The O/C was informed at the 21st O/C Meeting that OMNISTAR is no      |
| longer being considered as a possible bus for the METSAT program.     |
+-----------------------------------------------------------------------+
| [20-3-A: Advanced DCLS Study]{.underline} NASA to provide results of  |
| Advanced DCLS study to CNES and NESDIS by April 1986.                 |
|                                                                       |
| The results of the Advanced DCLS study was presented to the O/C the   |
| last day of the 20th O/C Meeting.                                     |
+-----------------------------------------------------------------------+
| [20-4-C/S: METSAT Communications Port]{.underline} A second           |
| communications port capability was added to the Meteorological        |
| Satellite (METSAT) Data Processing and Services Subsystem in          |
| November, 1986. The METSAT DPSS transmits DCLS data to the United     |
| States Argos Processing Center (USGPC) located in Landover, Maryland. |
| The Landover facility became operational on January 16, 1987. Data    |
| streams to the new USGPC and Toulouse are identical.                  |
+-----------------------------------------------------------------------+
| [20-5-S: HRPT Data Stream & Data Compression]{.underline} The data    |
| compression portion of this Action Item was completed June 10, 1986.  |
| The DCS data was compressed within the data transmission message sent |
| from NESDIS to Service ARGOS. A typical thirty-minute transmission    |
| has been reduced to approximately seven-minutes. The HRPT data stream |
| extraction portion of this action is scheduled for completion in June |
| 1987. This item was closed by correspondence, CLS,dt/l/88.029. (22nd  |
| O/C)                                                                  |
+-----------------------------------------------------------------------+
| [20-6-G: U.S. Processing Center Operational]{.underline} A schedule   |
| was established by the Joint Project Plan Ground System Managers and  |
| the U.S. Argos Processing Center became operational March, 1987. The  |
| schedule is contained in a letter to J. Koeppen from T. Babits and A. |
| Goasguen dated August 1, 1986.                                        |
+-----------------------------------------------------------------------+
| [20-7-C: Potential System Saturation]{.underline} CLS presented a     |
| study on possible Argos system saturation in the North Sea. After     |
| discussion of the study and proposal of actions made by Mr. Taillade, |
| it was agreed that rather than to refuse admission to a new           |
| applicant, it would be preferable to require more efficient use of    |
| the system.                                                           |
|                                                                       |
| The O/C recommended:                                                  |
|                                                                       |
| 1\. That users who are not using the system efficiently should be     |
| asked to reduce or maintain their use of Argos System capacity when   |
| requesting additional platforms.                                      |
|                                                                       |
| 2\. That review of applications should include an efficiency review   |
| of the users prior system use.                                        |
+-----------------------------------------------------------------------+
| [20-8-A/C/S: Consolidated Report]{.underline} It was agreed that no   |
| structural changes to the Consolidated Report are necessary. It was   |
| also agreed that revisions and additions be made as necessary to      |
| reflect decisions made by the O/C, or to reflect changes made by      |
| signature of the new MOU.                                             |
+-----------------------------------------------------------------------+
| [21-1-C: System Inefficiency Report]{.underline} System performance   |
| in particular areas may degrade during 1992-1993 because of the       |
| expected increase of platforms. To avoid system degradation, CNES     |
| requested that NOAA investigate the possibility of launching NOAA-K   |
| before NOAA-J, (ref, Action Item 22-3-S/A). This recommendation would |
| put the new Argos instrument in orbit at an earlier time than 1993,   |
| launch of NOAA-K. NOAA and NASA agreed to examine the feasibility of  |
| adding to the capacity of the space segment, earlier than the planned |
| launch of NOAA-K.                                                     |
+-----------------------------------------------------------------------+
| [21-2-S: Launch Vehicle Plans]{.underline} All NOAA spacecraft up to  |
| and including NOAA-J will use Atlas launch vehicles. NOAA-K, L, M     |
| will use Titan II launch vehicles.                                    |
+-----------------------------------------------------------------------+
| [21-3-S: VHF Argos Data Down-link Status]{.underline} The new command |
| uplink frequency is 2025.000 MHz with a bandwidth of +/- 250 MHz.     |
| This frequency will replace 148.560 MHz and be phased out when NOAA-J |
| terminates. The DSB VHF 136.77 MHz frequency will also be phased out  |
| with the launch of NOAA-K. The new VHF frequency is 137.35 MHz with a |
| +/- 34 KHz bandwidth.                                                 |
+-----------------------------------------------------------------------+
| [21-4-S/C/A: Reception of Blind Orbit Data]{.underline}               |
|                                                                       |
| NOAA-NESDIS Position. During the NOAA-K, L, M, era, NOAA will not     |
| require the Lannion Station for Blind Orbit Data; also NASA will not  |
| require Lannion for early orbit or contingency support. (22nd O/C)    |
|                                                                       |
| CNES Position. CNES is concerned that by not dumping Global Data for  |
| the 2-3 blind orbits will cause a significant increase in data        |
| delivery time for these orbits. CNES proposed an alternate use for    |
| Lannion an suggested that a Black-Box be used to tap the DCS data     |
| from STIP and HRPT data streams and then send them to the Argos       |
| Processing Centers, (U.S. & French). The objective is to use Lannion  |
| as a stand-alone-station, (no transmission of DCS data by NESDIS      |
| after a test period), and to increase real-time coverage over the     |
| North Sea and the Atlantic Ocean as requested by the Director de la   |
| Meteorologie Nationale, of the French National Weather Service. The   |
| Black-Box will be implemented in July 1988. For this reason, CNES     |
| plans to send a letter requesting NOAA to continue to dump blind      |
| orbits to the Lannion Station during the NOAA-K, L, M, era. (22nd     |
| O/C)                                                                  |
+-----------------------------------------------------------------------+
| [21-5-S/C: Publication of Location Accuracy]{.underline} Figures      |
| Re-identified as Item 22-4-A                                          |
+-----------------------------------------------------------------------+
| [21-6-A: EOS/IRIS Study]{.underline} In concept, an interrogation     |
| scheme would sequentially command and collect data from remote sites  |
| through a 1Mb/sec link resulting in approximately 186 Mbits/day/site. |
| A tentative RF frequency selection was made in the 7-8 GHz region due |
| to spectrum availability and bandwidth considerations. Additional     |
| design studies are planned.                                           |
+-----------------------------------------------------------------------+
| [21-7-S: NOAA San Francisco HRPT Data Access]{.underline} This Action |
| Item has been deferred because of the possibility of acquiring        |
| similar satellite coverage from other central and west coast S-Band   |
| stations.                                                             |
+-----------------------------------------------------------------------+
| [21-8-C: Simplified Tariff Structure]{.underline} Discussion was held |
| a new tariff structure. Reference Section 8.3.2.1 and 8.3.2.2.        |
+-----------------------------------------------------------------------+
| [21-9-C: Financial Inflation Adjustments]{.underline} CLS to include  |
| additional calculations in next-years financial status report to      |
| reflect adjustment for inflation and cumulative loss, adjusted in     |
| French Francs. Discussion was held a new tariff structure. Reference  |
| Section 8.3.2.1 and 8.3.2.2.                                          |
+-----------------------------------------------------------------------+
| [21-10-S: Silver Spring Consolidation]{.underline} The proposed move  |
| of NESDIS to Silver Spring, Maryland will not occur before 1992.      |
+-----------------------------------------------------------------------+
| [22-1-C: Dissemination of New System Capabilities]{.underline} CLS    |
| will inform the users and PTT manufacturers of new Argos system       |
| capabilities, (such as, increased repetition rates, interlaced        |
| messages, decreased message length, intermittent transmission, etc.)  |
| and following the recommendation of the O/C inform them of the need   |
| to take advantage of these capabilities in order to avoid inefficient |
| use of the system and additional cost for data processing. CLS        |
| reported of the different actions taken in order to complete the      |
| Action. (23rd O/C)                                                    |
+-----------------------------------------------------------------------+
| [22-2-S/A: Availability of Spare TIP Words]{.underline} The TIP data  |
| rates for NOAA-I and J were increased to 1200 bps. Unfortunately,     |
| NOAA-D will remain at 720 bps due to cost and schedule constraints.   |
+-----------------------------------------------------------------------+
| [22-3-S/A: Additional DCS Capability Earlier Than                     |
| Planned]{.underline} This action was intended to determine the        |
| feasibility of launching NOAA-K before I, or to place the K           |
| instrument on I. The early launch of K is not possible because of     |
| incompatibility between spacecraft deadlines and instrument delivery  |
| dates. The K instrument requires considerable interface modification  |
| to achieve compatibility with the NOAA-I bus.                         |
+-----------------------------------------------------------------------+
| [22-4-A: Include Location Accuracy Figures in Future                  |
| Publications]{.underline} NASA will use its best efforts to ensure    |
| that the improved location accuracy figures presented by CLS at O/C   |
| 21 are included in future publications.                               |
+-----------------------------------------------------------------------+
| [22-5-S/C: Potential frequency interference from the NOAA-type Wind   |
| Profiler]{.underline} NOAA and CNES will arrange to have letters sent |
| to the WMO for information and distribution and to profiler           |
| manufacturers regarding a ground control interrupt system and         |
| frequency allocation issues.                                          |
+-----------------------------------------------------------------------+
| [22-6-C/S: Winds Profiler Radar - Status]{.underline} The             |
| installation of Winds Profiler Radars (WPR\'s) poses the threat of    |
| frequency interference to Argos. In response, the relevant agencies   |
| in each country are considering the formal process of shifting the    |
| WPR frequency out of 401 - 406 MHz band. Such a decision would        |
| satisfy both WPR operators and the Argos and COSPAS SARSAT operators. |
+-----------------------------------------------------------------------+
| [22-7-S: HRPT Data Availability]{.underline} NESDIS will investigate  |
| providing all HRPT data received at its CDA stations. Several         |
| meetings have taken place on this subject. Technical discussions on   |
| the implementation of the French proposal continue.                   |
+-----------------------------------------------------------------------+
| [22-8-S/C: Alternative Data Reception Sites]{.underline} NOAA and CLS |
| will begin discussion of alternative paths for reception of DCLS      |
| data, given a NESDIS site or major system failure. Discussion will    |
| include system data intercept points and the possibility of CLS       |
| becoming a DOMSAT data user.                                          |
+-----------------------------------------------------------------------+
| [23-1-S: NOAA-D Upgrade]{.underline} If a major delay occurs for the  |
| NOAA D spacecraft schedule, NOAA will reconsider upgrading the Argos  |
| data rate on NOAA D. NOAA cannot reconsider upgrading the Argos data  |
| rates on NOAA D if schedule slips beyond June 26,1990.                |
+-----------------------------------------------------------------------+
| [23-2-S/C: Change to WPR frequency allocation]{.underline} NOAA and   |
| CNES will exchange letters by July 21, 1989, to support each others   |
| efforts to change the WPR frequency allocation. A letter from CNES    |
| should be addressed to Richard Barth, NOAA Radio Frequency Manager,   |
| and to the attention of Mr. C. Wooldridge. A letter from NOAA should  |
| be addressed to the Directeur General du CNES, a l\'attention de Mme. |
| Eydaleine. Letters have been exchanged by NOAA and CNES. It was noted |
| that this frequency issue may not be on the agenda for the 1992 World |
| Administrative Radio Conference (WARC).                               |
+-----------------------------------------------------------------------+
| [23-3-C: Argos / Post NOAA-M]{.underline} CNES will provide in        |
| writing a clarification of the CNES letter (88039/DG) of intent to    |
| provide Argos and SARSAT in the post NOAA-M era. CNES provided        |
| clarification to this letter.                                         |
+-----------------------------------------------------------------------+
| [23-4-C: IPOMS/ICWG Discussions]{.underline} NOAA will keep the O/C   |
| apprised of discussions taking place in the IPOMS and ICWG. Rather    |
| than continue this action item, the O/C established a new action item |
| (24-3).                                                               |
+-----------------------------------------------------------------------+
| [23-5-S/C: Non-Environmental Use]{.underline} NOAA and CNES will      |
| establish a Working Group to propose to the O/C Co-chairs guidelines  |
| for implementing non environmental use of the system. These           |
| guidelines will be available prior to the Ninth JTA Meeting in        |
| October 1989. O/C Co-chairs will exchange letters by July 21, naming  |
| members of the Working Group. New guidelines were developed,          |
| presented and signed by the Co-chairs.                                |
+-----------------------------------------------------------------------+
| [23-6-S/C: Fishing Vessel Tracking Applications]{.underline} NOAA and |
| CNES will establish the Working Group to study and develop            |
| recommended guidelines for applications concerning the tracking of    |
| fishing vessels. O/C Co-chairs will exchange letters by July 21,      |
| naming members of the Working Group. A working group on fishing       |
| vessel tracking met on several occasions to discuss and agree on the  |
| best way to handle the expected number of fishing vessels using the   |
| Argos system. Assistance was provided to NOAA NMFS (National Marine   |
| Fisheries Service) during technical discussion with Japan, South      |
| Korea and Taiwan.                                                     |
+-----------------------------------------------------------------------+
| [24-1-A: Argos location accuracy figures]{.underline} NASA will make  |
| corrections to Argos location accuracy figures when it publishes the  |
| information pamphlets for NOAA-I. A draft should be available 6       |
| months prior to the schedule launch of NOAA-I and will be distributed |
| by NASA for review and comment. Reference to exact number of PTT's    |
| will be eliminated from the NOAA I information pamphlets. CNES was    |
| asked to provide all changes to the presented material by the close   |
| of the 25th Argos O/C Meeting.                                        |
+-----------------------------------------------------------------------+
| [24-2-S/C: WPR Frequency Status]{.underline} The \"Status of Wind     |
| Profiler Radar (WPR) Frequency Allocations\" will be included as an   |
| agenda item in section \"J\" (Miscellaneous) for the next O/C         |
| meeting. The actions taken by NOAA and CNES for the frequency         |
| allocation of the Wind Profiler Radar (WPR) met the O/C               |
| recommendations. The frequency allocation planned by the U.S. in the  |
| 440/450 MHz band is satisfactory for Argos. NOAA and CNES will        |
| continue to monitor the situation.                                    |
+-----------------------------------------------------------------------+
| [24-3-S: IPOMS/ICWG Discussions]{.underline} NOAA will keep the O/C   |
| apprised of discussions taking place in IPOMS and ICWG. NOAA will     |
| continue to provide copies of minutes of ICWG Meetings. (continuing   |
| action)                                                               |
+-----------------------------------------------------------------------+
| [24-4-S: NOAA-K in place of NOAA-J]{.underline} NOAA will             |
| definitively answer questions from CNES regarding the launch of       |
| NOAA-K in place of NOAA-J. NOAA has concluded that a launch of NOAA K |
| before NOAA I cannot be considered at this time. An out of sequence   |
| launch would negate certain programmatic agreements, require          |
| accelerated instrument deliveries, and adversely impact scheduled     |
| plans for ground system changes and upgrades.                         |
+-----------------------------------------------------------------------+
| [24-5-S: NOAA-N]{.underline} NOAA will send a letter to CNES          |
| affirming the procurement and launch of NOAA-N. NOAA provided copies  |
| of letters between NOAA and CNES confirming procurement and launch    |
| plans for NOAA N.                                                     |
+-----------------------------------------------------------------------+
| [24-7-S NOAA Playbacks at Lannion]{.underline} NOAA will confirm its  |
| intent to continue the playback of blind orbits over Lannion for the  |
| NOAA K, L, M series. NOAA will provide STIP or SAIP data at Lannion.  |
+-----------------------------------------------------------------------+
| [24-8-C: NOAA-9, 10 STIP]{.underline} CNES will request in writing    |
| that NESDIS send enough data from NOAA-9 and 10 to continue           |
| orbitography processing so as to maintain these two stand-by S/C in   |
| hot redundancy. A letter was received by NOAA in June. NOAA responded |
| to the 3 proposals presented. Regarding STIP data (from NOAA 9, 10)   |
| over the Toulouse reference PTT, NOAA indicated that this would not   |
| be provided.                                                          |
+-----------------------------------------------------------------------+
| [25-1 S: Ingest Data]{.underline} NOAA to supply planned ingest       |
| schedule for STIP data on NOAA-9, 10 to CNES as soon as possible but  |
| not later than September, 1991. NOAA supplied a memo from Benjamin    |
| Watkins, Chief, Satellite Service Division, NESDIS, dated September   |
| 13, 1991 to Mr. Claude Gal, CNES containing the requested schedule.   |
+-----------------------------------------------------------------------+
| [25-2 N DCS Performance in Publications]{.underline} NASA to insure   |
| publication of the revised DCS performance parameters in the NOAA I   |
| launch data book. NASA\'s Metsat project published the NOAA I launch  |
| information pamphlet.                                                 |
+-----------------------------------------------------------------------+
| [25-3 S/C: JTA Representation]{.underline} CNES and NOAA to appoint   |
| representatives to JTA / Deficit reduction working group as soon as   |
| possible. Representatives were appointed.                             |
+-----------------------------------------------------------------------+
| [25-4 S/C: JTA/Deficit Reduction Working Group]{.underline} The       |
| JTA/Deficit Reduction working group shall review the JTA charter and  |
| guideline, and all associated correspondence. The working group shall |
| provide recommendation to the Argos O/C on the JTA's funding of Argos |
| Operating costs and deficit reduction. Recommendation was made to the |
| O/C Co-chairs, and was accepted by them. This recommendation was      |
| provided to the Chairman of the JTA. A historical paper on the role   |
| and guidelines of the JTA was presented at the 26th O/C Meeting.      |
+-----------------------------------------------------------------------+
| [25-5 S/C: Commercialization Working Group]{.underline} The Co-chairs |
| will appoint an ad hoc working group whose task is to provide         |
| recommendations to NOAA and CNES on commercialization and other       |
| policy issue during the negotiation of the agreement for Future Argos |
| collaboration. This group will report back regularly to the Co-chairs |
| on the progress of its discussions. The Co-chairs appointed members   |
| to the working group. No significant discussions have taken place on  |
| a future agreement.                                                   |
+-----------------------------------------------------------------------+
| [26-1-N: NOAA-K,L,M Deployment Schedule]{.underline} Provide revised  |
| NOAA K, L, M development schedule to NOAA for relay to CNES as soon   |
| as available. NASA presented the latest information available,        |
| reflecting a restart of the NOAA-K effort in July 1992.               |
+-----------------------------------------------------------------------+
| [26-2-S/C: Argos Evolution Working Group]{.underline} The O/C will    |
| establish an ad hoc working group to consider further evolution of    |
| the Argos mission and configuration. The Co-chairs will appoint       |
| members to the working group by May 5, the Working group will report  |
| back to the Co-chairs by August 1, 1992. NOAA responded in a letter   |
| of May 15, 1992, naming members and proposing that CNES prepare an    |
| initial paper of this issue. Considering that such discussions are    |
| only applicable to post NOAA Q, it was decided that any activity      |
| would be premature at this time.                                      |
+-----------------------------------------------------------------------+
| [26-3-C: Non-environmental Use Report]{.underline} CLS will provide a |
| draft of the non-environmental usage quarterly report by May 1, and   |
| will submit reports to NOAA quarterly thereafter. NOAA indicated that |
| reports have been regularly received by the U.S. Argos O/C            |
| Secretariat. Subsequently, these reports have been distributed to the |
| U.S. Committee participants and accepted. Several recommendations to  |
| expand the utility of these reports were presented.                   |
+-----------------------------------------------------------------------+
| [26-4-S: Revised MOU]{.underline} NOAA proposed that a new NOAA-CNES  |
| Argos MOU be signed by spring 1993. NOAA and CNES will consult each   |
| other to establish a date and location for a MOU negotiating session  |
| in October 1992. NOAA and CNES decided to postpone the October        |
| Meeting in light of the NOAA-EUMETSAT/ESA negotiations being delayed. |
+-----------------------------------------------------------------------+
| [26-5-C: Argos Joint Project Plan (JPP) Update]{.underline} NOAA,     |
| NASA and CNES will review the text of the JPP and provide any         |
| modifications to C. Wooldridge of NOAA by July 1, 1992. Extended to   |
| July 1, 1993, after which Mr. Wooldridge will make arrangements to    |
| have revised copies approved and signed.                              |
|                                                                       |
| [27-1-C/S: NOAA-N\' Argos Instrument]{.underline} For the NOAA-N\'    |
| mission, NOAA will inform CNES how soon a formal commitment is        |
| required for provision of an Argos instrument. NOAA and CNES will     |
| investigate the acceptability of providing a letter of intent as an   |
| interim measure. Concerning the NOAA-CNES Memorandum of               |
| Understanding, negotiation, conclusion, and signature or preferably   |
| amendment of the current Argos Memorandum of Understanding, covering  |
| NOAA N\', METOP-1, and 2, should be conducted in the same time frame  |
| as the NOAA-EUMETSAT Memorandum of Agreement, thus signature by       |
| mid-1995. AN extension of the 1986 MOU were agreed upon by letter     |
| exchange in 1998.                                                     |
+-----------------------------------------------------------------------+
| [27-2-C/S Establish a schedule for post NOAA-N MOU discussions /      |
| negotiations.]{.underline}                                            |
|                                                                       |
| NOAA and CNES representatives met in Washington, April 25-27, 1995,   |
| to address the future agreements structure in light of the            |
| CNES-EUMETSAT discussions on possible direct relationships for Argos  |
| on the METOP program. On April 27, 1995, CNES and NOAA                |
| representatives met with EUMETSAT Director Morgan and his staff.      |
+-----------------------------------------------------------------------+
| [27-3-C/S/N Argos JPP Update]{.underline} NOAA, NASA and CNES will    |
| review the text of the JPP and provide any modification to C.         |
| Wooldridge of NOAA by July 1st, 1993, after which C. Wooldridge will  |
| make arrangements to have copies approved and signed. A revised draft |
| of the Argos Joint Project Plan (JPP), which incorporated comments of |
| CNES, NOAA, and NASA, was distributed for final review and            |
| concurrence. The text of the JPP was finalized at the Meeting with    |
| the intent of having the revised documents signed by each agency by   |
| Oct. 1, 1994.                                                         |
+-----------------------------------------------------------------------+
| [27-4-C/S: Non-JTA Growth]{.underline} NOAA and CNES will form an ad  |
| hoc working group to investigate opportunities for growth outside the |
| JTA. NOAA and CNES will inform each other of their respective working |
| group members by July 15, 1993. Discussions were held to address this |
| matter. Since CLS/Service Argos is responsible for marketing the      |
| Argos system, the Committee decided that non-JTA growth opportunities |
| would be discussed on a case-by-case basis, as necessary.             |
+-----------------------------------------------------------------------+
| [27-5-S: FCC Licensing]{.underline} In regard to the FCC licensing    |
| process, NOAA will investigate the level of flexibility for           |
| commercial entities using the Argos frequency in the U.S. for         |
| environmental and limited non-environmental applications. NOAA        |
| presented guidance received from Richard Barth, the Department of     |
| Commerce frequency manager. It was suggested that this guidance be    |
| provided as an insert for Argos applications. After reviewing the     |
| proposed insert for Argos licenses, the O/C recommended clarification |
| for exactly which users will be impacted. Since this new policy will  |
| be implemented sometime in 1994, clarification is needed as soon as   |
| possible. Service Argos and NOAA will work together on a notice to    |
| the users (Item 28-1). (28th O/C)                                     |
+-----------------------------------------------------------------------+
| [28-1-C/S: FCC Licensing]{.underline} Service Argos Inc. and NOAA     |
| will work together to create a notice to users about FCC licensing    |
| requirements by June. CLS wrote a draft notice that was reviewed by   |
| NOAA. Notice to users was disseminated on June 6, 1994.               |
+-----------------------------------------------------------------------+
| [28-2-C/S/N: JPP Signatures]{.underline} The revised Joint Project    |
| Plan will be signed by each of the signatory agencies by Oct. 1,      |
| 1994.                                                                 |
|                                                                       |
| CNES and NASA will review the 1987 JPP and will provide modifications |
| to NOAA by August 31, 1996. NOAA will incorporate these modifications |
| and complete an exchange of letters with NASA vis-à-vis NASA          |
| responsibilities. NOAA will revise the cover page and signature page  |
| to reflect this change and will provide to CNES by October 1, 1996    |
| (30^th^ O/C)                                                          |
|                                                                       |
| A new action will be reconsidered when needed to incorporate planning |
| details for NOAA‑N\' (31^st^ O/C)                                     |
+-----------------------------------------------------------------------+
| [28-5-C/S: Third-satellite Data]{.underline} A working group composed |
| of M. Weaks, J. Silva, J. Budd, A. Shaw, R. Rolland will investigate  |
| ways to improve the availability of Argos data from three satellites. |
| As a result of this action, technical discussions between SAI and     |
| NOAA/NESDIS staff have been initiated and will be ongoing. The        |
| Co-Chairs will respond to the letter of December 12, 1995, from the   |
| JTA Chair on the availability of Argos data from a third satellite    |
| before the next JTA meeting scheduled for October 29-30, 1996.        |
| (30^th^ O/C)                                                          |
+-----------------------------------------------------------------------+
| [28-6-C/S/N: Down-Link Messaging Capability (Command Link)            |
| Request]{.underline} The French Co-Chair will provide a letter to     |
| NOAA formally proposing the enhanced Argos DCS command link           |
| capability presented at the Operations Committee meeting. The letter  |
| was prepared and submitted January 5, 1995. The letter indicated a    |
| meeting would be held to present technical characteristics.           |
+-----------------------------------------------------------------------+
| [28-7-C: Down-Link Messaging (Command Link) Antenna]{.underline} By   |
| mid-September, CNES will provide to NOAA and NASA results of a        |
| preliminary study of a UHF command link transmit antenna and a        |
| frequency allocations proposal. NOAA and NASA will respond to the     |
| proposal by the end of the year. See 28-6-C/S/N                       |
+-----------------------------------------------------------------------+
| [28-8-S: Instruments for Future Satellites]{.underline} The NESDIS    |
| Assistant Administrator will send a letter to the CNES Director       |
| General on provision of Argos instruments on NOAA N\' and METOP-1 and |
| 2. The letter from the NESDIS Assistant Administrator has been        |
| received by CNES.                                                     |
+-----------------------------------------------------------------------+
| 29-1-C/S Updated Consolidated Report                                  |
|                                                                       |
| CNES and NOAA will review the updated Consolidated Report before      |
| release of the document. Comment and approval with the possibility to |
| add supplemental explanatory material as introduction for a new       |
| reader, will be provided to SAI by the end of June in order for CNES  |
| to be able to provide the report to NASDA and EUMETSAT for            |
| information for ADEOS and METOP cooperation. SAI incorporated         |
| comments from reviewers of the Consolidated Report and provided this  |
| to CNES and NOAA for approval. The final report was also distributed  |
| to NASDA and EUMETSAT.                                                |
+-----------------------------------------------------------------------+
| 29-2-S Possibility of raising the orbit of NPOESS to 1000 km          |
|                                                                       |
| NOAA will report back to the Committee information concerning earlier |
| questions about the possibility of raising the orbit of NPOESS to     |
| 1000km. The IPO considered last year raising the altitude of the      |
| NPOESS constellation to 1000km. After conducting an analysis of the   |
| reliability of the NOAA and DMSP in-orbit assets, the IPO decided to  |
| delay the final decision on orbit altitude until the spacecraft       |
| design study is completed. For now, the nominal altitude for NPOESS   |
| is 850km.                                                             |
+-----------------------------------------------------------------------+
| 29-3-C/S Acquiring Argos data from ADEOS-II                           |
|                                                                       |
| NOAA and CNES will discuss alternative approaches to acquiring Argos  |
| data from ADEOS-II. See section 4.3.3.5 (30^th^ O/C)                  |
+-----------------------------------------------------------------------+
| 29-4-C/S Argos instrument proposed for N\'                            |
|                                                                       |
| CNES will provide to NOAA technical information on the Argos          |
| instrument proposed for N\' as soon as possible so NOAA may have an   |
| accommodation study completed by the end of 1995. See section 4.3.3   |
| (30^th^ O/C)                                                          |
+-----------------------------------------------------------------------+
| 29-5-C/S Basic user requirements for location and data collection     |
| services                                                              |
|                                                                       |
| CNES and NOAA will schedule a bilateral discussion in Fall 1995 to    |
| examine more thoroughly the future basic user requirements for        |
| location and data collection services, drawing upon the conclusions   |
| of the fifteenth Argos JTA meeting. See section 4.3.3 (30^th^ O/C)    |
+-----------------------------------------------------------------------+
| 29-6-C NOAA-K launch handbook                                         |
|                                                                       |
| CNES will provide comments on the description of the DCS in the       |
| NOAA-K launch handbook by September 1995. NOAA will send the draft    |
| NOAA-K handbook to CNES by July 17 1996. CNES will provide comments   |
| to NOAA who will provide to NASA (30^th^ O/C). CNES provided comments |
| to NOAA on the NOAA‑K handbook. (31^st^ O/C)                          |
+-----------------------------------------------------------------------+
| 29-7-C CNES/EUMETSAT and CNES/NASDA MOU's                             |
|                                                                       |
| CNES will inform NOAA on the progress made in the negotiations of     |
| bilateral MOUs (CNES/EUMETSAT and CNES/NASDA) by end of 1995. CNES    |
| provided NOAA with near-final version of the CNES/NASDA Argos MOU     |
| dated July 3 1996 for comments.                                       |
+-----------------------------------------------------------------------+
| 29-8-C/S Revision of the CNES/NOAA MOU                                |
|                                                                       |
| O/C members will provide comments on the proposed revision of the     |
| CNES/NOAA MOU that was prepared and presented by NOAA by end of July  |
| 1995. C. Wooldridge reported that NOAA and CNES have agreed to amend  |
| the current Argos MOU to cover NOAA-N. NOAA and CNES will coordinate  |
| a draft exchange of letters to accomplish this amendment in the same  |
| timeframe as the completion of the NOAA-EUMETSAT MOU which is         |
| expected by December 1996. (30^th^ O/C)                               |
+-----------------------------------------------------------------------+
| 29-9-C/S/A Roles and responsibilities of the Operations Committee     |
|                                                                       |
| O/C members will review and make recommendations on the roles and     |
| responsibilities of the Operations Committee during their review of   |
| the new draft MOU. Once agreement has been reached on this language,  |
| NOAA and CNES will jointly develop a Terms of Reference for an        |
| expanded Operations Committee providing guidelines on participation,  |
| membership, conduct of meeting, etc. by the end of March 1996.). C.   |
| Wooldridge (NOAA) and L. Ruiz (CNES) will coordinate development of a |
| draft Terms of Reference by the end of December 1996.                 |
|                                                                       |
| NOAA and CNES agreed in principle on a Terms of Reference for an      |
| expanded Operations Committee in March 1997. (31^st^ O/C)             |
+-----------------------------------------------------------------------+

30-1-S Extension to the current NOAA-CNES Argos MOU to cover NOAA-N'

NOAA will send a letter to CNES proposing an extension to the current
NOAA-CNES Argos MOU to cover NOAA-N'. NOAA will coordinate a draft of
this letter with CNES. NOAA and CNES agreed upon the text of a MOU
amendment package including the exchange of letters to effect the
amendment. NOAA and CNES to complete exchange of letters by December 31,
1997. (31^st^ O/S) Combined with 31-12-C/S. (32^nd^ O/C)

30-2-S DCS for NOAA-N' and NPOESS

NOAA will schedule a meeting between CNES and IPO for Fall 1996 with the
Integrated Program Office (NPOESS Program Management) to discuss DCS for
NOAA- N' and NPOESS.

NOAA and CNES representatives met with IPO staff on December 11, 1996.
(31^st^ O/C)

30-3-C Future additions of the Argos Applications form

For future additions of the Argos Applications form, CNES will include
the following:

\"UPON SIGNATURE BY ALL PARTIES THIS APPLICATION CONSTITUTES AN ACCESS
AGREEMENT.\" No longer applicable with the completion of Action Item
31-10-C/S, the drafting of a new \"System Use Agreement (SUA).\" (32^nd^
O/C)

30-4-C Wording of the Argos Application

CNES will change the current wording of the Argos Application to change
\"memorandum\" to \"document\" specifically: \"Except for such provision
as may be established elsewhere in this DOCUMENT, data collected for
users may be made available by the Operator to other interested
parties.\"

CNES changed the word \"memorandum\" to \"document\" in the revised
Argos Application provided at the meeting. (31^st^ O/C)

30-5-C Available commercial services in Argos Application form

CNES will modify the current Argos Application form to ask users if they
have considered use of available commercial services to meet their
needs. If they have, the form would request information on why the
commercial service cannot meet their program needs in terms of capacity,
speed, reliability, etc.

The Argos application was modified accordingly. (31^st^ O/C)

30-6-C/S Availability of commercial services and assessing impacts
vis-a-vis current Argos operations

C.) A Task Team comprised of members to be identified by the Co-chairs
by August 1 will actively assist in analyzing availability of commercial
services and assessing impacts vis-a-vis current Argos operations and
planning for future systems. This group will provide the following
deliverables to the Co-chairs:

1.  by November 1, 1996 \-- prepare an analysis of the impacts of
    discontinuing commmercial non-environmental use and a proposal to
    implement any resulting recommendations.

2.  2\. by November 1, 1996 \-- review and comment or draft presentation
    materials to be presented at the NOAA Public Meeting in the U.S. in
    the Fall.

3.  3\. by January 1997 \-- provide an analysis of Fall public meeting
    and proposed recommendations for next steps on future evolution of
    Argos system.

NOAA and CNES Task Team met in December 1996, and March 1997 on system
use policy. NOAA and CNES coordinated relevant materials, documentation
and activities. See section 7.1.1. (31^st^ O/C)

30-7-C/S Answer to JTA Chair on the availability of Argos data from a
third satellite

The Co-Chairs will respond to the letter of December 12, 1995, from the
JTA Chair on the availability of Argos data from a third satellite
before the next JTA meeting scheduled for October 29-30, 1996.

A letter was prepared and sent by Operations Committee Co‑Chairs to JTA
chairman. Letter is attached as O/C 31-Exhibit \# 4. (31^st^ O/C)

30-8-C CNES/NOAA/NASDA meeting

CNES will coordinate a CNES/NOAA/NASDA meeting to take place in early
1997.

CNES, NASDA and NOAA met on March 18, 1997, in Paris. (31^st^ O/C)

30-10-C Enhanced ARGOS-2 unit for possible integration on NOAA-N

CNES will provide technical information on the enhanced ARGOS-2 unit for
possible integration on NOAA-N. This unit will comprise an additional
box on the ARGOS-2 unit to incorporate the forward message capability.

A letter was sent to CNES indicating NOAA\'s decision not to include the
forward messaging capability on NOAA‑N. Claude Gal (CNES) confirmed the
decision in a phone conversation with Jim Silva (NOAA). (31^st^ O/C)

31-1-C Argos-3 / SARP-3 Designs prior to the System Design Review

CNES will organize a technical meeting with NASA and NOAA
representatives (late November time frame) to review Argos-3 / SARP-3
Designs prior to the System Design Review (SDR / January 1998).
Reference agenda item E-3. NOAA and NASA will provide comments to CNES
by end of January 1998. During the Argos-3/Sarsat-3 Technical Interface
meeting in December 1997, NASA and Lockheed Martin met with CNES
representatives and reviewed the Argos-3/SARP-3 design. The memorandum
dated February 28, 1998, sent by M. Mignogno (NOAA) addressed most of
the critical action items including design issues which could affect the
accommodation of Argos-3 and SARP-3 instruments on the NOAA-N'
satellite. The comments were accepted. (32^nd^ O/C)

31-2-C/S Argos-3 Mission Specification document

Operations Committee will approve the revised Argos-3 Mission
Specification document (Reference agenda item E-7 including additional
page for message transmission/acknowledgement requirement). CNES will
send a draft copy to NASDA by September 1997. The Argos-3 Mission
Specification document was revised during OC 32 to reflect the
capabilities of the system deployed on METOP 1-3 and NOAA N'. The text
of the revised document was reviewed and approved by the Operations
Committee and distributed as an annex to the NOAA/CNES meeting minutes
of September 11, 1998 (32^nd^ O/C)

31-3-C/S Common metrics to report end-to-end system performance

CNES and NOAA will form a Task Group to adopt common metrics to report
end‑to‑end system performance including processing statistics. The Task
Group in the future will include participation from NASDA and EUMETSAT
to standardize system‑wide reporting. Preliminary discussions took place
with CLS in December 1997. Current metrics were discussed with NOAA in
June 1998. Ground processing discussions during OC 32 highlighted the
need to identify a common approach to measure system performance
utilizing well defined parameters such as processing thresholds,
performance objectives, etc. NOAA defined the current metrics for the
U.S. data processing system at OC 33 and proposed that these metrics
serve as a baseline for continuing discussions. New Action Item opened
(34-3-C/S) to coordinate with NASDA and EUMETSAT in the definition of
final parameters..(34^th^ O/C)

31-5-C/S NOAA\'s User Agreements data base reporting requirements

CNES and NOAA will form a Task Group to discuss and implement NOAA\'s
User Agreements data base reporting requirements.

Preliminary discussion with CLS, December 1997 followed by letter of
January 22, 1998, providing initial listing of Non-Government and
Non-environmental programs. Listing expanded to include all categories
of programs. Continuing to refine informational requirements and
reporting frequency. (32^nd^ O/C). NOAA/CLS discussions in February 1999
refined requirements based upon SUA format (see 33^rd^ O/C Exhibit \# 15
). CNES to provide NOAA with semi annual updates of the requested
database beginning in September, 1999 until Argos 2001 SUA database is
functional (33^rd^ O/C) CLS provided initial database. Argos 2001
database (Oracle) estimated to be completed in late 2000. (34^th^ O/C)

31-7-S Technical and cost impacts of receiving all modes of ADEOS II

NOAA will coordinate with NASA and NASDA to assess the technical and
cost impacts of receiving all modes of ADEOS II DCS data and implement
as feasible.

Gene Legg of NOAA reports that CNES\'s proposal for a redundant DCS data
path for ADEOS II, has been agreed to by the U.S. (NOAA‑NASA) and NASDA
and has become part of the interface control documents, signed by the
U.S. and Japan.

During Mode 1 operations, NASDA will receive all recorded DCS data, and
send to CNES/Tokyo‑NASDA as well as NOAA. U.S. ground stations (ASF and
Wallops) will receive Real‑Time DCS and forward similarly. Kiruna and
EOC will receive real time DCS and forward to NASDA/Tokyo and NOAA.

During Mode 2 operations, DCS recorded data will be dumped at Wallops,
ASF, Kiruna, and EOC and sent to NOAA and NASDA (for CNES/Tokyo‑NASDA).
Real Time DCS will be received at the ground stations and forwarded as
in Mode 1.

There are no additional or incremental costs, as the data sets are very
small in relation to GLI and AMSR data moving back to the U.S. Costs on
trans‑Pacific link are shared by US and Japan. Communications costs
between Kiruna and EOC have the responsibility of NASDA. Costs for
moving data from ASF/WFF to NASDA and NOAA are responsibility of
NASA/NOAA. (32^nd^ O/C)

31-10-C/S "System use Agreeement" and the "Program Description"

CNES and NOAA will form a writing team to draft the \"System use
Agreeement\" and the \"Program Description\". The team will be composed
of K. Alvarez, R. Bassett and C. Wooldridge for NOAA, and L. Mesnier, L.
Ruiz and J. Wingenroth for CNES/CLS. The documents should be prepared as
soon as possible, but it should be noted that changes may be necessary
once the US regulatory process is completed. The team will also look
into an electronic edition of the form.

The SUA was revised during OC 32 and approved by the Operations
Committee. (32^nd^ O/C)

31-12-C/S MOU to include N\'

NOAA to send a letter to CNES, proposing to modify the MOU to include
N\' (objective May 1997). Letter sent on July 07, 1998 (32^nd^ O/C)

31-13-C/S MOU to include N\'

CNES to answer the NOAA\'s letter within two months after reception.
Letter sent on July 15, 1998 (32^nd^ O/C)

31-15-C/S Terms of Reference of an expanded operations Committee
(including NOAA, NASDA, EUMETSAT and CNES).

A working group composed of C. Gal, L. Ruiz, M. Cazenave, K. Alvarez, R.
Bassett and C. Marzin will prepare a revised draft of the Operations
Committee Terms of Reference by the end of 1998, for approval at the
33^rd^ Operations Committee meeting and subsequent inclusion in the
consolidated report. The Terms of Reference need to fully reflect the
current mode of operation of the Argos Operations Committee meeting in
order to prepare for the future involvement of EUMETSAT and NASDA. The
working group will provide EUMETSAT and NASDA with copies of working
papers for comment as appropriate.

The Terms of Reference for the Argos Operations Committee were discussed
during meetings attended by NOAA, CNES and CLS on September 10-11, 1998.
Meeting minutes were sent to NASDA and EUMETSAT. Results of the
discussion were presented under Agenda Item H-2 and the Terms of
Reference were approved and will be included in chapter 2.2 of the
Consolidated Report. (33^rd^ O/C)

32-1-S Plans for processing Argos DCS data from "Operational and non
operational Satellites

NOAA will clarify the plans for processing Argos DCS data from
"Operational Satellites" and other non-operational (i.e., standby or
retire) satellites. NOAA will examine current and past practices by NOAA
and explore opportunities to maximize Argos data recovery with future
satellites flying the Argos instrument and provide the information to
CNES and CLS.

As discussed during the meetings on September 10-11, 1998, NOAA outlined
the current funding policy for maintaining two, operational
polar-orbiting satellites. Argos DCS data recovery from other
non-operational (i.e., standby or retire) satellites has been performed
on a "case by case" basis when these satellites are utilized to augment
the operational constellation. (32 O/C)

32-2-C Central frequencies for future Argos platforms

The Argos Operations Committee, recognizing the need to optimize the use
of the frequency bandwidth, currently allocated to the Argos System
401.650 MHZ +/- 12 KHz, resolves:

\- that the central frequency to be used by future Argos Data Collection
Platforms be 401.650 MHZ, 401.648 MHZ and 401.652 MHZ. All three
frequencies being equally used,

\- that CLS shall take the necessary measures for manufacturers to
develop corresponding Argos DCPs,

-   that CLS should undertake the necessary studies to further optimize
    the utilization of the band allocated to the Argos System.

CLS sent a letter to each transmitter manufacturer, followed by visits
in order to collect their recommendations on implementing the move away
from the Central Frequency. The general attitude of all the
manufacturers was constructive and none were openly opposed to the
assignment of frequencies. A final meeting with all manufacturers is
scheduled for 6-10 September in Largo, Maryland. Resulting from a study
conducted in conjunction with CNES for Argos-3, a proposal to optimize
the utilization of the frequency bandwidth allocated to Argos-2 as well
as to Argos-3 was presented. After discussion, this proposal was
approved by the Operations Committee and should be implemented in
February 2000 after the launch of NOAA-L (33^rd^ O/C)

32-3-N NOAA L to N' schedule

NASA/GSFC will provide CNES with Spacecraft Integration and Test
schedules for NOAA L, M, N, and N' as they are updated.

NASA provides schedules as available throughout the year and provided an
update at the 33^rd^ OPSCOM meeting (33^rd^ O/C)

32-4-C Alternate operational scenarios involving nominal and stand-by
satellites

CLS will identify and describe alternate operational scenarios involving
nominal and stand-by satellites to maximize data collection and to
report results to NOAA, EUMETSAT, and CNES. This input will be
considered by NOAA, EUMETSAT, and CNES in the definition of NOAA and
EUMETSAT ground segment operations.

M. Cazenave stated that the satisfaction of the large diversity of Argos
users requires non only reliability of data collection but also regular
updating of the data collected with short delays in reception and
distribution. The most optimal scenario should then require the maximum
utilization of all existing payloads. More than 20 years of experience
in operations have demonstrated that the average lifetime of the
satellites is approximately 7 years. Assuming this is likely to continue
and including ADEOS-11 and METOP satellites, a constellation of 5 to 6
satellites could be available in the future. Reception of all data
collected by these satellites, even in slightly delayed mode as it has
been the case throughout 1999, will allow to improve Argos contribution
to worldwide science and governmental requirements. (33^rd^ O/C)

32-5-N/S Comments to METOP ICD

CNES will deliver to EUMETSAT and NOAA identical ARGOS/3 instruments.
NASA/GSFC will produce a Unique Instrument Interface Specification
(UIIS) for NOAA-N' which is identical in technical content with that for
METOP. NOAA/NASA will review the METOP ICD and provide comments to CNES
by August 15, 1998. A draft UIIS will by sent to CNES for review by
September 30, 1998. NOAA letter sent September 4,1998 with review
comments. (32^nd^ O/C)

32-6-C/S CANSAT satellite

NOAA and CNES to check whether the CANSAT satellite may interfere with
the Argos system and to request their respective regulatory authorities
to undertake the appropriate coordination measures. Recommend EUMETSAT
and NASDA request similar coordination measures from their regulatory
authorities.

NOAA calculations (April 14, 1998) indicated CANSAT interference with
GOES and consequently Argos DCS. Federal Communications Commission
message to Canadian official (July 16,1998) highlighted U. S. concerns
that the CANSAT-LL2 may be a source of harmful interference to a number
of U.S. systems. ESA letter of July 15,1998, outlined the concerns of
EUMETSAT and ESA member states in a protest note to the ITU. CNES to
discuss with NASDA. (32^nd^ O/C) CNES reported that upon consultation
with the ITU it was discovered that since there are no allocations for
Missile Satellite Systems (MSS) in the 401-406 band then CANSAT has no
right to request coordination in this band where the DCS system
operates. (33^rd^ O/C)

32-7-C Master beacons in Fairbanks

CNES to send letters to NOAA and EUMETSAT about the possible
implementation of master beacons in Fairbanks and at the planned
EUMETSAT CDA.

CNES letter of July 29, 1998, requesting feasibility study sent to NOAA.
NOAA concurrence sent September 4, 1998. (32^nd^ O/C) A new action
Action was opened to begin coordination with EUMETSAT. (33^rd^ O/C)

32-8-C Brazilian DCS

CNES to send a letter to provide NOAA with the status of CNES/INPE
discussions related to the coordination between the DCS and the
Brazilian DCS.

Status letter sent to NOAA on July 15, 1998. CNES will continue to
update NOAA on further developments using the framework of the Argos
OPSCOM. (32^nd^ O/C)

32-9-C/S Update Consolidated Report

Update Consolidated Report for the purpose of making it more convenient.
Present Consolidated Report at the 33^rd^ OPSCOM meeting.

Following NOAA/CLS discussions in February 1999, a table of contents and
new format for the document was proposed. The proposed framework of the
report was reviewed at the 33^rd^ OPSCOM meeting and approved. Priority
given to core documents and target dates for completion were
established. (33^rd^ O/C) Draft copy distributed for review by OC 34
members in June 2000. Initial comments/perceptions were discussed at OC
34 with more detailed comments/changes requested from OC members by
September 2000. Task group will consolidate and incorporate all
comments/changes to produce a final copy by May 2001. (34^th^ O/C) NOAA
to submit revised edition to CNES by September 2001. Review comments
from all participants and incorporate by December 2001.(35^th^ O/C)

NOAA/CNES meeting (November 2001) discussed need to restructure portions
of the report (CONREP) so that it can be easily updated annually at the
OPSCOM meeting. Both parties noted that the CONREP did not include
significant items/decisions from the past few OPSCOM meetings. NOAA to
compile a list of recommended inclusions by September 2002 for
discussion at the intersessional meeting. (36^th^ O/C)

32-10-C/S Application eligible to a priori approval procedure

Identify and propose applications that could be eligible for an "a
priori" approval procedure as a possible means of streamlining the SUA
process and reducing administrative burden.

O/C 33 approved the « a priori » approval procedure for the renewal of
Environmental, Governmental, wildlife applications where the user
requirements for using the Argos System are low power transmitters,
(e.g. Bird Tracking) where there is no commercial space-based service
that can meet the user requirement. (33^rd^ O/C)

32-11-C/S Implementation Plan to include NOAA N for Argos-2

Prepare and respond to letter extending the current Project
Implementation Plan to include NOAA N for the Argos-2 instrument.

NOAA has drafted the extension letter. The letter still needs to be
reviewed and routed for signature. A. Wade to send letter by September
1999. (33^rd^ O/C) NOAA delivered an advance copy to CNES and is mailing
the final letter. (34^th^ O/C)

32-12-C/S Implementation Plan for the Space Segment of NOAA N' for
Argos-3

Draft and approve a new Project Implementation Plan (PIP) for the Space
Segment of NOAA N' for the Argos-3 instrument.

NOAA has completed the first draft of the PIP and requested comments
from CNES, NASA and NOAA System Acquisition Office (SAO). (33^rd^ O/C)
Draft circulated, reviewed and revised. Corrected draft to be
recirculated for review by September 2000 and signatories identified.
Final draft pending resolution of instrument delivery schedule. (34^th^
O/C) The final draft is complete awaiting final review and signature.
Expected completion date is June 2001 (35^th^ O/C) PIP signed September
6, 2001 (36^th^ O/C)

32-13-C/S Project Mission and Operations Implementation Plan for the
Argos DCS planned to fly on NOAA N, N', ADEOS II and METOP

Draft and approve a new Project Mission and Operations Implementation
Plan (PMOIP) for the Argos DCS planned to fly on NOAA N, N', ADEOS II
and METOP.

NOAA and CNES will develop a plan of action to draft the PMOIP by
January 2000.(33^rd^ O/C) NOAA beginning to draft the PMOIP. NOAA and
CNES to develop a timetable for completion. (34^th^ O/C). NOAA/CNES
meeting (November 2001) discussed progress on the rough draft. NOAA will
route the rough draft to CNES/CLS (September 2002) for discussion at the
intersessional meeting. (36^th^ O/C) NOAA/CNES meeting (April 2003)
discussed progress on the rough draft. CNES provided copy of ADEOS II
PMOIP for review as a template. (37^th^ O/C)

32-14-C Additional information on Argos-3 system

Per NOAA request, CNES to provide additional information on Argos-3
system including beacon design characteristics, concept of operation,
effects on instrument and spacecraft status and the proposed
installation plan and schedule. CNES offered to provide a briefing as
desired.

CNES has provided additional information on beacon design
characteristics which has been forwarded to NOAA Fairbanks CDA personnel
for review and comment. (33^rd^ O/C)

33-1-C Implementation of a Master beacon at the planned EUMETSAT CDA
station

CNES to send a letter to EUMETSAT requesting a possible implementation
of a Master beacon at the planned EUMETSAT CDA station . CNES will also
provide the Master Beacon Constraints installation document.

Letter sent to EUMETSAT dated August 3, 1999. (34^th^ O/C)

33-2-N Draft of the UIIS for Argos-3

NASA to send a copy of the latest draft of the UIIS for Argos-3 to CNES
for review and to NPOESS via NOAA as a starting point for technical
coordination.

Draft sent and reviewed. (34^th^ O/C)

33-3- Plan of action to exchange technical information on Argos-3

NOAA took the action to identify and liaise with the NPOESS technical
POC. The goal is to establish a plan of action to exchange technical
information on Argos-3.

CNES/IPO discussions conducted in November 1999 and March 2000. NPOESS
technical POCs identified and liaison established. (34^th^ O/C)

33-4-C/S Meeting of Operators of current and future non-geostationary
DCS

NOAA and CNES facilitate a meeting of Operators of current and future
non-geostationary DCS at the next CEOS meeting to encourage high level
coordination between the different systems.

Refer to Action Item 34-13-C/S (34^th^ O/C)

33-5-C/S Improve the timeliness of the SUA

NOAA and CNES to identify methods to further streamline and improve the
timeliness of the SUA administrative process :

-   establishing time limits for requesting SUA clarification by the
    Participating Agencies

```{=html}
<!-- -->
```
-   Identify and propose additional Argos applications for possible "a
    priori" approval.

Time limits dependent upon the modernization of the SUA submission and
tracking process which is in progress. OC 34 noted that a two-week
processing period for the OPSCOM principals was reasonable in light of
the current manual handling of SUAs. It was generally agreed that
electronic submission should speed processing and that efforts should
continue to design an electronic SUA. "A priori" approval is in practice
for specific "wildlife monitoring " applications and appears to be
working well.  'A priori ' approval expanded OC34 to all wildlife
applications where one of the user requirements for using the Argos
system are low power transmitters. This policy will be reviewed annually
by the OPSCOM.   (34^th^ O/C) O/C agreed an A priori approval extended
to E/G low power transmitters above 60° of latitude (35^th^ O/C)

33-6-S Test Data sets for NOAA-15 and NOAA-14

NOAA to provide CNES with yak Test Data sets for NOAA-15 and NOAA-14

Y2K data sets sent to Service Argos and subsequently to CLS. (34^th^
O/C)

33-7-C/S Review the current System Use Policy

NOAA and CNES to review the current System Use Policy to identify areas
for clarification and propose future revisions to the policy.

Preliminary discussions held with Service Argos in August 1999 focussed
on methods to clarify the current System Use Policy such as fact sheets,
frequently asked questions, and proposed revisions of the SUA, for
electronic submission. At OC 34, additional policy areas were identified
for clarification such as Property Data handling and hazardous material
monitoring. The OPSCOM endorsed efforts to revise the SUA and directed
the drafting of a fully revised SUA by September 2000 for approval by
the OPSCOM principals. (34^th^ O/C) Revised SUA form proposed (35^th^
O/C)

33-8-C/S SARSAT briefing for the IPO in 2000

NOAA/CNES coordinate SARSAT briefing for the IPO in 2000.

Briefing held March 2000. Subsequent side discussions focussed on Argos
issues. (34^th^ O/C)

33-9-S Data Dissemination plan for NPOESS

NOAA provide CNES with proposed Data Dissemination plan for NPOESS and a
Point of Contact for future coordination.

Discussions held March 2000 between CNES (C. Gal, L. Ruiz) and IPO (M.
Haas) outlined that current communication plans call for the real-time
DCS data stream to be down-linked via the High Rate Data (HRD) channel.
The HRD channel is planned to transmit in the X-band at a rate of 15-20
Mbps. (34^th^ O/C)

33-10-S Data Encryption plan for NPOESS

NOAA provide CNES with proposed Data Encryption plan for NPOESS and a
Point of Contact for future coordination.

Discussions held March 2000 between CNES (C. Gal, L. Ruiz), IPO (M.
Haas), IIA (R. Masters, C. Marzin) and NESDIS (R. Bassett, J. Mulligan,
A. Wade) restated the precedent that Argos data has never been denied as
it is environmental data of world benefit and that an open policy for
access to the data should be maintained. (34^th^ O/C)

33-11-C Need for Internet security measures

CNES/CLS will investigate the need for Internet security measures to
prevent unauthorized access to messages sent from the DMMC to the Master
Beacons.

M. Cazenave presented a report outlining the planned security measures.
(34^th^ O/C)

33-13-C Preliminary site visit to the Fairbanks CDAS

CNES/CLS will conduct a preliminary site visit to the Fairbanks CDAS to
work out the details of the Master Beacon installation.

Site visit by engineers from CLS SAI completed in June-2001. (35^th^
O/C)

33-14-C/S Formal approval of the Master Beacon installation

NOAA/CNES will seek formal approval of the Master Beacon installation
with an appropriate exchange of letters and other necessary
documentation.

NOAA drafting letter to document the feasibility of the Master Beacon
installation and will request CNES documentation of installation and
maintenance requirements to seek formal approval for installation.
(34^th^ O/C) NOAA will send CNES approval letter in August 2001.

34-2-S Cooperation past NOAA-N' in the NPOESS era

After consultation with the Integrated Program Office, NOAA will propose
to CNES, by the Fall 2000, to exchange letters of intent to recognize
the common interest in continuing the cooperation past NOAA-N' in the
NPOESS era.

Exchange of letters completed 1 August 2001 (35^th^ O/C)

34-3-C/S Common metrics to report end-to-end system performance

A CNES/NOAA Task Group will coordinate with NASDA and EUMETSAT to adopt
common metrics to report end-to-end system performance including
processing statistics. The Task Group will use current metrics utilized
in the NOAA data processing system as the starting point to standardize
system-wide reporting.

New action 35-17-C/S/J/E was opened to develop common data processing
metrics from a high level viewpoint. (35th O/C)

34-4-C/S MOU for Argos instruments on the NPOESS satellites

Following the exchange of letters of intent to continue cooperation in
the NPOESS era, NOAA and CNES to initiate an MOU for Argos instruments
on the NPOESS satellites, consistent with the NPOESS Instrument delivery
need date.

Negotiations for a new MOU is to be initiated by December 2001. (35^th^
O/C) NOAA and CNES meeting (November 2001) discussed CNES preliminary
timetable for NPOESS cooperation i.e. Program Decision mid-2004,
Instrument Delivery mid-2006. NOAA and CNES to investigate internal
requirements for MOU documentation and develop a timetable for MOU
implementation by April 2003. New action item (36-XX-C/S) opened,
recognizing timeline agreed to in principle at March, 2002, meeting
among NOAA, IPO, and CNES. (36^th^ O/C)

34-5-C Future contribution of the Argos DCS to environmental studies

CNES will conduct a comprehensive analysis of the future contribution of
the Argos DCS to environmental studies. The 1995 user requirements
survey will be reviewed and used as appropriate. An interim report will
be presented at the 35^th^ OPSCOM meeting and NOAA/CNES will use this
information to discuss future A-DCS mission specifications.

Initial results of this study show that a new channel with a data
transmission bit rate up to 40kbps might cover the long term needs of
ocean and climate (35^th^ O/C)

34-6-C Current and future user requirements

CLS-SAI will conduct an ongoing dialogue with users to identify their
current and future requirements. CLS-SAI will present their preliminary
results at OPSCOM 35.

Initial results of this study show that a new channel with a data
transmission bit rate up to 40kbps might cover the long term needs of
ocean and climate (35^th^ O/C)

34-7-C Prospective analysis of technologies

CNES to conduct a prospective analysis of technologies which will become
available for the development of future DCS instruments.

New action (35-8-S) was opened. Recommendation for technical
improvements to accommodate users requirements to be prepared and
presented to NOAA by December 2001 for consideration in NPOESS era.
(35^th^ O/C)

34-11-C/J Test of the NOAA/NESDIS/SAI interface

NASDA will coordinate with CLS for the test of the NOAA/NESDIS/SAI
interface (ADEOS-II/Argos DCS data).

NOAA to provide a set of data for the test (35^th^ O/C). NOAA provided a
set of data for the test completed successfully in November 2001.
Additional tests to be scheduled approximately 4 months prior to launch.
(36^th^ O/C)

34-12-C Optimizing the use of all available ground system facilities

CLS/SAI to propose to NOAA a scenario for optimizing the use of all
available ground system facilities in view of improving the data
recovery, processing and distributing system to better meet user
requirements.

CLS advised to submit the user program impacts resulting from proposed
satellite constellation changes so that NOAA can modify the
constellation as appropriate. (36th O/C)

35-1-C/S

NOAA and NASA coordinate with CNES the importation of the Master Beacon
hardware for installation at the Fairbanks Command and Data Acquisition
Station.

Master Beacon installed October 2001. (36th O/C)

35-2-C/I

INPE and CNES will complete the operational assessment of the INPE DCS
and will provide a report of the main conclusion. Report will be made
available by end of 2001 by correspondence.

NOAA/CNES meeting (November 2001) discussed that INPE and CNES should
complete the assessment by March 2002. CNES/CLS proposed next steps at
OC 36 (36th O/C)

35-3-C/S

CNES / CLS and NOAA will develop standard operating procedures and a
timetable to address the SUA renewal process. The timetable will
delineate the timeframes for 1^st^, 2^nd^ and 3^rd^ renewal
notifications and data delivery termination. The procedures will include
renewal tracking, OPSCOM notification and feedback to the user.

NOAA/CNES meeting (November 2001) developed a notification procedure
that will be proposed to the OPSCOM co-chairs for approval and
implementation by February 2002. (36^th^ O/C)

35-4-S

NOAA/IPO will draft and send letter to CNES and NPOESS Preliminary
Design and Risk Reduction Contractors to facilitate the exchange of
technical information. The letter will delineate the technical agents
for each organization and outline information exchange procedures.

Letters sent September 2001. (36^th^ O/C)

35-5-C/I

INPE and CNES will explore possible ways for future cooperation
regarding integration of INPE DCS and Argos DCS. Those ways of
cooperation will be assessed taking into account the rules and
principles of the existing Argos international cooperation and the
existing DCS Chinese Brazilian cooperation.

Cooperative efforts outlined as per section E-3-3. New action item opend
(36 - -) to implement further efforts. (36^th^ O/C)

35-6-S

NOAA to clarify the delivery of pre-processed data (ie : CLS and/or SAI)
and include statistic metrics definitions.

NOAA sends the same pre-processed data to both CLS and SAI. This
situation will be reflected on the NOAA processing system report along
with definitions of the statistical metrics used to measure processing
efficiency. (36th O/C)

35-7-C

CNES/CLS to investigate the availability of the environmental
measurements data via GTS Distribution on a quarterly and monthly basis.

Data available on Data Buoy Cooperation Panel (DBCP) website. (36^th^
O/C)

35-8-C/S

CNES/CLS and NOAA will investigate and compile user and system
requirements for the NPOESS era. A meeting will be set up to discuss
user and system requirements for the NPOESS era.

NOAA/CNES meeting (November 2001) discussed preliminary requirements for
increased data throughput, increased sensitivity/signal processing and
real-time data transmission (X or L band). CNES/CLS to further
investigate these requirements in preparation for a meeting with the
NPOESS Integrated Program Office in March 2002. (36^th^ O/C). CLS
presented a report on "Future Requirements for Argos Evolution" at O/C
37 (37^th^ O/C)

35-9-S Wildlife applications requirements

NOAA will coordinate wildlife applications requirements within NOAA.

NOAA and SAI to develop a requirements survey and complete survey by
December 2002. (36^th^ O/C) NOAA/CNES meeting (April 2003) decided not
to conduct formal survey in light of information gathered at a recent
Argos Animal Tracking Symposium (AATS). Informal liaison with the user
community will continue. (37^th^O/C)

35-10-C IMO resolutions and international maritime bureau interactions

CNES/CLS to provide documentation of IMO resolutions and international
maritime bureau interactions with IMO with regards to governmental and
law enforcement applications (ie. Anti-piracy).

Documentation provided in July 2001. (36^th^ O/C)

35-11-C Analysis of non-environmental system use

CNES/CLS to provide statistical analysis of non-environmental system use
by additional metrics, with specific categories of use.

NOAA/CNES meeting (November 2001) discussed that the current method used
to measure non-environmental use (kbits non-environmental/kbits total)
presents the best representation. The non-environmental use will be
reported by categories such as national security, humanitarian, law
enforcement and episodic (loss of life) for the OPSCOM meeting. (36^th^
O/C)

35-12-S Expanded system use for non-environmental, government's

NOAA to conduct a preliminary analysis of the appropriateness of
expanded system use for non-environmental, government's interest
purposes with regards to national policies.

NOAA/CNES meeting (November 2001) discussed NOAA plans to modify the
System Use regulations by March 2002. Use of the system will continue to
be predominantly environmental while the limit on non-environmental use
will be lifted to permit governmental use of the system for national
priorities. (36^th^ O/C)

35-13-C/S Plan for implementation of electronic submission of initial
and renewal SUAs

NOAA and CNES/CLS to develop plan for implementation of electronic
submission of initial and renewal SUAs, to include a technical analysis
of the means for verification of identity of applicant.

NOAA/CNES meeting (November 2001) discussed CLS implementation of Argos
2001 database and electronic SUA submission scheduled for February 2002.
CLS to send NOAA a sample of the SUA data and screen captures for
development of the NOAA electronic routing system by January 2002. NOAA
investigation of internal requirements for verifying identity of the
applicant indicated valid email addresses are sufficient. Status of
project discussed t OC 36 (G-3) with a projected implementation by
September 2002. (36^th^ O/C)

35-14-S Widest possible use of SUA's with inputs from Argos
participating agencies

NOAA to assure that its contract, when issued, for the development of an
electronic application and tracking system allows for the widest
possible use with inputs from Argos participating agencies.

Contract, issued in September 2001, allows for multiple organizational
levels of approval and distribution. Exploring options for forwarding
submitted SUAs to all OPSCOM Principals as desired. (36^th^ O/C)

35-15-C/S Changes to the SUA

CNES/CLS will coordinate and incorporate proposal changes to the SUA and
submit it to OPSCOM co-chairs for approval.

NOAA/CNES meeting (November 2001) discussed additional changes to the
SUA. A revised version of the SUA was produced by CLS (June 2002) which
was discussed in section G-4. Some addition minor modifications were
approved at OC 36, which will be implemented by July 2002. (36th O/C)

35-16-C Agreement with Eumetsat

CNES to provide file copy of agreement with Eumetsat.

Copy provided (36^th^ O/C)

35-17-C/S/J/E End-to-end data processing performance

Joint task team will develop common metrics to report end-to-end data
processing performance from a high level viewpoint.

Difficulties in developing common metrics discussed in Section F-1.
Opened action item 36-6-C/S to investigate feasibility of utilizing
performance measures on NOAA processing system. (36^th^ O/C)

35-19-C/S Plans for carriage of DCS on NPOESS orbits

CNES and NOAA to discuss and finalize plans for carriage of DCS on
NPOESS orbits. NOAA/OSDPD to inform NOAA/IPO of discussion results.

ADCS requirements for NPOESS discussed in section E-3-1. Opened action
item 36 - - C/S to draft Letter of Intent. (36th O/C)

35-20-C/S Plans for the provision of DCS data on the low rate data (LRD)
stream

CNES and NOAA to discuss and finalize plans for the provision of DCS
data on the low rate data (LRD) stream in addition to the DCS data being
provided as part of the global stored data and the real-time high rate
data (HRD) stream for NPOESS. NOAA/OSDPD to inform NOAA/IPO of
discussion results.

ADCS requirements for NPOESS discussed in section E-3-1. Opened action
item 36 - - C/S to draft Letter of Intent. (36^th^ O/C)

35-21-C/S Extending the existing CNES/NOAA MOU to include the NPOESS

NOAA/IA to investigate extending the existing CNES/NOAA MOU to include
the NPOESS constellation.

After internal review, NOAA determined that the existing CNES/NOAA MOU
could be extended to include the NPOESS constellation. However, NOAA
recommended that a new MOU be negotiated that would recognize history of
the program, the expanded participation within the OPSCOM of NASDA,
Eumetsat and INPE, the modifications to the existing MOU that have been
made in the past, and any other changes NOAA and CNES may negotiate.
(36^th^ O/C)

35-22-C/S NPOESS Project Plan for DCS

NOAA/IPO to lead the drafting of the NPOESS Project Plan for DCS with
the collaboration of CNES and the other prospective participating
agencies i.e. NASDA and EUMETSAT.

NPOESS Project Plan to be discussed at CNES/NOAA intersessional meeting
in November 2002. (36^th^ O/C) NPOESS Project Plan discussed at
CNES/NOAA meeting in January 2003. CNES provided NOAA/IPO with a draft
for review. (37^th^ O/C)36-2-C/N Information about Argos instrument
onboard NOAA-M

CNES to provide NASA with the correct information for the Argos
instrument onboard NOAA-M and NASA to update associated handbook.

NOAA-M handbook published. NASA will identify POC for submission of
NOAA-N information. CNES encouraged to submit correct information to
NASA and NOAA. (37^th^ O/C)

36-1-C Utility of Argos data from NOAA-11

CNES/CLS to investigate and report to NOAA / NASA the utility of Argos
data from NOAA-11, NOAA-12, and NOAA-14 following the launch of NOAA-M.

Report provided and utilized to adjust POES constellation in accordance
with operational requirements. (37^th^ O/C)

36-3-C/S Checklist for future launches

CNES/CLS and NOAA to develop a checklist for future launches, to
delineate required actions such as handbook updates, constellation
configuration changes, etc.

NOAA-N scheduled launch in June 2004. Checklist should be completed by
December 2003. (37^th^ O/C) Content of check list to be clarified and
validated prior to NOAA N launch. (38^th^ O/C)

36-4-C/S Requirements for the NPOESS constellation

CNES and NOAA to draft a Letter of Intent from the OPSCOM to the
NOAA/IPO to clarify, provide and coordinate the A-DCS requirements for
the NPOESS constellation

NOAA letter dated January 15, 2003 confirmed NOAA's intent to continue
Argos continuity into the NPOESS era. (37^th^ O/C)

36-6-C/I New cooperative activities between the Brazilian and Argos DCS

CNES and INPE will explore how, building upon the ongoing CNES/INPE
cooperative efforts, the data sharing can be expanded into a larger
cooperative framework. Specific proposals for new cooperative activities
between the Brazilian and Argos DCS and for further integration of the
two systems will be presented at the next Operations Committee.

36-7-C SAR/A-DCS receiving antenna situation on board METOP

CNES to investigate about the SAR/A-DCS receiving antenna situation on
board METOP.

There is no impact A-DCS receiving antenna performance and C. Gal has
the relevant EUMETSAT documentation. (38^th^ O/C)

36-9-C/S Estimated expiration date for all System Use Agreements

CLS will add estimated expiration date for all System Use Agreements to
be included in the Program Review notification sent back to users.

CLS presented proposed wording of program review notification at O/C 37.
(37^th^ O/C)

36-10-C/S SUA renewal letters

SUA renewal letters to be revised, to include a timetable for expiration
of SUA and the potential for suspension of data processing and
distribution, and recycling of user identification numbers.

SUA renewal letters were presented and approved at O/C 37. (37^th^ O/C)

36-11-C/S Draft MOU to govern cooperation on the NPOESS

Draft MOU to govern cooperation on the NPOESS series of satellites to be
circulated for review by CNES, NOAA, and NOAA IPO, recognizing the
timelines discussed at the March, 2002 meeting among NOAA / IPO and
CNES, and in the CNES report for E-3-1 at 36th O/C.

Draft MOU undergoing internal NOAA review. (37^th^ O/C)

36-12-C/J ADEOS II Argos DCS data release

NASDA / CNES to coordinate the ADEOS II Argos DCS data release

ADEOS II-Argos DCS data distribution began April 2003. (37^th^ O/C)

36-14-C Procedure to assign frequencies for Argos applications

CLS will propose a procedure to assign frequencies for Argos
applications.

CLS presented a proposal at OPSCOM 37 for approval. However
implementation was deemed unfeasible at this time. (37^th^ O/C) No
allocation of channels is recommended. (38^th^ O/C)

36-15-C/S/J/E Reporting system performance via three metrics

Joint task team to investigate feasibility of reporting system
performance via three metrics: timeliness (delay in delivering data sets
to users), quantity (number of data sets delivered) and quality (bit
error rate).

Performance metrics for the NOAA POES DCS was discussed at O/C 37. It
was recommended the specific system metrics for other Argos data
processing systems (i.e. ADEOS II, METOP) be defined in their
performance reports. (37^th^ O/C)

36-16-C/S System use statistics on four categories

CLS to work with NOAA to provide system use statistics on four
categories: national security/homeland defense, humanitarian operations,
law enforcement and episodic.

Statistics required to monitor non-environmental use of the system for
regulatory compliance. (37^th^ O/C)

36-17-S NPOESS contractor

NOAA to provide letter informing CNES of winning NPOESS contractor and
contacts/procedures to resume planning discussions.

NOAA/IPO letter dated September 27, 2002 sent to CNES (37^th^ O/C)

36-18-C Dedicated, stand-alone Brazilian DCS station

CNES/CLS to conduct and report on a cost and performance evaluation for
the implementation of a dedicated, stand-alone Brazilian DCS station.

Implementation feasible, however, any installation will be in accordance
with user requirements and should optimize INPE satellite plans. (37^th^
O/C)

37-1-S Argos data requirements for NOAA blind orbits

NOAA to submit and coordinate Argos data requirements for NOAA blind
orbits

NOAA will continue to follow the possible solution with collecting blind
orbits. There is a plan to test IPO ground equipment at Salvard with the
two operational POES satellites. (38^th^ O/C)

37-2-C Prioritised list for satellite downloads from NOAA 11, 12, 14,
and 15

CNES/CLS to provide NOAA with a prioritised list for satellite downloads
from NOAA 11, 12, 14, and 15 to supplement NOAA 16 and 17 (no blind
orbits) for coordination of the POES constellation

37-3-C Integration of the A-DCS on NPOESS

CNES to provide NOAA with a technical memorandum outlining the
requirements for integration of the A-DCS on NPOESS in preparation of an
interface meeting to be held in September 2003.

37-4-S NPOESS coordination meeting

NOAA to arrange NPOESS coordination meeting and agenda with the IPO.

37-5-C Prioritised list of regional HRPT stations

CNES/CLS to assess the areas of the world where real time data
requirements and thus regional HRPT station coverage are the most
critical and to provide NOAA with a prioritised list of regional HRPT
stations to upgrade for the integrated POES/EPS real time network.

37-6-S Plans for upgrading HRPT stations to receive METOP data

NOAA to investigate and verify current plans for upgrading HRPT stations
to receive METOP data.

37-7-C/S/I Bandwidth requirements for the INPE DCS

NOAA, CNES and INPE to coordinate on bandwidth requirements for the INPE
DCS.

37-8-W/C Argos tariff determination and future evolution in completion
of five-year plan

JTA and CNES/CLS to introduce new framework for Argos tariff
determination and future evolution in completion of five-year plan.

-   Initial proposal to JTA 23 (October 2003)

-   Draft proposal to OPSCOM 38 (June 2004)

-   Final approval by JTA 24 (October 2004)

-   Implementation: January 2005

37-9-C Quarterly reports of non-environmental use

CNES/CLS to provide quarterly reports of non-environmental use in the
following categories: Homeland security, National Defense, law
enforcement, humanitarian and episodic use.

37-10-S/C Draft letter to Chilean VMS Authorities

NOAA and CNES/CLS to draft letter to Chilean VMS Authorities outlining
the Argos System Use Policy and its impact on the current VMS situation.

37-11-S/C SUA form

CNES/CLS and NOAA will revise current SUA form to reflect changes in
Argos Participating Agencies, SU Policy and Financial Liability.

37-12-C/I Mission requirements of INPE future DCS Transponder.

INPE to consult with CNES and the other Argos participating agencies
about the mission requirements of their future DCS Transponder.

37-13-S SUA review system

NOAA to document the structure and procedures of its electronic SUA
review system and provide to the OPSCOM attendees.

37-14-C Interim SUA review process

CNES/CLS to document the procedures for the interim SUA review process
to reflect the addition of NASDA as a Participating Agency and
distribute to all OPSCOM attendees.

37-15-C Access procedures to CNES/CLS SUA database

CNES/CLS to document access procedures to their SUA database and provide
to NASDA.

37-16-S/C/N Revised TOR

NOAA to revise TOR to reflect changes in Argos OPSCOM membership and the
implementation of streamlined SUA approval procedures.

NOAA provided an edited document for review (38^th^ O/C)

37-17-C METOP operations and procedures documentation

CNES to provide NOAA with copies of METOP operations and procedures
documentation to assist in developing the PMOIP

37-19-C/S SUA renewal letter procedure

CNES/CLS and NOAA to draft SUA renewal letter procedure and data denial
procedure.

37-20-C/S Application categories on Argos Agreements

CNES/CLS and NOAA to review and verify application categories on Argos
Agreements listing

New Action item coding (O/C 38^th^)

C - CNES I - INPE

N -- NOAA E - EUMETSAT

J -- JAXA W -- WMO

38-1-C METOP-1 frequency submission to the ITU for the A-DCS

CNES to provide feedback to NOAA on the METOP-1 frequency submission to
the ITU for the A-DCS. NOAA would like to know if an objection was
raised by the FCC/NTIA.

38-2-I Remote sensing symposium in April 2005

INPE to provide information on their proposed data collection and
application, section on the remote sensing symposium in April 2005.

38-3-S/C Granule size in the Argos data delivery system

NOAA/CNES/CLS Coordinate requirements for granule size in the Argos data
delivery system in the METOP (IJPS) and NPOESS era.

38-4-N/C Metric and mechanism for approval of non environmental
applications of Argos

NOAA and CNES/CLS to develop a metric and mechanism for approval of non
environmental applications of Argos to be applied within the constraints
the current DCS SUA policy and for review by NTIA.

38-6-S/C/I/W/N Possible gap filler between NOAA 15 and NPOESS C3 in the
early morning orbit

OPSCOM participants to explore options and plans for possible gap filler
between NOAA 15 and NPOESS C3 in the early morning orbit.

38-7-S/C Data delivery anomaly notification between NOAA and the USGPC

NOAA/CNES/CLS/SAI Coordinate data delivery anomaly notification between
NOAA and the USGPC. NOAA to review SAI contacts to ensure current
information. NOAA to ensure SAI is on IPD notification via e-mail.

38-8-S/C Collection of sensitive use SUA

NOAA/CNES/CLS to review the collection of sensitive use SUA and ensure
program documentation are up to date.

38-9-S/C NPOESS MOU

NOAA/CNES to continue negotiation for the Argos MOU for the NPOESS era
in light of legal issue raised by the Jason 2 MOU.

# O/C MEETING Open Actions

Action item coding (O/C 38^th^)

C - CNES I - INPE

N -- NOAA E - EUMETSAT

J -- JAXA W -- WMO

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

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

36-5-C/I Formalizing the present (CNES/INPE) data sharing experiment

CNES and INPE will develop and implement an agreement based upon the
terms of the CNES letter to INPE for formalizing the present data
sharing experiment and for making it permanent.

CLS receiving Argos data from INPE on an operational basis. (37^th^ O/C)
A Letter was sent to Mr. Perondi in October 2003 by CLS and there is no
position from INPE up to now (38^th^ O/C)

36-13-C/S Consolidated Report

Update Consolidated Report and present at 37th O/C meeting.

Content and Plan of Action was discussed at O/C 37. A renewed effort to
document Argos policies and procedures to augment existing MOU's and
project plans. (37^th^ O/C)

37-18-C/S Project Mission and Operations Implementation Plan for NOAA N'

CNES/CLS and NOAA to draft and approve a Project Mission and Operations
Implementation Plan for NOAA N' to reflect changes due to Argos-3
capabilities.

38-5-C User requirements summary study

CNES/CLS to provide user requirements summary study for review by
OPSCOM.

38-10-C SUA renewal procedure

CNES/CLS to review the SUA renewal procedure and data access policy and
provide comments to the OPSCOM for further discussion.

39-1-N

The OPSCOM recommends NOAA continue to pursue an increase of NOAA 12
contacts taking advantage of the de-commissioning of NOAA-14 or the
collection of blind orbits at Svalbard.

Action: C. O'Connors, M. Fitzmaurice by June 2006

39-2-C/N

The Argos Operation Committee will provide comments on the edited Terms
of Reference section 2.2.2. NOAA drafted new language, which addressed
the new responsibility of the OPSCOM to monitor non environmental use.
The level of non environmental use is to remain within the 5% system
capacity measured in Erlang.

Action: All by September 2005

39-3-N

NOAA will provide an update at the next OPSCOM on the frequency
management issues related to the downlink messaging on the Argos-3
instruments.

Action: C. O'Connors by June 2006

39-4-N

NOAA is evaluating the direct broadcast frequencies on back-up
satellites to minimize interference and would like to limit the impact
to the user community. NOAA will look to coordinate frequency changes
and to identify potential impacts to the Argos direct readout network.

Action: M. Fitzmaurice by December 2005

39-5-C

CLS/SAI to share the contents of their daily report on HRPT data sets
received from their 42 direct readout ground station network with NOAA.
NOAA is evaluating the direct broadcast frequencies to minimize
interference and would like to minimize the impact to the user
community.

Action: B. Woodward by September 2005

39-6-C

CLS will provide an update on the 2005 expected costs and the 2005
income collected to date one month prior to the JTA meeting.

Action: C. Vassal by September 2005

#   {#section-1 .unnumbered}

#  ANNEX

## Argos DCS Program and Policy Documents 

-   NOAA -- NASA -CNES Argos Memorandum of Understanding (MOU) 1974

-   NOAA-CNES Argos Memorandum of Understanding (MOU) 1986

-   NOAA-CNES 1986 Argos MOU Annexes and Amendments

```{=html}
<!-- -->
```
-   Annexe on Confidential Treatment of Data

-   Exchange of letters on establishment of a U.S. processing center
    (1986)

-   May 1990 amendment on \"environmental protection\" as a basis for
    system access

-   Terms and Conditions for Implementation of 5% Non-environmental Use
    (1990)

-   February 1991 Amendment extending MOU to cover NOAA-N.

-   July 1998 Letter exchange to extend MOU to include NOAA N' and a
    statement on liability

```{=html}
<!-- -->
```
-   Argos Joint Tariff Agreement (JTA) Meeting Minutes