Regional Information Meeting and Workshop - Submission of Digital Requirements for the Draft Plan

1. Regional Information Meeting and Workshop related to the RRC-06 for the Administrations of the Arab Group of countries Damascus, 16-18 August 2005 “Submission of Digital Requirements for the Draft Plan” A. Méndez BR/TSD/TPR

2. Objectives of this presentation • Share BR’s experience about submission issues during the Planning exercise • Describe changes to the notice format and submission process for the Draft Plan • Describe/show use of BR’s Software for • Data Capture • Data Validation • Data Correction • Final Assembling of files • Data Query & extraction

3. Some statistics from the Planning Exercise

4. Statistics from Planning Exercise (cont.) ~30 %of the notices received had errors • Wrong file format • Identification data repeated or inconsistent (SFN Id, Notice Id, etc.) • Technical data missing or incorrect • Allotment areas wrongly defined (crossing segments, points outside the territory) • Analog assignment (for conversion) not found • etc.

5. Distribution of submissions received by the BR % of notices What happened for the planning exercise Ideal expected distribution date

6. BR’s goals for the next submission phase • Increase the quality (correctness and completeness) of the submitted data • Reduce number of “time consuming” activities (i.e. correspondence exchanged between BR and administrations) • Develop new software tools to facilitate validation • Reduce bottlenecks in data processing

7. Basic questions on digital requirements • Deadline for submission of requirements for the Draft Plan? • 31st October 2005 (see CR/241) • Who can submit requirements? • Only authorized contact persons • What should be submitted? • ALL digital requirements (in SGMLfile format), even if there are no changes with respect to those submitted for the planning exercise • How to prepare the requirements files? • Using different appropriate software tools

8. Changes to submission procedure • Changes in the data structure and forms(following decisions on coordination information taken by IPG-1 in July) • Administrations are invited to use the new BR software tools(to facilitate complete data validation)

9. Changes in requirement forms layout New

10. Changes in requirement forms elements New field rrc_coord_self New sections COORD_A and COORD_O

11. Changes in database structure 1 new field 2 new tables

12. News about BR’s software for requirements submission • Announced in CR/241 • Overview of changes • Update of notice forms (DT1, DT2, DS1 & DS2), database structure and all applications with new coordination information • Consolidated single software application (capture, correction, validation, etc.) • Addition of a tool for “final assembling of files” • Updates available on the Web for free download(http://www.itu.int/ITU-R/conferences/rrc/rrc-04/intersession/index.asp)

13. New Updated

14. How to prepare requirement files effectively? • Administration’s own software • Text processors • MS Access • BR’s software

15. Submission process (1) Administration’s own software Val OK? Electronic SGML file Data Validation (DVal) Yes BR’s Data Capturesoftware (Dcap) No Text editor (Notepad) Correction (Dcor/Editor)

16. Submission process (2) File 1 File 2 File 3 File n File assembling and final data Validation (Dnotif) Val OK? Yes Yes No No Reference database Valid consolidated file Correction (Dcor/Editor)

17. Submission process (3) Administration Radiocommunication Bureau Before 31.10.2005 RRC Digital requirements database brmail@itu.int BR full data Validation Draft Plananalysis… admin@… Valid consolidated file

18. Data validation tool: DVal Stamps input file DVal Electronic NotificationsSGML file Validation report(text file) (link) Text editor (Notepad)

19. Data validation tool: DVal Sequential process 1st step (file format) 2nd step (data type, length, etc.) 3rd step (range of values, mandatory keys, Geographical, etc.) Text editor or DCor Text editor

20. Data correction tool: DCor Note: Dcor does not only allow for correction of input SGML files but also validates and converts to mdb format Corrected SGML file Filename.corr Input requirements file Dcor (Val/Conv/Corr) Output Input Link Correcteddatabase file Filename.mdb Text editor (Notepad)

21. Files assembling and Final Validation tool File 1 File with notices ready for submission to BR File 2 File 3 File assembling and final data Validation (DNotif) File n Val OK? Reference Database(analog TV,other services) Notices with errors

22. Submission of requirements to BR • Preferably by Email • brmail@itu.int • Message subject: “RRC- Submission of digital requirements for the Draft Plan“ • Message body: summary of file contents (N° of notices, notice types, etc), signature • Attachment: valid SGML file

23. References • RRC Report (revised version) • Report of IPG-1 • BR Circular Letters (CR/…) • BR IFIC (MIFR/Plans ST61-GE89) • ITU Web site “http://www.itu.int/ITU-R/conferences/rrc/rrc-04/intersession/index.asp” (database structure, software, additional documentation) • BR Contact address: brmail@itu.int

24. RRC Input data Processing Team B. Rackov S. Pinnagoda A. Skokova B. Ba A. Méndez Thank you ALL!!!

25. Workshop (this afternoon) and BR IFIC (on request)