RRC - Administrative declarations for the Draft Plan – Damascus, 16-18 August 2005 1 Regional...
-
Upload
abigail-newton -
Category
Documents
-
view
217 -
download
0
Transcript of RRC - Administrative declarations for the Draft Plan – Damascus, 16-18 August 2005 1 Regional...
1RRC - Administrative declarations for the Draft Plan – Damascus, 16-18 August 2005
Regional Information Meeting and Workshop related to the RRC-06 for the Administrations of the Arab Group of
countries
“Coordination and Administrative declarations for the
Draft Plan”
A. Méndez BR/TSD/TPR
Damascus, 16-18 August 2005
2RRC - Administrative declarations for the Draft Plan – Damascus, 16-18 August 2005
Clarify the concept
Share BR’s experience during the Planning exercise
Present a summary of the IPG-1 decisions on Administrative declarations for the Draft Plan
Present the data format for notification
Objectives of this presentation
3RRC - Administrative declarations for the Draft Plan – Damascus, 16-18 August 2005
Searching for a definition of “Administrative Declarations”
• RRC Report Chapter 1
• RRC Report Chapter 5 (5.1.6.2)– Reduce incompatibilities
– Negotiation/agreement between administrations
– Possible request for assistance to the BR
4RRC - Administrative declarations for the Draft Plan – Damascus, 16-18 August 2005
• RRC Report 5.3.1.1.1.5
Searching for a definition of “Administrative Declarations” (cont.)
Adm AReq 1
Adm AReq 2declares compatibility/
incompatibilityAdm AReq 1
Adm BReq 2
• RRC Report 5.3.1.1.2.4(Same concept between requirement / recorded assignment)
5RRC - Administrative declarations for the Draft Plan – Damascus, 16-18 August 2005
RR - Definition of Coordination
• Coordination– Area– Contour– Distance
• Article 9 – Process of seeking an agreement of other administration
RR
6RRC - Administrative declarations for the Draft Plan – Damascus, 16-18 August 2005
Comparison between Administrative declarations and Coordination
Notifying ADM “A” states that ADM “B” had agreed that “A’s” notified requirementdoes not affect any of “B’s” recorded assignments (analog BT / other services)
Notifying ADM “A” states that it acceptsinterference to their requirement xxx causedby recorded assignment or requirement yyy from ADM “B”
Administrative declaration
Coordination information
7RRC - Administrative declarations for the Draft Plan – Damascus, 16-18 August 2005
Administrative declarations for the Planning exercise
• Addendum 1 to CR 229 (24.05.2005)– Provisional solution (requirements)
– Guidelines
– File format
– 15 days after publication of requirements
8RRC - Administrative declarations for the Draft Plan – Damascus, 16-18 August 2005
Some statistics from the Planning Exercise
35 notifying Administrations
50 incoming emails
<5 outgoing emails
<10 telephone calls and unregistered emails
4 days Total processing time
150 000 valid input administrative declarations for the exercise
Percentage of errors: LESS than 1 % of the declarations received!!!!
9RRC - Administrative declarations for the Draft Plan – Damascus, 16-18 August 2005
1. Encourage ALL administrations to submit declarations
2. Keep the notification procedure as simple as possible
3. Avoid bottlenecks in submission
BR’s goals for the next phase
10RRC - Administrative declarations for the Draft Plan – Damascus, 16-18 August 2005
IPG-1 Decisions
- Annex 14 “Review of the results of the first planning exercise”
- Annex 18 “Review of Time Schedule”
- Annex 21 “Report from ad hoc Group 2 on administrative declarations”
11RRC - Administrative declarations for the Draft Plan – Damascus, 16-18 August 2005
IPG-1 Decisions (cont.)
• Additional run of the Planning Exercise
• Administrations may submit additional administrative declarations
Date limit: 22 August 2005Format: add.1 to CR/229
12RRC - Administrative declarations for the Draft Plan – Damascus, 16-18 August 2005
• When to submit (for Draft Plan)?– Before 27.01.2006 (see also time schedule)
• Who can notify?– Authorized contact person
• What should be notified?– ALL declarations, even if there are no changes with
respect to those submitted for the planning exercise
• How to prepare the notification files?– Using a text processor or Excel (equivalent) software
Basic questions on administrative declarations
13RRC - Administrative declarations for the Draft Plan – Damascus, 16-18 August 2005
Draft Plan - Time Schedule (source IPG-1 report annex 18)
Activity/event Duration Deadline Action by
Production of the draft Plan
Reference situation date 31.10.2005 Administrations
Last submission of input data prior to the second session of the RRC
31.10.2005 Administrations
Validation, correction and publication of input data
3 months
31.01.2006 BR and administrations
Submission of administrative declarations 27.01.2006 Administrations
Production of the draft plan1
month
BR assisted by experts See
resolve 1a)
Meeting of the Inter-sessional Planning Group; submission of the draft plan to RRC-06
February 2006
IPG
Publication of the draft plan 28.02.2006 BR
Analysis of the draft Plan by administrations 2 months
Administrations
Submission of additional administrative declarations
20.03.2006 Administrations
Publication of additional synthesis results 31.03.2006 BR
Beginning of the second session of RRC May 2006
14RRC - Administrative declarations for the Draft Plan – Damascus, 16-18 August 2005
Annex 21 of IPG-1 Report
• To remove constraints from the Synthesis process• To cover cases between different or same
administration• Valid if “date declaration” > “date of requirement”• “Definitive Recording” not yet defined (issue
submitted to RPG)
Scope of pre-coordination
15RRC - Administrative declarations for the Draft Plan – Damascus, 16-18 August 2005
• “Primary tool” for indication of agreement!
• COORD_A and COORD_O only when single channel requested
Annex 21 of IPG-1 Report (cont.)
New mechanism
16RRC - Administrative declarations for the Draft Plan – Damascus, 16-18 August 2005
• One single file per administration• Declarations should be submitted by both
administrations– BR validates and eventually excludes
• BR publishes the files on the Web• Changes in requirements need new declaration
Procedure for submission
Annex 21 of IPG-1 Report (cont.)
17RRC - Administrative declarations for the Draft Plan – Damascus, 16-18 August 2005
How to prepare notification files?
Administration’s own softwareText processorsExcel softwareBR’s software tool under preparation
18RRC - Administrative declarations for the Draft Plan – Damascus, 16-18 August 2005
Administrative declarations
Administration code of the
affected requirement
Unique identifier of the affected requirement
Administration code of
interfering requirement
Unique identifier of the interfering requirement
Declaration
MKD DAB-1 HRV HRR0901 compatibleMKD DAB-1 HRV HRR8102 compatibleMKD DAB-1 HRV HRR8202 compatibleMKD DAB-1 HRV HRR8302 compatibleMKD DAB-1 I I__00312 compatibleMKD DAB-2 BUL BUL-TDAB-001 compatibleMKD DAB-2 BUL BUL-TDAB-002 compatibleMKD DAB-2 BUL BUL-TDAB-007 compatibleMKD DAB-2 BUL BUL-TDAB-008 compatibleMKD DAB-2 HRV HRR0902 compatibleMKD DAB-2 HRV HRR0901 compatibleMKD DAB-2 HRV HRR8102 compatibleMKD DAB-2 HRV HRR8202 compatibleMKD DAB-2 HRV HRR8302 compatible
Sample file (Excel format)
19RRC - Administrative declarations for the Draft Plan – Damascus, 16-18 August 2005
Administrative declarations
Sample file (delimited text format)
20RRC - Administrative declarations for the Draft Plan – Damascus, 16-18 August 2005
References
- RRC Report (revised version)- IPG-1 Report (plus IPG-1 documents)- BR Circular Letters (CR/…)- ITU Web site
(http://www.itu.int/ITU-R/conferences/rrc/rrc-04/intersession/index.asp)
- BR Contact address: [email protected]
21RRC - Administrative declarations for the Draft Plan – Damascus, 16-18 August 2005
Summary
• Still possible to submit administrative declarations for an additional run of the Planning Exercise– Date limit: 22 August 2005
– Format: add.1 to CR/229
• Administrative declarations for the Draft Plan should be in accordance with Annex 21 of IPG-1 Report
Pre-coordination: Key element for a successful Plan