1. SANA Report to CMC Marc Blanchet, Guillaume Leclanche Viagénie CCSDS Noordwijkerhout 2013-04-07 Marc.Blanchet@viagenie.ca Guillaume.Leclanche@viagenie.ca http://www.viagenie.ca

2. Activities since San Antonio Operating the registries CCSDS Glossary update Google Analytics complete implementation SM&C XML Schemas Assisting CCSDS working groups RESTful API: Integrating and normalizing Spacecraftid registry

3. Analytics reports (Website Stats) Top Cities Origin of the traffic Operating Systems

4. SANA Spacecraft Registry Summary Resolving issues between old SCID registry (text file) and source materials has been a challenge Paper forms with “sticky notes” & “scribbles” Missing forms, missing Email, missing requests or responses Registries are now 90% plus updated in working version of DB Assignment overlaps for identified for three (3) S/C (GALEX, LRO, Syracuse-3B), but operational impacts are not expected (see next page) Version 2 SCID assignment space nearly exhausted, limited ability to satisfy explicit number, identical V1 & V2, or large requests Developed new transaction based, automated, form with built in checking and workflow, form operational in March 2014 Some open questions remain, will be resolved in SSG via telecon Need final updates and agency contact verification, then into production

5. The SCID Conflicts VersionGSCID (Hex) CriticalAgency #1SC #1Agency #2SC #2Probable true SC 1075NONASAORBVIEW-4ESAASTRO-SPASORBVIEW-4 1089NONASAEO-1ESAARABSAT2-BSS-1- both - 103DNONASAJUNOESAINTELSAT-K-TVJUNO 10D4YESNASAGALEXESAINTELSAT-K-TV- both - 10A5YESNASALRONASAMAP- both - 10E2NOCNESSPIRALE-2NASAST5-2SPIRALE-2 10E4NOCNESSPRALE-SIMNASAST5-3SPIRALE-SIM 10F7YESESASYRACUSE-3BNSPOROCSAT-2- both - 1246NOCNESSKYNET-5DCNESSKYNET-5CSKYNET-5D 0D4: GALEX was initially assigned « other » GSCIDs but NASA requested D4 for it and it was assigned although already used by INTELSAT-K-TV. There are differences in the frequencies used. No mention whether the projects were notified or not. 0A5: There are only a few MHz difference in the frequencies used. The projects had already been informed by the previous SCID registry maintainer. 0F7: There are differences in the frequencies used. The projects had already been informed by the previous SCID registry maintainer.

6. Upcoming Work Combined and unified contact database  MACAO, Spacecraftid reps, agency reps, etc  to be coordinated with CCSDS main web site  goal: a single storage of information with API to cross- reference Object identifiers registry tree-view (CSTS request) Ticket system for tracking requests, integrated with info@sanaregistry.org

7. Upcoming Work Update web site (to have similar look&feel of ccsds.org) Handling of Versioning (ex: Schemas) RESTful API in production Considering use of the web registration form/process developed for spacecraftid for all registries Meet/Assist various working groups for upcoming/current work (D-DOR, CSTS,...) Spacecraftid registry updated and in production

8. Backup Contents SANA(ty) report SCID issue examples V1 and V2 SCID registry analysis Conflicts Open Issues

9. Spacecraft IDs Registry Sanity Report and Actions Marc Blanchet Guillaume Leclanche Viagénie Marc.Blanchet@viagenie.ca Guillaume.Leclanche@viagenie.ca http://www.viagenie.ca

10. SCID Assignments Most assignment requests come with special instructions:  requesting specific ID is not always possible  requesting a large set of consecutive IDs  The technical reasons are not always obvious

11. SCID Registry Cleanup Context reminder:  before: different sources of authoritative data for spacecraftid (paper, WDC excel sheet, WDC text registry). Contradictory data. Need to cleanup. Hired secretary for 3 months, full time. Started early January, ended March 28th. Cleanup mostly done.  ~ 1000 spacecraftids verified/corrected/enhanced  ~ 100 spacecraftids remaining to be verified When cleanup finalized, then merged clean database will be put into production.

12. SCID Registry Cleanup, contd The only real authoritative data was the paper forms. Some were missing. A lot of scribbling on the papers. Period in which the registry was in limbo. Printed emails show that agencies were running their own registry which ran into duplicated registrations. Papers were scanned. Each spacecraftid now has an attachment with the paper forms, for future reference (but kept private).

13. Examples of Paper Trail

14. Status of Spacecraftid Registry

15. SCID Version 1 (TM) Not Assigned: 254 (24%)  white Returned: 54 (5%)  pale blue Assigned: 710 (69%)  green Uncleared: 6 (1%)  red

16. SCID Version 2 (TC) Not Assigned: 41 (16%)  white Returned: 23 (8%)  pale blue Assigned: 192 (75%)  green Uncleared: 0 (0%)  red

17. SCID Version 3 (Prox) Free: 1011 (98%)  white Returned: 2 (1%)  pale blue Assigned: 11(1%)  green Uncleared: 0 (0%)  red

18. New conflicts are discovered by the agencies CNES asked us to check a specific SCID  It was allocated by e-mail, but never recorded  There are no traces in the records  The only trace is the e-mail history on CNES server  After verification, it creates a new conflict if used in real flight by CNES. How should SANA proceed ?

19. Spacecraft IDs New Backend Transaction-based:  For each existing ID, we record all transactions  Assignments, returns, reassignments are separate transactions  Allows to easily rebuild the history of an ID and check consistency We build Unit Tests  Simple tests checking the consistency of the backend: Do all returns correspond to an assignment ? Are all dates valid ? Etc. We generate the public record from this backend directly without human intervention.

20. Assignment Request Form Process Requests are now handled by a web request form and its processing engine Request by the Agency Representative: Request by the End-User:

21. Assignment Request Form Advantages Spacecraftid registry history has shown that many issues are related to manual re-entry of data.  Automating requests starting at the source minimize this problem. Simple straightforward process. Fill the form, then click on links in e-mails. Requires only manual validation of the allocation by SANA Went through a beta program with a few requests. Put into production in march. For any question, contact info@sanaregistry.org !info@sanaregistry.org

22. Registry Questions What should be the returns display Policy?  Display all Returns ever done  Display only Returns that are the last transaction on an SCID (not yet reassigned)  Don't display Returns at all For Returns, which date to display ?  Return Date  Assignment Date  Both Should additional data be shown publicly?  currently not shown: frequencies, launch dates,...

23. Registry Questions Updating spacecraftid records:  Missions/Spacecrafts: change name during the life of the mission have multiple names for the same mission may change data (frequencies, launch date,...)  How can SANA receives the latest changes? Special requests such as:  V1 and V2, synchronized  specific id  Currently handled in free text in the form, requires manual intervention. Would like to automate, which means offering various possibilities in the form.

24. Agency Representatives Looking for “Godfathers”  GISTDA (TH) – V1 212 (THEOS) 2004-12-06  OSTIN (SG) – V2 1E2 (POPSAT-HIP1) 2013-07-10  Assigned with authorization from CCSDS Secretary [GR] Hellenic National Space Committee  Need an e-mail address  Need an abbreviation [DK] Danish Space Research Institute  Need an abbreviation. Is “DSRI” ok ? [IL] Ministry of Communications  Need an abbreviation. Is “MOC” ok ? [SE] Swedish Space Corporation  Need an abbreviation. Is “SSC” ok ? [RU] Central Research Institute of Machine Building  Need an abbreviation. Is “TSNIIMASH” ok ?

25. Spacecraft ID Next Steps Finish cleanup task Send questions to agency representatives for spacecrafts that have an unclear status Final integration and QA. Put into production the new database.

26. Questions? info@sanaregistry.org Marc.Blanchet@viagenie.ca Guillaume.Leclanche@viagenie.ca