12.07.2015 Views

Before the Federal Communications Commission Washington, D.C. ...

Before the Federal Communications Commission Washington, D.C. ...

Before the Federal Communications Commission Washington, D.C. ...

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Federal</strong> <strong>Communications</strong> <strong>Commission</strong> FCC 02-64as 2,500 headends and nodes. 20 Commenters express concern that some broadcast stations and cablesystems, particularly smaller entities, may forego equipment upgrades necessary to incorporate <strong>the</strong>revised codes because of <strong>the</strong>se costs. 21 As we discuss in more detail below, we do not wish to imposeadditional costs and burdens on EAS participants that may result in reduced voluntary participation instate and local EAS activities. We are also very concerned that revision of <strong>the</strong> existing codes may cause<strong>the</strong> public to miss emergency warnings for <strong>the</strong>se important events if some broadcast stations and cablesystems choose not to upgrade <strong>the</strong>ir EAS equipment.10. Moreover, NWS disputes our suggestion in <strong>the</strong> NPRM that it has <strong>the</strong> capability totransmit both existing and revised codes for Tornado Warning, Severe Thunderstorm Warning andEvacuation Immediate events during a transition period, asserting that NWR-SAME systems cannotencode two event codes in <strong>the</strong> same message header. 22 O<strong>the</strong>r commenters also raise strenuous objectionsto this suggestion, arguing that <strong>the</strong> simultaneous transmission of existing and revised codes for <strong>the</strong>seimportant events could lead to confusion and error. 23 Thus, it appears that providing a transition periodduring which both existing and revised codes could be used is not a viable option. Particularly in view of<strong>the</strong> cost and safety concerns cited above, we are unwilling to revise any existing event codes withoutbeing able to afford broadcast stations and cable systems an adequate period of time to ease <strong>the</strong>transition.b. New Event Codes11. Section 11.31(e) of <strong>the</strong> Rules lists <strong>the</strong> authorized three-letter event codes for nationalEAS events and tests, which broadcasters and cable systems are required to receive and transmit, and forstate and local EAS events, which broadcasters and cable systems voluntarily participating in state andlocal area EAS plans may transmit on an optional basis. 24 We sought comment in <strong>the</strong> NPRM on requestsby NWS and o<strong>the</strong>rs that we amend Section 11.31(e) to add new state and local event codes foremergency conditions not included in <strong>the</strong> current list and for certain administrative messages and non-EAS applications. 25 We included a listing of <strong>the</strong> recommended new event codes in an Appendix to <strong>the</strong>NPRM. 26 We also sought comment on whe<strong>the</strong>r, as an alternative to adding new state and local eventcodes and location codes, we should amend <strong>the</strong> rules to provide that any modifications to existingauthorized EAS equipment that are necessary to implement revisions in EAS codes are Class I permissivechanges that do not require a new application for and grant of equipment certification. 27 Under thisalternative, broadcasters and cable systems could satisfy <strong>the</strong>ir EAS obligations with equipment designedto function with ei<strong>the</strong>r <strong>the</strong> existing codes or an expanded range of codes. Additional state and local event20NCTA Comments at 5.21NCTA Comments at 4; Named StBAs Comments at 6; WSAB/WA SECC Comments at 4; Seven RangesComments at 11.222324252627NWS Comments at 2.Named StBAs Comments at 7; WSAB/WA SECC Comments at 4.47 C.F.R. § 11.31(e).NPRM, 16 FCC Rcd at 7257.Id. at 7268-69.Id. at 7261. See 47 C.F.R. § 2.1043.6

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!