Preparation of requirements for the production of Draft Plan Borislav M. Rackov ITU/BR/TSD/TPR...

Preparation of requirements for the production ofDraft Plan

Borislav M. Rackov ITU/BR/TSD/TPR

Preparation of requirements for the production ofDraft Plan

Borislav M. Rackov ITU/BR/TSD/TPR

Second Regional Meeting and Workshop related to the RRC-06 for the administrations of the African countries

Accra, Ghana, 10 - 14 October 2005



Requirements for the Draft Plan - Borislav M. Rackov ITU/BR/TSD/TPR



New, to allow the administration to do final assembly of the requirement file and complete all validation pertinent

to a consolidated requirement file

Updated to comply with the new format given in CR/241



Accra, Ghana, 10 - 14 October 2005 fmtv_terra

terrakey INTEGERintent CHAR(8)fragment CHAR(8)assgn_id CHAR(9)adm_ref_id CHAR(20)notice_typ CHAR(3)adm CHAR(3)ctry CHAR(3)call_sign CHAR(10)stn_id CHAR(20)addr_code CHAR(2)op_agcy CHAR(3)d_adm_ntc DATETIMEd_inuse DATETIMEd_rcv DATETIMEprov CHAR(12)region CHAR(1)freq_assgn DOUBLEfreq_vcarr DOUBLEfreq_scarr DOUBLEtv_chan CHAR(3)freq_stabl CHAR(9)oset_v_12 INTEGERoset_v_khz DOUBLEoset_s_12 INTEGERoset_s_khz DOUBLEstn_cls CHAR(2)tran_sys CHAR(2)color CHAR(5)emi_cls CHAR(5)bdwdth DOUBLE

hgt_agl DOUBLEeff_hgtmax INTEGERerp_dbw DOUBLEerp_kw DOUBLE

erp_h_dbw DOUBLEerp_h_kw DOUBLE

erp_v_dbw DOUBLEerp_v_kw DOUBLEpolar CHAR(2)ant_dir CHAR(2)azm_max_e DOUBLEpwr_ratio DOUBLEsite_name CHAR(30)long_deg INTEGERlong_ew CHAR(1)long_min INTEGERlong_sec INTEGERlat_deg INTEGERlat_ns CHAR(1)lat_min INTEGERlat_sec INTEGERlong_dec DOUBLElat_dec DOUBLElong_rdn DOUBLElat_rdn DOUBLEsite_alt INTEGEReu_ref DOUBLEeu DOUBLEfdg_observ CHAR(1)d_recog DATETIMEsrc_notice CHAR(8)d_updated DATETIMEsrc_update CHAR(20)stage CHAR(1)amend_type CHAR(12)is_notice CHAR(5)is_public CHAR(5)is_resub CHAR(5)is_digital CHAR(5)is_pub_req CHAR(5)d_pub_req DATETIMEtarget INTEGERfreq_min DOUBLEfreq_max DOUBLE

fmtv_op_prd

terrakey INTEGERop_hh_fr INTEGERop_hh_to INTEGER

fmtv_rmks

terrakey INTEGERrmk_type CHAR(12)rmk_seq_no INTEGERrmk_code CHAR(12)

rmk_text CHAR(80)

fmtv_ant_diag

terrakey INTEGERazm DOUBLEpolar CHAR(1)attn DOUBLE

fmtv_ant_hgt

terrakey INTEGERazm DOUBLEeff_hgt INTEGER

rrc_elements

terrakey INTEGERsys_var CHAR(2)nb_carr CHAR(2)guard_interval CHAR(2)rx_mode CHAR(1)ref_plan_cfg CHAR(4)typ_ref_netwk CHAR(3)sfn_id CHAR(30)sfn_tx_tim INTEGERadm_allot_id CHAR(20)spect_mask CHAR(1)freq_block CHAR(60)channel CHAR(60)conv_freq_assgn DOUBLEconv_long_deg INTEGERconv_long_min INTEGERconv_long_sec INTEGERconv_long_ew CHAR(1)conv_lat_deg INTEGERconv_lat_min INTEGERconv_lat_sec INTEGERconv_lat_ns CHAR(1)email_addr CHAR(50)coord_self CHAR(5)

rrc_allotment

terrakey INTEGERallotkey INTEGERallot_name CHAR(30)geo_area CHAR(3)nb_sub_areas INTEGER

rrc_sub_area

allotkey INTEGERcontourkey INTEGER

rrc_contour

contourkey INTEGERcontour_id INTEGERadm CHAR(3)ctry CHAR(3)nb_test_pts INTEGERremarks CHAR(80)

rrc_contour_pt

contourkey INTEGERtest_pt INTEGERlong_deg INTEGERlong_min INTEGERlong_sec INTEGERlong_ew CHAR(1)lat_deg INTEGERlat_min INTEGERlat_sec INTEGERlat_ns CHAR(1)

rrc_sfnID_proc

terrakey INTEGERsfn_id CHAR(30)adm CHAR(3)notice_typ CHAR(3)adm_allot_id CHAR(20)

rrc_coord_analog_BCBT

terrakey INTEGERadm CHAR(3)

rrc_coord_other_service

terrakey INTEGERadm CHAR(3)

One new Field

Two new Tables




Validation of requirement with errors

in Allotments




Validation of requirement with errors

in SFN_ID




New software: Files Assembly and Final Validation tool

http://www.itu.int/ITU-R/conferences/rrc/rrc-04/intersession/index.asp

File assembly and final data

validation(DNotif)

ReferenceDatabase

(analog TV,other

services)

Val OK?

File with notices ready for

submission to BR

Yes

No

File 1

File 2

File 3

File 4

File …n

Notices with errors



Accra, Ghana, 10 - 14 October 2005 Goals for the next submission phase

Neat & timely submissions – quick and clear messages !!!

ADM:Increase the quality (correctness and completeness) of the

submitted data

Notify on time having in mind “time consuming” activities (i.e. correspondence exchanged between BR and administrations)

BR:Develop new software tools to facilitate validation prior to

submission

Reduce bottlenecks in data processing




Identification of most common errors

– Wrong file format– Identification data repeated or inconsistent (SFN Id, Administrations Unique Identifier, etc.) – Technical data missing or incorrect– Allotment areas wrongly defined (crossing segments, points outside the territory) – Analog assignment (for conversion) not found– etc.




Draft Plan notificationPlease keep in mind 31-10-2005 and notify as soon as possible !!!

* Re-check the status of your assignments in appropriate Plan for the Reference Situation (publication in Part B must be requested using TB3 notice form) !!!

* Some practical recommendations to speed-up the processing of your submission:

- please, always send your submissions to [email protected] only - please put indication “RRC- Submission of digital requirements for the Draft Plan” in subject line of the e-mail. This will help identify your message and apply appropriate routing - please put in message body: summary of file contents (file name, number of notices, notice types, etc), signature - please send a telefax indicating e-mail address from which the submission was sent, content of the e-mail and of the attachments and name of the sender. This is essential for e-mail authentication and will help in (very, very rare) case of not arrival of the e-mail. [email protected] sends a confirmation of submission receipt at the moment of registering the e-mail. - please do not attach anything else but the validated SGML file. Access files (with extension .mdb) activate virus protection software - please …




Draft Plan notification (2)Think about 31-10-2005 but act NOW !!!

*…and some recommendations related to the sender’s e-mail

- please note that ONLY authorized person may submit on behalf of administration. This may be administration itself or “contact person” designated by the administration. Insist with your administration to submit the name of “contact person” - please use corporate e-mail address. If forced to use “portable” e-mail addresses (yahoo, hotmail…) make sure that you can send/receive attachments 2 – 5 MB and to have at least 10 MB of free space. Google mail (…@gmail.com) seems appropriate – this is not an advertisement! - please check regularly your “Inbox”, at least once a day, to be able to react promptly

*… finally, do not forget to:

- regularly check the ITU web site for all kind of information and software updates - feel free to contact (by e-mail or by phone) the ITU whenever in doubt or necessity




… … Excessive input requirements for Excessive input requirements for the available spectrum and errors in the available spectrum and errors in the preparation and submission of the preparation and submission of input requirements by input requirements by administrations …administrations …

”Report of the first meeting of the Intersessional Planning Group ”Report of the first meeting of the Intersessional Planning Group (IPG)”(IPG)”(Geneva, 4-8 July 2005) annex 15 , page 127(Geneva, 4-8 July 2005) annex 15 , page 127

Think about Think about it!it!Requirements for the Draft Plan - Borislav M. Rackov ITU/BR/TSD/TPR




They are going to receive and process your requirement …

A. Méndez

S. Pinnagoda

A. Skokova

B. BaB. Rackov

Preparation of requirements for the production of Draft Plan Borislav M. Rackov ITU/BR/TSD/TPR...

Documents

Transcript of Preparation of requirements for the production of Draft Plan Borislav M. Rackov ITU/BR/TSD/TPR...