1 / 25

NOAA’s Beacon Registration Database (RGDB)

NOAA’s Beacon Registration Database (RGDB). www.beaconregistration.noaa.gov. NOAA SARSAT PROGRAM. Topics To Be Covered. RGDB – mass mailing efforts SAR User Access Creation of accounts Resolving lock out situations Deactivating accounts How RGDB is updated with RCC feedbacks

cleo
Download Presentation

NOAA’s Beacon Registration Database (RGDB)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. NOAA’s Beacon Registration Database(RGDB) www.beaconregistration.noaa.gov NOAA SARSAT PROGRAM

  2. Topics To Be Covered • RGDB – mass mailing efforts • SAR User Access • Creation of accounts • Resolving lock out situations • Deactivating accounts • How RGDB is updated with RCC feedbacks • SAR Usage of RGDB • Suggestions on how RCCs can help improve RGDB info

  3. RGDB Mass Mailing Effort • Started in May, 2009 • Finished December, 2009 • Emailed/mailed a special letter to all registered owners with registration information to particularly pay attention to beacon id Results • NOAA surprised to learn that beacon owners made lot more mistakes on beacon id vs NOAA data entry personnel • Lots of false incorrect beacon ids – older beacons • IRT Recommendations – NOAA has started to look into ways to make changes to minimize chance of error on beacon ids by any user

  4. Access to RGDB &IHDB by USCG • Anytime a new user joins the USCG RCC, the following needs to happen: • An email request needs to go to USCG headquarters to: • LCDR Mark Turner U.S. Coast Guard Headquarters Office of Search and Rescue (CG-5342) SARSAT Liaison Officer Tel: (202) 372-2089 Mark.W.Turner@uscg.mil

  5. Access to RGDB &IHDB by USCG • Once LCDR Turner validates the user to be added for the RGDB and IHDB, a Microsoft Excel file is sent to NOAA with the following information: • User Name • First Name • Last Name • Organization Name • Phone Number • Email Address

  6. Access to RGDB &IHDB by USCG • NOAA: • creates a user account and password for each new member for RGDB and IHDB • encrypts the new output file with the password information • sends the encrypted file to LCDR Turner to be distributed to the respective USCG RCCs

  7. Access to RGDB &IHDB by AFRCC • Dan Conley sends an email request: • Dan Conley, USAF AFRCC Chief of Operations Tyndall AFB, FL 850-283-5688 Danny.Conley@tyndall.af.mil

  8. Access to RGDB &IHDB by AFRCC • NOAA: • creates a user account and password for each new member for RGDB & IHDB • relays the user ids and passwords for IHDB over the phone to Mr. Conley • an encrypted file could not be received by AFRCC • in future, hope to exchange this information electronically with AFRCC

  9. Access to RGDB & IHDB by AKRCC • When a new user joins the AKRCC, the following needs to happen: • An email request comes to NOAA from: • Current alternate contact: Dan Conley, USAF • AFRCC • 850-283-5688 • Danny.Conley@tyndall.af.mil

  10. Access to RGDB &IHDB by AKRCC • NOAA: • creates a user account and password for each new member for RGDB and IHDB • relays the user ids and passwords for IHDB over the phone to Mr. Conley at this time • an encrypted file could not be received by AFRCC • hope is the ability to exchange this information electronically with AKRCC in the near future

  11. Lock Out Procedure • If a RCC user is locked out of the RGDB or the IHDB system: • Only call the USMCC 24/7 at 301.817.4576 • Provide the specific user Id and subsystem and which organization the user is calling from • A new password will be issued to the user for this subsystem • Please ignore the phone number displayed on the Registration Database website when a SAR user id is locked out. • 301.817.4515 (this line is for beacon owners only and not for SAR users)

  12. Inactive User Accounts • When controllers leaveNOAA needs the following to take away access to these subsystems: • An electronic file containing: • User name • First name • Last name • Organization name • Phone number • Email address

  13. 406 MHz Registration Requirements • All 406 MHz beacons coded with a USA country code must be registered with NOAA • Title 47 - Parts 80, 87, and 95 in the Code of Federal Regulations • Owners should be informed of the following: • ``WARNING--failure to register their beacon with NOAA before installation could result in a monetary forfeiture being issued to the owner.''

  14. 406 MHz Proof of Registration • NOAA letters state the following: • The proof of registration decal or the proof of registration data sheet provided by NOAA may be used as proof of beacon registration • Currently, this guidance only applies to ELTs when owners call us • In the future, NOAA will customize the letters by beacon registration type to satisfy the proof of registration requirement: • Decals will not be issued for ELTs • Decals will be issued for EPIRBs • Decals may be issued for PLBs

  15. RCC Feedback • The RCC should provide specific new phone number information when it is different than what is listed on the registration. Having a name with a phone number is always preferred. John Doe’s new cell number is XXX-XXX-XXXX. • “NONE OF THE BEACON REGISTRATION CONTACT NUMBERS WOULD WORK.” – prefer comments such as: • tried all owner/operator phone numbers, • tried all vessel numbers, looked up the vessel by documentation number, tried all emergency point of contact numbers. They all had a recording to indicate the number is disconnected or out of service or re-assigned to someone else.

  16. RCC Feedback • “Vessel was sold multiple times and is in Mexico contacted RCC Mexico to attempt to locate with negative results.” • Updated the RGDB with: • “7/1/09-per CDG07 Vessel was sold multiple times” • We updated due to the fact the decal was quite old and adding these comments could assist with the rescue. If it has a current decal, it could be misleading due to the fact the owner may still have the beacon and not the vessel and updating the comment could possibly give false hope to search for the vessel when the owner may still have the beacon.

  17. RCC Feedback “OWNER RPTED SELLING VESSEL IN 2005” What happened to the beacon? Was the beacon sold with the vessel or did the owner keep it? “BEACON IS ON A DIFFERENT TAIL” If a beacon is on a different tail, indicate beacon on a different tail than on registration and also provide the current tail number. Is this a temporary change or permanent change? Is the owner planning on updating this information with NOAA if it is a permanent change?

  18. RCC Feedback • NOAA will update the actual fields on the registration when specific feedback is provided by RCCs. For example: • John Doe’s new cell is NNN-NNN-NNNN per RCC comments • Cell number for John Doe will be updated and a comment in additional data will reflect some duplicated entry to reflect what action took place and the source of the RCC that caused the change • If John Doe is the registered owner, John Doe will be contacted on this number to make sure all the other information on the registration is current and NOAA will provide guidance to owner on how to make the necessary updates.

  19. RCC Feedback • The RCC notes indicate the new beacon owner’s name and phone number • NOAA will • Update the RGDB additional data • Call old owner to confirm sale • Inform the new owner to register the beacon • The RCC notes indicate vessel or tail number has changed • NOAA will • Update the RGDB additional data with this new change • Contact the registered owner to review the registered information and provide guidance to owner to make changes to the registration information.

  20. RGDB Usage For Year 2010

  21. RGDB Accuracy For Year 2010

  22. Suggestions On How RCC Personnel Can Help • Inform new and existing beacon owners regarding the option to register, make updates to registration information or re-register the beacons via Web. • Inform the owner to make sure they list phone numbers for owner/operator information which will add value to Search and Rescue efforts if the beacon goes off • Inform the owner/operator not to list the same phone numbers under owner operator section and the emergency point of contact section • Emergency point of contacts should be someone who will not likely be involved if there is an emergency • Inform owners to make updates when information changes and not wait till the renewal time

  23. Home Port State For Unlocated Alerts ELTs & EPIRBs • SRR chosen per Home Port State provided • If Home Port State not provided, RCC chosen based on mailing state PLBs • SRR chosen per mailing state • For Alaska, SRR chosen by mailing city and state

  24. GeoSort 406 RGDB SRR Assignments

  25. Future SRR Assignment Issues • NOAA needs to assign SRR by homeport country • The Registration Database software needs to be modified • Agreement from the RCCs what SRR to assign • Address ELT, EPIRB, PLB separately • When HomePort country is not provided, the SRR will • be provided using mailing country • Registration mechanics • Drop down list for home port/mailing country

More Related