WPC 2 BJZCourier3|a x6X@`7X@HP LaserJet 5Si LPT2:HPLAS5SI.PRSx  @\$ZX@ X4#C\  P6QɒP#X01Í ÍX01Í Í#XP\  P6QynXP#2B<KTXKCourierTimes New Roman"i~'^09CSS999S]+9+/SSSSSSSSSS//]]]Ixnnxg]xx9?xgxx]xn]gxxxxg9/9MS9ISISI9SS//S/SSSS9?/SSxSSIP!PZ9+ZM999+999999S9S/xIxIxIxIxIlnIgIgIgIgI9/9/9/9/xSxSxSxSxSxSxSxSxSxSxIxSxRxSxSxS]SxIxIxInInInZnIxigIgIgIgIxSxSxSxZxSxZxS9/9S999Su]ZZxSg/gCg9g9g/xSbxSxSxSxSxn9n9n9]?]?]?]ZgFg/gMxSxSxSxSxSxSxxZgIgIgIxSg9xS]?g9xSi+SS88WuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxNI\\>>>\g0>03\\\\\\\\\\33gggQyyrg>Frgygrr>3>T\>Q\Q\Q>\\33\3\\\\>F3\\\\QX%Xc>0cT>>>0>>>>>>\>\3QQQQQwyQrQrQrQrQ>3>3>3>3\\\\\\\\\\Q\Z\\\g\QQQyQyQycyQtrQrQrQrQ\\\c\c\>3>\>>>\gcc\r3rIr>r>r3\l\\\\y>y>y>gFgFgFgcrMr3rT\\\\\\crQrQrQ\r>\gFr>\t0\\=!=WxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxNBnnBT\>Q\\\\\3;\7;\7>>QQ\??n\\nBnnBmgg>Q\7"yyyy\njc\gnn\Times New RomanTimes New Roman BoldTimes New Roman ItalicCourierfootnote reference# a8DocumentgDocument Style StyleXX` `  ` 2pkqkGa4DocumentgDocument Style Style . a6DocumentgDocument Style Style GX  a5DocumentgDocument Style Style }X(# a2DocumentgDocument Style Style<o   ?  A.  2Evt  a7DocumentgDocument Style StyleyXX` ` (#` BibliogrphyBibliography:X (# a1Right ParRight-Aligned Paragraph Numbers :`S@ I.  X(# a2Right ParRight-Aligned Paragraph Numbers C @` A. ` ` (#` 2> w  a3DocumentgDocument Style Style B b  ?  1.  a3Right ParRight-Aligned Paragraph Numbers L! ` ` @P 1. ` `  (# a4Right ParRight-Aligned Paragraph Numbers Uj` `  @ a. ` (# a5Right ParRight-Aligned Paragraph Numbers_o` `  @h(1)  hh#(#h 2p8a6Right ParRight-Aligned Paragraph Numbersh` `  hh#@$(a) hh#((# a7Right ParRight-Aligned Paragraph NumberspfJ` `  hh#(@*i) (h-(# a8Right ParRight-Aligned Paragraph NumbersyW"3!` `  hh#(-@p/a) -pp2(#p Tech InitInitialize Technical Style. k I. A. 1. a.(1)(a) i) a) 1 .1 .1 .1 .1 .1 .1 .1 Technical2ja1DocumentgDocument Style Style\s0  zN8F I. ׃  a5TechnicalTechnical Document Style)WD (1) . a6TechnicalTechnical Document Style)D (a) . a2TechnicalTechnical Document Style<6  ?  A.   2fxa3TechnicalTechnical Document Style9Wg  2  1.   a4TechnicalTechnical Document Style8bv{ 2  a.   a1TechnicalTechnical Document StyleF!<  ?  I.   a7TechnicalTechnical Document Style(@D i) . 2%3 Q!eU%a8TechnicalTechnical Document Style(D a) . Doc InitInitialize Document Stylez   0*0*0*  I. A. 1. a.(1)(a) i) a) I. 1. A. a.(1)(a) i) a)DocumentgPleadingHeader for Numbered Pleading PaperE!n    X X` hp x (#%'0*,.8135@8:a݅@  I.   X(# 2g*#y($)%l)&l)SubheadingSubheading#0\ E A.  Default ParaMtDefault Paragraph FontRK+7*P0_ f—+7*b$Default Paragraph FoDefault Paragraph Font% Document 8Document 8& 2U,'x*(l+)l}+*l+Document 4Document 4'  Document 6Document 6( Document 5Document 5) Document 2Document 2* 21+l,,,-/.l/1Document 7Document 7+ Right Par 1Right Par 1,` hp x (#X` hp 0X` hp 0` hp x (#Right Par 2Right Par 2-` hp x (#X` hp X` hp ` hp x (#Document 3Document 3. 2E:/1031 62'8Right Par 3Right Par 3/` hp x (#X` hp 0X` hp 0` hp x (#Right Par 4Right Par 40` hp x (#X` hp X` hp ` hp x (#Right Par 5Right Par 51` hp x (#X` hp X` hp ` hp x (#Right Par 6Right Par 62` hp x (#X` hp X` hp ` hp x (#2B3w:4<5(>6$@Right Par 7Right Par 73` hp x (#X` hp 0X` hp 0` hp x (#Right Par 8Right Par 84` hp x (#X` hp X` hp ` hp x (#Document 1Document 15` hp x (#X` hp X` hp ` hp x (#Technical 5Technical 56` hp x (#X` hp  X` hp ` hp x (#2QH7$1C8lUE9lE:$-FTechnical 6Technical 67` hp x (#X` hp  X` hp ` hp x (#Technical 2Technical 28 Technical 3Technical 39 Technical 4Technical 4:` hp x (#X` hp  X` hp ` hp x (#2UO;lH<$H=$K>7MTechnical 1Technical 1; Technical 7Technical 7<` hp x (#X` hp  X` hp ` hp x (#Technical 8Technical 8=` hp x (#X` hp  X` hp ` hp x (#toc 1toc 1>` hp x (#` hp x (#2W?O@QASBUtoc 2toc 2?` hp x (#` ` ` hp x (#toc 3toc 3@` hp x (#` ` ` hp x (#toc 4toc 4A` hp x (#  ` hp x (#toc 5toc 5B` hp x (#hh` hp x (#2_C1XDvOZEZF\toc 6toc 6C` hp x (#` hp x (#toc 7toc 7D toc 8toc 8E` hp x (#` hp x (#toc 9toc 9F` hp x (#` hp x (#2fG3_HQaIocJveindex 1index 1G` hp x (#` ` ` hp x (#index 2index 2H` hp x (#` ` ` hp x (#toa headingtoa headingI` hp x (#` hp x (#captioncaptionJ 2xhKl5fL^fMdfNcg_Equation Caption_Equation CaptionK FOOTNOTEFootnote - AppearanceLPHIGHLIGHT 1Italics and BoldldeddM+. DRAFT ONHeader A Text = DRAFT and DateN X =8` (#FDRAFTă r  ` (#=D3 1, 43 12pt (Z)(PC-8))T2Dă  ӟ2kOhPXBiQ1iR1jDRAFT OFFTurn Draft Style offO@@    HEADERHeader A - AppearancePLETTER LANDLetter Landscape - 11 x 8.5Q 3'3'Standard'3'3StandardLetter Portrait - 8.5 x 11 ;   LEGAL LANDLegal Landscape - 14 x 8.5Rf 3'3'Standard'A'AStandardZ K e6VE L"nu;   2VoS1.lT1_mUnnVXnLETTER PORTLetter Portrait - 8.5 x 11SL 3'3'Standard3'3'StandardZ K e6VE L"nU9   LEGAL PORTLegal Portrait - 8.5 x 14T 3'3'StandardA'A'StandardLetter Portrait - 8.5 x 119   TITLETitle of a DocumentUK\ * ăFOOTERFooter A - AppearancedV2@qWoXi pYdrpZjpBLOCK QUOTESmall, single-spaced, indentedWN X HEADING 33rd Heading LevelX| XHIGHLIGHT 2Large and Bold LargeYB*d. HIGHLIGHT 3Large, Italicized and UnderscoredZ V -q2;w[rq\Es]-t^8vLETTERHEADLetterhead - date/margins[u H XX  3'3'LetterheadZ K e VE L"n3'3'LetterheadZ K e VE L"nE9    * 3'3'LetterheadZ K e VE L"n3' II"n"Tv3'StandarddZ K e VE L"nU9 Ѓ   INVOICE FEETFee Amount for Math Invoice\ ,, $0$0  MEMORANDUMMemo Page Format]D.   ! M E M O R A N D U M ă r  y<N dddy   INVOICE EXPSEExpense Subtotals for Math Invoice^:A ,p, $0$002z_8mw`xaXFzb[zINVOICE TOTTotals Invoice for Math Macro_z 4p, $0$00INVOICE HEADRHeading Portion of Math Invoice`+C`*   4X 99L$0 **(  ӧ XX NORMALReturn to Normal TypestyleaSMALLSmall Typestyleb2|c[+{d[{e[{f[<|FINEFine TypestylecLARGELarge TypestyledEXTRA LARGEExtra Large TypestyleeVERY LARGEVery Large Typestylef2g|hL~ip~jq;ENVELOPEStandard Business Envelope with Headerg+w ,,EnvelopeZ K e VE L"n,,EnvelopeLarge, Italicized and Under;    ,, 88+  `   footnote tex#h']#d6X@C@#Document[8]'Eg%Document StyleE O  O g% W4I O gi` ` ` Document[4]'Eg%Document Style W4A O g% W4I O gj  . 2keleCmnp;Document[6]'Eg%Document Style W4A O g% W4I O gk  Document[5]'Eg%Document Style W4A O g% W4I O gl  Document[2]'Eg%Document Style W4A O g% W4I O gm*    Document[7]'Eg%Document Style W4A O g% W4I O gn  ` ` ` 2Co݁poq rRight Par[1]Eg%Right-Aligned Paragraph NumbersO g% W4I O go8 @  Right Par[2]Eg%Right-Aligned Paragraph NumbersO g% W4I O gpA@` ` `  ` ` ` Document[3]'Eg%Document Style W4A O g% W4I O gq0     Right Par[3]Eg%Right-Aligned Paragraph NumbersO g% W4I O grJ` ` ` @  ` ` ` 2_sut"u؅vRight Par[4]Eg%Right-Aligned Paragraph NumbersO g% W4I O gsS` ` `  @  Right Par[5]Eg%Right-Aligned Paragraph NumbersO g% W4I O gt\` ` `  @hhh hhh Right Par[6]Eg%Right-Aligned Paragraph NumbersO g% W4I O gue` ` `  hhh@ hhh Right Par[7]Eg%Right-Aligned Paragraph NumbersO g% W4I O gvn` ` `  hhh@  2&wxbyzRight Par[8]Eg%Right-Aligned Paragraph NumbersO g% W4I O gww` ` `  hhh@ppp ppp Document[1]'Eg%Document Style W4A O g% W4I O gxF    ׃  Technical[5]Eg%Technical Document Style O g% W4I O gy&!"  . Technical[6]Eg%Technical Document Style O g% W4I O gz&#$  . 2͌{X|}~Technical[2]Eg%Technical Document Style O g% W4I O g{*%&    Technical[3]Eg%Technical Document Style O g% W4I O g|''(   Technical[4]Eg%Technical Document Style O g% W4I O g}&)*   Technical[1]Eg%Technical Document Style O g% W4I O g~4+$,     2׏  Technical[7]Eg%Technical Document Style O g% W4I O g&-.  . Technical[8]Eg%Technical Document Style O g% W4I O g&/0  . CitatorFormat Secretary's Citator Output FileW r5-#d6X@`7Ͽ@# XX  X B r5-S  BFormat DownloadFormat Downloaded Documentiޛ r5- XX    \ #d6X@`7Ͽ@#2v ~iMACNormal;     X` hp x (#%'0*,.8135@8:<    #:}D4P XP#T I. A. 1. a.(1)(a) i) a)T,0*ÍÍ,*Í ., US!!!! ! #:}D4P XP#     X` hp x (#%'0*,.8135@8:<    #:}D4P XP#,0*ÍÍ,*Í ., US!!!! ! #:}D4P XP#reference;#FxX  Pg9CXP#itemizeX1&V 8F ` hp xr#FxX  Pg9CXP#header2I ` hp x`    #FxX  Pg9CXP# 2a}+0áa1Paragraph+%X,1. a. i. (1) (a) (i) 1) a)%8=(%  H*%F$ a2Paragraph+%X,1. a. i. (1) (a) (i) 1) a)%8=(%  H*%F/ a3Paragraph+%X,1. a. i. (1) (a) (i) 1) a)%8=(%  H*%F: a4Paragraph+%X,1. a. i. (1) (a) (i) 1) a)%8=(%  H*%FE 2y<a5Paragraph+%X,1. a. i. (1) (a) (i) 1) a)%8=(%  H*%FP   a6Paragraph+%X,1. a. i. (1) (a) (i) 1) a)%8=(%  H*%F[   a7Paragraph+%X,1. a. i. (1) (a) (i) 1) a)%8=(%  H*%Ff  a8Paragraph+%X,1. a. i. (1) (a) (i) 1) a)%8=(%  H*%Fq 2 Xۦ[footnote refK&7>footnote referenceGw) "7>NGI "+WXpage numberK&7>page number"Gw* "7>NGI "(YZendnote refeK&7>endnote referenceGw- "7>NGI "+_+`2;1uannotation rK&7>annotation referenceGw. "7>NGI "OaOb#Xv P7XP##Xv P7XP#annotation tK&7>annotation textGw/ "7>NGI "2c(d2G2*(K&7>Right-Aligned Paragraph Numbers"7>NGI "8ij@  3G3*(K&7>Right-Aligned Paragraph Numbers"7>NGI "Akl@` ` `  ` ` ` 2BI4G4*(K&7>Right-Aligned Paragraph Numbers"7>NGI "Jmn` ` ` @  ` ` ` 5G5*(K&7>Right-Aligned Paragraph Numbers"7>NGI "Sop` ` `  @  6G6*(K&7>Right-Aligned Paragraph Numbers"7>NGI "\qr` ` `  @hhh hhh 7G7*(K&7>Right-Aligned Paragraph Numbers"7>NGI "est` ` `  hhh@ hhh 2:pӯC8G8*(K&7>Right-Aligned Paragraph Numbers"7>NGI "nuv` ` `  hhh@  9G9*(K&7>Right-Aligned Paragraph Numbers"7>NGI "wwx` ` `  hhh@ppp ppp 10G0*(Q&7tDocument Style Gl0 "7t GI "םGH` ` ` 11G1*(Q&7tTechnical Document Style "7t GI "מ4I$J     2o%V12G2*(Q&7tTechnical Document Style "7t GI "ן*KL    13G3*(Q&7tTechnical Document Style "7t GI "נ'MN   14G4*(Q&7tTechnical Document Style "7t GI "ס&OP   15G5*(Q&7tTechnical Document Style "7t GI "ע&QR  . 2µ&016G6*(Q&7tTechnical Document Style "7t GI "ף&ST  . 17G7*(Q&7tTechnical Document Style "7t GI "פ&UV  . 18G8*(Q&7tTechnical Document Style "7t GI "ץ&WX  . 19G9*(Q&7tRight-Aligned Paragraph Numbers"7t GI "צ8YZ@  2320G:*(Q&7tRight-Aligned Paragraph Numbers"7t GI "קA[\@` ` `  ` ` ` 21G;*(Q&7tRight-Aligned Paragraph Numbers"7t GI "רJ]^` ` ` @  ` ` ` 22G<*(Q&7tRight-Aligned Paragraph Numbers"7t GI "שS_`` ` `  @  23G=*(Q&7tRight-Aligned Paragraph Numbers"7t GI "ת\ab` ` `  @hhh hhh 2ڻȸO 24G>*(Q&7tRight-Aligned Paragraph Numbers"7t GI "׫ecd` ` `  hhh@ hhh 25G?*(Q&7tRight-Aligned Paragraph Numbers"7t GI "׬nef` ` `  hhh@  26G@*(Q&7tRight-Aligned Paragraph Numbers"7t GI "׭wgh` ` `  hhh@ppp ppp 1wSg 6w Document Style=(H8g ܺ*HںwSg EF *  ׃  2Ҿ ]27wSg K6w Right-Aligned Paragraph Numbersܺ*HںwSg EJmn` ` @  ` `  28wSg L6w Right-Aligned Paragraph Numbersܺ*HںwSg ESop` `  @  29wSg M6w Right-Aligned Paragraph Numbersܺ*HںwSg E\qr` `  @hh# hhh 30wSg N6w Right-Aligned Paragraph Numbersܺ*HںwSg Eest` `  hh#@( hh# 2̿p 31wSg O6w Right-Aligned Paragraph Numbersܺ*HںwSg Enuv` `  hh#(@- ( 32wSg P6w Right-Aligned Paragraph Numbersܺ*HںwSg Ewwx` `  hh#(-@pp2 -ppp 33wSg R6w Document Style=(H8g Rܺ*HںwSg E{|` ` ` 34wSg S6w Technical Document Styleg Sܺ*HںwSg E4}$~     29 35wSg T6w Technical Document Styleg Tܺ*HںwSg E*    36wSg U6w Technical Document Styleg Uܺ*HںwSg E'   37wSg V6w Technical Document Styleg Vܺ*HںwSg E&   38wSg W6w Technical Document Styleg Wܺ*HںwSg E&  . 2ku39wSg X6w Technical Document Styleg Xܺ*HںwSg E&  . 40wSg Y6w Technical Document Styleg Yܺ*HںwSg E&  . 41wSg Z6w Technical Document Styleg Zܺ*HںwSg E&  . 42wSg [6w Right-Aligned Paragraph Numbersܺ*HںwSg E8@   2`Y43wSg \6w Right-Aligned Paragraph Numbersܺ*HںwSg EA@` `  ` ` ` 44wSg ]6w Right-Aligned Paragraph Numbersܺ*HںwSg EJ` ` @  ` `  45wSg ^6w Right-Aligned Paragraph Numbersܺ*HںwSg ES` `  @  46wSg _6w Right-Aligned Paragraph Numbersܺ*HںwSg E\` `  @hh# hhh 2Q47wSg `6w Right-Aligned Paragraph Numbersܺ*HںwSg Ee` `  hh#@( hh# 48wSg a6w Right-Aligned Paragraph Numbersܺ*HںwSg En` `  hh#(@- ( 49wSg b6w Right-Aligned Paragraph Numbersܺ*HںwSg Ew` `  hh#(-@pp2 -ppp 50wSg c6w Document Style=(H8g cܺ*HںwSg EF *  ׃  2z'51wSg d6w Right-Aligned Paragraph Numbersܺ*HںwSg EJ` ` @  ` `  52wSg e6w Right-Aligned Paragraph Numbersܺ*HںwSg ES` `  @  53wSg f6w Right-Aligned Paragraph Numbersܺ*HںwSg E\` `  @hh# hhh 54wSg g6w Right-Aligned Paragraph Numbersܺ*HںwSg Ee` `  hh#@( hh# 2pg55wSg h6w Right-Aligned Paragraph Numbersܺ*HںwSg En` `  hh#(@- ( 56wSg i6w Right-Aligned Paragraph Numbersܺ*HںwSg Ew` `  hh#(-@pp2 -ppp 57wSg j6w Document Style=(H8g jܺ*HںwSg E` ` ` 58wSg k6w Technical Document Styleg kܺ*HںwSg E4$     2U~59wSg l6w Technical Document Styleg lܺ*HںwSg E*    60wSg m6w Technical Document Styleg mܺ*HںwSg E'   61wSg n6w Technical Document Styleg nܺ*HںwSg E&   62wSg o6w Technical Document Styleg oܺ*HںwSg E&  . 2V5?63wSg p6w Technical Document Styleg pܺ*HںwSg E&  . 64wSg q6w Technical Document Styleg qܺ*HںwSg E&  . 65wSg r6w Technical Document Styleg rܺ*HںwSg E&  . 66wSg s6w Right-Aligned Paragraph Numbersܺ*HںwSg E8@   2*#t67wSg t6w Right-Aligned Paragraph Numbersܺ*HںwSg EA@` `  ` ` ` 68wSg u6w Right-Aligned Paragraph Numbersܺ*HںwSg EJ` ` @  ` `  69wSg v6w Right-Aligned Paragraph Numbersܺ*HںwSg ES` `  @  70wSg w6w Right-Aligned Paragraph Numbersܺ*HںwSg E\` `  @hh# hhh 2n\71wSg x6w Right-Aligned Paragraph Numbersܺ*HںwSg Ee` `  hh#@( hh# 72wSg y6w Right-Aligned Paragraph Numbersܺ*HںwSg En` `  hh#(@- ( 73wSg z6w Right-Aligned Paragraph Numbersܺ*HںwSg Ew` `  hh#(-@pp2 -ppp 74wSg {6w Document Style=(H8g {ܺ*HںwSg EF *  ׃  23qe975wSg |6w Document Style=(H8g |ܺ*HںwSg E*   76wSg }6w Document Style=(H8g }ܺ*HںwSg E0    77wSg ~6w Document Style=(H8g ~ܺ*HںwSg E  . 78wSg 6w Document Style=(H8g ܺ*HںwSg E  2ep5p79wSg 6w Document Style=(H8g ܺ*HںwSg E  80wSg 6w Document Style=(H8g ܺ*HںwSg E` ` ` 81wSg 6w Document Style=(H8g ܺ*HںwSg E` ` ` 82wSg 6w Technical Document Styleg ܺ*HںwSg E4$     2A(83wSg 6w Technical Document Styleg ܺ*HںwSg E*    84wSg 6w Technical Document Styleg ܺ*HںwSg E'   85wSg 6w Technical Document Styleg ܺ*HںwSg E&   86wSg 6w Technical Document Styleg ܺ*HںwSg E&  . 2s}87wSg 6w Technical Document Styleg ܺ*HںwSg E&  . 88wSg 6w Technical Document Styleg ܺ*HںwSg E&  . 89wSg 6w Technical Document Styleg ܺ*HںwSg E&  . 90wSg 6w Right-Aligned Paragraph Numbersܺ*HںwSg E8@   2ha91wSg 6w Right-Aligned Paragraph Numbersܺ*HںwSg EA@` `  ` ` ` 92wSg 6w Right-Aligned Paragraph Numbersܺ*HںwSg EJ` ` @  ` `  93wSg 6w Right-Aligned Paragraph Numbersܺ*HںwSg ES` `  @  94wSg 6w Right-Aligned Paragraph Numbersܺ*HںwSg E\` `  @hh# hhh 2Y!95wSg 6w Right-Aligned Paragraph Numbersܺ*HںwSg Ee` `  hh#@( hh# 96wSg 6w Right-Aligned Paragraph Numbersܺ*HںwSg En` `  hh#(@- ( 97wSg 6w Right-Aligned Paragraph Numbersܺ*HںwSg Ew` `  hh#(-@pp2 -ppp 98wSg 6w Default Paragraph Font8g ܺ*HںwSg E;;#x6X@7X@##b6X@C@#2Jvendnote text6w endnote textH̺=(H8g ܺ*HںwSg EE;#x6X@7X@##b6X@C@#99wSg 6w endnote referenceH8g ܺ*HںwSg E>>#x6X@7X@##b6X@ C@#100wSg 6w footnote text̺=(H8g ܺ*HںwSg EE;#x6X@ 7X@##b6X@ C@#101wSg 6w footnote referenceH8g ܺ*HںwSg E>>#x6X@ 7X@##b6X@ C@#2|J _Equation Ca6w _Equation CaptionH8g ܺ*HںwSg E;!;"#x6X@7X@##b6X@C@#endnote referenceendnote reference44#Xv6X@CX@##b6X@C@#footnote textfootnote text;1#Xv6X@CX@##b6X@C@#102OQ6CDocument Style=(5Qܺ*5ںOQEF#$ *  ׃  2KKKPK"i~'^,3g\\>>>\g0>03\\\\\\\\\\>>ggg\yyrF\yrgyy>3>j\>\gQgQ>\g3>g3g\ggQF>g\\\QI(I_>0_j>>>0>>>>>>\>g3\\\\\QyQyQyQyQD3D3D3D3g\\\\gggg\\g\\\\pg\\\QQ_QyQyQyQyQ\\\_\gjF3FgF>Fgg__gy3ySy>yIy3ggg\\QQQgFgFgFg_y^y>yjgggggg_yQyQyQgy>ggFy>\0\\=2=WxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxNBnnBa\>\\\\\\7>\7>\7>>\\\??n\\nBnnBsgg>\\7"yyyy\nlc\gnn\"i~'^,3TKK~333KT'3'*KKKKKKKKKK33TTTKlcllc]uu9Kuclu]ulTcllllc3*3WK3KTBTB3KT*3T*~TKTTB93TKlKKBM\\>>>\}0>03\\\\\\\\\\>>}}}\rryrr>Qygyrr\grrggF3FM\>\\Q\Q3\\33Q3\\\\FF3\QyQQFI3Ic>0cM>>>0>>>>>>\>\3r\r\r\r\r\yyQrQrQrQrQ>3>3>3>3y\\\\\\\\\gQr\\\\gQ\r\r\r\r\yQyQycyQnrQrQrQrQ\\\c\c\>3>\>>>\\ccyQg3gBg>g;g3y\jy\y\\\yrFrFrF\F\F\FccgBg3gM\\\\\\ygcgFgFgF\g>y\\Fg>g\n0\\=(=WddddddddddddddddddddddddddddddddddddddddNBnnB_\F\\\\\\3;\7;\7>>gg\??n\\nBnnBb\\>g\7"yyyy\njc\}nn\"i~'^ %,77\V%%%7>%7777777777>>>0eOIIOD>OO%*ODaOO>OI>DOOgOOD%%37%07070%777V7777%*77O77055;%;3%%%%%%%%%7%7O0O0O0O0O0aHI0D0D0D0D0%%%%O7O7O7O7O7O7O7O7O7O7O0O7O6O7O7O7>7O0O0O0I0I0I;I0OED0D0D0D0O7O7O7O;O7O;O7%%7%%%7M>;;O7DD,D%D%DO7AO7O7O7O7aOI%I%I%>*>*>*>;D.DD3O7O7O7O7O7O7gOO;D0D0D0O7D%O7>*D%O7E77%%WMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxN(BB(37%07777j7#TT7!#TT7T!%%007n&&Bn77lBTn(nBB(AZZ>>n%07\n!"IIIITTenn7TnB@;7>lBBn7"i~'^"(22TN"""28"2222222222888,\HBBH>8HH"&H>XHH8HB8>HH^HH>"".2",2,2,"222N2222"&22H22,006"6."""""""""2"2H,H,H,H,H,XAB,>,>,>,>,""""H2H2H2H2H2H2H2H2H2H2H,H2H1H2H2H282H,H,H,B,B,B6B,H?>,>,>,>,H2H2H2H6H2H6H2""2"""2F866H2>>(>">">H2;H2H2H2H2XHB"B"B"8&8&8&86>*>>.H2H2H2H2H2H2^HH6>,>,>,H2>"H28&>"H2?22!!WFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxN$<<$.2",2222`2 LL2 LL2L"",,2d""\IODOD7>OD\D>>**.7%77070770O7777**70I00*,,;%;.%%%%%%%%%7%7D7D7D7D7D7aII0D0D0D0D0%%%%I7O7O7O7O7O7O7O7O7>0D7O7O7O7>0O7D7D7D7D7I0I0I;I0OBD0D0D0D0O7O7O7O;O7O;O7%%7%%%7T7;;I0>>(>%>#>I7@I7I7O7O7gID*D*D*7*7*7*;;>(>>.O7O7O7O7O7O7\I>;>*>*>*O7>%I77*>%>7B77%%WMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMddddddddddddddddddddddddddddddddddddddddN(BB(97*77777l7#TT7!#TT7T!%%>>7a&&Bn77lBTn(nBB(;TT77a%>7\n!"IIIITTenn7TnB@;7KlBBn7y.X80,ɒX\  P6G;P 2a=5,u&a\  P6G;&Pm)P2,,P\  P6G;P2e=5,&e4  pG;&m)S2,,T4S4  pG;@|ND,_|\  P6G;P@ND,4  pG;\0_=5,%&_*f9 xr G;&XP:% ,J:\  P6G;JP H5!,),5\  P6G;,P\{,W80,%BZW*f9 xr G;X\Q9% ,%:@J9*f9 xr G;JX<~9nnn,<n6X@`7&@<?xxx,<x6X@`7X@ 2 S'Kb yO';| `(#(#K#&a\  P6G;u&P# S'#<\  P6QP##&I\  P6Qu&P#  S'  #&I\  P6Qu&P#Federal Communications Commission`g(#bFCC 98234 ă   yx`dddy u S'WTB Tracking Number: 980163hhC#P\  P6G;P#q[ULS DRAFT R&O: 8/28/98: noon; version 7.1 ]#&a\  P6G;u&P#Њ  a4#|\  P6G;_P#  a4[ Before the b Federal Communications Commission  a4Washington, D.C. 20554 #&a\  P6G;u&P#у X` hp x (#%'0*,.8135@8: *  yOr'ԍ FIT Comments at 45.> Similarly, TIA proposes that fixed pointtopoint microwave applicants use Form 415 for applications, transfers, and assignments, because this form was designed specifically for  SX'microwave services.>X  yO'ԍ TIA Comments at 34.>  S' 14.ؠ We disagree with the view that we should continue using existing servicespecific forms for wireless services. The current array of over forty servicespecific forms confuses the public and vastly increases the amount of time and staff resources needed to process applications. In addition, these forms were not designed for ULS, and in many instances cannot be electronically filed. While there may be instances where licensees are accustomed to using a particular servicespecific form, the far greater benefits of ULS will not be fully realized if we were to continue using the existing forms. The new forms are not only consolidated, but are specifically designed for electronic filing in ULS. Moreover, applicants and licensees filing for multiple services will no longer need to submit duplicative information. Thus, while adoption of ULS forms will require wireless services applicants" J 0*@%@%>" and licensees to make some adjustments initially, over time consolidation of the forms will increase the speed and accuracy of the application process and expedite service to the public. It is also consistent with our objective to eliminate unnecessary servicespecific distinctions in our application and licensing procedures, and provide the public with a consistent set of procedures and rules applicable to all wireless services.  S'15.ؠ Some parties also commented on the length of Form 601 and the number of proposed  S'schedules to the form.P yOP'ԍ FIT Comments 35; TIA Comments at 34.P In fact, while the form and schedules in their totality appear substantial, they will be far less so in actual practice. Form 601 is structured much like the current Form 600, with a main form for basic applicant information and separate schedules for servicespecific technical information. Generally, Form 601 filers will complete only the main form and the particular schedule(s) with information relevant to their particular wireless service. In addition, electronic filing of Form 601 will be faster and more efficient than filing Form 600, because the system will automatically "prefill" licensee information already in the system for Form 601 and will display only the portions of the form and schedules that require completion for the applicant's or licensee's  S 'indicated purpose.\ X {O'ԍ ULS Notice at 9687,  32. Online help, including form instructions, is provided for electronic filers. One may also call the FCC Technical Support Hotline at (202) 4141250; this phone line is generally available  {O2'Monday through Friday, 8 a.m. to 6 p.m. All calls to the FCC Technical Support Hotline are recorded.Ċ This feature of ULS will lessen the burden on applicants and licensees, and will reduce the staff's processing time for wireless applications, so that licensees may provide service to the public quickly.  S'16. Nevertheless, in light of the significant changes to our wireless services forms, we will allow continued use of all existing (preULS) forms for a transition period of six months after the  S'effective date of this Report and Order.| yO'ԍ This transition period does not apply to longform applications by winning bidders in upcoming auctions. Such applications must be filed on Form 601. This transition period is consistent with our past practice for  S'introducing new forms. {O'ԍ See "Wireless Telecommunications Bureau Announces Schedule for Implementation of New FCC Form  {O'415," Public Notice, rel. February 3, 1997 (permitting a three month transition period); "Wireless  {O'Telecommunications Bureau Clarifies Acceptable Editions and Use of FCC Form 574," Public Notice, rel. August 16, 1996 (allowing applicants to file the FCC Form 574 for eight months even though it had been  {O,'replaced by the FCC Form 600); "FCC Form 442," Public Notice, DA 963, rel. June 26, 1996 (accepting a previous version of the FCC Form 442 for six months). A sixmonth transition period will provide wireless services applicants and licensees with sufficient time to plan an orderly transition from using existing forms to using the new ULS forms. At the conclusion of this period, only ULS forms will be accepted. Of course, wireless services applicants and licensees may begin using ULS forms sooner if they prefer, and we encourage" T 0*@%@%"  S'them to do so. {Oh'ԍ All applicants and licensees must include their registered TIN on the new forms. See Section III.B.10,  {M2'infra.ĸ It is in the applicant's or licensee's interest to use the ULS forms as they were created for ULS compatibility and will reduce processing time. In addition, an applicant or licensee electing to use an existing form must provide any new information now asked for on the ULS forms.  S`'17. We received a variety of suggestions from commenters for modifying elements or  S8'particular questions on the proposed forms.@8" yO'ԍ Bennet Comments at 2 (suggesting ownership structure be provided in diagram form and contends the Form 602 does not capture an applicant's affiliate relationships under 1.2110(b)(4)); PCIA Comments at 6 (suggesting more questions answerable by a "check mark" similar to "clickbox" bidding in auctions); W5YI Comments at 79 (recommending changes to Form 605 for applicants and licensees in the Amateur Radio  yO 'Services); GTE Comments at 1416 (recommending changes to Schedule F of the Form 601). @ We find that many of these suggestions have merit, and  S'we will modify the forms accordingly. For example, as suggested by a number of commenters,m yO'ԍ BAM Comments at 4; AT&T Wireless Comments at 6; SBC Comments at 4.m we  S'will combine Forms 603 and 604 into a single combined form for both assignments and transfers. b  {O'ԍ See discussion in Section III.B.8, "Assignments of Authorization and Transfers of Control,"infra. We will also modify the questions on Form 601 relating to alien ownership to limit the scope of questions that must be answered by noncommon carrier licensees who are not subject to section310(b) ownership requirements, and to account for indirect ownership of licensees by investors from World Trade Organization (WTO) member countries. Additionally, pursuant to section 1.2110(b)(2) of the Commission's rules, we will modify Forms 601 and 603 to collect information on  S 'a voluntary basis regarding the race, ethnicity and gender of wireless licensees and applicants.T!  {O'ԍ See 47 CFR  1.2110(b)(2). This information will be used for informational purposes only and will not affect the substantive review or processing of applications. The information collected also conforms to the  {O'revised OMB standards for classification of data on race and ethnicity. See Office of Management and Budget,  {O'Revisions to the Standards for the Classification of Federal Data on Race Ethnicity, Notice of Decision, 62 Fed.  yO'Reg. 58782 (October 30, 1997). T  S '18.ؠ FCBA requests that we provide applicants with the ability to provide supplementary  S 'information which clarifies any question on a wireless application that calls for a "yes/no" response.?"  yO'ԍ FCBA Comments at 35.? ULS forms and the application database will allow any applicant to file attachments to its wireless services application to clarify or explain its answer to a question. Whether filed electronically or manually (i.e, filed on paper), such attachments will be entered into the system as text files and will" :"0*@%@%"  S'become part of the application record in ULS.#" yOh'ԍ Although ULS successfully receives most Word, WordPerfect, and Excel files, the success of an attachment upload depends heavily on content. As a result, word processing files containing graphics and tables  {O'may not upload to ULS successfully. See Appendix G, infra, for a list of acceptable file formats for a ULS upload. Thus, attachments will be viewable online by the  S'applicant or licensee, the Commission, and the public.$ yO*'ԍ Because attachments are created by the applicant or licensee and stored as text files, however, they will not be searchable based on discrete data elements, unlike ULS forms themselves.  S'19.ؠ BAM interprets the ULS Notice as requiring a wireless services licensee to file a Form 601 every time a licensee makes any type of change to an existing license, even if it is a minor  S:'change.<%:  yO 'ԍ BAM Comments at 2.< We clarify that the purpose of creating a single database for wireless services is to eliminate the traditional practice of wireless applicants or licensees submitting duplicative and overlapping applications. Any time a wireless services applicant or licensee logs onto ULS to file an application, information previously entered into ULS will "prefill" or appear on the screen for inspection. If any information concerning the applicant or licensee has changed, it is the responsibility of the filer to  Sr'update the information on its application as required by the Commission's rules.&r {O'ԍ See 47 C.F.R.  1.65 (requiring applicants or licensees to ensure the accuracy of information furnished to the Commission).  S ' 2. Mandatory Electronic Filing  S '20.ؠ MANDATE  MANDATE  Background. In the ULS Notice, we proposed requiring applicants, licensees, and frequency coordinators filing applications on behalf of applicants and licensees in all of the wireless  S\'services to file electronically beginning on January 1, 1999.L'\  {O'ԍ ULS Notice at 9682,  21.L We stated our belief that beginning mandatory electronic filing on this date would be in the public interest because it would help to accomplish our goals of: (a) a rapid transition to ULS; (b) streamlining our wireless services application processing; (c) affording parties a quick and economical process to file wireless services applications; and (d) making all licensing information quickly and easily available to interested parties  S'and the public.4(  {O 'ԍ Id. 4 Although we believe these benefits warrant mandatory electronic filing, we recognized that some wireless services applicants or licensees might lack access not only to high  SD'quality telephone lines but also computers capable of submitting their applications electronically.E)D {O#'ԍ Id. at 9683,  22.E For"D)0*@%@%" these reasons, we solicited comments on whether certain wireless radio services, or classes of  S'applicants or licensees, should be exempt from our proposed requirement to file electronically.4* {O@'ԍ Id. 4 We also requested comment on whether supplying Commission maintained computer facilities for public  S'use would facilitate electronic filing.E+Z {O'ԍ Id. at 9683,  23.E  S8' ` ` a. Transition Period  S'21.ؠTRANSITION Most commenters agree that the use of electronic filing for wireless applications should be expanded and encouraged. AAR, for example, notes that electronic filing will allow quicker and less costly filing by applicants or licensees, quicker and more accurate processing by Commission staff,  Sp'and speedier access to wireless services application and licensing information by the public.=,p yO 'ԍ AAR Comments at 3. = This  SH 'view is echoed by a broad range of commenters, such as AMTA, PCIA, AT&T, and Motorola.-H | yOd'ԍ AMTA Comments at 2; PCIA Comments at 3; AT&T Comments at 7; and Motorola Comments at 2. Nevertheless, many of these same commenters urge the Commission to proceed cautiously before making electronic filing mandatory. While our proposed January 1, 1999 deadline is not without  S 'support,A.  yO|'ԍ Motorola Comments at 2.A the majority of commenters argue that this date is too soon to impose mandatory electronic  S 'filing./  yO'ԍ ADT Comments at 3; AAA Comments at 3; AICC Comments at 3; AirTouch Comments at 3; ARRL Comments at 1718; AMTA Comments at 4; APCO Comments at 34; API Comments at 6; BAM Comments at 7; BellSouth Comments at 8; FCBA Comments at 7; Nextel Comments at 3; Radiofone Comments at 1; TIA Comments at 8; UTC Comments at 3; Winstar Comments at 34; and of ADT Reply Comments at 12; AICC Reply Comments at 12.  Many of the commenters cite the need for more time to work out technical glitches that are  S 'inevitably found in new software packages.0 L  yOl'ԍ ADT Comments at 3; AAA Comments at 3; AICC Comments at 3; AirTouch Comments at 4; API Comments at 6; FCBA Comments at 7; Radiofone Comments at 1. Several commenters also argue that the wireless industry  SX'will need a longer transition period than was proposed in the ULS Notice to obtain experience using  S2'ULS.12 yOv 'ԍ AirTouch Comments at 4; APCO Comments at 34; BAM Comments at 6; BellSouth Comments at 8; FCBA Comments at 7; Nextel Comments at 3; UTC Comments at 3; Winstar Comments at 34. Some commenters urge the Commission to provide more time for licensees to verify the  S 'accuracy of existing Commission records before ULS becomes operational.2  yO#'ԍ FCBA Comments at 1011 (advocating that the Commission establish a program of scheduled review of databases by licensees modeled on the tower inventory and registration program of the past two years). A number of alternative" T20*@%@%"  S'dates are suggested for the implementation of mandatory electronic filing.,3X yOh'ԍ API Comments at 6 (six months after the final rules to implement ULS are published in the Federal Register); BAM Comments at 7 (120 days after the Commission issues a public notice stating that the necessary upgrades and other changes to ULS have been made)., Finally, several  S'commenters oppose mandatory electronic filing for the foreseeable future.4 yO`'ԍ Cochran Comments at 3; Consolidated Comments at 1; Leef Comments at 1; NSMA Comments at 23; PRSG Comments at 23; REACT at 3; Silver Comments at 1; TIA Comments at 8.  S'22. We conclude that the record supports requiring electronic filing for all services that are  S`'licensed by auction. This approach is consistent with our prior decision in the Part1 Third Report  S:'and Order to require electronic filing for FCC Form 175 applications filed prior to auction and for  S'FCC Form 601 applications filed after the auction by winning bidders.u5@ {O 'ԍ Part 1 Third Report and Order, 13 FCC Rcd. at 40912,  5762.u Our decision today will expand mandatory electronic filing to include other types of applications in auctionable wireless services, including transfer and assignment applications, renewals, license modifications, waiver requests, and notifications. We note that mandatory electronic filing will apply to licensees in services  St'subject to auction even if the particular license was not acquired by auction, e.g., cellular and paging licensees who obtained their licenses by lottery will be required to file licenserelated applications and notifications electronically when these mandatory filing requirements take effect. We also require mandatory electronic filing of common carrier services which are not subject to auction because they  S 'operate on shared spectrum (e.g., CMRS licenses operating on shared 929 MHz paging channels or Business Radio frequencies below 800 MHz). We believe that common carriers generally have the resources and technical capacity to support electronic filing.  S8'23. While we conclude that mandatory electronic filing should be implemented to the extent  S'discussed above, we will adopt a longer transition period than was proposed in the ULS Notice. Since  S'the adoption of the Notice, development of ULS has proceeded quickly, and the deployment that has occurred so far has demonstrated the ease and efficiency of electronic filing in ULS. Nevertheless, the new rules, forms, and procedures adopted in this order will not go into effect until late 1998, and full implementation of the system is still a number of months away for some services. We agree with commenters that electronic filing will ultimately be more successful if a reasonable transition period is provided for applicants and licensees to use ULS voluntarily before we implement mandatory electronic filing.  S'24. Therefore, we will not impose the mandatory filing requirements adopted in this order for services that are subject to licensing by auction and for common carrier services subject to auction until (1) July 1, 1999, or (2) six months after application processing in ULS begins for that service, whichever is later. Previously, we have announced the commencement of use of ULS in a particular"450*@%@%W"  S'service by public notice.6Z {Oh'ԍ See, e.g., Public Notice, Wireless Telecommunications Bureau Announces New Procedures for Filing Part 22 Paging Applications in Universal Licensing System (ULS) Starting June 1, 1998, DA 98989 (rel. May 22, 1998). The Wireless Bureau will continue to release servicespecific public notices announcing the relevant commencement date for the processing of applications in ULS. This transition period will provide a reasonable time for wireless services applicants and licensees to make the transition to electronic filing.  S8'25.ؠ In taking this action, we are not disturbing our prior decision in the Part1 Third Report  S'and Order to require electronic filing as of January 1, 1999 of FCC Form 175s filed prior to an  S'auction and FCC Form 601s filed by winning bidders.v7 {Ov 'ԍ Part 1 Third Report and Order, 13 FCC Rcd. at 40912,  57 62.v Electronic filing has been successfully used in the 800 MHz SMR auction and the LMDS auction. The latter auction was conducted after the  S'adoption of the Part 1 Third Report and Order. In light of this experience, we see no reason to adjust our timetable with respect to mandatory electronic filing for auctionrelated shortform and longform applications.  S ' ` ` b. Exempt Wireless Services  S '26.  EXEMPT  Commenters also urge the Commission to exempt certain services or classes of users from mandatory electronic filing. These commenters argue that mandatory electronic filing would impose an undue burden on persons and entities who have limited resources or technical expertise, or who lack access to the necessary computer hardware and software. APCO, for example, contends that  S'many public safety agencies do not have the ability to connect with the FCC via modem.?8| yO*'ԍ APCO Comments at 34.? SBT argues that mandatory filing would disproportionately impact small businesses, minorities, and others  S'who do not have and cannot afford access to computer technology.@9  yOj'ԍ SBT Comments at 1920.@ ARRL contends that mandatory  S'electronic filing would stand as a barrier to access for many Amateur licensees.A: yO'ԍ ARRL Comments at 1718.A GMRS licensees and  Sn'licensee groups contend that mandating electronic filing would stifle their service.U;n,  yO:'ԍ PRSG Comments at 23; Silver Comments at 1.U We are aware that certain, limited impediments that might make it difficult for all licensees and applicants to communicate with the Commission electronically. For example, some persons still use party lines that may be inadequate to transmit the signals from modern telecommunications devices like modems. Accordingly, we conclude that the record broadly supports moving to mandatory electronic filing for certain wireless services, but that electronic filing should remain optional in other services for the time being."~ ;0*@%@%"Ԍ S'ԙ27. For the time being, we will not extend mandatory electronic filing requirements to services that are not subject to licensing by auction. We agree with commenters who noted that in many of these services, licensees consist primarily of individuals, small businesses, or public agencies that may lack resources to convert quickly to electronic filing. Therefore, manual filing will continue to be an option for applicants and licensees in the following categories: (1) the Part 90 Private Land  S8'Mobile Radio services for shared spectrum,<8 yO'ԍ ULS will be programmed to recognize entities filing under radio service codes RS, IG and YG as exempt from mandatory electronic filing. spectrum in the public safety pool below 746 MHz, and spectrum in the public safety allocation above 746 MHz (however, Commissioncertified frequency  S'coordinators must file electronically; see the following paragraph); (2) the Part 97 Amateur Radio  S'Service (however, Volunteer Examination Coordinators must file electronically; see the following paragraph); (3) the Part 95 General Mobile Radio Service and Personal Radio Service (excluding 218219 MHz Service licenses); (4) the Part 80 Maritime Services (excluding the VHF 156162 MHz  SL 'Public Coast Stations); (5) the Part 87 Aviation Services; (6) Part 13 Commercial Radio Operators ; and (7) Part 101 licensees who are also members of any of the foregoing classes. We note, however, that this decision could be subject to future modification. As computer and modem equipment becomes less costly and more available, we anticipate that electronic filing will become feasible for most if not all wireless applicants and licensees. We will review this issue in the future and may extend mandatory electronic filing to any wireless service where we find that electronic filing is both operationally feasible and cost-effective for licensees and applicants in the service. Adoption of mandatory electronic filing requirements for such services will not require further notice and  S 'comment,$=Z   yO'ԍ Although we have sought comment on this issue in this proceeding, we note that mandating electronic  {O'filing is a procedural rule change that is not subject to notice and comment requirements. See 5 U.S.C.  552(b)(3)(a).$ but we will provide at least six months public notice before such a requirement will take effect.  S'28. We also note that in a number of the above services, wireless applications must be coordinated prior to being filed with the Commission, and are often filed by the frequency coordinator on the applicant's behalf. We conclude that where wireless services applications are filed by frequency coordinators or other Commissioncertified entities such as Amateur Radio volunteer examinercoordinators (VECs), such applications must be filed electronically. This requirement was  S'proposed by several commenters, including some coordinators.>B yO'ԍ APCO Comments at 34; Motorola Comments at 2;W5YI Group Comments at 10; ITA Reply Comments at 3. Requiring frequency coordinators and VECs to file electronically will not impose a hardship on these entities, because they have the incentive and the resources to develop electronic filing capability as a service to their customers. Indeed, many of the frequency coordinators for private land mobile services already have electronic filing capability, and the Wireless Bureau has been working extensively with the frequency coordinators to convert their electronic filing protocols for use in ULS. Electronic filing by">0*@%@%'" coordinators will also provide an alternative for wireless services applicants and licensees who are reluctant to file electronically themselves, and will increase the Commission's processing efficiency because a large percentage of applications will be filed by frequency coordinators.  S`' ` ` c. Computer Facilities  S'29.ؠ COMPUTER  Winstar supports our proposal to maintain computer facilities to allow members of the public to file forms and pleadings electronically because supplying these facilities will allow applicants  S'without computer access to make use of ULS.@? yO( 'ԍ Winstar Comments at 7.@ Additionally, Winstar advocates that the Commission maintain public computer facilities to allow ULS to be accessed for the purpose of conducting license  Sp'and application searches.@@pX yOh 'ԍ Winstar Comments at 7.@ On the other hand, W5YI argues that public computer facilities would go  SH 'unused due to the wide availability of independent filing services.>AH  yO'ԍ W5YI Comments at 12.> W5YI asserts that privatization of government functions conserves the federal budget, and transfers the cost of the service to those who  S 'reap the benefits.>B x yO'ԍ W5YI Comments at 12.> We believe that, pursuant to section 309(j)(3)(B) of the Act, we have an obligation to facilitate access to ULS for members of the public that lack computer access or have other  S 'technological problems that hinder access to ULS.C  {OP'ԍ See 47 U.S.C.  309(j)(3)(B). We note that other technological difficulties may arise but ULS is a flexible enough to adapt to the needs of the system's users. We will provide computer terminals in our Public Reference Room. Users of the Commission's public computer facilities will be permitted to view ULS publicly available information or file wireless services applications.  S'30.ؠ We also are committed to making electronic filing and other electronic applications of ULS accessible to persons with disabilities to the fullest extent possible. Although we did not receive specific comments on this issue, we note that ULS is subject to the program accessibility requirements  S'of section 1.850 of the Commission's rules.;Db  yO'ԍ 47 CFR  1.850; In addition, since the adoption of the ULS Notice, Congress has revised the requirements for access by persons with disabilities to federal information  SB'technology programs in the Workforce Improvement Act of 1998.|EB  yO 'ԍ Workforce Improvement Act of 1998, P.L. No. 105220, 112 Stat. 936 (Aug. 7, 1998).| Section 508 of the Act provides that persons with disabilities and nondisabled persons must have comparable access and ability to use electronic technology and information, and federal agencies must take steps to ensure such comparable access for persons with disabilities unless an undue burden would be imposed. If an undue burden" E0*@%@%X" would be imposed, the agency must provide an alternative means of access that allows persons with disabilities to access and use the information.  S'31.ؠ In comparison to our current licensing systems, we anticipate that ULS will provide greater access to the Commission's application and licensing databases for persons with disabilities. Most fundamentally, ULS benefits many persons with disabilities because it enhances the ability of the public to file applications and access licensing data remotely. In addition, as we pointed out in the  S'ULS Notice, ULS has some specific features that will make it easier for persons with particular  S'disabilities to use the electronic filing and public access functions.KF {O* 'ԍ ULS Notice at 9676,  6.K For example, the ULS technical support hotline will have text telephone capabilities (TTY) for persons with hearing or speech disabilities, and ULS will allow individuals who are blind or who have low vision to determine the status of pending license applications through a touch tone phone using Interactive Voice Response (IVR) technology.  S '32.ؠ While it is our goal to maximize access to ULS for persons with disabilities, we recognize that in some instances, it may be difficult for persons with some disabilities to use the electronic access components of the system as currently configured. In particular, the accessibility of ULS forms and certain types of electronic files raises complex technical issues. We will continue to work on these issues and fully expect that with advances in technology, we will be able to enhance the accessibility of ULS for persons with disabilities. In the interim, we will provide accommodations to individuals with disabilities who are unable to fully use ULS on a casebycase basis.  Sj' 3. Copy and Microfiche Requirements  S' 33. FICHE  Background. In 1985, the Commission required that cellular applicants in the top90 and  S'above markets file initial cellular applications on microfiche.VGZZ yO'ԍ Amendment of the Commission's Rules to Allow the Selection from Among Mutually Exclusive Competing Cellular Applications Using Random Selection or Lotteries Instead of Comparative Hearings,  {O|'Memorandum Opinion and Order on Reconsideration, 101 FCC2d 577, 604,  50 (1985).V Subsequently, the Commission expanded its use of microfiche. The Commission adopted an order in 1988 requiring that all non S'cellular and noninitial cellular Mobile Services Division applications be submitted on microfiche.HZ| yO'ԍ Amendment of Part 22 of the Commission's Rules to Revise Certain Filing Procedures for Mobile  {O'Services Division Applications and to Eliminate Form 430, CC Docket No. 88161, Report and Order, 3 F.C.C.R. 6684 (1988). The Commission stated its belief that the use of microfiche would enable the Commission to serve the public in a more efficient, secure, and expeditious manner and would result in more efficient use of  S*'Commission space.3I* {Oh$'ԍ Id.3"*0 I0*@%@%d"Ԍ S'ԙ!34. In the ULS Notice, we proposed to amend the Commission's rules so that applicants or licensees that file applications electronically would not be required to provide paper copies, diskettes,  S'or microfiche.LJ {O'ԍ ULS Notice at 9684,  25.L We tentatively concluded that these requirements are unnecessary under ULS because  S'all information will be available online to interested parties.4KZ {O'ԍ Id. 4 In addition, we stated that data filed on paper will be entered or scanned, as necessary, to allow access to it in the same fashion as  S:'electronically filed information.FL: {O 'ԍ Id. at 9684,  25. F We sought comment on our proposal, and on whether it would impose a significant burden on paper filers to require them to file a diskette containing an electronic  S'copy of all attachments and exhibits.4M~ {O 'ԍ Id. 4  S'"35.ؠ Discussion. AASHTO supports our proposal to enter or scan manually filed data so that  Sr'it will be available in the same manner as electronicallyfiled information.?Nr yO"'ԍ AASHTO Comments at 4.? To the extent that paper filing will be permitted under the Commission's rules, we will enter or scan data filed on paper as necessary to make it available in ULS in the same fashion as electronically filed information. In light of our decision to enter or scan manually filed data, we will no longer require the submission of microfiche by applicants or licensees, whether filing manually or electronically. We required the submission of microfiche to enable us to permanently store application records without the necessity of storing bulky paper files. The ULS system makes this requirement obsolete because all applications will be stored electronically.  S '#36.ؠ AT&T Wireless, BAM, and Nextel support our proposal to eliminate the filing of  S'supplemental paper copies or diskettes for electronic filers.oO yO"'ԍ AT&T Wireless Comments at 8; BAM Comments at 8; Nextel Comments at 4.o They agree that such requirements would  S'be unnecessary under ULS.oP0  yO'ԍ AT&T Wireless Comments at 8; BAM Comments at 8; Nextel Comments at 4.o We conclude that the filing of paper copies or diskettes is unnecessary when filing electronically because all information will be available to interested parties online. We therefore adopt our proposal to eliminate the requirement that electronic filers submit paper copies or  SB'diskettes.bQB  {O!'ԍ See Appendix G, infra, proposed  1.913. b "R Q0*@%@%"Ԍ S'$37.ؠ BAM and Nextel support a requirement that paper applications be accompanied by a  S'diskette containing the complete application and any exhibits.RR yO@'ԍ BAM Comments at 8; Nextel Comments at 4.R Nextel states that requiring paper filers to submit a diskette would not impose a significant burden, and that the requirement would  S'likely ease the administrative burden on the Commission.?SX yO'ԍ Nextel Comments at 4.? While we encourage the submission of a diskette when filing a paper application, we find that our decision to enter or scan data makes such a requirement unnecessary.  S' 4. Electronic Filing of Pleadings Associated with Applications  Sp'%38.ؠPLEADINGS Background. Section 1.49 of the Commission's rules requires that pleadings and  SH 'documents filed in any Commission proceeding be filed on paper.rTH  {O'ԍ See 47 C.F.R.  1.49 (1997); ULS Notice at 9684,  26.r In the ULS Notice, we proposed modifying our Part 1 rules to allow electronic filing in ULS of pleadings associated with wireless applications, including petitions to deny, petitions for reconsideration, applications for review, motions for extension of time, and opposition and reply pleadings related to such filings. Since the adoption of  S 'the ULS Notice, we modified the Commission's rules to allow electronic filing of comments in all  S 'rulemaking proceedings.U z yO'ԍ In the Matter of Electronic Filing of Documents in Rulemaking Proceedings, GN Docket No. 97113,  {Of'Report and Order, 13 FCC Rcd. 11322 (1998) (ECFS R&O).  S4'&39. We anticipated that our proposal to allow electronic filing of pleadings in ULS would allow the system to quickly and easily associate pleadings with applications and make such pleadings readily available to the public efficiently. Initially, we determined that parties filing pleadings  S'electronically should continue to serve paper copies on all interested parties.LV {O0'ԍ ULS Notice at 9684,  87.L We also sought comment on whether to allow electronic filing of other WTB pleadings that were not associated with a  Sl'particular application or a docketed proceeding (e.g. requests to stay filing deadlines).3Wlf  {Or'ԍ Id.3 Finally, we sought comment on whether to require parties filing paper pleadings to submit a copy of the pleading  S'on diskette.5X  {O!'ԍ Id.  5 " X0*@%@%"Ԍ S''40.ؠ  Discussion. Virtually all commenters agree that we should permit electronic filing of  S'pleadings associated with applications.YX yO@'ԍ AAR Comments at 4; AASHTO Comments at 4; ADT Comments at 4; AAA Comments at 45; AICC Comments at 45; BAM Comments at 9; FCBA Comments at 24; Nextel Comments at 4; Radiofone Comments at 4; FIT Comments at 4. Motorola observes that electronic filing of pleadings is consistent with our goal of "making all licensing information available to interested parties and the public [because] electronic filing of pleadings would make it convenient for interested parties and the  S`'public to download all of the comments in a given proceeding."AZ` yO'ԍ Motorola Comments at 3.A AAR and Nextel believe electronic filing of pleadings associated with applications will result in speedier, less costly filings and timely  S'public access.R[x yO( 'ԍ AAR Comments at 4; Nextel Comments at 4.R BAM notes immediate and full access to pleadings is critical given that responsive pleadings are time sensitive and current service rules do not require formal service for all informal  S'objections or comments on specific applications.<\ yOh'ԍ BAM Comments at 8.< Only one commenter, FIT, argues that the need for electronic filing is not compelling because these pleadings relate to specific applications, and are normally of interest only to the parties involved and paper copies can be distributed easily to interested  SH 'parties and Commission personnel.=]H  yO'ԍ FIT Comments at 10.=  S '(41. We agree with the majority of commenters that we should encourage electronic filing in ULS of pleadings associated with applications. Electronic filing of pleadings will reduce parties' filing and research costs, make it easier for parties to find and review filed pleadings, and will allow the public greater access to our proceedings. Implementing electronic filing of pleadings in ULS is also consistent with our recent decision establishing the Electronic Comment Filing System (ECFS) for  S0'electronic submission of comments in rulemaking proceedings.G^0(  {O'ԍ ECFS R&O, passim.G In both instances, we are fulfilling our commitment to use new information technologies to provide access to our processes and to serve the public.  S')42. Although we believe it is in the public interest to allow electronic filing of pleadings associated with applications, we must consider a number of issues raised by the commenters that may affect the ability of the parties to obtain electronically filed pleadings. The commenters asserted that lack of access to equipment and software, validity of electronic signatures, proper service of copies of pleadings, and filing of diskette copies of the pleadings could affect the ability of a party to file pleadings associated with applications. " ^0*@%@%"Ԍ S'*43. First, while supporting electronic filing of pleadings, FCBA cautions that we should consider the interests of parties who have standing to file pleadings but may lack the correct computers  S'and appropriate software.>_ yO'ԍ FCBA Comments at 24.> We agree, and emphasize that electronic filing of pleadings in ULS is  S'optional, not mandatory. However, it is also important to note that, as in the case of ECFS,V`X {O'ԍ ECFS R&O at 1133237 ,  2233.V we have designed ULS to accept filings generated in most of the commonly used electronic document formats, including Microsoft Word, WordPerfect, Adobe Acrobat, and ASCII text, as well as Microsoft Excel for spreadsheets. For viewing and printing, ULS will automatically convert these files into Adobe Acrobat Portable Document Format (PDF) so that users can access the formatted files even if they do  S'not have the word processor used to create the document.CaX yOJ 'ԍ Paragraph numbering makes it easier for readers to cite specific passages. For that reason, we encourage electronic filers to number their paragraphs. However, we will not require paragraph numbering and will not consider the failure to include paragraph numbers a fatal defect.C Over time, as users' needs change and  S'technology advances, we will add additional file formats if technically feasible.b  yOB'ԍ Electronically filed documents must be selfcontained. We will not allow hyperlinks to sites on the Internet to be included in electronically filed documents.  SH '+44.ؠ Second, other commenters express concern that they may lack access to scanning  S 'equipment needed to make legible digital copies of paper documents.c b  yO"'ԍ ADT Comments at 4; AAA Comments at 45; AICC Comments at 45; Radiofone Comments at 4. We will allow parties who file pleadings electronically to file a paper copy of exhibits and other attachments that cannot be converted to electronic form. The electronic filer should submit the paper filing on the same day as the electronic filing and reference the paper filing in attachments to the pleading.  SX',45.ؠ Third, a few commenters question whether electronic filing is consistent with our signature requirements for pleadings or suitable for filing documents that are signed under penalty of  S'perjury.d  yO'ԍ ADT Comments at 4; AAA Comments at 45; AICC Comments at 45; Radiofone Comments at 4. As we discussed in the ECFS R&O, our signature requirements do not pose an obstacle to  S'electronic filing of pleadings.Le  {O'ԍ ECFS R&O at 11327,  10. L The Commission's rules already provide for electronic signatures on  S'applications,]f {On!'ԍ See 47 C.F.R.  1.743(e) and 1.913(e).] and we similarly amend our pleading rules to allow electronic signatures on  S'pleadings.Jg {O#'ԍ See Appendix F,  1.45.J "8g0*@%@%H"Ԍ S'ԙ-46. Fourth, with respect to service of electronically filed pleadings, most commenters agree  S'with our proposal to require filers to serve paper copies on any interested parties.Rh yO@'ԍ AAR Comments at 4; Nextel Comments at 4.R As in the ECFS  S'R&O, however, we will allow electronic service where the party to be served consents to electronic  S'service in advance.OiX {O'ԍ ECFS R&O at 1133637,  32. O We are exploring adding a field in ULS to allow parties to check whether they will accept electronic service. In the meantime, parties should indicate their willingness to accept electronic filing in their pleadings. Additionally, we believe that when a party has agreed to electronic service of a document, the three-day mailing rule for computation of time purposes is inappropriate.  S'As we decided in the ECFS R&O, when parties agree to electronic service, service will be considered  S'the same as facsimile service.hj {OP 'ԍ ECFS R&O at 11337,  33; see, 47 C.F.R. 1.4(h).h  Sv'.47.ؠ Finally, some commenters believe we should allow paperfiled pleadings but require the submission of a diskette copy of the pleading, perhaps containing files in several word processing  S& 'formats as well as in ASCII format.hk& | yOB'ԍ AASHTO Comments at 4; BAM Comments at 9; Nextel Comments at 4.h As in the case of paper filed applications, we conclude that it is better at this point to encourage, rather than require, parties filing paper pleadings to include a  S 'diskette.Ql  {O'ԍ See Section III.A.2, supra.Q  S^' 5. Letter Requests  S'/48.ؠ LETTERS נBackground. Currently, in some wireless services, the Commission's rules permit letter  S'requests instead of formal applications for certain actions.Lm {O$'ԍ ULS Notice at 9686,  29.L These rules result in thousands of letter  S'requests annually that are not in a suitable format for entry into database fields.En0  {O'ԍ Id. at 9685,  28.E Letter requests, which cannot be entered into ULS, require separate processing tracks, rather than the uniform licensing process we seek to establish here. Under ULS, Form 601 is the designated form for filing applications, modifications, renewals, amendments, extensions, cancellations, requests for special temporary authority, and name and address changes for all wireless services, except Maritime, Aircraft, Amateur, Restricted and Commercial Operator, and General Mobile Radio Services. The Form 605 will be used in the named services to file new applications, modifications, amendments, renewals, cancellations, withdrawals, or requests for duplicate copies of licenses. We did not propose to amend" n0*@%@%("  S'the fee schedule in the ULS Notice, so that matters heretofore filed by letter request and not subject to a fee would continue not to require a fee under our universal filing system.  S'049.ؠIn the ULS Notice, we requested comments on whether requiring the filing of ULS forms for wireless licenses or applications rather than continuing to accept and process letter requests serves  S<'the public interest.Eo< {O'ԍ Id. at 9686,  29.E Additionally, we invited comments concerning whether letter filings for applications, modifications, renewals, amendments, extensions, cancellations, special temporary authorizations, and name and address changes, except for the Special Situations set forth in section  S'308(a) of the Communications Act, should be eliminated.p"Z {O 'ԍ Id. at 9686,  29. The special situations set forth in section 308(a) of the Communications Act of 1934, as amended, pertain to: 1) cases of emergency involving danger to life or property; 2) cases arising during a national emergency; or, 3) cases of emergency where the Commission finds that it would not be feasible to follow normal licensing procedures.  St'150.ؠDiscussion. Replacement of letter requests with forms received support from commenters. For example, the FCBA ". . . applauds the Commission's proposal to streamline and simplify the  S$ 'application process and the forms used in connection with wireless authorizations. . . "=q$ D yO'ԍ FCBA Comments at 3.= Nextel  S 'agrees that letter requests should be eliminated and replaced by forms.Ar  yOp'ԍ Nextel Comments at 45.A We conclude that using form filing, in certain circumstances, instead of letter requests will facilitate implementation of ULS, reduce applicant and licensee burdens, increase efficiency and better serve the public interest. Form 601 shall be used to file applications, modifications, renewals, amendments, extensions, cancellations, special temporary authorizations, and name and address changes. Where there is a need for Commission action regarding license application which cannot be addressed by Forms 601, 603 or 605, letter requests may continue to be submitted to the Commission for further resolution.  S'251.ؠ Another reservation concerned the use of forms for special temporary authorizations (STAs) because commenters feared FCC staff would not be alerted to the fact that the applicant is  Sl'making an STA filing that needed immediate attention.sld  yOp'ԍ EEC Comments at 89; GTE Comments at 1113; Rinker at 89 (express a need for explicit notification on the forms for STAs and other emergency filings). We recognize the need for prompt identification and resolution of STA requests. Typically, where an immediate STA is required because of an emergency or natural disaster, the Commission will accept requests by telephone or fax, and" s0*@%@%"  S'such requests can be granted orally.t" {Oh'ԍ See 47 U.S.C.  308. The special situations set forth in section 308(a) of the Communications Act of 1934, as amended, pertain to: 1) cases of emergency involving danger to life or property; 2) cases arising during a national emergency; or, 3) cases of emergency where the Commission finds that it would not be feasible to follow normal licensing procedures.  In these circumstances, the rules require that an application be  S'submitted as soon as possible after the initial request.ju {O*'ԍ See former 47 C.F.R.  1.925, now 47 C.F.R.  1.931.j Under the rules we adopt in this proceeding, the procedures for requesting an emergency STA by telephone or fax remain unchanged. The subsequent application will now be submitted on Form 601 or Form 605 with an exhibit to provide an explanation of the emergency circumstances. For instance, a small paging operator, who needs an emergency STA, will be able to call the Commission and speak with a knowledgeable employee who can approve the STA while on the telephone. This applicant would subsequently submit Form 601 or Form 605 and an exhibit explaining the emergency. In circumstances where applicants or licensees submit requests for STAs using only the Forms 601 or 605, they can be easily identified by the staff for expedited processing; Forms 601 and 605 ask all applicants or licensees to identify if the request is for an STA. Moreover, applicants or licensees continue to be able to consult with the staff about the  SH 'status of an STA request by telephone or in person, as is now the practice.vXH D yO,'ԍ We emphasize that the Commission's rules do not contemplate routine grants of STAs. Although we continue to receive requests for STAs in a broad number of circumstances, we will limit the grant of STAs to the situations described above.  S '352.ؠComments by SBC Communications, Inc. and Nextel Communications, Inc. expressed  S 'opposition to form filing if new fees would be assessed.w d  yO'ԍ SBC Comments at 16; Nextel Comments at 5. The comments for both parties stipulate their support for form filing upon clarification that new fees will not triggered by using the forms. Nextel qualified its support of forms instead of letter requests when it noted, ". . . Provided no filing fee is imposed, use of forms for such requests under ULS should be less burdensome for the filer and should enable the Commission to  SX'improve its speed in processing such minor requests . . . "?xX  yO'ԍ Nextel Comments at 5.? SBC suggests that letter requests should  S0'remain an option if form filing would trigger filing fees for an otherwise nonfeeable event.By0L  yO'ԍ SBC Comments at 15 16.B We did  S'not propose to amend the fee schedule in the ULS Notice; therefore, matters heretofore filed by letter request and not subject to a fee will continue to be free from any fee under ULS. Additionally, we will provide a link to the Commission's homepage for the public to examine our fee filing schedule. "y0*@%@%."Ԍ S'453.ؠFCBA anticipates a negative effect on small business licensees if letter requests are  S'replaced with forms.z yO@'ԍ FCBA Comments at 24, ". . . .we do not think [electronically filed forms] should be made mandatory, as that would deny licensees, particularly small licensees, the necessary flexibility to conduct their businesses. . . ." Because manual filing would continue to be acceptable, the only "new" factor when converting to forms is accessing the forms. The forms would be available through the FCC website, by a tollfree telephone call, tollfree TTY call, and by faxondemand service. The easy accessibility of the forms, we believe, will facilitate this less burdensome method of making requests to the Commission. Once parties have obtained one copy of Form 601, they may simply make as many copies of the form as they need. This is an added benefit of combining most application purposes on one form and should virtually eliminate any inconvenience to parties once they have obtained a copy of Form 601. Because forms quickly identify a purpose, we believe that such requests will be more accurately and promptly processed. This benefit is threefold; it helps Commission staff perform their duties more efficiently and facilitates a more prompt response to the applicant, which makes information more readily available to the public. In order to have a universal licensing system, we must require standardized data fields and have access to the correct and complete data to enter into those fields. Letter requests simply do not provide information in a format that is suitable for ULS. We have taken this action to simplify the process for licensees, reduce timeconsuming, resourceintensive review by FCC staff to determine the purpose of STAs and letter requests, and increase the public's assess to information.  S0'554.ؠ Furthermore, FCBA opposes mandatory electronic filing of letter requests and suggests  S'that each applicant would use forms voluntarily if using forms benefits its organization.={  yO'ԍ FCBA Comments at 9.= We are requiring that a form be used rather than a letter because of the overall benefit to the public which ULS will produce. In contrast to letter requests, requests filed on standardized forms are more quickly and easily processed, are less likely to be misrouted or lost, and are more likely to contain all of the necessary information for the staff to analyze the request, resulting in fewer delays. We will provide a six month implementation period that allows licensees time to prepare to access, review and use the forms. The six month implementation period will begin following the effective date of this order. As mentioned earlier, easy access makes form use convenient for all licensees, large and small.  Sx' B. Standardization of Practices and Procedures for WTB Applications and Authorizations  SP'  S(' 1. Consolidation of Procedural Rules in Part 1 ` `  S'655. CONSOLIDATE Background. In the ULS Notice, we proposed to consolidate all wireless services  S'procedural rules into Part 1.L| {O#'ԍ ULS Notice at 9687,  31.L Until now our practice has been to adopt servicespecific rules for processing applications in each particular service. As a result, the public must familiarize itself with"B|0*@%@%" procedural rules for each service prior to filing an application. This biennial review and the implementation of ULS provide a unique opportunity for us to consolidate the wireless services procedural rules under Part 1. We proposed to unify these disparate service rules, and sought comment on eliminating outdated or unnecessary procedural rules and conforming inconsistencies in  S`'the Commission's rules where feasible.E}` {O'ԍ Id. at 9687,  33.E However, we also recognized that certain servicespecific rules must be retained to further technical, operational or policy considerations for that service. We sought comment on which of our proposed rules may be unnecessary or inconsistent, and whether  S'retaining certain service-specific rules was warranted.L~Z {O 'ԍ Id. at 9686,  3033.L  S'756. Discussion. We adopt our consolidation proposals set forth in the ULS Notice and will streamline our wireless services procedural rules under Part 1, with the exception of those servicespecific rules that require retention. Only one commenter, CenturyTel, opposes this proposal, contending that consolidating the procedural rules for all wireless services would increase the  S 'regulatory burden on private wireless licensees.Z  yO'ԍ CenturyTel Comments at 9. CenturyTel interprets our consolidation proposal as bringing private licensees within the scope of ownership reporting requirements that currently do not apply to them. As discussed  {O'in Section III.B.3, infra, we have imposed no new ownership reporting requirements on private licensees.  We conclude that CenturyTel's concerns are misplaced. By consolidating our procedural rules in Part 1, we improve the consistency of the Commission's rules across wireless services and provide a single point of reference for applicants, licensees, and the public seeking information regarding our licensing procedures. This consolidation will reduce confusion among applicants or licensees, increase the probability that filings will be done correctly, accelerate the application process, and speed wireless service to the public.  S'857. Commenters make a wide variety of specific suggestions for modifying particular procedural rules in Part 1. We have adopted many of these suggestions, which we discuss in greater detail in the following sections. In addition, some commenters propose that we consolidate additional servicespecific rules into Part 1. SBC, for example, identifies eleven rules currently in Parts 22, 24  SB'and 101 that it recommends be moved to Part 1.?B yO'ԍ SBC Comments at 56. ? SBC also suggests that developmental authorizations and incidental communication services also be addressed in Part 24 to create regulatory  S'parity.e {O0 'ԍ See 47 C.F.R.  22.401 and 47 C.F.R.  22.323.e Because we believe that these proposals are beyond the scope of the proceeding, we will consider them when we undertake further streamlining and consolidation of these rules in subsequent proceedings. Likewise, the Wireless Bureau has recently released a public notice seeking comment on"0 0*@%@%"  S'PCIA's letter to the Commission proposing that wireless regulations be further streamlined. {Oh'ԍ Public Notice, Wireless Bureau Seeks Comment on July 31, 1998 Letter From Personal Communications Industry Association Proposing Streamlining of Wireless Regulations, DA 981687 (rel. August 21, 1998). To the extent they are not addressed herein, we will address PCIA's proposals in further proceedings in this docket and other dockets as appropriate.  S8' 2. Standardization of Rules Regarding Major and Minor Amendments  S'` ` a. Consolidated Rule  S'958. MAJORMINOR Background The implementation of ULS provides a unique opportunity to replace our servicespecific rules with a single set of uniform standards for defining major and minor amendments  SH 'and modifications in all wireless services. In the ULS Notice, we therefore proposed to adopt a single rule in Part 1 for purposes of defining whether an amendment to a wireless application or a request for  S 'a wireless license modification is a major or minor change.L " {O'ԍ ULS Notice at 9688,  35.L We proposed that these major and minor categories should uniformly govern the filing date of applications in all wireless services. As  S 'stated in the ULS Notice, the distinction between major and minor application filings has significant procedural consequences in the application process, because a major amendment to an application causes the application to be considered newly filed, while a minor amendment generally has no impact  S4'on the filed date.4 {O'ԍ Id. at 9688,  34. 47 U.S.C.  309(b) requires a thirtyday public notice period before a newly filed application may be granted, with certain exceptions to this rule being provided in  309(c). We did not propose revising the types of applications which require public notice  S 'or frequency coordination.3  {O'ԍ Id.3  S':59. In proposing a single consolidated rule, however, we noted that some differentiation between wireless services remains necessary. First, we noted that where wireless services are licensed on a geographic area basis, there are far fewer types of potential modifications than where licensing is sitespecific, because a geographic licensee can make technical modifications to its system without modifying its license, provided it complies with basic operational and technical rules. Where the  S'license is sitespecific, by contrast, technical changes to the licensed facility (e.g., a change of coordinates, antenna height, or power) require the Commission to modify the license. Second, we noted that among sitespecific services, some differentiation is required in defining major and minor changes due to the differing technical parameters governing sitebased mobile and fixed services. Within our proposed consolidated rule, therefore, we proposed specific classifications of major and  S.'minor changes based on these different classes of licenses.O. {On$'ԍ Id. at 968990,  3740.O ".2 0*@%@%~"Ԍ S'ԙ;60. Discussion. Commenters generally support our proposal to consolidate the Commission's  S'rules regarding major and minor modifications. yO@'ԍ AirTouch Comments at 6; AT&T Wireless Comments at 8; BAM Comments at 910; Nextel Comments at 5. However, AirTouch and FCBA caution that we should not overlook genuine differences between the wireless services in this regard, and express concern that our consolidation not result in the imposition of new filing requirements on licensees and  S`'applicants.q`  yO 'ԍ AirTouch Comments at 6; FCBA Comments at 25; FCBA Reply Comments at 16.q Several commenters also express concern that the proposed Part 1 rule could result in  S8'some changes that have been traditionally classified as minor being reclassified as major changes.8 yO 'ԍ FCBA Comments at 27; B&B Comments at 4; EEC Comments at 3 (changes to site location previously considered minor could be reclassified as major). We address these comments in greater detail below. These commenters oppose any such reclassification and seek clarification of our tentative conclusions  S'and proposed consolidated rule. As FCBA notes, this could have significant consequences because  S'major and minor filings follow very different procedural paths in the application process.` {Oh'ԍ FCBA Comments at 18; see note 111, supra. `  Sp'<61.ؠ We conclude that a single rule in Part 1 that defines categories of major and minor changes for all wireless services is consistent with our goals in this proceeding. We agree with commenters, however, that some modification and clarification of the rule is appropriate. By creating  S 'a consolidated rule, it is not our intent to change the substance of our existing definitions of major and minor changes, or to impose new filing requirements on licensees and applicants. Instead, our purpose is to adopt a consistent standard for all wireless services, eliminate unnecessary or redundant rules, and retain servicespecific rules where only such rules are necessary because of the unique characteristics of the wireless service. We therefore modify our proposed rule in certain respects and offer the following clarifications.  S' ` ` b. Major Changes for All Wireless Services  S'=62.ؠ Background. In the ULS Notice, we tentatively concluded that the following changes should be considered major changes for all wireless services whether licensed geographically or on a sitespecific basis: any substantial change in ownership or control; any addition or change in frequency, excluding removing a frequency; any request for partitioning or disaggregation; any modification or amendment requiring an environmental assessment; any request requiring frequency  S'coordination (nonCMRSNX yO!'ԍ Commercial mobile radio service (CMRS) is defined as a mobile service that is provided for profit and makes interconnected service available (A) to the public, or (B) to such classes of eligible users as be effectively available to a substantial portion of the public. 47 U.S.C.  332(d).N private land mobile only); or any modification or amendment requiring notification to the Federal Aviation Administration as defined in 47 C.F.R. Part 17 Subpart B. "z 0*@%@%"Ԍ S'>63. Discussion. We adopt our tentative conclusions and define certain actions as major changes for all wireless services, regardless of whether the service is licensed geographically or on a sitespecific basis. We also clarify our consolidated rule to maintain consistency with our current servicespecific rules for major and minor changes. These actions include initial and renewal  S`'applications, nonpro forma transfers and assignments (include partitioning and disaggregation requests), applications that have significant environmental effect, applications requiring frequency coordination, and applications requesting an additional frequency or a frequency block that is not currently licensed to the applicant. With respect to this last category, we note that some commenters read our proposed rule as requiring geographic licensees to file a major modification application every  S'time they make internal system changes (e.g., frequency changes, adding or moving an internal site,  St'changing transmitter power) within their licensing area.pt yO 'ԍ AirTouch Comments at 8; SBC Comments at 10; BellSouth Comments at 11. p This outcome was not our intent in the ULS  SN 'Notice. We agree with these commenters that in geographically licensed services, internal site and frequency changes within the licensing area and on spectrum covered by the license do not require  S 'Commission approval or notification except in very limited circumstances (e.g., a site that requires  S 'approval under NEPA). Similarly, in most sitebased mobile services (e.g., paging, SMR), licensees may make changes to internal sites without Commission notice or approval provided that they do not expand the service area or interference contour of the system as a whole. We have modified the  Sd'language of the final rule to avoid potential confusion on this issue.RdX {O\'ԍ See Appendix G, infra,  1.929.R  S'?64.ؠ Some commenters also expressed concern regarding our proposal to classify as major any application or amendment that requires notification to the FAA under Part 17 of the Commission's  S'rules.Q yON'ԍ BAM Comments at 9; FCBA Comments at 25.Q They point out that licensees must often obtain FAA clearance for internal sites in their systems, but contend that this requirement should not require the filing of a major modification application with the Commission. We agree. The purpose of FAA registration and notification is to maintain safety in air navigation. These purposes are accomplished by filing FAA Form 7460-1 with the FAA and obtaining clearance for the facility in question. However, not all actions that require FAA clearance have licensing implications for the Commission. In the case of an internal site that does not otherwise require Commission notification or approval, the fact that FAA clearance is required does not give rise to such a requirement. Therefore, so long as the licensee complies with the FAA's requirements, there is no need for the licensee to file a modification application or notification with the Commission. Accordingly, we have deleted this element of our proposed rule. Tower owners continue to be responsible for notifying the FAA and registering any FAAapproved towers with the Commission by using FCC Form 854. " z0*@%@%"Ԍ S'@65.ؠ In the ULS Notice, we stated that any request requiring frequency coordination would be considered a major modification, but limited this provision to nonCMRS private land mobile  S'services.L {OB'ԍ ULS Notice at 9689,  38.L AMTA seeks clarification of this proposal, noting that under Part 90 of the Commission's rules, certain frequencies that are subject to frequency coordination requirements may be licensed to  Sb'both CMRS and PMRS systems.=b yO'ԍ AMTA Comments at 5.=֠ As AMTA suggests, we will delete the exclusion of CMRS licensees from this provision. Most frequencies that are subject to frequency coordination are not available to CMRS providers. However, there are some instances in which CMRS providers may  S'operate on coordinated frequencies and, therefore, must comply with coordination requirements.rZ yO 'ԍ For example, both PMRS and CMRS providers may operate on shared paging channels in the 929 MHz  {Od 'band, and on shared Business Radio channels; see also, 47 C.F.R.  90.175 for a detailed description of frequency coordination requirements including a list of those frequencies that require coordination.r We see no reason to treat an application that requires coordination as major in one instance and minor in another instance based on the regulatory classification of the applicant.  SJ 'A66.ؠ Motorola requests that we limit our proposed definitions for major modifications so that the definitions will not apply to shared frequencies. Motorola contends that this limitation will ensure that approval of applications for shared frequencies is not unnecessarily delayed by use of procedures  S 'for major filings that only have relevance to licensing on an exclusive basis.C 4 yO'ԍ Motorola Comments at 45.C We agree that classifying an application as major may have different procedural consequences depending on whether the license is for shared or exclusive spectrum. However, we do not agree that our major modification definitions should not apply to shared frequencies. There are numerous instances in which an application could significantly affect other licensees on a shared frequency, and should therefore be considered major. We will therefore apply our major change rule to both exclusive and shared frequencies as proposed.  S'B67. A number of commenters expressed concern regarding our proposed rule with respect to changes of coordinates and increases in antenna height or power level for wireless services licensed on  SB'a sitespecific basis.dB yO'ԍ FCBA Comments at 27; B&B Comments at 4; EEC Comments at 3.d Commenters also sought clarification whether our rule would require sitebased  S'licensees to file modification applications for changes to internal sites.`T  yO 'ԍ Airtouch Comments at 67; BellSouth Comments at 1314.` As noted above, we have modified the language in our rule to make clear that a change in coordinates or an increase in antenna height or power level for a sitespecific license is not a major modification if it does not affect the composite interference contour or defined service area of the system. However, because we use different technical criteria to define these parameters in particular services, we have determined that some servicespecific elements of our existing rules should be retained in the consolidated rule. We"R! 0*@%@%" have also retained certain other servicespecific criteria that were inadvertently deleted from our proposed rule. For example, our current rules regulating the use of fixed transmitters under Parts 22 and 90 were omitted from proposed section 1.929 but are now incorporated in our consolidated rule.  S`' ` ` c. Fixed Microwave Services  S'C68. Background. Regarding stations licensed to provide exclusively fixed pointtopoint, multipointtopoint, or pointtomultipoint, communications on a sitespecific basis, we proposed additional actions which we would consider a major change. Specifically, we proposed the following  S'actions in the ULS Notice: any change in transmit antenna location by more than 5 seconds in latitude  Sr'or longitude (e.g., a 5 second change in either latitude or longitude would be minor); any increase in frequency tolerance (Fixed Microwave only); any increase in bandwidth; any change in emission type; any increase in EIRP greater than 3 dB; any increase in EIRP greater than 1.5 dB (DEMS only); any increase in transmit antenna height (above mean sea level) more than 3 meters; any increase in transmit antenna beamwidth; any change in transmit antenna polarization (fixed microwave only); any change in transmit antenna azimuth greater than 1 degree; any change in latitude or longitude that requires special aeronautical study; or any change which together with all minor modifications or amendments since the last major modification or amendment produces a cumulative effect greater than  S4'any of the above major criteria.L4 {O'ԍ ULS Notice at 9689,  38.L  S'D69. Discussion. With respect to fixed pointtopoint, pointtomultipoint, and multipointtomultipoint services licensed on a sitespecific basis, we adopt additional criteria for distinguishing major and minor changes that are based on the distinctive technical characteristics of these wireless services. We also adopt our proposal to treat multiple minor modifications as major if the cumulative effect of these modifications would be a major change to the system. We note that some commenters expressed concern that the proposed rule was too imprecise for applicants and licensees to comprehend  S'easily, and we have endeavored to address these concerns with the rule we adopt today.lZ {O'ԍ SBC Comments at 11; see  1.929, Appendix G, infra.l We conclude that the rule is consistent with our existing policies for licensing microwave services. Therefore, we will require microwave licensees filing minor modifications to certify on Form 601 that the minor modifications do not give rise to a cumulative major modification.  S,' E70.ؠ We proposed to combine the two categories of minor filings in Part 101 into one  S'category that we would not place on public notice.L {O 'ԍ ULS Notice at 9690,  40.L CellNet agrees with the NSMA opposition to the proposed elimination of public notices for actions taken on fixed microwave applications. CellNet states that it uses the public notices to track the progress of applications and correct any errors that""~0*@%@%"  S'occur, and that public notices help frequency coordinators ensure the accuracy of their databases.Z yOh'ԍ NSMA Comments at 4; CellNet Reply Comments at 2.Z  S' We agree with CellNet and NSMA that the release of public notices by fixed microwave licensees should continue, because it allows frequency coordinators to ensure the accuracy of their databases.  S`' ` ` d. Minor Changes  S'F71. Background. We proposed to allow licensees to implement all minor changes, as defined  S'in the consolidated rule, without prior Commission approval.LX {O 'ԍ ULS Notice at 9691,  41.L Instead, licensees would be required  S'only to electronically notify the Commission within thirty days of implementing the change.4 {OJ 'ԍ  Id. 4 We noted the possibility, however, that an applicant or licensee could submit multiple amendments or modifications each of which would be individually considered minor but which would cumulatively constitute a major change. We proposed to treat such cumulative changes as major, and sought  S 'comment on how to apply this standard to applicants and licensees.H | {O<'ԍ Id. at 969091,  41.H  S 'G72. Discussion. As proposed, we will define as minor changes all amendments to applications and license modifications that are not specifically defined in our rule as major. These minor changes  S 'include but are not limited to: (1) any pro forma transfer or assignment; (2) any name change not involving a change in ownership or control of the license; (3) changes to administrative information,  S2'e.g., address, telephone number, or contact person; or (4) conversion of multiple sitespecific licenses into a single widearea license, where there is no change in the licensee's composite interference  S'contour or service area.I {O'ԍ  See 47 C.F.R.  1.929.I We also adopt our proposal to allow licensees to make most minor modifications to their licenses without prior Commission approval, provided they notify the Commission within thirty days after implementing the change. We clarify that prior approval  Sl'continues to be required, however, for pro forma assignments and transfers that are not subject to the  SF'Commission's forbearance policy,_F {O'ԍ See Discussion at Section III.B.8, infra._ and for conversion of multiple sitespecific licenses into a single widearea license.  S'H73. We also clarify that the notification requirement for minor changes only applies to changes to the licensing or technical information contained on the license or that may be the subject of specific notification requirements in the Commission's rules. In general, minor system changes that do  SV'not affect licensing information (e.g., internal sites in geographically licensed systems or internal sites"V#2 0*@%@%" within the composite interference contour or service area) require no notification to the Commission,  S'and we will not collect such data in ULS.I {O@'ԍ See 47 C.F.R.  1.929.I  S`' 3. Submission of Ownership Information  S'I74.OWNERINFO Background. We currently have various servicespecific requirements for wireless applicants and licensees to provide ownership information to confirm that these licensees are in compliance with ownership restrictions imposed by the Communications Act as well as certain  S'Commission rules. In the ULS Notice, we proposed to adopt a consolidated rule governing the submission of ownership information by wireless applicants and licensees, and to create a ULS form  SJ 'for collection of such information. We noted that in the Part 1 Third Report and Order, the Commission had adopted a uniform set of ownership reporting requirements in section 1.2112 of the  S 'rules for applicants and licensees in services subject to auction.f Z {O'ԍ Part I Third Report and Order, 13 FCC Rcd. 374 (1997).f We proposed to use the new ULS Form602 to collect this information, which would enable licensees in services subject to our competitive bidding rules to provide ownership information for all of their licenses on a single form. In accordance with section 1.2112, applicants or licensees would then be required to update the form only as necessary when filing an additional license application or an application for license assignment  S4'or transfer of control.L4 {O'ԍ ULS Notice at 9692,  45.L  S'J75. To further the streamlining objectives of both ULS and the Part 1 proceeding, we also proposed to eliminate all duplicative or inconsistent ownership reporting requirements in our service S'specific rules associated with wireless services subject to our competitive bidding requirements.E~ {O'ԍ Id. at 9692,  46.E For example, we noted that section 22.108 of the Commission's rules requires Part 22 applicants to report  SF'all persons or entities who hold a five percent or greater ownership interest in the applicant, while section 1.2112 requires reporting only of parties with a ten percent or greater interest. Accordingly, we proposed to delete section 22.108 in order to remove this inconsistency and carry out the intent of  S'the Part 1 Third Report and Order and to conform our reporting requirements for such services. In so doing, however, we noted that we were not precluding the possibility of requiring certain applicants or  S'licensees to provide more specific information where necessary (e.g., to verify eligibility for small  SZ'business status in an auction).KZ {O "'ԍ Id. at 96929693,  46.K "2$0*@%@%~"Ԍ S'K76. Finally, we sought comment on whether to use the ULS system to collect ownership information from licensees and applicants in wireless services for which our competitive bidding rules  S'do not apply.E {O'ԍ Id. at 9693,  48.E Although we did not propose to collect ownership information in these services, we did propose to require applicants and licensees in these services to disclose realparty in interest information and certify that it is not a representative of a foreign government, as is currently required  S8'for all microwave applicants or licensees in sections 101.7(a) and 101.19(a)(1).E8Z {O2'ԍ Id. at 9693,  47.E We also sought comment on whether we should expand the current ownership reporting requirements for applicants and licensees in these services. For example, we asked commenters to address whether commercial entities holding private wireless licenses, i.e., railroads or utilities, should be required to submit ownership information for all of their licenses regardless of whether the service was subject to our competitive bidding rules. We tentatively concluded that licenses held by governmental entities should not be subject to any ownership reporting requirements. We also tentatively concluded that due to the personal nature of the Amateur Radio Service, General Mobile Radio Services and Commercial Radio Operators, extension of ownership reporting requirements to these services was unnecessary. We  S 'sought comment on these tentative conclusions.L  {O\'ԍ Id. at 9693,  4748.L  S 'L77. Discussion. As proposed, we will require applicants and licensees in wireless auctionable services, subject to section 1.2112, to file or update Form 602 in connection with any initial license application, renewal application, or application for assignment or transfer. This decision, which we codify in new section 1.919(e), merely implements the information collection requirements of section  S'1.2112(a) of the Commission's rules as adopted in the Part 1 Third Report and Order.J~ {O'ԍ See 47 C.F.R.  1.2112.J These requirements apply to all applicants or licensees in wireless services subject to our competitive bidding rules which are defined in section 309 of the Act, as amended by the 1997 Budget Act. We note that this requirement includes all licensees in such services, regardless of whether the particular license in question was originally acquired by auction, except the services listed as exempt in paragraph 24,  S'supra. For example, because all common carrier licenses are subject to auction under section 309(j) of the Act where mutual exclusivity exists, we treat them as subject to the reporting requirements of Part 1 even though some common carrier licensees obtained their licenses before we had auction authority or can obtain licenses without going to auction because they do not face mutually exclusive applications. Thus, common carrier licensees who acquired their licenses by lottery or by other means besides auction are subject to these ownership reporting requirements when they apply for assignment, transfer, or renewal of a license.  S'M78. We emphasize that Form 602 is specific to the applicant or licensee rather than the particular application. Thus, an applicant for multiple licenses in an auction is required to file only"%0*@%@%" one Form 602. Moreover, once the applicant or licensee files the form for the first time, it has no need to file the form with subsequent applications, regardless of service, so long as the ownership  S'information on the previous form remains current.H {O'ԍ See 47 C.F.R.  1.65.H Instead, ULS will associate all future applications filed by the same applicant with its Form 602 already on file. Moreover, if the Form 602 requires updating when a subsequent application is filed, the applicant need not resubmit the entire form but can simply access the portions of the form that require updating and submit the updated information electronically. ULS will then replace the existing information with the updated information. These streamlined requirements made possible by ULS are broadly supported by  S'commenters.Z yO 'ԍ BellSouth Comments at 1415 (supporting the use of one form for multiple licenses); Nextel Comments at5 (favoring a consolidated Form 602 to simplify reporting requirements).  Sp'N79. We also will not extend Form 602 filing obligations beyond those services that are subject to our competitive bidding rules, except for common carrier licensees operating on spectrum that is not subject to auctions (e.g., shared spectrum). Numerous commenters interpreted our proposed section 1.919 as requiring applicants and licensees in private, nonauctioned services to file Form 602. In fact, while we did seek comment on whether ownership reporting requirements should be applied to these services, we did not propose an expansion of these requirements beyond existing rules. As commenters note, existing rules do not require applicants or licensees in these services to report  SX'detailed ownership information.XX yO'ԍ API Comments at 8; BellSouth Comments at 15; CenturyTel Comments at 910; Motorola Comments at 10; Ameritech Reply Comments at 67; ITA Reply Comments at 34; PCIA Comments at 12; SBT Reply Comments at 14. Instead, an applicant must typically identify the real party in interest to the application (if different from the applicant), and certify that it is not a foreign government or a representative of a foreign government. Because these questions are contained on Form 601, we agree that there is no need for filing a separate Form 602 by applicants or licensees in these services.  Sh'O80. We also emphasize that Form 602 need only be filed or updated when the applicant is filing a license application (either an initial application or a renewal application) or when the license is  S'the subject of an assignment or transfer of control. Some commenters incorrectly interpreted the ULS  S'Notice as proposing that licensees be required to update Form 602 every time there is a minor change  S'in the licensee's ownership or management, e.g.,when a noncontrolling investor changes or a new director is elected. In fact, it was not our intent to require applicants or licensees to update their ownership information when such minor changes occur. This submission is not required by section 1.2112, nor do we impose such a requirement here. We also decline to impose a requirement that  S.'Form 602 be updated annually, as was suggested by FCBA.D. yO#'ԍ FCBA Comments at 18.D Although such a requirement might improve the accuracy of ownership information on file with the Commission, we have concluded that"&b 0*@%@%4" it is sufficient to require updates only in connection with significant licensing events. We decline to revisit that decision in this proceeding. However, we note that licensees may voluntarily update their Form 602 information at any time, whether or not the update is required.  S`'P81. A number of commenters object to the level of detail about ownership that we are requiring on Form 602. AT&T, BAM, and FCBA, for example, argue that our proposed requirement to identify direct and indirect owners with at least a tenpercent interest in the licensee is excessive  S'and burdensome, because in most instances, a tenpercent owner does not control the licensee.t yOP'ԍ AT&T Wireless Comments at 45; BAM Comments at 12; FCBA Comments at 2829.t However, the elements of Form 602 to which these commenters object simply track the ownership  S'reporting requirements that we adopted in the Part 1 proceeding.iX {O 'ԍ Part 1 Third Report and Order at 419420,  7677.i Thus, to the extent that commenters object to these reporting requirements, their arguments are beyond the scope of this  SJ 'rulemaking.|J  yO'ԍ Some commenters object to our proposal to collect TIN information from attributable owners identified  {O'on Form 602. We address this argument in Section III.B.10, infra. Other commenters urge us to reconsider or  {Of'forbear from implementing our section 1.2112 reporting requirements. See, e.g., FCBA Reply Comments at 21. (Commission should use its section 11 authority to eliminate section 1.2112 requirements). We will incorporate these comments into the record of the Part 1 proceeding for further review and disposition. Should we change any of the reporting requirements in Part 1, such changes will be incorporated into subsequent versions of Form 602.  Moreover, we note that in the case of PCS and Part 22 licensees, the Part 1 Third  S$ 'Report and Order actually narrowed the scope of applicable ownership reporting requirements, which  S 'previously required reporting of all interestholders down to the fivepercent level.^ .  {O'ԍ Part 1 Third Report and Order at 418,  75.^ In furtherance of  S 'the streamlining goals of the Part 1 Third Report and Order, we also eliminate the more stringent servicespecific reporting requirements of sections 22.108 and 24.813, which are inconsistent with section 1.2112.  S8'Q82. After review of the comments, we also conclude that there is no basis in the record for expanding ownership reporting requirements designed for auctioned services to nonauctioned services. We have revised proposed section 1.919 to remove any possible ambiguity on this issue. As commenters uniformly pointed out, these operations do not affect the competitive balance in the  S'marketplace.X  yO'ԍ API Comments at 8; BellSouth Comments at 15; CenturyTel Comments at 910; Motorola Comments at 10; Ameritech Reply Comments at 67; ITA Reply Comments at 34; PCIA Comments at 12; SBT Reply Comments at 14. Moreover, we will not extend ownership reporting requirements to entities, such as railroads or utilities, that hold only private wireless licenses in nonauctioned services. Due to the fact that these operations are for internal communications, ownership information for the purpose of monitoring the competitive marketplace is not necessary. " '0*@%@%"Ԍ S'ԙR83. While we do not extend ownership reporting requirements to exempt services as discussed  S'supra, we will continue to require all applicants and licensees who use Form 601, including those in nonauctioned services, to provide realpartyininterest information and to certify that they are not representatives of foreign governments. We also clarify the realpartyininterest definition in the  Sb'instructions to Form 601, as requested by FCBA,Ab yO'ԍ FCBA Comments at 1718.A and revise Form 601 to allow identification of multiple realpartiesininterest where control of the license is shared by more than one person or entity.  S' 4. Frequency Coordination of Amendment and Modification Applications  SJ 'S84.ؠ COORD נBackground. In the ULS Notice, we noted that the Commission's rules in Parts 90 and 101 differ with regard to coordination requirements for major technical amendments and modifications; our goal is to make rules as consistent as possible among the wireless services. Section 90.175 of the Commission's rules identifies numerous changes that do not require frequency  S 'coordination, including minor technical changes.J X {O'ԍ See 47 C.F.R.  90.175.J Section 101.103(d), on the other hand, requires a  S 'new coordination statement for minor technical changes.N  {O'ԍ See 47 C.F.R.  101.103(d).N Accordingly, in the ULS Notice, we proposed to amend section 101.103 by requiring frequency coordination only for those applicants or licensees filing amendments and modifications that involve changes to technical parameters that are classified as major in accordance with the new unified standards of section 1.929 of the Commission's  S'rules.N| {O'ԍ ULS Notice at 9694,  50. N Thus, licensees making minor changes to technical parameters would only be required to notify the Commission, as well as the entity(ies) with which they normally engage in frequency coordination, of the minor change. In seeking comment on this proposal, we noted that the proposed  Sn'change to section 101.103 will provide uniformity among the rules for all of the affected services.3n {O'ԍ Id.3  S'T85.ؠDiscussion. The majority of commenters addressing this issue support the proposed amendment to section 101.103 because it will provide uniformity in the rules and support their  S'consistent application. yO!'ԍ API Comments at 14; BAM Comments at 13; Nextel Comments at 6; FIT Comments at 1415; CellNet Comments at 6; BellSouth Comments at 16; APCO Comments at 2, 5. APCO recommends that the FCC Form 601 Instructions direct applicants to send all applications which contain one or more "major" items or request a new frequency directly to"( 0*@%@%"  S'the appropriate frequency coordinator.= yOh'ԍ APCO Comments at 5.= FCBA, while supporting this proposal, urges the Commission  S'to be consistent in defining "major" and "minor" throughout its rules.>X yO'ԍ FCBA Comments at 37.> PCIA recommends that the notification provision specifically requires that the appropriate frequency advisory committee be furnished with an exact copy of the form or document filed with the Commission which indicates the  S`'change, in order to facilitate its frequency recommendations.` {O'ԍ PCIA Comments at 12; for the notification provision, see 47 C.F.R.  90.175.  S'U86.ؠNSMA and Comsearch, on the other hand, both argue that the Commission should not amend the Part 101 procedures to allow notification for minor technical amendments and  S'modifications.z yO 'ԍ NSMA Comments at 89 and Reply Comments at 2; Comsearch Comments at 35 and Reply Comments at 14. NSMA states that the reporting of all changes, whether minor or major, will allow  S'coordinators to maintain accurate databases and enhance their ability to make interference decisions.= yO 'ԍ NSMA Comments at 9.= Comsearch argues that this standard should be maintained separate and apart from the definition of  SH 'major and minor changes for filing purposes.JH b  yOJ'ԍ Comsearch Reply Comments at 14.J Comsearch and FCBA believe that differences in Part  S '90 and Part 101 coordination mechanisms may justify different treatment under the rules.`  yO'ԍ Comsearch Reply Comments at 2; FCBA Comments at 3738.` Under Part 101, explains Comsearch, all potentiallyaffected parties are notified of any changes, no matter how minor, and this procedure has proved very successful in helping to identify and avoid potential  S 'interference problems.H  yO'ԍ Comsearch Reply Comments at 2.H Along these lines, NSMA contends that should the Commission adopt this proposal, the phrase "entity(ies) with which it normally engages in frequency coordination" should be clarified to indicate that notice of an amendment or modification of coordinates be sent to all parties  S0'involved in the original coordination, and not simply the original coordinator.=0 yO'ԍ NSMA Comments at 9.= Comsearch responds to other commenters who contend that coordination of minor changes is unnecessary, stating its belief that it is inappropriate to equate application filing requirements (major versus minor) with coordination requirements, because, it argues, "minor" changes can significantly increase the potential for  S'interference.H yO#'ԍ Comsearch Reply Comments at 3.H As for claims that coordination of minor changes increases financial burdens,")20*@%@%U" Comsearch notes that Part 101 has a "notification only" mechanism that is routinely completed in one day, and, further, rectifying interference conflicts after they have occurred is significantly more  S'expensive and time consuming for all involved parties.J yO'ԍ Comsearch Reply Comments at 34.J  S`'V87.ؠWe conclude that we will modify section 101.103 as proposed in the ULS Notice because our concern was the same as the FCBA's, namely that we need to make the Commission's rules consistent. This modification serves that goal by making Parts 90 and 101 consistent on the issue of when a new coordination is necessary, building on our establishment, in new section 1.929 of the Commission's rules, of "major" and "minor" categories that are as uniform as possible. Because a central component of the criteria in section 1.929 is whether an amendment or modification will materially alter the original engineering and technical information of an application or license, we are confident that only those changes considered major have the potential to impact an original coordination enough to merit a new coordination. In other words, coordinators seldom, if ever, should need to alter substantially frequency and/or site recommendations based on a minor amendment to an application or modification of a license. As a result, we believe that there is insufficient justification to continue to require licensees and applicants to obtain a new coordination analysis for minor amendments and modifications.  S2'W88.ؠWe are confident that requiring the licensee or applicant to notify the Commission and the entity(ies) with which it normally engages in coordination is sufficient to allow coordinators, and other interested parties, to remain aware of such changes and keep their databases uptodate. We find it unnecessary to broaden our proposed language to include "all parties involved in the original coordination." Should the licensee notify only the coordinator of a minor change, other "interested" parties can obtain the information from the coordinator. We do not believe that the universe of parties affected by, or interested in, minor changes, as defined in new section 1.929, will be significant.  S' 5. Returns and Dismissals of Incomplete or Defective Applications  S'  Sz'X89. RETURNS  Background. Our current regulations contain a variety of servicespecific rules and  SR'procedures for dismissal or return of incomplete or facially defective applications. In the ULS Notice, we proposed to unify our filing rules so that all wireless applicants and licensees would be subject to  S'consistent rules regarding dismissals and returns.LX {O'ԍ ULS Notice at 9695,  53.L We noted, however, that in the case of interactively filed electronic applications, ULS would be able to identify and alert the applicant to certain types of application errors in real time, thus enabling the applicant to make immediate corrections before submitting the application. However, in the case of batchfiled electronic applications and manual filed applications, the same errors would not be detected until after the application was filed. We therefore proposed to establish procedures so that batch, interactive, and manual filers would be treated similarly with respect to application errors. In the case of minor" *0*@%@%" defects or missing information, we proposed that an applicant who filed a paper application that was accepted by ULS be notified of the defect and given thirty days to file a corrected application. We also proposed several exceptions to the thirtyday right to refile. First, if the applicant submitted a major amendment, the applicant's ability to refile would depend on whether major amendments were allowed under the circumstances. Second, we proposed that certain defects in an application would result in immediate dismissal. These defects included filing the application without a sufficient fee, filing outside of an applicable filing window, or filing an application without a valid signature. Finally, we proposed to establish procedures for handling and protecting filings in ULS for which the applicant seeks confidential treatment.  Sp' Y90.ؠ Discussion. We adopt a consolidated rule in Part 1 governing the filing of incomplete or  SH 'otherwise defective applications in all wireless services, and we modify the proposal in the ULS Notice to further limit the circumstances under which defective applications will be returned for correction. Under the consolidated rule, as under existing rules, the Commission has the discretion to return applications for correction of minor filing errors, but it also has the authority to dismiss any  S 'incomplete or defective application without prejudice.D  yO'ԍ Appendix G,  1.934(d).D Pursuant to this rule, and as proposed in the  S 'ULS Notice, we will automatically dismiss any application that is defective because the applicant failed to sign the application, failed to pay the required filing fee, or filed outside of the applicable filing window. These defects are fatal to the consideration of the application. This policy ensures equal treatment regardless of the manner in which the application is filed. In the case of an interactive electronic filing, submitting the application with any of these defects would be impossible, because ULS will automatically reject the application as defective on its face. To ensure equivalent treatment of electronically batchfiled or manually filed applications that are unsigned, untimely, or not feecompliant, such applications will be automatically dismissed by ULS after they are initially entered into the system. Accordingly, we remove those sections of the rules that provided for return and  S'correction of applications with errors."X {O'ԍ See former 47 C.F.R.  1.959, 90.141, 90.611 (f), 90.711(a)(5), 101.35(c), 1.962(e), 1.1109(d).  S'Z91. We will also dismiss batchfiled and manually filed applications with other types of defects that are automatically screened by ULS when an application is interactively filed, e.g., missing technical data or technical parameters that are inconsistent with the rules (where no waiver request is  ST'filed). In the ULS Notice, we proposed that aside from unsigned, untimely, and nonfeecompliant applications, we would return batchfiled and manually filed applications that are entered into the system and subsequently discovered to have errors, even if those errors were of the type that would have prevented the application from being filed interactively because they would have been  S'automatically screened by ULS.L {O@"'ԍ ULS Notice at 9695,  53.L On further consideration, we conclude that in some circumstances, this approach could inadvertently cause manual and batchfilers to have an advantage over interactive filers. For example, if we returned the application of a manual filer who omitted necessary technical"f+|0*@%@%g" data, the filer would have additional time to obtain the data and amend the application without losing its filing priority based on the initial filing date. However, an applicant who files an electronic application interactively would not have the same opportunity, because the system would identify the defect while the application was being filled out by the applicant. The system would then prompt the applicant to correct the application, and if the necessary information could not be obtained before the filing window closed, the applicant could miss its filing deadline. To avoid this disparity, which might otherwise discourage electronic filing, we will dismiss manual and batchfiled applications with screenable errors of this type after they are initially entered into the system. Such dismissal will be without prejudice to the right of the applicant to refile, provided the relevant application window remains open.  SH '[92. While we will generally dismiss defective or incomplete applications, we retain the discretion to return an application for correction if circumstances warrant. In such cases, we will  S 'adopt the return procedures proposed in the ULS Notice, i.e., the application will be returned to the applicant, and the applicant will have thirty days from the date the notification is sent to file an amended application correcting the defect. Although some commenters supported a longer period to  S 'amend, such as sixty or 120 days,C  yO'ԍ Motorola Comments at 67.C we agree with FCBA that thirty days is ample time for an  SZ'applicant to submit corrections.>ZX yOR'ԍ FCBA Comments at 38.> Moreover, in some instances, we believe it is appropriate to require an applicant to submit an amended application in less than thirty days. Therefore, we provide that applicants may be required to amend in less than thirty days, so long as the return notice clearly specifies the amount of time the applicant has to file the amendment. We also delete those service S'specific rules that provided a longer period for applicants to submit corrections.W {OB'ԍ See, e.g., 47 C.F.R.  90.141.W  Sj'\93. When an application is returned for correction, we will hold the application for the designated period so that a corrected application may be filed. If the applicant files a timely corrected application, it will ordinarily be processed as a minor amendment in accordance with the  S'Commission's rules.Iz {O 'ԍ See 47 C.F.R.  1.929.I Thus, it will have no effect on the initial filing date of the application or the applicant's filing priority. If, however, the amendment made by the applicant is not a simple correction but constitutes a major amendment to the application, it will be governed by the rules and  Sz'procedures applicable to major amendments, i.e., it will be treated as a new application with a new filing date. Finally, if the applicant fails to submit an amended application within the period specified  S,'in the notification, the application will be subject to dismissal for failure to prosecute.L,  {O"'ԍ See 47 C.F.R.  1.934(c).L ",0*@%@%A"Ԍ S']94. Finally, we adopt the proposal set forth in the ULS Notice regarding the protection of confidential information filed in ULS, which was supported by the FCBA. The basic elements of that proposal entailed putting the following security measures in place: (1) any attachment designated as confidential will not be accessible from publicly available query utilities; and (2) a special user name  Sb'and password will be required for Commission employees to view confidential attachments.Mb {O'ԍ ULS Notice at 9695,  54.M Should the Commission decide not to grant a request for confidential treatment, the applicant will be so informed so that it may determine whether to maintain the applications as filed, to amend the  S'application by deleting the attachments, or to withdraw the application or filing.Z {O 'ԍ See Examination of Current Policy Concerning the Treatment of Confidential Information Submitted to the Commission, GC Docket No. 9655 (rel. Aug. 4, 1998). The FCBA also urges the Commission to take other measures to protect confidential information against inadvertent or accidental disclosure, such as maintaining it in a secure database or file separate from other application  Sr'information.Br yO'ԍ FCBA Comments at 2021. B We believe that the safeguards we have identified will be sufficient to protect against inadvertent disclosure of confidential information. However, we will continue to explore other safeguards to increase the level of protection afforded to applicants and licensees.  S ' 6. Discontinuation of "Reinstatement" Applications  SZ'^95.REINSTATEנBackground. Under current rules, licensees in the Commercial Radio Operator Service, PLMRS, Amateur Radio Service, and Fixed Microwave Radio Services, who fail to file timely renewal applications are afforded a thirtyday period following the expiration of their licenses in which  S'to request reinstatement.D {O'ԍ See 47 C.F.R.  13.13(b), 21.44(b), 24.443(a), 26.325(b), 90.149(a), 97.21(b) and 101.65(b). Although this practice was instituted due to the large number of latefiled  S'applications in these services, we observed in the ULS Notice that it is inconsistent with other wireless  S'service licensing rules where reinstatement is not permitted.t {O 'ԍ ULS Notice at 9696,  55; see, e.g., 47 C.F.R.  22.145.t With the implementation of ULS  Sl'presenting a unique opportunity to establish regulatory symmetry among all wireless services, the ULS  SF'Notice proposed to use ULS for automatic license preexpiration notification to all licenses, explaining that this notification would eliminate the reinstatement period and instead automatically cancel the  S'license following expiration.^\h  {O!'ԍ Id. at 9696,  56. As we stated in the ULS Notice, this proposal does not affect the five year grace period within which holders of Commercial Radio Operator licenses may renew expired licenses without retaking  {O"'the required examination. See 47 C.F.R.  13.13(b).^ "- 0*@%@%K"Ԍ S'_96.ؠDiscussion. We will adopt our proposal to eliminate reinstatement procedures in those wireless services that currently allow such applications, and instead use ULS to provide all licensees  S'with preexpiration notification ninety days prior to the expiration of their licenses.5X yO'ԍ Because we are confident that ninety days is more than sufficient time for all licensees to file renewal applications, we reject Motorola's suggestion that we send the renewal notification at least 120 days in advance of license expiration. Motorola Comments at 67.5 Such notification will be sent by mail to the point of contact listed in the ULS database for each callsign. We conclude that notifying wireless radio licensees of the expiration of their licenses at least ninety days prior to the relevant deadline is reasonable. Our decision to use this reminder letter as a convenience to licensees does not in any way absolve licensees from timely filing their renewal applications. Failure to file for license renewal before the end of the license term will result in  S'automatic cancellation of the license.X {OH 'ԍ See Appendix G, infra,  1.949.X Our proposal received support from several commenterslz yO 'ԍ Nextel Comments at 7; CellNet Comments at 3; AASHTO Comments at 6.l and is consistent with the purpose of this proceeding of implementing consistent licensing procedures wherever feasible. All licensees are responsible for knowing the terms of their licenses and for filing  SH 'a timely renewal application if they seek to operate beyond that term.H  {O'ԍ Industrial Communications and Electronics, Inc., Station WNMD402, Order on Reconsideration, DA 98667, at  13 (rel. April 28, 1998) (Commercial Wireless Division). We clarify, however, that our decision to eliminate reinstatement procedures does not affect the renewal process for for Commercial Radio Operators Licenses or Amateur licensees Unlike licensees in other services, Commercial Radio Operators and Amateurs obtain their authorizations by taking and passing an examination. Our current rules provide that Commercial Radio Operators may renew their its authorizations up to five years after expiration and that Amateurs may renew their licenses up to two years after license expiration  SX'without having to retake the required examinations.[Xd  {O\'ԍ See 47 CFR  13.13(b) and 97.21(b).[ We see no reason to modify these rules, which recognize that a licensee that has previously passed an examination does not need to demonstrate again his or her knowledge of the required material.  S'`97.ؠ Among the commenters that urge the Commission to retain reinstatement procedures,.  yON'ԍ Winstar Comments at 1011; AMTA Comments at 56; APCO Comments at 45; API Comments at 11 and Reply Comments at 12; SBC Comments at 1314; Bennet Comments at 67; FCBA Comments at 3940; FIT Comments at 1516; NSMA Comments at 13; PCIA Comments at 9; ADT Comments at 8 and Reply Comments at 4; AICC Comments at 89 and Reply Comments at 4; AAA Comments at 8; ITA Reply Comments at 4; Radiophone Reply Comments at 4; Century Comments at 11; PNI Comments at 2; SBT Reply Comments at 7; Ameritech Reply Comments at 89.. the majority are licensees, or are involved with licensees, in services which currently have such mechanisms. Some commenters suggest extending such procedures to other services, such as the"h.n0*@%@%"  S'Commercial Mobile Radio Services (CMRS). yOh'ԍ AMTA Comments at 56; Ameritech Reply Comments at 89; ADT Reply Comments at 5, n.5; AICC Reply Comments at 5, n.5. Commenters' reasons for supporting reinstatement vary, from arguing its importance to licensees in services subject to filing freezes or relicensing on  S'only a secondary basis,_  yOp'ԍ AMTA Comments at 6; Ameritech Reply Comments at 910._ to discussing the potential for many private wireless licensees to file their renewal applications late since use of their authorizations is secondary to their primary business  S`'operations.` yO 'ԍ API Reply Comments at 12; AAA Comments at 8; ADT Comments at 8 and Reply Comments at 5; AICC Comments at 89 and Reply Comments at 5. We are not persuaded by arguments that removing these reinstatement procedures will result in too severe a punishment for inadvertent failures to file renewal applications. Elimination of the reinstatement period will benefit all licensees and entities interested in acquiring abandoned spectrum. Our action herein will also facilitate the Commission's ability to efficiently and quickly perform its licensing responsibilities by reducing the amount of latefiled renewal applications and eliminating the processing of reinstatement applications. We believe that eliminating reinstatement applications is appropriate because licensees will have direct notification that their licenses are about to expire and, therefore, the responsibility to file a timely renewal application will lie where it belongs, namely in the hands of the licensee. Finally, we believe that interactive electronic filing will make it easier for all licensees to timely file renewal applications. Further, licensees should be able to obtain the necessary renewal form more easily than ever before as Commission forms are widely available to  S 'the public through the FCC world wide web page,U  {OP'ԍ See http://www.fcc.gov/formpage.html.U via a toll free telephone number,@  yO'ԍ 1800418FORM (3676).@ via a toll free  S 'TTY number, and through a faxondemand service. *  yOJ'ԍ Call 12024180177 from the handset of any fax machine and follow the recorded instructions. We will not implement this decision to eliminate reinstatement applications for any wireless service until (1) July 1, 1999, or (2) six months after the commencement of application processing in ULS for that service, whichever is later. This transition period will provide a reasonable time for applicants and licensees to familiarize themselves with this procedure.  S'a98.ؠ We note that FCBA argues that these changes will result in an increase, rather than a  Sh'decrease, in the filing of pleadings and petitions.Ah  yO 'ԍ FCBA Comments at 3940.A In response, we clarify that the correct procedure for a licensee that has allowed its license to lapse is to file a new application, and if necessary, a request for special temporary operating authority. We are confident that the ULS notification procedure will prompt licensees to file their renewal applications on time. We also anticipate that ULS will produce staffing efficiencies that will streamline the consideration of any requests for special"/J 0*@%@%>" temporary authority. We conclude that this action serves the public interest because it will improve the efficiency with which the Commission makes spectrum available for reuse after a license has lapsed. Finally, the ULS notification procedure does not replace the license renewal provisions set  S'forth in the Commission's rules.X {O'ԍ See Appendix G, infra,  1.949.X Accordingly, even if a licensee does not receive a renewal reminder notice, the licensee still must timely file its renewal application. Also, not receiving a renewal reminder notice does not excuse the licensee's failure to seek a timely renewal.  S'b99.ؠWe conclude that we will not adopt a separate and distinct procedure for public safety and local government licensees. We agree with APCO that the consequences of the cancellation of a public safety license potentially fall not only on the licensee but on the public which relies on the  Sp'licensee to protect the safety of life and property.?pZ yOj 'ԍ APCO Comments at 45.? Nonetheless, for the same reasons that other licensees must file their renewal applications on time, so must public safety licensees. Public safety entities are acutely aware of the value of their licenses, and we believe that with the benefit of their own systems for taking responsibility for their licenses, and with the help of the Commission's notification procedures, such entities should be able to file their renewal applications in a timely fashion. We therefore reject APCO's suggestion that we not only retain the reinstatement period, but  S 'also send a notification both ninety and thirty days in advance of license expiration.9  {O 'ԍ Id. at 5.9 We note that where in fact continued operations are immediately critical to essential safety operations, the public safety entity that has allowed its license authority to lapse is likely to file a request for special  S'temporary authority.J| {O$'ԍ See 47 U.S.C.  309(f).J  S'c100.ؠAlthough a license expires automatically on the date specified on the individual license, ULS will not show a license expiration as final until approximately thirty days after the renewal deadline. We note that the purpose of this delay is not so that the licensee may seek reinstatement of the license that has now expired, but to ensure that the Commission does not inadvertently fail to recognize that a timely renewal application has been submitted. After the license expiration the previous licensee may file a new application for use of those frequencies subject to any service specific rules. Once that thirtyday period has elapsed, or the prior holder of the license files a new application for that spectrum, the license will then be available for the Commission to reassign by competitive bidding or other means according to the rules of the particular service.  S('d101.ؠFinally, based on commenters' concerns, we will not adopt our proposal to allow licensees and applicants to decide whether they want to continue to be notified of Commission actions in writing via regular mail or instead be notified of Commission actions concerning applications"00*@%@%"  S'contained in ULS via electronic mail.L {Oh'ԍ ULS Notice at 9697,  58.L Applicants and licensees will continue to be notified of official Commission action by regular mail only. Parties should note that pursuant to the the  S'Commission's rules there is only one official point of contact per license.GZ {O'ԍ See 47 C.F.R.  1.5.G Licensees and applicants should keep all mailing and contact information current. While the Commission is optimistic that a system of electronic communication at some time in the future may offer a substantial increase in efficiency and paper reduction, we are sympathetic to commenters' concerns about the use of an  S'electronic notification process at this time.U  yO 'ԍ PCIA Comments at 67; API Reply Comments at 1314; BellSouth Comments at 2526 and Reply Comments at 7; CenturyTel Comments at 6; EEC Comments at 9; ADT Comments at 7; AAA Comments at 7; AICC Comments at 7; Metamora Comments at 9; PAI Comments at 9; Radiophone Comments at 56; Rinker Comments at 9.U We note, however, that in this era of tremendous technological advancement, we may revisit this issue at a later time should circumstances so warrant.  Sp' 7. Construction and Coverage Verification  S 'e102. CONSTRUCTBackground. In the ULS Notice, we recognized that in many wireless services, licensees are subject to construction and, in some instances, coverage requirements, and are subject to automatic license cancellation if these requirements are not met. We noted that different procedures have  S 'evolved in different services for verifying whether licensees have in fact met these requirements.V  {O'ԍ ULS Notice at 969798,  5960.V In some wireless services subject to construction requirements, the Commission's rules provide that licenses cancel if the licensee fails to notify the Commission that it has met its construction or  S2'coverage requirement.#footnote reference#P2f 3 {O'ԍ See, e.g., 47 C.F.R.  21.44.P In other wireless services, licenses cancel automatically if a licensee fails to  S 'construct by its construction deadline.)footnote reference)#footnote reference#u  3 {OY'ԍ See, e.g., 47 C.F.R. 22.142, 90.155, 90.629, 101.63, 101.65.u In some, but not all, of the latter services, the Commission staff sends letters to determine compliance and then notifies licensees that their licenses are cancelled when licensees fail to certify compliance or state that they did not meet the construction or coverage requirements. In some services that are licensed by geographic area, licensees may forfeit their license by failing to meet coverage requirements, but no procedures have been established for notifying  SB'licensees of approaching deadlines or confirming that these deadlines have been met.)ڗfootnote reference)#footnote reference#mB 3 {O#"'ԍ See, e.g., 47 C.F.R. 24.203, 90.665, 90.833, 95.833.m "10*@%@%"Ԍ S'f103. We proposed to establish uniform procedures for using ULS to notify all wireless radio  S'licensees of upcoming construction or coverage deadlines.L {O@'ԍ ULS Notice at 9698,  60.L We thought that such a consolidation would conform the rules for all wireless services licensees so that similarly situated applicants and licensees would be treated equally. In addition, we thought that such an action would lessen the burden on applicants and would ensure that deadlines are met or that the public receives timely  S8'notification of terminations.48Z {O2'ԍ Id. 4 We also proposed requiring notifications filed by wireless services  S'licensees to be filed electronically.E {O 'ԍ Id. at 9698,  61.E In addition, we proposed to require wireless licensees to certify compliance with construction requirements relating to modification applications that involve additional frequencies. Also, we proposed to require fixed microwave licenses awarded on a sitebysite basis to certify compliance with construction requirements for additional or increased service area coverage  Sp'(e.g., a new station, a change in antenna height or EIRP).Ep~ {O'ԍ Id. at 9698,  62.E We also proposed to amend our microwave rules ) footnote reference)to require fixed microwave licensees to file a further modification application if the  S" 'licensee fails to construct a granted modification.G"  {O'ԍ Id. at 96989,  62.G  S 'g104. Discussion. Commenters generally support our proposal to use ULS to notify wireless  S 'licensees in advance of applicable construction or coverage deadlines.Q  yO'ԍ API Comments at 12; BAM Comments at 13.Q Commenters suggest that  S 'such notice be given to licensees between sixty to 120 days prior to the relevant deadlines. 2  yOT'ԍ API Comments at 12 and Cellnet Comments at 5 (60 days), BAM Comments at 1314 (90 days) and Motorola Comments at 9 and Bennet and Bennet Comments at 7 (120 days). We conclude that notifying wireless radio licensees of impending construction and coverage deadlines at least ninety days prior to the relevant deadline is reasonable. We will send these notices to the relevant licensees by mail. We emphasize, however, that the notification procedure adopted here is not intended to replace the basic construction and coverage requirements set forth in the Commission's rules. That means that even if a licensee does not receive a reminder letter, it remains obligated to meet its construction and coverage benchmarks and cannot cite the lack of notification as an excuse for noncompliance. The licensee is solely responsible for complying with its construction and coverage requirements.  S'h105. Some commenters oppose our proposal to require all wireless licensees to notify the Commission that they have met their construction or coverage requirements, and to terminate the"2 0*@%@%K"  S'license if such notice is not received by the Commission.g yOh'ԍ ADT Comments at 78; AAA Comments at 78; AICC Comments at 8.g These commenters express concern that this procedure could result in termination of licenses for facilities that are in fact operational, simply  S'because the licensee failed to provide notice.cX yO'ԍ ADT Comments at 8; AAA Comments at 8; AICC Comments at 8.c FCBA also suggests that this procedure could jeopardize a licensee who reports that it has met its construction requirement early and therefore  S`'assumes there is no need to respond to a subsequent reminder letter sent by the FCC.A` yO'ԍ FCBA Comments at 4142.A Finally, AirTouch and BellSouth note that the Commission recently eliminated the requirement for common carrier microwave licensees to file FCC Form 494A certifying completion of construction, and argue that reinstating a certification requirement is inconsistent with the deregulatory objectives of this  S'proceeding.x {O 'ԍ AirTouch Comments at 78; BellSouth Comments at 16 (both commenters citing The Part 101 Report  {O'and Order, 11 FCC Rcd. 13449, 13458 n.17 (1996)).  Sp'i106.ؠ We agree with FCBA and other commenters that the purpose of our construction notification procedure should be to verify whether licensees have in fact met their construction and coverage obligations, not to terminate licenses for legitimately operating facilities based on a failure to  S 'notify by the licensee that could be the result of a mailing error.A  yOl'ԍ FCBA Comments at 4041.A This policy is reflected in the fact that our proposed rule provides for automatic license termination not based on whether the Commission has received confirmation of construction, but based on actual failure by the licensee to  S 'meet its construction or coverage deadline.L d  {O'ԍ ULS Notice at 9690,  25.L Nevertheless, if a licensee fails to confirm timely construction, we believe it is reasonable to initiate the license termination process as proposed. First, we are enhancing our procedures by using ULS to send construction reminder notices to licensees in  S'all wireless services that have construction performance requirements, which was not possible  S'previously.iX  yOx'ԍ A licensee that meets its construction or coverage requirements early need not wait until the deadline to provide notification of construction, but can do so at any time. ULS will process such early notifications and notices will not be sent for these licenses because they have already been confirmed as constructed. i Second, ULS simplifies the confirmation process for the licensee by allowing for  S'instantaneous electronic filing of the notification. Finally, as proposed in the ULS Notice, we provide that when the Commission fails to receive timely confirmation of construction from the licensee, ULS will generate a letter to the licensee and issue a public notice thirty days before the termination becomes final. This period provides a licensee that has timely met its construction or coverage obligations with additional notice and the opportunity to prevent termination of its license by submitting documentation that is has timely constructed. Once that thirtyday period has elapsed,"30*@%@%{" without notification from the licensee, the license will then be available for the Commission to reassign by competitive bidding or other means according to the rules of the particular service.  S'j107. We also conclude that it is reasonable to require microwave licensees to comply with the same construction notification procedures as other wireless licensees, notwithstanding our prior elimination of the Form 494A filing requirement. As noted above, notification in ULS is simpler and faster than filing the old form, which could not be filed electronically. Notification also provides significant benefits for the public, the Commission, and licensees themselves by increasing the accuracy of the ULS database and promoting more efficient spectrum use. On balance, we conclude that these benefits outweigh the small burden on licensees of filing a notification. We will also modify our proposal to require construction notifications to be filed electronically, which elicited the  SH 'same reservations from commenters as our general electronic filing proposals.QH  {O 'ԍ See Section III.A.2, supra.Q Accordingly, only those services that are subject to mandatory electronic filing will be required to file construction notifications electronically. We will not implement this decision on construction notification procedures for any wireless service until (1) July 1, 1999, or (2) six months after the commencement of application processing in ULS for that service, whichever is later. This transition period will  S 'provide a reasonable time for applicants and licensees to familiarize themselves with this procedure.3 Z {Oz'ԍ Id.3  S0'k108. Finally, we will require licensees to certify compliance with construction requirements relating to modification applications that involve additional frequencies. Many microwave commenters oppose these proposals out of concern that they would result in a licensee losing its preexisting  S'authorization if it fails to complete construction of the granted modification.} yOD'ԍ BellSouth Comments at 1617; Cellnet Comments at 56; CenturyTel Comments at 1213.} They object to our proposal that in such a situation, the licensee must file a modification application deleting the additional frequencies. Instead, they argue that ULS should automatically return the relevant license to  S@'its "premodification grant" status.]@| yO\'ԍ CenturyTel Comments at 14; ADT Reply Comments at 7.] We have reviewed this option, and have determined that programming this logic into ULS would be so complex as to be unworkable. In addition, our original proposal does not put preexisting licenses in jeopardy as these commenters fear; it merely provides a mechanism in ULS for the licensee to meet its obligation to provide accurate information regarding what it has constructed and what it has not. We also clarify that ULS will not cancel the preexisting license of a licensee that fails to construct a new site or frequency so long as the modification was a  SP'request to add the site or frequency, rather than to replace the original site or frequency. This enables a licensee to test the viability of a new site or operations on a new frequency without losing preexisting rights if it fails to commence permanent operations on the new site or frequency. "4 0*@%@%"Ԍ S' 8. Assignments of Authorization and Transfers of Control  S'l109.ؠ ASSIGN  Background. In the ULS Notice, we proposed to consolidate our transfer and assignment rules for all wireless services in Part 1, and to eliminate inconsistencies between the procedures that currently govern CMRS and microwave licenses. First, we proposed to replace the multiple existing forms for transfers and assignments in the various services with two ULS forms, FCC Form 603 for  S'assignment of licenses and FCC Form 604 for transfers of control.[ {Oz'ԍ See Appendix G, infra,  1.948(c).[ Our proposal to use a separate form for each type of transaction rather than a single consolidated form for all assignments and transfers was based on the fact that transfers and assignments do not require identical types of information from the applicant. In addition, the two types of transactions have different processing results: in an assignment transaction, a new license is issued to the assignee, while in a transfer of control, the identity of the licensee generally remains the same. We therefore proposed using two different forms tailored to the two categories of transactions.  S 'm110.ؠ We also proposed to conform the Commission's rules for all wireless services to require posttransaction notification that a Commissionapproved transfer or assignment has been  S 'consummated.L Z {O|'ԍ  ULS Notice at 9700,  66.L We acknowledged that the current Part 90 rules for private mobile radio service (PMRS) and the Part 101 rules for microwave services do not require such notification, but noted that problems occur when an assignment or transfer approved by the Commission is entered into the  S 'licensing database under this streamlined procedure and is not subsequently consummated.3  {O'ԍ Id.3 With the advent of ULS, we tentatively concluded that a uniform postconsummation notification process could  S'be established that would be efficient and easy to use for all wireless licensees.3~ {O'ԍ  Id.3 Using the electronic filing capabilities of the system, licensees would be able to provide such notification by accessing their previously filed transfer or assignment application and entering updated information regarding its consummation. We therefore proposed to require postconsummation notification under ULS using procedures similar to those currently applicable to CMRS transfers and assignments. We also tentatively concluded that these notification procedures should be reinstated for transfers and assignments of microwave licenses, notwithstanding our prior elimination of the postconsummation  S'notification requirement in the microwave services.E {OR 'ԍ Id. at 9700,  67.E  SR'n111.ؠ Finally, we proposed to apply these same postconsummation procedures to pro forma  S,'transactions for which we have recently adopted streamlined procedures in response to the FCBA  S'forbearance petition. Thus, in the case of pro forma transfers and assignments involving"50*@%@%N" telecommunications carriers, for which prior Commission approval is no longer required, we tentatively concluded that licensees should provide the required postconsummation notification and  S'related information regarding the transaction on Form 603 or 604.F {O'ԍ Id. at 9700,  68. F  S`'o112.ؠ Discussion. In general, our proposals for adopting uniform transfer and assignment procedures and forms in ULS were supported by commenters. ADT supports use of ULS for filing  S'and processing of license assignment and transfer of control applications.RZ yO 'ԍ ADT Comments at 2; AICC Comments at 2. R Nextel supports the proposal to replace the multiple forms currently used for assignments and transfers with Form 603 for  S'assignments and Form 604 for transfers of control.? yOJ 'ԍ Nextel Comments at 8.? CenturyTel and Radiofone support the use of ULS for the filing and processing of license assignment and transfer of control applications, but urges that such transactional applications be processed separately from facilities applications to expedite  SH 'processing.\H z yOb'ԍ CenturyTel Comments at 5, Radiofone Comments at 4.\ FIT, however, comments that while the Commission's proposal to replace some current forms used for transfers and assignments has merit, it should retain Forms 1046 and 703, now used in the private services, because they are easy to use and provide the Commission with all necessary  S 'information.<  yOz'ԍ FIT Comments at 4.<  S 'p113.ؠ We believe that consolidating our assignment/transfer rules and replacing servicespecific forms with consolidated forms will provide the public with a consistent set of procedures and filing requirements and will increase the speed and accuracy of the assignment/transfer process. Continuing to use existing servicespecific forms for some services, as FIT suggests, would impede these objectives and create public confusion. We also agree that assignments and transfers need to be processed in a quick, efficient manner. The electronic filing and automated processing capabilities of ULS will enable us to meet this requirement. For example, in the case of transfer and assignment applications that must be placed on thirty days public notice under section 310(d) of the Act, ULS has the ability to automatically generate a weekly public notice of applications received during the previous week. Prompt placement of these applications on public notice will facilitate swifter processing, and will ultimately lead to more expeditious grants of assignments and transfers in most cases.  Sx'q114.ؠ Several commenters proposed that we combine Form 603 and 604 into a consolidated  SP'transfer/assignment form, rather than using separate forms as proposed in the ULS Notice.=P& yO#'ԍ SBC Comments at 4.= SBC comments that the proposed forms are largely duplicative, and that with a minimum of revision one"*6* 0*@%@%q" form could be used for both transfers of control and assignments of license, as is currently the case  S'with Form 490.m yO@'ԍ BAM Comments at 4; AT&T Wireless Comments at 6; SBC Comments at 4.m SBC says that consolidation of these forms would shorten waiting and approval times and would mitigate the paperwork burden on the carrier as well as the administrative burden on  S'the Commission.<X yO'ԍ SBC Comments at 5.<  S8'r115. After review, we agree with the commenters that the transfer and assignment forms can and should be combined. Although there are some differences in the information requirements for  S'transfers and assignments, as we noted in the ULS Notice, we find that there is a sufficient degree of overlap in the questions that must be answered by both types of applicants that the forms can be combined. In addition, to the extent that there are differences in the informational requirements for transfers and assignments, we have designed the revised form (which we designate as Form 603) so that the applicant will only be required to answer the questions pertinent to the type of transaction involved. Thus, in a transfer of control, no new licensee information will be required because the licensee remains the same and a new license is not issued. In an assignment, on the other hand, information regarding the new licensee will be required. Applicants who file Form 603 electrically will only have to complete those fields applicable to the type of transaction indicated. For manual filers, the instructions to the form will explain which questions must be answered based on whether a transfer or assignment is involved.  S 's116. We will make certain other changes to Form 603, some of which have been suggested by commenters. For example, one commenter noted that the proposed form did not contain a schedule for notification of consummation of a transaction, but that such notification was instead provided on a  S'proposed schedule to Form 601.> yO'ԍ FCBA Comments at 33.> We agree that Form 603 should include a mechanism for filing consummation notifications, and have added a notification schedule to the form for this purpose. We have also modified Form 603 so that it can be used by telecommunications carriers to notify the  S'Commission of pro forma assignments and transfers that do not require prior Commission approval  S'under our streamlined forbearance procedures.Sx {O 'ԍ See Federal Communications Bar Association's Petition for Forbearance from section 310(d) of the Communications Act Regarding NonSubstantial Assignments of Licenses and Transfers of Control Involving  {O'Telecommunications Carriers Licensed by the Wireless Telecommunications Bureau, Memorandum Opinion and  {Oh'Order, 13 FCC Rcd. 6293 (1998), in which the Commission adopted streamlined notification procedures for pro  {O2 'forma transfers and assignments by telecommunications carriers.S Telecommunications carriers will be able to file notifications and provide the required licensing information directly into ULS on Form 603 so that  S'ULS can update its licensing records to reflect the pro forma transaction. 0  yOt#'ԍ Carriers filing notifications under this procedure will also be required to update Form 602 if they are subject to ownership reporting requirements and the information on Form 602 is not current."7 0*@%@%"Ԍ S'ԙt117. We have also updated the instructions on Form 603 regarding indirect alien ownership under section 310(b)(4) of the Act to elicit information regarding whether such ownership is held by aliens from countries making commitments to the WTO Basic Telecommuncations Agreement (WTO  S'Agreement)." \ {O'ԍ See Rules and Policies on Foreign Participation in the U.S. Telecommunications Market, IB Docket No.  {O'97-142, Report and Order and Order on Reconsideration, FCC 97-398, 12 FCC Rcd. 23,891,  97-118, 131 (1997)." Accordingly, we also revised the questions on Form 603 regarding alien ownership under section 310(b)(4) of the Act to elicit information regarding indirect ownership by aliens from countries making commitments under the WTO Agreement. The revised Form 603 also requires the transferee or assignee to certify that is in compliance with all pertinent crossownership, attribution, and spectrum cap rules, or has sought a waiver of such rules. Finally, in accordance with our new ownership reporting requirements for auctioned services, Form 603 will ask assignees/transferees in such services to certify that a current Form 602 is on file or that one is being filed simultaneously  Sp'with the Form 603.Q p {O 'ԍ See Section III.B.3, supra.Q   S 'u118.ؠ In the ULS Notice, we proposed to reinstate the consummation notification requirement  S 'for all PMRS licensees and microwave licensees which we had previously eliminated. $ ~ {O'ԍ ULS Notice at 9700,  66; see also, Reorganization and Revision of Parts 1, 2, 21, and 94 of the Rules to Establish a new Part 101 Governing Terrestrial Microwave Fixed Radio Services, WT Docket No. 94148,  {O'Report and Order, 11 FCC Rcd. 13449, 1345556 (1996), recon. pending (Part 101 Report and Order). See also 47 C.F.R.  90.153. In the absence of a notification procedure, no efficient mechanism exists for correcting the database under these circumstances. Instead, we have generally required the filing of a second transfer application that reflects the "return" of the license from the putative transferee to the original licensee. AirTouch opposes extending notification procedures to services such as PMRS or microwave that currently do not have them. Airtouch argues that this notification constitutes unnecessary reregulation of these  S 'services.A  j  yO'ԍ AirTouch Comments at 6.A The FCBA, AAR, and API support establishing a uniform notification procedure for all  S'wireless services including services such as PMRS and microwave.  yO|'ԍ FCBA Comments at 32 and Reply Comments at 22, AAR Comments at 10, API Reply Comments at 8.  S' v119.ؠ Our experience with assignments and transfers in those services that do not require postconsummation notification is that confusion and database errors have resulted when an approved transaction is not consummated. Restoring the notification requirement will ensure the integrity of the database and enable the Commission, licensees, and the public to accurately track ownership. Furthermore, licensees will no longer have to refile assignment or transfer applications with the required fee when a transaction has not been consummated. We also disagree with AirTouch that this notification constitutes unnecessary reregulation. The rationale for eliminating the notification"8 0*@%@%" requirement is no longer applicable under ULS. Licensees may provide notification in ULS almost  S'instantly for electronic filers completing FCC Form 603. Moreover, in the case of pro forma transfers and assignments that require no prior Commission approval under our forbearance order, notification  S'will be the only filing that is required.g\ {O'ԍ See Federal Communication's Bar Association's Petition for Forbearance from section 310(d) of the Communications Act Regarding NonSubstantial Assignments of Wireless and Transfers of Control Involving  {O'Telecommunications Carriers, Memorandum Opinion and Order, 13 FCC Rcd. 6293 (1998).g Thus, we find that imposing this requirement will not constitute a significant burden on licensees.  S' w120.ؠ While commenters generally expressed support for use of ULS to electronically file transfer and assignment applications, FCBA and API questioned how both parties to a transaction  S'would be able to enter information and electronically sign the form.Q yON 'ԍ FCBA Comments at 37, API Comments at 4.Q These commenters express concern that electronic filing could inadvertently enable a party to file a fraudulent assignment or transfer application without the knowledge of the current licensee. They point out that fraudulent applications have not been an issue in the past because transfer and assignment applications were filed manually, enabling both parties to certify their respective sections and sign the application before filing it with the Commission. To address the issue, API proposes that the Commission require a "comparison" electronic filing which could only be made by the assignor using the TIN and related  S 'password or through the submission of an original executed paper version of the electronic filing.> | yO'ԍ API Comments at 45.> The FCBA opposes API's proposal, but states that the Commission must address the issue if it intends  SZ'to allow electronic filing of transfer and assignment applications.DZ  yO'ԍ FCBA Reply Comments at 13.D  S 'x121.ؠ We agree with FCBA and API that safeguards are necessary to ensure that both parties to a transfer or assignment application can ensure the accuracy of information on electronically submitted forms. We also agree that neither party should be able to file a transfer or assignment form electronically without the knowledge and consent of the other. Assignment and transfer applications raise unique concerns in this respect because they are twoparty in nature and require the signature of both parties to the transaction. We are also aware that as a practical matter, one party (usually the assignee or transferee) often prepares the application for the other party to review and sign. In ULS, we have instituted several safeguards to protect against inaccurate or unauthorized filings. First, ULS will allow the assignee or transferee to access the portions of the application that contain information  S'regarding itself. yO!'ԍ If the assignee/transferee is not already registered in ULS, it will have to register its TIN and obtain a password in order to use the system. However, ULS will not allow the assignee or transferee to enter information into the assignor/transferor's section of the application, nor will it allow the assignee/transferee to designate"z9 0*@%@%"  S'the call signs that are the subject of the proposed transaction. yOh'ԍ Thus, a prospective assignee/transferee cannot unilaterally add a call sign that the assignor/transferor does not intend to include within the transaction. ULS will also enable each party to sign the application electronically, but will not allow either party access to the signature block of the other party. ULS will safeguard against modifications (by either party) after the application has been  S'signed by either party. Finally, ULS will safeguard against any party making modifications to the application after it has been signed by either party.  S'y122.ؠ We believe that the above safeguards will provide both parties with the same comfort and security afforded in the paper filing of transfer and assignment applications, and will ensure compliance with the Commission's rules. In addition, as in the case of other types of applications, ULS will allow assignment and transfer applicants to print preview their applications in draft, so that both parties can review and verify their responses before filing, and without the draft applications being viewable by the Commission staff or the public. Thus, while electronic filing of transfer and assignment applications may require some adjustment by the parties to such transactions, we believe that electronic filing will prove to be easy and efficient. We will issue a public notice describing in greater detail the procedures for using ULS when filing an assignment or transfer application. We also intend to conduct demonstrations for the public and the communications bar.  S0' 9. Change to North American Datum 83 Coordinate Data  S' z123. DATUM83  Background. To perform its licensing role, the Wireless Bureau requires that certain applicants and licensees submit site coordinate data (latitude and longitude) with their applications. Presently, applicants and licensees are required by the Commission's rules to submit coordinate data referenced to the North American Datum of 1927 (NAD27). The more recent North American Datum of 1983 (NAD83) was defined using modern surveying technology and in many cases provides a more accurate method of specifying coordinates. As a result, many applicants and licensees, at their option, provide NAD83 coordinate data with their applications today. On September 1, 1992, we issued a  S'public notice noting the change and stating that we would be converting our databases to NAD83.  {O'ԍ Public Notice, The Federal Communications Commission Continues to Require Applicants to Use Coordinates Based on the North American Datum of 1927, 7 FCC Rcd. 6096 (1992). On September 15, 1992, the Commissions Office of Engineering and Technology held a tutorial on  Sx'converting from NAD27 to NAD83.xz yO'ԍ "North American Datum Geographical Coordinate System Tutorial," DA 911195, 57 FR 41937 (September 14, 1992). However, we allowed applicants and licensees to continue submitting data in NAD27 until the Commissions databases could be converted. "(:0*@%@%q"Ԍ S'{124. On October 15, 1992, the Federal Aviation Administration (FAA) converted all  S'coordinate data associated with the National Airspace System to NAD83. yO@'ԍ "Transition From the North American Datum of 1927 (NAD27) to the North American Datum of 1983 (NAD83)," 57 FR 20141 (May 11, 1992). At the same time, it began requiring applicants and licensees notifying the FAA of proposed constructions (over 200 feet above ground or near an airport) to submit data in NAD83. For years, tower owners have been required to submit NAD83 data to the FAA and NAD27 data to the Commission. Because of this  S8'inconsistency and the benefits of using the more accurate NAD83 data, we proposed in the ULS Notice to require applicants and licensees in all wireless services to submit NAD83 data. We sought  S'comment on this proposal.L  {O 'ԍ ULS Notice at 9701,  70.L  S'|125. Discussion. Commenters addressing this issue overwhelmingly support our proposal to  Sr'transition from NAD27 to NAD83 site data.r yO'ԍ BellSouth Comments at 19; BAM Comments at 14; CenturyTel Comments at 7; and Nextel Comments at 8. As the commenters point out, this action unifies FAA and the Commissions requirements for the submission of site data, while taking advantage of the more accurate NAD83 reference datum. Thus, we will adopt a policy implementing NAD83 for all  S 'wireless services in a uniform manner. Beginning six months from the effective date of this Report  S 'and Order, we will require coordinates submitted to the Wireless Bureau regarding sites located in the continental United States, Puerto Rico, the U.S. Virgin Islands, Alaska, Hawaii, Guam, American Samoa, and offshore sites adjacent to these areas (e.g., the Gulf of Mexico) to be expressed in terms  S^'of latitude and longitude referenced to NAD83. X^  yO'ԍ During the transition period, applicants or licensees may submit coordinates in NAD27 or NAD83 manually using non-ULS forms. Applicants and licensees filing electronically via ULS, however, must submit coordinates in NAD83.  Sites located in the Northern Mariana Islands, Midway Island, and Wake Island should continue to be referenced to the applicable local datums. This exception for the Pacific insular areas is necessary because NAD83 is not applicable to these areas.  S'}126. Appendix D explains how licensees may use the National Oceanic and Atmospheric Administration, National Geodetic Survey's (NOAA/NGS) "NADCON" software to convert  SF'coordinates from NAD27 and other local datums to NAD83.LF*  {O 'ԍ See Appendix D, infra.L NADCON is available free of charge  S'via the Internet.  yOz"'ԍ The NADCON software is available for downloading via the internet at http://www.fcc.gov/wtb/uls. The NADCON software allows for the conversion of coordinates interactively one at a time, as well as the conversion of entire databases of coordinates by using an input data file. As an added measure of convenience for our licensees, the Wireless Bureau is in the process of providing";L 0*@%@%>" a web browserbased NADCON interface and investigating the possibility of including the NADCON conversion as part of ULS functionality. The Wireless Bureau will announce the release of these conversion tools by future public notices as they become available.  S`'~127.ؠ When implementing the transition to NAD83, FCBA urges the Commission to deal  S8'carefully with the rounding of converted data.>8 yO'ԍ FCBA Comments at 42.> We agree with FCBA and have devised a conversion approach that will not result in discrepancies due to rounding errors. Presently, site data is stored in the Wireless Bureau's databases referenced to NAD27 and rounded to the nearest second. The NADCON software will convert NAD27 data and provide results in terms of several decimal places. To avoid further rounding errors, we will convert existing databases using NADCON and store the resulting seconds of latitude and longitude in terms of two decimal places. Coordinates will be viewable online up to one decimal place. We take this opportunity to clarify that we are not requiring applicants or licensees to resurvey sites or conduct initial sites surveys in order to submit data accurate to the first or second decimal place. As in the past, applicants and licensees should determine site coordinates to the accuracy required by the applicable radio service rules and round the seconds of  S 'latitude and longitude consistent with the particular method of measurement being used (e.g., 7.5 = map, handheld GPS receiver, GPS receive with differential corrections).  S2'128. We also agree with suggestions by CenturyTel, Comsearch, and Radiofone to provide a transition period during which applicants and licensees may submit data referenced either to NAD27  S'or NAD83.yX yO'ԍ CenturyTel Comments at 7; Comsearch Comments at 5; and Radiofone Comments at 6.y We believe, however, that a sixmonth transition period is more appropriate than the oneyear transition suggested by some of the commenters. As a threshold matter, many licensees already submit coordinates on FCC Form 600 referenced to both NAD27 and NAD83. As the commenters point out, the FAA already requires submission of coordinates on FAA Form 74601 (notification of FAA for air safety purposes) in NAD83. Thus, structures over 200 feet above ground or located near a commercial use airport are already converted by applicants and licensees in order to meet FAA filing requirements. Further, the NAD83 conversion is not a difficult process. As described above and in Appendix D, the conversion of site data to NAD83 can be achieved by using the NADCON software and can be easily applied on a case by case basis, or to large databases. Prolonging the transition period would only serve to delay implementation of the more accurate datum and the benefits of unifying our requirements with those of the FAA. Applicants and licensees submitting NAD27 coordinates during the six-month transition can only do so manually using  S'non-ULS forms. yO 'ԍ The ULS forms, as approved by OMB, do not provide for the submission of data in NAD27 and it is not practical to reprogram the ULS and revise the forms for a short, six-month transition period. Consequently, the Commission's staff entering the non-ULS forms and converting from NAD27 to NAD83 may result in processing delays. For this reason, we urge applicants and licensees to convert their licensing records to NAD83 as soon as possible. "<@0*@%@%"Ԍ S'129. At the same time the Wireless Bureau is requiring applicants and licensees to convert to NAD83, the Wireless Bureau must convert all site coordinates in each of its databases from NAD27 (or local datums) to NAD83. We disagree with the commenters' recommendation to convert all of the  S'Wireless Bureau's databases at the same time.Y  yO'ԍ Nextel Comments at 8; CenturyTel Comments at 7.Y We have chosen to implement ULS on a servicebyservice basis and have already implemented the Paging and Radiotelephone Service and Offshore Radiotelephone Service with others to follow in the coming months. In this connection, we are converting to NAD83 at the same time we are converting each of our databases to ULS. This approach minimizes the number of programming resources necessary for conversion to ULS. Further, because we are providing a sixmonth transition period, licensees have the option to continue filing in NAD27 until all radio services have been converted to ULS. During the transition period, the Commission will convert data submitted in NAD27 to NAD83.  S '130.ؠAlthough the conversion to NAD83 does not involve the physical relocation of any tower sites, there may be instances when the distance between neighboring sites may appear to change when NAD83 is used. Several commenters ask that we grandfather licensees that may appear to be shortspaced as a result of the mathematical conversion, and that the conversion should not initiate  S 'finders preference or license revocation proceedings.! X yOx'ԍ PCIA Comments at 11; SBC Comments at 15; API Reply Comments at 910; and SBT Reply Comments at 13. Over a small geographic area, the conversion to NAD83 will affect neighboring sites in the same way, so the calculated distances between these sites will effectively remain constant. When sites are separated by large distances, however, site  S4coordinates will be #&n6X@DQ &@#"# &J\  P6Qu&P#shifted#&n6X@DQ &@#"# &J\  P6Qu&P# by different amounts based on local geography, and thus, the calculated distances between these sites may appear to decrease. This effect will be most prominent in the western United States, Alaska, Hawaii, and the Caribbean. Again, this is not a result of the relocation of tower sites, but rather the more precise determination of site coordinates. We agree with the commenters that, in cases where stations appear to be "shortspaced" under the rules as a result of the conversion, licensees may continue to operate under their existing authorizations indefinitely. This approach minimizes the number of programming resources while permitting the continued operation of existing stations. Further, we clarify that we do not intend to take any form of enforcement action in this regard based solely on the NAD83 conversion.  Sx'131. As a final matter, we agree with FCBA that the NAD83 conversion policies developed  SP'for our licensing databases should also apply to our Antenna Registration database.>"P yO'ԍ FCBA Comments at 42.> Presently, FCC Form 854 "Application for Antenna Structure Registration" permits tower owners to specify site coordinates referenced to NAD27 or NAD83 and stores the data in NAD27. Upon implementation of ULS, we will require tower owners applying for registrations to submit site data in NAD83. This approach provides for the consistent treatment of all applicants and licensees submitting site data to the Wireless Bureau."=@"0*@%@%"Ԍ  S' 10. Use of Taxpayer Identification Numbers  S'132.  TINS  Background. In 1996, Congress enacted the Debt Collection Improvement Act  S`'(DCIA),#` {O'ԍ See the Debt Collection Improvement Act of 1996, PL 104134, 110 Stat. 1321 (1996) (codified at 31 U.S.C.  3701). as part of an effort to increase the government's effectiveness in collecting debt from  S8'private entities. The DCIA requires, inter alia, that each federal agency collect the Taxpayer  S'Identification Number (TIN) of any person doing business with that agency. The TIN for an individual is generally that person's Social Security Number, while entities use a Tax Identification  S'Number or Employer Identification Number.$" yO 'ԍ As used herein "Taxpayer Identification Number" or "TIN" refers to all of these types of numbers. This information is shared with the U.S. Department of Treasury, as required by the DCIA.  SJ ' 133.ؠ Pursuant to its responsibility under the DCIA, the Commission has already begun to collect TIN information from Commission licensees. We also require auction applicants to provide  S 'their TINs with their shortform applications. In the ULS Notice, we further proposed to require that all applicants and licensees filing applications in ULS be required to register their TINs as a  S 'prerequisite to using the system.L%  {O'ԍ ULS Notice at 9702,  73 L We also sought comment on the suitability of the TIN as a unique system identifier for each applicant and licensee in ULS. In addition we proposed steps to prevent unauthorized disclosure or misuse of TIN information. We sought comment on these proposals.  S ' 134.ؠ Discussion. We received comments regarding a variety of issues relating to the use of TINs in ULS. Some commenters question whether the TIN can serve effectively as a unique system identifier. They note that some governmental and private entities have a single TIN that is used by multiple subagencies or subsidiaries which may hold licenses in their own name. Thus, use of the "parent" TIN could generate confusion and processing complications due to several entities using the  SD'same number.?&DD yO('ԍ AASHTO Comments at 7.? These commenters propose that we program ULS so that additional numbers or letters could be added to the basic TIN to identify subagencies or subsidiaries. We agree that a need for more discrete identification of government agency and large private entity filers exists. We are therefore developing a protocol in ULS that will allow an applicant or licensee to obtain a unique "subgroup" identifying number as an extension of its TIN. Thus, entities with a common TIN belonging to the parent agency or entity will be uniquely identified in ULS by different subgroup identifiers.  S' 135.ؠ Some commenters, particularly Amateur radio operators, argue that being required to disclose their TINs raises privacy concerns and assert that collecting TINs is unnecessary to our">&0*@%@%"  S'regulatory goals.' {Oh'ԍ See ARL Comments at 1617 (contending they are nonfeeable service and not subject to DCIA). Commenters also question whether ULS will contain sufficient security measures  S'to protect against disclosure of TIN information.^( Z yO'ԍ ARRL Comments at 1617; Bennet Comments at 7; FCBA Comments at 15 (proposing applicants and licensees to use user names and passwords in addition to TINs and associated passwords); FIT Comments at 1718; PCIA Comments at 9; NSMA Comments at 1011 (suggesting TINs be used for only those owed a fee refund).^ Conversely, some commenters note that there is no reason to protect the TINs of publiclyheld corporations, which must disclose this information in any  S'event for compliance with tax collecting requirements.P)B yOj 'ԍ Brown & Schwaninger Comments at 1011.P NSMA is concerned with providing any  S`'party outside the Commission with TINs, including frequency coordinators and test examiners.>*` yO 'ԍ NSMA Comments at 10.>  S' 136. With regard to the general security of TIN information in our database, we have already initiated steps to ensure security in access to ULS. Access to ULS for drafting, filing, or amending applications or pleadings is obtained using a secure widearea network (WAN) site. Each applicant or licensee's prefiled draft applications, forms, or pleadings will be protected by two levels of security: the applicant's or licensee's TIN and a unique selfassigned password. TIN information is not available to either the public or Commission staff through ULS. Instead, only a small number of Commission staff will have access to such data in order to effect necessary compliance with the DCIA. For public access purposes, ULS will issue each licensee a "masking" number that identifies it in the publicly available database. The "masking" or public ID number will be used for querying and for other purposes where revelation of the TIN could affect the applicant's or licensee's security concerns.  SX'137.ؠ With regard to use of or access to the TIN by frequency coordinators and VECs, we are aware that these entities are not comfortable with the responsibility of maintaining security for their individual clients' TINs. We agree this concern has merit. Accordingly, we are developing the capability for VECs and frequency coordinators to submit applicant information into ULS without having access to the applicant's TIN. Because the coordinators and VECs are Commissioncertified and carry out quasipublic responsibilities, we will provide each VEC and frequency coordinator with its own secure code giving it access to the relevant portions of the database. The coordinator will then be able to use its own access code, in combination with the public identification number of the applicant, to electronically file on the applicant's behalf. We emphasize, however, that in order for the coordinator or VEC to file on behalf of an applicant, the applicant must previously have registered its TIN in ULS.  Sx' 138. #&a\  P6G;u&P#Certain commenters question our authority to collect TIN information at all,  SP'particularly from applicants and licensees who do not pay fees.y+Pb  {OR$'ԍ See ARRL Comments at 1617; Bennet Comments at 8; FCBA Comments at 3031.y The DCIA subjects all those "doing"P? +0*@%@%" business" before a Federal agency to provide a TIN as a condition to receiving governmental benefits,  S'regardless of whether fees are collected.N, {O@'ԍ See 31 U.S.C.  7701(c)(1).N The DCIA defines a person "doing business with a Federal Agency" as "an applicant for, or recipient of, a Federal license, permit, rightofway, grant, or benefit  S'payment administered by the agency. . .."Q-Z {O'ԍ See 31 U.S.C.  7701(c)(2)(B).Q Thus, the statute makes plain that all applicants and licensees are "doing business with a Federal agency" and thus must provide their TINs. The statute does not distinguish between licensees and applicants who pay fees and those who do not, or otherwise exclude applicants and licensees who do not pay fees from the definition of "doing business" and the accompanying obligation to provide their TINs. Therefore, nonfeeable services such as most amateur and other public safety entities are still required to register their TINs with the Commission.  Sp' 139.ؠ Bennet maintains that those "doing business" with the Commission, as defined in the  SH 'DCIA, does not include minority interest holders.A.H  yO'ԍ Bennet Comments at 78.A Further, FCBA contends that the DCIA requires only applicants and licensees to provide TINs, and not those entities with a 10 percent or greater  S 'interest.A/ | yO'ԍ FCBA Comments at 3031.A FCBA argues that applicants and licensees are the ones enjoying the government benefits  S 'of a Commission license, and not attributable interest holders.30  {O|'ԍ  Id.3 We disagree with these contentions. One of the overarching purposes behind the DCIA is to improve the cash and debt collection  S 'management of the Federal Government.e1b  yO'ԍ The Debt Collection Improvement Act of 1996 has seven purposes: 1) to maximize collections of delinquent debts owed to the Government by ensuring quick action to enforce recovery of debts and the use of all appropriate collection tools; 2) to minimize the costs of debt collection by consolidating related functions and activities and utilizing interagency teams; 3) to reduce losses arising from debt management activities by requiring proper screening of potential borrowers, aggressive monitoring of all accounts, and sharing of information within and among Federal agencies; 4) to ensure that the public is fully informed of the Federal Government's debt collection policies and that debtors are cognizant of their obligations to repay amounts owed to the Federal Government; 5) to ensure that debtors have all appropriate due process rights, including the ability to verify, challenge, and compromise claims, and access to administrative appeals procedures which are both reasonable and protect the interests of the United States; 6) to encourage agencies, when appropriate, to sell delinquent debt, particularly debts with underlying collateral; 7) to rely on the experience and expertise of  {OV 'private sector professionals to provide debt collection services to Federal agencies. See 31 U.S.C.  3701. e In order to identify debtors, Congress decided to use TINs, a ubiquitous identifier. It is the Commission's responsibility to ensure compliance with the DCIA. In order for the Commission to comply, we must collect TINs from all individuals or entities"0@10*@%@%"  S'"doing business" with us.2 {Oh'ԍ See 31 U.S.C.  7701(c)(1); see also "Frequently Asked Questions About the Debt Collection Improvement Act of 1996 (updated Feb. 10, 1998) < http://www.fms.treas.gov/debt/dmfaq.html#TINs> . Under the DCIA, "doing business" before an agency is defined as "...an  S'applicant for or recipient of a Federal license, ..."T3" {O'ԍ See 31 U.S.C.  7701(c)(1)(2)(B).T Therefore, we consider those with attributable interests under section 1.2112 of the Commission's Rules as being "applicant[s] for, or recipient[s] of,  S'a Federal license. . . " for purposes of the DCIA.J4 {O'ԍ See 47 C.F.R.  1.2112.J We believe that entities subject to the disclosure requirements of section 1.2112 entities from whom we require submission of ownership information regarding their relationship with the applicant of record are components of the applicant and thus constitute "an applicant for, or recipient of, a Federal license . . . ." In short, if an entity holds an interest level that necessitates disclosure under section 1.2112, we believe that entity holds a level of  S'interest that justifies recognition as an "applicant" for purposes of the DCIA.5F yO'ԍ We clarify that only those applicants and licensees required to file a Form 602 need to provide the  {On'detailed ownership information under  1.2112. See Section III.B.3., supra. Moreover, considering such an interest holder as an applicant for purposes of the DCIA is consistent with our decision in the  Sp'Part 1 Third Report and Order that any interest holder subject to the disclosure requirements of  SJ 'section 1.2112 must be treated as akin to an "applicant."6$J  yO'ԍ In addressing the term "applicant" and the scope of disclosure requirements which are now in Form 602, we stated "[a] 10 percent or greater interest reporting requirement is consistent with the revised definition of the  {O'term 'applicant' we adopt for...the anticollusion rule..." Part 1 Third Report and Order, 13 FCC Rcd. at 419,  {O' 75; see 47 C.F.R.  1.2105(c)(6)(i).   S '140. Moreover, an entity with an attributable interest in a Commission license undoubtedly enjoys a public benefit and thus constitutes an "applicant for, or recipient of," the license. In fact, the Treasury Department clearly states "providing a TIN has now become a condition of receiving a  S '[Federal] benefit."7  yO'ԍ Frequently Asked Questions About the Debt Collection Improvement Act of 1996 (updated Feb. 10, 1998) . We disagree with those commenters who argue that only the named applicant or licensee reaps the benefits of a license. In reality, all those investing in an applicant's business plan enjoy the financial and public interest benefits of a license. To that end, we treat all individuals or entities with a 10 percent or greater interest in an applicant or licensee as component members of the "applicant."  S'141. Therefore, for the purposes of implementing the ULS system, based upon the foregoing discussion and applicable statutes and regulations, the requirement for the TIN will operate as follows: "BA70*@%@%"Ԍ All applicants for licenses and all licensees must register their TIN with this Commission through ULS.  S' The real party in interest and/or the entity having actual/de facto control of any applicant or licensee, however such control may manifested or styled, must supply its TIN.  Applicants and licensees who must identify officers, directors, and holders of ownership interests in the license of 10 percent or greater pursuant to section 1.2112(a) must supply the TINs of  S'such officers, directors, interest holders.M8 {O* 'ԍ See 47 C.F.R.  1.2112. M  Sr'142. Finally, we note that members of the general public seeking access to the ULS system  SJ 'for queries or research, as contemplated in the ULS Notice, will not be required to provide a TIN to obtain access to ULS. Third parties seeking to file pleadings in a pending matter need not provide a TIN to file the pleading, but such parties at their option, will be able to utilize a password or identifier  S 'chosen by them.T9 Z {O'ԍ ULS Notice at 97023,  735.T  S\' C. Collection of Licensing and Technical Data  S ' 1. Overview ` `  S'143.ؠ DATAVIEW  Background. In conjunction with the development of the ULS, we have conducted a thorough review of our current data collection and licensing functions to identify those requirements  Sl'which can be streamlined. As a general matter, in the ULS Notice we tentatively concluded that it would serve the public interest to equalize, as much as possible, the reporting burden on geographic area licensees in order to treat similarly situated licensees in a consistent manner and to allow us to  S'more effectively collect the data we need to fulfill our statutory mandates.X: {O'ԍ ULS Notice at 9704,  789.X We sought comment on what reporting requirements, both technical and nontechnical, should be established for geographic  S'area licensees.4;~ {O'ԍ Id. 4  SV'144.ؠ Several commenters argue that the Commission should collect additional technical information from geographic licensees for coordination purposes. FCBA argues that technical data reporting requirements for geographic area licensees will aid coordination with adjacent market licensees and are needed to facilitate licensing in services that are licensed both on a geographic and a"B;0*@%@%"  S'sitebysite basis.A< yOh'ԍ FCBA Comments at 2122.A FIT supports the continued collection of technical information from licensees in the VHF bands in order to allow the forest products industry to obtain sufficient information to coordinate mobile and fixed relay stations, and suggests that required information should include the  S'location of fixed or base stations, ERP, antenna height, and emission strength.@=X yO'ԍ FIT Comments at 1819.@ Other parties who commented on this issue argue that certain reporting requirements applicable to geographic licensees should be eliminated or modified to make reporting requirements consistent across services. For example, some LMDS commenters specifically supported our proposed elimination of requirements that they report type acceptance number, line loss, channel capacity, and baseband signal type under  S'Part 101.> yOH 'ԍ WNP Comments at 15 (supporting the Commission's general conclusion); BellSouth Comments at 25.  Sp'145.ؠ Discussion. We remain convinced that it serves the public interest to streamline our rules to minimize and standardize the technical reporting requirements for geographic area licensees as much as possible. For example, as several commenters point out, our rules contain inconsistent requirements with respect to the obligation of geographic area licensees to provide the Commission with information regarding the location and technical characteristics of individual transmitter sites. WNP Communications and Winstar Communications point out that LMDS licensees must notify the Commission of the "addition, removal, or relocation of" all facilities within their geographic service  SX'areas.?Xx {Op'ԍ WNP Comments at 15; Winstar Reply Comments at 23. See 47 C.F.R.  101.61(c)(10), 101.1009(b). Similar provisions are also contained in our 800 MHz SMR and 220 MHz geographic  S0'licensing rules.R@0  {O'ԍ See 47 CFR  90.683, 90.763R By contrast, commenters point out that in other geographically licensed services, such as 39 GHz, geographic licensees are not required to provide this type of site information to the  S'Commission.^A {O'ԍ See, e.g., 47 C.F.R.  101.149.^  S'146. We agree that our notification requirements for LMDS, 800 MHz, and 220 MHz geographic licensees are inconsistent with our rules for other geographically licensed services. The notification requirements in these services were intended to facilitate coordination and prevent interference between geographic licensees and sitebased incumbents operating on the same frequencies  S'in the same licensing areas who had been grandfathered prior to geographic licensing.qB^.  {O!'ԍ See, e.g., Amendment of Part 90 of the Commission's Rules to Facilitate Future Development of SMR  {O"'Systems in the 800 MHz Frequency Band, First Report and Order, Eighth Report and Order, and Further Notice  {OR#'of Proposed Rulemaking, 11 FCC Rcd. 1463 (1995),  52. q However, requiring geographic licensees to file notifications of every new, relocated, or removed site in a multi"CT B0*@%@%K"ԫsite system imposes a significant filing burden of the very type that geographic licensing was designed to mitigate. In addition, we have not adopted this approach in other geographically licensed services that also have sitebased incumbent licensees, such as paging, 900 MHz SMR, and 39 GHz.  S`'147. We also conclude that for the Commission to collect site data from geographic licensees through a notification process is not necessary to achieve the public interest goals we have identified, and that less burdensome requirements will serve the same purpose as effectively. First, in all of these services, our rules impose technical limitations on the operations of geographic licensees in order to afford interference protection to incumbent facilities. Second, while collecting site information may be helpful to coordination between geographic licensees and incumbents to prevent interference, it is not a substitute for actual coordination between the licensees themselves. Even without such technical information, the Commissions database will contain sufficient information to ensure that neighboring operators can identify the licensees with whom they must coordinate, rather than requiring all operators to maintain updated, detailed information with the FCC for full coordination analysis. This places the primary responsibility for coordination in geographically licensed services on the licensees themselves, where we believe it should be. It also reduces the regulatory burden on licensees. Standardizing the information required across all services which license by geographic service area will allow consistent treatment of licensees in similar situations.  S'148. Accordingly, we will remove the site notification requirement from Part 101 for LMDS geographic licensees, as well as from the Part 90 rules pertaining to auctioned 220 MHz and 800 MHz geographic licenses. Our conclusion here is in accord with our treatment of PCS, 900 MHz SMR, paging, 39 GHz,and other microwave services that are we have auctioned or plan to auction based on geographic areas. We will instead require geographic licensees to maintain site information as part of their station records and to provide it to incumbents and the public on request. Moreover, if an interference issue arises between a geographic licensee and a sitebased incumbent, we have the authority under section 308 of the Act to compel production of site location information by the geographic licensee as needed. While we eliminate the above notification requirements, however, we emphasize that there continue to be circumstances where collecting individual site data is necessary. Therefore, we continue to require all licensees, including geographic service area licensees, to comply with existing procedures for environmental, quiet zone, and FAA approval of specific antenna sites where required by our service rules.  S'149.ؠ In the ULS Notice we tentatively concluded that, at a minimum, applicants for geographic area licenses in the wireless telecommunications services should provide technical information when proposed antenna structures are more than 200 feet above ground or are located near an airport. FCBA objects to this proposal to the extent that it proposes anything greater than the  S:'Commission's current antenna structure registration requirements.AC: yO!'ԍ FCBA Comments at 2122.A We did not propose to increase our antenna structure registration requirements. Instead, we proposed to retain FCC Form 854 in its" DXC0*@%@%"  S'current format, and moreover, we did not propose to amend Part 17 of our Rules.VD {Oh'ԍ ULS Notice at 9704,  78 and n.126.V Our current Part 17 requirements ensure that Commissionregistered structures do not create safety hazards. Consistent, with the goals of this proceeding, we will not require applicants or licensees to provide technical data for FAAapproved sites, except for major modifications, as described in section 1.929. We also note commenters' suggestion that we not consider the location of a facility in a floodplain to be a major  S8'action requiring an environmental assessment.DE8Z yO2'ԍ GTE Reply Comments at 67.D Because this proceeding does not affect our statutory requirements under the National Environmental Protection Act (NEPA), we believe that it is necessary for geographic area licenses to continue to comply with all aspects of our NEPA rules, and we will not adopt this suggestion.  Sp'150.ؠ Once ULS is fully implemented, we will further review our data collection requirements to identify other aspects that may be unnecessary. For example, BellSouth questions the need for  S 'cellular licensees to continue to file maps in light of the mapping feature of ULS.[F  yO'ԍ BellSouth Comments at 7; Airtouch Comments at 10.[ Eventually, the mapping utility included with ULS may eliminate the need to collect maps of cellular geographic service areas (CGSAs) and display service areas of site-based licensees. Implementation of the mapping utility for the cellular service, however, requires the integration of licensee-submitted System Information Update (SIU) maps into ULS. At such time as the SIU maps are fully integrated into ULS, we will revisit this issue with the intention of eliminating the requirement to file maps. For  S0'now, we will continue to collect this information from cellular licensees.KG0z {OJ'ԍ See  1.929, Appendix G.K We delegate authority to the Wireless Bureau to determine the proper time for the elimination of this requirement.  S' 2. Use of Notification or Certification in Lieu of Informational Filings  Sh'  S@'151.NOTIFICATIONנ Background. We proposed to replace informational filings with notification or certification to best utilize the electronic filing system, reduce applicant and licensee burdens and  S'increase efficiency within the Wireless Bureau.LH  {O'ԍ ULS Notice at 9705,  80.L In some cases where there is an informational or other data requirement, we proposed to use certifications or notifications by the applicant or licensee  S'instead. The proposed rule sections in the ULS Notice appendices contained the new certification or  S|'notification procedures, as do the proposed forms and schedules.4I| {O"'ԍ Id. 4 An example of a new certification requirement in lieu of an information filing requirement is in proposed section 101.701, which requires common carrier fixed microwave licensees to certify that substantial nonprivate use is being made of",E0 I0*@%@%" facilities used to relay broadcast television signals. An example of a new notification requirement in lieu of an informational filing is in proposed section 101.305, where nondominant common carriers planning to discontinue service must give electronic notification of discontinuance to the Commission. We requested comments on these proposals.  S8'152.ؠ Discussion. Four parties commented on our proposals. Of the four comments received, each supports the Commission's conclusion that electronic filings via notification or certification  S'would reduce licensee burdens and enable more efficient operations.J yOR'ԍ AASHTO Comments at 7; FCBA Comments at 22; FIT Comments at 19; Nextel Comments at 9.  We conclude that use of the notification and certification processes will substantially reduce the administrative burdens on the Commission and the filing burdens on applicants and licensees. However, we caution applicants and licensees that they must be prepared to provide the underlying information upon which their notification or certification depends, upon Commission request. Accordingly, we find that the proposed rules dispensing with informational filings, and replacing them with certifications or notifications, are in the public interest.  S ' 3. Public Mobile Radio Service Data Requirements  S2'153.PUBLICMOBILE Background. In the ULS Notice, we proposed eliminating the requirement for certain Public Mobile Radio Service applicants and licensees to file antenna model, manufacturer, and type  S'with the Commission.PKX {O'ԍ See 47 C.F.R.  22.529(b)(3).P We stated that we could eliminate this information since we fundamentally  S'altered the method for determining service contours and CGSAsLX yOF'ԍ Amendment of Part 22 of the Commission's Rules to Provide Filing and Processing of Applications for Unserved Areas in the Cellular Service and to Modify Other Cellular Rules, CC Docket No. 906, 8 FCC Rcd. 1363 (1993). in the paging and radio telephone  S'service.M  {O>'Ѝ ULS Notice at 9705,  82; see also, Revision of Part 22 of the Commission's Rules Governing the Public  {O'Mobile Services, Report and Order, 9 FCC Rcd. 6513 (1994) (Part 22 Rewrite).   SD'154. We also proposed to eliminate the requirement that unserved area applicants in the Cellular Radiotelephone Service submit paper copies of: (a) an application cover, (b) transmittal sheet,  S'(c) table of contents, and (d) numerous engineering exhibits.JNf  {O 'ԍ See 47 C.F.R.  22.953.J We believed these paper copy requirements are inconsistent with our proposal to require electronic filing by cellular applicants and"F N0*@%@%>"  S'proposed to eliminate this requirement for cellular unserved applicants.LO {Oh'ԍ ULS Notice at 9706,  83.L We requested comments on these proposals.  S'155.ؠ Discussion. The FCBA supported the elimination of technical antenna informationAPZ yO'ԍ FCBA Comments at 2223.A as well as the proposed elimination of certain formatting requirements for Cellular Radiotelephone Service unserved area applications. The FCBA agrees with the Commissions conclusion that such  S'requirements are superfluous,:Q {O 'ԍ Id. at 23.: inconsistent with an electronic filing environment,3R| {O, 'ԍ Id.3 and should thus  S'be eliminated when unserved area applications are filed electronically.;S {O'ԍ Id. at 23.;  S'156.ؠ There was some opposition to our proposal to eliminate the requirement for applicants or  Sp'licensees in the Part 22 mobile services to submit the make and model number of their antenna.Tp yO'ԍ CenturyTel Comments at 8; EEC Comments at 5; Metamora Comments at 5; PAI Comments at 5; Radiofone Comments at 7; Rinker Comments at 5. Commenters contend that knowledge of the antenna model is critical in making the determination of  S 'how the interference contour is formed, i.e., without antenna model information, the Commission and the public will be unable to determine whether the effective radiated power (ERP) listed for the eight cardinal bearings on Schedule J emanate from calculations using an appropriate antenna pattern  S 'showing an acceptable fronttoback ratio.U  yOB'ԍ EEC Comments at 6; CenturyTel Comments at 8; Metamora Comments at 67; PAI Comments at 67; Rinker Comments at 6. Commenters are concerned that without this information,  S 'carriers could mistakenly or unscrupulously encroach upon protected service areas,V P  yOr'ԍ CenturyTel Comments at 8; EEC Comments at 67; Rinker Comments at 6; Metamora Comments at 6; PAI Comments at 6. or render it impossible for Part 22 VHF/UHF paging licenses to comply with rule 22.537, which requires such licensees to provide contour protection to cochannel stations along the entire service contour, and not  S 'just at those points that coincide with the eight cardinal bearings.W  {OR!'ԍ EEC Comments at 6 citing RAM Mobile Communications of Colorado, Inc.,  4 FCC Rcd. 2384,  56 (MSD 1989); PAI Comments at 67; Metamora Comments at 67. Commenters also contend that this" GW0*@%@%" information is particularly important in Part 22 VHF/UHF paging because these stations have been  S'engineered to abut one another based upon contour protection.X yO@'ԍ EEC Comments at 6; Metamora Comments at 6 and n.3; PAI Comments at 6 and n.3; Rinker Comments at 6, n.3.  S'157.ؠ Commenters also expressed concern that FCC Form 601 will not provide enough information for an incumbent licensee on the lower band frequencies to modify its station and be sure  S8'that it is fully protected by the cochannel licensee auction winner.\Y8  yO'ԍ CenturyTel Comments at 8; Radiofone Comments at 7.\ Commenters believe the reduced antenna information may make it more difficult for the auction winner to ensure that an incumbent co S'channel licensee is staying within its authorized contours.\Z yO8 'ԍ CenturyTel Comments at 8; Radiofone Comments at 7.\ CenturyTel notes that Schedule J to Form 601 elicits information about the beam width of a directional antenna, as well as ERP and height above average terrain along the eight cardinal radials, but only for fixed stations and not base stations;  Sp'this information should also be required for base stations.C[p@ yOP'ԍ CenturyTel Comments at 8.C  S '158.ؠ AirTouch states that the proposed rules are unclear as to whether cellular applicants will  S 'continue to be required to file maps in connection with their applications.B\  yOh'ԍ AirTouch Comments at 10.B AirTouch states that the proposal retains section 22.929(c), which imposes a map filing requirement, but also proposes to  S 'eliminate section 22.953, which establishes the formatting requirements for such maps.3] `  {O'ԍ Id.3 AirTouch states that, because ULS is able to generate maps from licensee-provided information, it is unclear  SX'why the Commission would retain an additional requirement to submit maps.4^X  {O'ԍ Id. 4 We agree with the commenters that the requirement for cellular licensees to file maps should be eliminated as soon as possible. As we discussed above, this requirement must be retained for a short time so that cellular map data already on file with the Commission may be fully integrated with the ULS's mapping utility. We will revisit this issue in the near future when integration with the ULS mapping utility is completed.  S@'159.ؠ After evaluating our procedures and rules we find that we no longer need to collect and record technical antenna information nor do we need unserved area applicants in the Cellular Radiotelephone Service to submit the aforementioned paper exhibits. We therefore eliminate these requirements. However, we will require all licensees to maintain this information as part of their station records and to provide it to licensees and applicants upon request. Moreover, if an interference"H ^0*@%@%" issue arises, we have the authority under section 308 of the Act to compel production of antenna information.  S`' 4. Fixed Microwave Service Data Requirements  S'160.ؠFIXEDMICROנBackground. Effective August 1996, the Commission eliminated and combined many of the fixed microwave service rules of Parts 21 and 94 of the Commission's rules and consolidated the  S'remaining rules into a single, new Part 101.p_^ {O( 'ԍ See Reorganization and Revision of Parts 1, 2, 21, and 94 of the Rules to Establish a new Part 101  {O 'Governing Terrestrial Microwave Fixed Radio Services, WT Docket No. 94148, Report and Order, 11 FCC  {O 'Rcd. 13449 (1996), recon. pending (Part 101 Report and Order).p In the ULS Notice, the Commission proposed to further streamline the rules by eliminating the requirement that fixed microwave service applicants and licensees submit type acceptance number, line loss, channel capacity, and baseband signal type for  SJ 'each application.m`J  {O'ԍ ULS Notice at 9706,  84; see 47 C.F.R.  101.21.m We noted that as we place an increasing amount of responsibility for interference  S" 'coordination on the parties themselves,Na"  {OB'ԍ See 47 C.F.R.  101.103(d).N this information is not critical nor does it provide useful data  S 'in support of the Wireless Bureau's licensing processes.Lb  {O'ԍ ULS Notice at 9706,  84.L  S '161. Discussion. Commenters that addressed this issue express near unanimous support for  S 'the Commission's proposal.cX  yO'ԍ WNP Comments at 5; CellNet Comments at 7; BellSouth Comments at 25; API Comments at 15; Pathnet Comments at 5; Comsearch Comments at 6; FCBA Comments at 23; Nextel Comments at 9; SBC Comments at 14. Some of these commenters urge the Commission to go further and also eliminate other requirements. For example, the FCBA states that in light of the goal of collecting less data because licensees are increasingly responsible for interference coordination, the Commission should consider eliminating the filing of the following "extraneous" information: transmitter manufacturer name, digital modulation rate, digital modulation type, median receiver signal level,  S'antenna manufacturer name, and antenna model number.>d  yO'ԍ FCBA Comments at 23.> For the same reason, Comsearch suggests the Commission eliminate the requirement of listing the digital modulation type, because it has no  Sj'bearing on the technical merit of an application.BejT  yO^"'ԍ Comsearch Comments at 6.B NSMA, on the other hand, opposes the elimination of this technical data submission requirement for pointtopoint microwave service applicants to the"BIe0*@%@%"  S'extent that this information is necessary to "evaluate the interference environment.">f yOh'ԍ NSMA Comments at 10.> NSMA also suggests that the Commission require submission of received signal level (RSL) data with these  S'applications as it would be useful in interference studies.<gX {O'ԍ Id. at 910.<  S`'162. We adopt our proposal in the ULS Notice to eliminate the requirement that applicants and licensees include type acceptance number, line loss, channel capacity, and baseband signal type for each application. The overwhelming majority of commenters agree with our tentative conclusion that this information is not necessary for licensing purposes. As we conclude that reducing the burden on applicants and licensees is in the public interest, we decline to adopt NSMA's suggestion that we require RSL data to be submitted with applications. We are not convinced at this time, however, that we should eliminate the filing of other technical information as proposed by the FCBA and Comsearch.  S '163. Teligent proposes that the Commission modify section 101.5(b) of the Commission's  S 'rulesLh  {O\'ԍ See 47 C.F.R.  101.5(b).L to eliminate the requirement that DEMS licensees file a separate application for each new  S 'DEMS nodal station they seek to add to their systems.Ci | yO'ԍ Teligent Comments at 14.C Teligent states that this requirement is inconsistent with the requirements imposed on other similarly situated fixed wireless service licensees,  SZ'such as 38 GHz and LMDS licensees,\jZ  {O'ԍ See 47 C.F.R.  101.147(v), 101.1009.\ that are also licensed on a widearea basis and have exclusive  S2'use of their licensed frequencies in their geographic areas.Ck2 yOp'ԍ Teligent Comments at 23.C On the other hand, NSMA opposes Teligent's proposal on the grounds that because a DEMS licensee would not be able to conduct an interference evaluation for nodal stations in adjacent areas owned by another licensee, continued  S'frequency coordination for new stations is necessary to prevent interference problems.Cl.  yO'ԍ NSMA Reply Comments at 2.C Teligent also proposes that the Commission eliminate the corresponding requirements in sections 101.5(b) and 101.503 that a DEMS licensee apply for authority to serve a specific number of user stations for each  SB'separately licensed nodal station.FmB  yO!'ԍ Teligent Comments at 4, n.7.F We decline to adopt Teligent's proposals as part of this Report  S'and Order. The Commission has consistently upheld the DEMS service rules, and granted waivers where appropriate, and should changes in those rules be justified they will be made in a future proceeding. "JN m0*@%@%X"Ԍ S'ԙ164.ؠWinstar suggests that the Commission amend section 101.215Kn {Oh'ԍ See 47 C.F.R.  101.215.K to exempt Part 101  S'geographic area licensees from information posting requirements for customer stations,IoZ yO'ԍ Winstar Reply Comments at 910.I and modify section 101.149(b) to eliminate the specific requirement that 39 GHz licensees post a service area  S'authorization at each operating station.Hp yO'ԍ Winstar Reply Comments at 34.H It argues that these requirements are unduly burdensome for geographic area licensees that ultimately will maintain facilities at hundreds of customer sites in each  S8'city in which they provide service.@q8z yOR 'ԍ Winstar Comments at 9.@ For similar reasons, Winstar recommends that the Commission amend its rules to exempt Part 101 geographic area licensees from the station recordkeeping  S'requirements of section 101.217.dr  {O'ԍ Winstar Comments at 10. See 47 C.F.R.  101.217.d This Commission consistently maintains rules requiring that transmitter sites be identified with either the station authorization or with information indicating where  S'the station information can be found.`s {O'ԍ See, e.g., 47 C.F.R.  22.303, 24.415(j).` The Part 101 rules on this matter are found at 47 C.F.R.  101.215 and 101.149. We believe that availability of this information is important to ensure accountability of the licensee to the public. For example, a transmitter causing interference due to poor maintenance or accident can be found with directionfinding equipment, but without information regarding the owner/operator available at the site, an aggrieved party will not know who to contact for relief from the interference. This onsite information becomes even more important because elsewhere  S 'in this Report and Order we relieve licensees of the requirement to file the location of each of its transmitters with this Commission. Accordingly, we believe that the public interest in having an readily identifiable contact at each transmitter site outweighs the inconvenience to licensees. With regard to station record information required under section 101.217, we believe for similar reasons that this information is as important for geographic licensees as it is for sitebased licensees. It becomes even more important that licensees keep complete records of their transmitters because under ULS, this Commission will no longer collect that information unless it is necessary to review the information in connection with a complaint or other question regarding transmitter engineering. Accordingly, we decline to adopt Winstar's suggestions in this regard.  S' 5. Maritime and Aviation Services Data Requirements  S'165.ؠ SEASKY  Background. In the ULS Notice, we requested comment on whether the proposal to eliminate various rules that require attachments of showings and coordination statements could  S|'negatively affect the quality of maritime or aviation communications.Lt|.  {OJ$'ԍ ULS Notice at 9706,  85.L"|K t0*@%@%"Ԍ S'ԙ166.ؠ Discussion. The sole commenter to the proposed Aviation Services rule raised one objection. The Aerospace and Flight Test Radio Coordinating Council (AFTRCC) opposes the elimination of the independent statement by a frequency coordinator for flight test station  S'applicants.Au yO'ԍ AFTRCC Comments at 24.A Currently, section 87.305 of our rules requires a flight test station applicant to secure a statement from a frequency advisory committee that comments on the station's probability of  S8'interference with an existing station.v8X {O0'ԍ See 47 C.F.R.  87.305. Which provides requirements for the frequency advisory committees. AFTRCC suggests that the proposal to replace the independent  S'statement with a certification does not address the certainty required for aviation radio operations.?w yO 'ԍ AFTRCC Comments at 4.? While it is our intention to facilitate electronic filing and eliminate burdens upon applicants, we want to maintain maximum public safety. We have decided to continue to require the independent frequency coordinator statement for flight test station applicants.  SH '167.ؠ Maritime Services parties did not comment on our proposal to delete various showings and attachments currently required to be provided with applications in these services. Some showings were replaced with the requirement that applicants certify that they meet the rule requirements, other showings were replaced with the requirement that relevant information be available upon Commission request. We continue to believe that these streamlined application requirements fulfill our statutory responsibilities and reduce the regulatory burden on applicants and licensees. Accordingly, we adopt our proposals for the streamlined rule provisions in Part 80 of the Commission's rules.  S' 6. Commercial Radio Operator License Data Requirements  S'168.ؠCOMMERCIALOPRS Background. Currently, applicants seeking commercial radio operator licenses must pass one or more written examinations administered by a Commissioncertified Commercial Operator  S@'License Examination (COLE) Manager and obtain a proof of passing certificate (PPC). xZ@z yOZ'ԍ See, e.g., 47 C.F.R.  207211. No examination is required to obtain either the Restricted  {O"'Radiotelephone Operator Permit or the Restricted Radiotelephone Operator PermitLimited Use. See 47 C.F.R.  201(b).  Once the PPC is obtained, the applicant must then provide the original PPC to the Commission upon application  S'for a license.y yO, 'ԍ Each application for a new General Radiotelephone Operator License, Marine Radio Operator Permit, Radiotelegraph Operator's Certificate, Second Class Radiotelegraph Operator's Certificate, Third Class Radiotelegraph Operator's Certificate, Ship Radar Endorsement, Six Months Service Endorsement, GMDSS Radio Operator's License or GMDSS Radio Maintainer's License must be made on FCC Form 756. Each application for a Restricted Radiotelephone Operator's Permit must be made on FCC Form 753. Each application for a restricted Radio Telephone Permitlimited Use must be made on a FCC Form 755. 47 C.F.R. "$x0*@%@%$" 13.9.  In order to electronically automate the licensing procedures, we proposed three"LXy0*@%@%a"  S'options in the ULS Notice by which to electronically verify PPCs. We sought comments on whether COLE Managers should: (1) electronically file with the Commission data showing which examination elements an examinee has passed; (2) establish procedures that would allow COLE Managers issuing a PPC to verify the authenticity of that PPC, upon Commission request; or (3) require COLE Managers  Sb'to submit applications on behalf of the applicants.QzbX {OZ'ԍ ULS Notice at 97078,  8890.Q  Q:'  S'169.ؠ Discussion. We received little comment on the abovementioned proposals. Although the comments regarding electronic filing were positive, no commenter specifically addressed the option  S'proposed in the ULS Notice for electronically verifying PPCs. Further, no comments were received as to how the Commission should automate the application process. Therefore, we will adopt a rule that embodies our goals of electronic automation while best serving the public interest. With regard to a  SL 'first filing, a renewal, or a modification application, the applicant may use the current procedures.H{L  {O'ԍ See 47 C.F.R.  13.9.H Alternatively, the applicant may file electronically using FCC Form 605. For a new license, the applicant must file Form 605 and mail the PPC to the processing office in Gettysburg, Pennsylvania. For renewals, the applicant need only file Form 605, since no attachments are required. With respect to PPC verification by COLE Managers, the current procedures will remain intact. We are committed to ULS and electronic filing believing that these new rules will gradually phasein electronic filing while making the submission process less onerous for applicants and COLE Managers.  S '170. W5YI encouraged changes to the Temporary Operator Permit section in Schedule "D" of Form 605 by suggesting a perforated, tearoff part which the applicant could retain. We agree that this change will promote convenience and ease of use for the applicant and we will implement the proposed change in a future version of Form 605.  SD'171. We want to make it clear that in announcing the above rules, we are not mandating electronic filing for Commercial Radio Operators, rather we are strongly encouraging it in the belief that the public interest is best served by this practice. In addition, we will consider in a future proceeding more efficient methods of verifying PPCs other than manual submission.  ST' 7. Amateur Radio Services   S'172. AMATEUR נBackground. In the ULS Notice, we requested comment on whether we should authorize  S'reciprocal operation by foreign amateur radio operators by rule.L|| {O"'ԍ ULS Notice at 9708,  91.L Currently, in order to obtain an alien amateur reciprocal permit, the visitor must apply using FCC Form 610A. No test or other"M|0*@%@%" standard is required of these applicants other than that they possess a license from their country of citizenship. There is no fee. Accordingly, the FCCissued permit merely confirms that holders of such permits also hold a license from their country of citizenship and that the United States has a reciprocal treaty agreement with their country. Our proposal to authorize reciprocal operation by rule would eliminate the need for foreign citizens to file Form 610A and receive an additional permit from  S8'the U.S. In addition, in the ULS Notice we sought comment on whether the Commission should accept the services of any organizations for the purpose of providing Club, Military Recreation and Radio Amateur Civil Emergency Services (RACES) station call signs that meet the minimum requirements set forth in section 4(g)(3)(B) of the Communications Act, and that complete a pilot electronic autogrant batch filing project similar to that completed by the 16 VolunteerExaminer Coordinators (VECs).  S" '173. In an earlier proceeding, we had proposed to amend the Amateur Service Rules in order to facilitate implementation of two international reciprocal operating arrangements the European Conference of Postal and Telecommunications Administrations (CEPT) radioamateur license, and the InterAmerican Convention on an International Amateur Radio Permit (CITEL/Amateur  S 'Convention).}^  {O'#C\  P6QɒP#э See Amendment of the Amateur Service Rules to Authorize Visiting Foreign Amateur Operators to  {O'Operate Stations in the United States, Notice of Proposed Rule Making, WT Docket No. 96188, 11 FCC Rcd.  {O~'11768 (1996)(CEPT/CITEL NPRM).#Xx6X@DQ X@#ѣ Comments to the CEPT/CITEL NPRM indicate that these operating arrangements are desired by amateur operators who want to operate their stations during international travel without first  S4'obtaining a permit from each country visited.~4 yO'#C\  P6QɒP#э Twentytwo countries in Europe have implemented the CEPT agreement. Eight South American countries, Mexico and Honduras countries have implemented CITEL.  S'174. Discussion After reviewing the comments we have received to both the CEPT/CITEL  S'NPRM and the ULS Notice, we conclude that all alien amateur radio reciprocal operation should be authorized by rule. As we proposed, however, this decision does not permit any citizen of the United States to operate under this procedure on the authority of a second citizenship and an amateur license from another country. Our decision herein is supported by most commenters, who generally agree with the concept of authorization by rule of reciprocal operating privileges by persons holding a CEPT radioamateur license issued by a participating CEPT country, or an International Amateur Radio  S'Permit (IARP) issued under the authority of a participating CITEL country.F {O'ԍ See, e.g., AARL Comments at 2; Daniel Plett Comments at 1; Eric and Bonnie Hall Comments at 1; Nick Leggett Comments at 1; see also AARL Reply Comments at 10. Citizens of CEPT and CITEL countries that are visiting the United States as tourists, attendees at conferences, students and visiting professors, for example, would benefit from having a convenient procedure available whereby they could operate their amateur stations while here in the United States. Additionally, United States citizens who travel in Europe or in the Americas for short visits would similarly benefit. "N0*@%@%'"Ԍ S'175.ؠ In authorizing by rule CEPT licensees and CITEL licensees to operate from locations where the amateur service is regulated by the FCC, the Commission's rules also must specify the operating privileges granted and the station identification requirements. The operating privileges should be consistent with the two classes of CEPT radioamateur licenses, and IARPs. Class 1  S`'licenses require s knowledge of the international Morse code and carries all operating privileges. It is, therefore, similar to our Amateur Extra Class. Class 2 licenses do not require knowledge of telegraphy and carries all operating privileges above 30 MHz. A Class 2 license, therefore, is similar to our Technician Class operator license. Class 1 operators, therefore, are authorized the frequency privileges of Amateur Extra Class operators. Class 2 operators will receive the frequency privileges of Technician Class operators. For station identification purposes, when the station is transmitting under the authority of a CEPT radioamateur license, or an IARP, an indicator consisting of the appropriate letternumeral designating the station location must be included before, after, or both before and after, the call sign issued to the station by the licensing country.  S '176. For a United States citizens to operate an amateur station in a CEPT country, certain requirements of the CEPT European Radio Committee (ERC) must be met for participation by nonCEPT Administrations. Under the CEPT Agreement, to activate operating authority, a traveler would have to carry credentials in English, French and German that the person, if a U.S. Citizen, and if a Commissionauthorized amateur operator, is entitled to certain amateur station operating privileges in the specific countries that have implemented the CEPT Agreement. For this purpose, we intend to rely upon: (1) a public notice containing the above information; (2) proof of Commissionauthorization to operate; and, (3) proof of U. S. citizenship.  Sh'177. For a United States citizen to operate an amateur station in a CITEL country, an International Amateur Radio Permit (IARP) is necessary. According to the CITEL Agreement, the IARP may be issued by the home administration. Such issuance of the IARP by the home administration may also be delegated to a membersociety of the International Amateur Radio Union  S'(IARU). {O0'#X\  P6G;ɒP#э See Article 3 of the CITEL/Amateur Convention.Ĕ The ARRL has offered its services to the Department of State to issue the IARP document to U.S. citizens for their use when they travel to CITEL countries. The ARRL would provide this service on a nondiscriminatory basis, at no cost, charge or expense to the United States  SP'Government.BZPZ yOJ'#X\  P6G;ɒP#э Letter from Christopher D. Imlay, Esq., General Counsel, ARRL, to the Director, Radio Spectrum  {O'Policy, U.S. Department of State (August 2, 1995). See also ARRL Petition for Rule Making, RM8677, at 12 and 1112. B We have no objection to the mechanism that ARRL wishes to establish for the issuance of the IARP document to U.S. citizens. Details of this mechanism can be worked out between the AARL and the Department of State. In the future, the Commission may delegate to other entities the authority to issue the IARP.  S'178.ؠ We note that authorization by rule of CEPT and CITEL licensees merely follows our longstanding precedent permitting Canadian citizens, who hold a license from their home country, to"`O|0*@%@%Z"  S'operate an amateur station in the United States without any further authorization or documentation.M {Oh'ԍ See 47 C.F.R.  97.107(a).M We conclude that authorization by rule of CEPT and CITEL licensees would be in the public interest and would benefit foreign visitors to the United States. In accordance with the procedures discussed above, United States citizens who travel abroad to Europe and to countries in Latin America would benefit equally.  S'179.ؠ With respect to our specific proposal to authorize reciprocal operation by rule in the ULS  S'Notice, the American Radio Relay League, Inc. (ARRL) is concerned about proposed section 97.25(b)  S'of the Rules, which would eliminate the oneyear term for an alien reciprocal permit.Z yO '#C\  P6QɒP#э #C\  P6QɒP#47 C.F.R.  97.25(b). We note, however, that this limitation serves no regulatory purpose or benefit since our current rules permit alien amateur radio operators to reapply for new permits indefinitely. Further, we observe that most visitors with reciprocal permits operate only temporarily in the United States and that they are not authorized under the Commission's rules to use more permanent, sophisticated systems such as  S 'beacons repeaters, and auxiliary stations.  yO'#C\  P6QɒP#э #C\  P6QɒP#47 C.F.R.  97.201, 97.203 and 97.205. Accordingly, we believe that retention of the one year limitation would perpetuate unnecessary regulation. Moreover, the rule we adopt here is similar to the  S 'one that governs operation by Canadian citizens. z yO'#C\  P6QɒP#э #C\  P6QɒP#47 C.F.R.  97.5(c)(2). In that instance, we believe that reciprocal operation authorized by rule has not encouraged Canadian permitees to operate in the United States permanently.  S '180.ؠ ARRL also raised the issue of license documents. Currently, an amateur service license is granted when the licensing data is entered into the Commission's licensee data base, not when the  S'applicant receives the paper document.\  yOf'#C\  P6QɒP#э #C\  P6QɒP#Amendment of the Amateur Service Rules to Change Procedures for Filing an Amateur Service License  {O.'Application and to Make Other Procedural Changes, Memorandum Opinion and Order, 10 FCC Rec 5417 (1995)  {O'(Amateur Licensing MO&O).ĸ The ARRL maintains, however, that the paper license is a  S'nonreplaceable necessity which establishes certain entitlements..  yOb'#C\  P6QɒP#э #C\  P6QɒP#ARRL Comments at 915. While we appreciate ARRL's  Sl'concerns, we are not willing to reassess this settled issue. In our Amateur Licensing MO&O, we  SF'reiterated that "operation is authorized when the grant of the license has occurred (emphasis  S 'added)."   {O~"'#C\  P6QɒP#э #C\  P6QɒP#Amateur Licensing MO&O, supra. We believe that this procedure affords several benefits overlooked by the League. Most importantly, it provides authority to the licensee to undertake operations almost immediately. Once the applicant's license grant is posted on the web site, the licensee is authorized to start operating"PP 0*@%@%K" immediately, without having to wait for a paper document. This procedure will reduce the wait for a licensee from several months to a matter of days. Finally, we note that presently VECs and other entities have authority to acknowledge an entry in the Commission's database by issuing a paper document to the licensee, based on information downloaded from the Commission's database.  S8' 181.ؠ ARRL further opposes our proposal to use certain eligible private sector entities, on a volunteer, uncompensated and unreimbursed basis, for the issuance of Club and Military Recreation  S'station call signs.\ yOP'#C\  P6QɒP#э #C\  P6QɒP#ARRL Comments at 1622. In a recent Commission proceeding, we proposed to phase out RACES  {O 'licenses. See 1998 Biennial Regulatory Review Amendment of Part 97 of the Commission's Amateur Service  {O 'Rules, Notice of Proposed Rule Making, WT Docket No. 98143, 13 FCC Rcd. 15798 (1998). It questions our reinstituting the administrators for these stations after vacating the  S'rules in a previous Commission action. {OL '#C\  P6QɒP#э#C\  P6QɒP# Amendment of the Amateur Service Rules to Establish Station Call Sign Administrators for Club and  {O 'Military Recreation Stations, Order, 8 FCC Rcd. 3594 (1993); Amendment of the Amateur Service Rules to  {O 'Establish Call Sign Administrators for Club and Military Recreation Stations, Memorandum Opinion and Order, 9 FCC Rcd. 103 (1993); Amendment of the Amateur Service Rules to Implement a Vanity Call Sign System,  {Or'Notice of Proposed Rule Making, PR Docket No. 93305, 9 FCC 105 (1993). In that action, the Commission established call sign administrators for Club and Military Recreation Stations. Upon reconsideration, however, the Commission vacated that action based on procedural grounds, stating that the matter should have been  SH 'a rule making proceeding rather than adoption of final rules by order."H  {O'ԍ#X\  P6G;ɒP# Id. The Commission also noted that it was not necessary to retain those rules because the needs of persons interested in obtaining a Club station license would be met in the Vanity Call Sign proceeding." We continue to believe that the use of call sign administrators would alleviate the Commission's burden of processing applications for Club and Military Recreation stations. By including call sign administration within the ULS  S 'electronic filing we believe the licensing process will become more efficient and costeffective.  yOn'ԍ#X\  P6G;ɒP# Club Station call sign administration only applies to nonfee applications. Therefore, we will accept the services of any organizations that meet the requirements of section 4(g)(3)(B) of the Communications Act.  S0'182.ؠ A few commenters also suggest changes to the proposed amateur service application  S'form, FCC Form 605.398 Both the W5YI Group and ARRL noted that there was no Physician's Certification of Disability (Physician's Certification) on the Form. We agree that this is necessary and  S'it will be included as Part "2" of Schedule "D" of the Form 605. In the ULS Notice, the Alien Amateur Radio Request to Operate in the United States (Alien Operation) was formerly located in Part "3." However, as correctly noted by ARRL in its comments, reciprocal authorization by rule obviates  SB'this Part and will , therefore , be removed from the Form 605. We believe that the above changes promote ease of use and best serve the public interest. "Q 0*@%@%"Ԍ S' 8. General Mobile Radio Service  S'` ` a. Inclusion in this Proceeding  S`'183. GMRS נINCLUSION Background. GMRS, a Part 95 Personal Radio Service, was originally established as the Citizens Class A Radio Service, and was allocated for use by individuals and entities who were not eligible for licensing in the public safety, industrial, and transportation services. Although the Commission adopted changes to the GMRS in PR Docket No. 87265 to make the service more  S'efficient and effective for personal users, these changes are now nearly ten years old.  yO* 'ԍ Amendment of Subparts A and E of Part 95 to Improve the General Mobile Radio Service (GMRS), PR  {O 'Docket No. 87265, Report and Order, 3 FCC Rcd. 6554, 6562,  72 (1988) (GMRS Report and Order).  The current rulemaking complies with our statutory directive to conduct a biennial review of wireless services, and we take this opportunity to reevaluate GMRS in order to identify and eliminate regulations that have become unnecessary in the past decade, as well as to ensure that our streamlined licensing process collects the minimum information needed of GMRS licensees and applicants consistent with our statutory responsibilities to license and regulate the use of this service.  S '184.ؠDiscussion. Several parties question whether it was appropriate to evaluate the current GMRS rules in this docket, and urge us to reserve our inquiry into the GMRS for a separate rulemaking. For example, PRSG claims that this proceeding should not be used to introduce rule changes that do not exclusively relate to the development and implementation of ULS, while SBT states that many of the proposed GMRS rule changes are technical in nature and should be considered  S'separately from ULS." {O'ԍ PRSG Comments at iii.; SBT Reply Comments at 910; see also, Riechel Reply Comments at 1; Vandercook Comments at 1. We believe that the GMRS rules we proposed and which we adopt herein are both appropriate and necessary under the current docket. We stated at the outset that ". . . as part of our 1998 biennial review of regulations, we are initiating this proceeding to streamline our wireless  Sj'licensing rules by eliminating regulations that are duplicative, outmoded, or otherwise unnecessary."Kj| {O'ԍ ULS Notice at 9674,  1.K The proposed changes to the GMRS rules likewise are consistent with our announcement that "the scope of this first biennial review will be broader than required by the 1996 [Telecommunications] Act," and the Chairman's statement that the biennial review "gives us an opportunity to promote meaningful deregulation and streamlining where competition or other considerations warrant such  S'action." {OP 'Ѝ Public Notice, "1998 Biennial Review of FCC Regulations Begun Early; To Be Coordinated by David  {O!'Solomon," Public Notice (rel. Nov. 18, 1997). In the case of GMRS, we have identified numerous rules to be eliminated and streamlined as duplicative or unnecessary to our regulatory responsibilities. Moreover, the requirements contained in the GMRS rules are inextricably linked to the conversion of our data collection procedures and databases to ULS, so we believe that streamlining our GMRS rules is properly included in this"*Rj 0*@%@%~"  S'proceeding. For these reasons, our ULS Notice outlined the broad scope of our proceeding, specifically discussed our proposed changes to the GMRS, and included a comprehensive list of proposed rule changes. Accordingly, we believe that we have met the requirements outlined under the  S'Administrative Procedures Act, and we disagree with Kobb's suggestion to the contrary.= yO'ԍ Kobb Comments at 2.=  S:'` ` b. Regulatory Policy  S'185. REGPOLICY Background. Many commenters view the ULS Notice as an effort by the Commission to fundamentally alter the purpose or form of the GMRS. We disagree. Although we have not hesitated to streamline and consolidate rule sections which request information unnecessary for ULS or other regulatory purposes, we have not altered eligibility requirements, permitted communication, the frequency allocation or other rules that could fundamentally alter the purpose of GMRS. Further, we believe the effect of these rule changes will actually increase users' flexibility in using GMRS and will promote use of the service.  S '186. Discussion. A large number of the commenters view the proposed changes as an initial step toward delicensing the GMRS. Parrish objects to any attempt to reduce or eliminate current Commission licensing procedures with the goal of moving GMRS towards an unlicensed service, such as the Citizens Band Radio Service, while FIT supports the proposed changes and suggests that we  S 'consider authorizing the operation of GMRS stations by rule.T X yO'ԍ Parrish Comments at 3; FIT Comments at 20.T We reject both FIT's proposal and individual GMRS commenters' suggestions. Under the authority granted by the Communications Act of 1934 (as amended), the Commission may authorize the operation of radio stations by rule and  S'without individual licenses only for specific services.M {O'ԍ See 47 U.S.C.  307(e)(1).M The Commission has never considered  Sl'interpreting this authority to include GMRS. Moreover, the ULS Notice did not propose to change the status of the GMRS to a service which may be licensed by rule pursuant to the statute. To the contrary, our goals in this proceeding are to comply with our Biennial Review responsibilities and to amend the Commission's rules in a way which facilitates electronic filing and automatic processing as much as possible consistent with our statutory responsibilities. Accordingly, we conclude that Parrish's (and other commenters') concerns in this regard are not applicable to the rule amendments we adopt herein to meet our stated goals and responsibilities.  S.'187.ؠ Numerous parties also express concern that our proposed changes will alter the nature of communications within the GMRS. Some of these comments were broad in scope: that the changes would allow "unscrupulous radio operators an opportunity to devastate the GMRS band;" would cause  S'the service to become "user unfriendly;" and would be "potentially disruptive."pz yO#'ԍ Hilke Comments at 1; J. Davis Comments at 1; Vandercook Comments at 1.p To the extent that"S 0*@%@%" these fears are based on the mistaken belief that we are eliminating licensing and the requirement that users share channels and cooperate with each other, we reiterate that we retain and will continue to enforce these rules. All GMRS users, whether longtime, new, or migrants from another radio band, have always been expected to follow all service rules, including those relating to the mitigation of interference, station identification, and permissible communication. We will continue to hold licensees  S8'to this standard.407 The rules we are eliminating are largely unenforceable and hortatory, and serve to make the GMRS overly complicated and less useful to existing and potential users. Accordingly, we cannot agree that the licensing process for the GMRS serves an independent good by making only the  S'most serious users conduct the procedures necessary in order to secure a license.A yO( 'ԍ J. Davis Comments at 1.A We strive to adopt rules that serve their stated purpose, and cannot support retention of a rule solely based on its secondary effect.  S '188.ؠ Although PRSG is among the parties that question the scope of our review of the GMRS, it proposes a new definition of GMRS that would "establish a more definitive description of  S 'the basic purpose of GMRS from which all authority for subsequent regulatory restrictions would  S 'derive" (emphasis in original),= X yO'ԍ PRSG Comments at 3.= as well as modifications to the description of a GMRS "system."A  yO2'ԍ PRSG Comments at 1617.A We will not adopt the proposed changes, as PRSG's proposed definitions would fail to include some existing GMRS users and would eliminate components of the service such as fixed station use.  S '` ` c. Eligibility  S'189. ELIGIBILITYBackground. In our last major evaluation of the GMRS, we adopted rules to "reorient the  S'GMRS to accommodate more fully the needs of personal users."cx {O'ԍ GMRS Report and Order, 3 FCC Rcd. at 6562,  72.c Significantly, we limited eligibility for obtaining a new GMRS system license to individuals in order to discourage large commercial operations, "grandfathered" existing nonindividual (i.e. business) GMRS licenses, and prohibited those  S'"grandfathered" licensees from making major modifications.3  {O'ԍ Id.3 Under the proposed rules, we retain the ineligibility of business entities to obtain GMRS system licenses and the prohibition against business  S'licensees making major modifications.H {O!'ԍ See 47 C.F.R.  95.5.H We remove and relocate to Part 1 the specific rules for  S'applying for a new or modified license..  {Op#'ԍ See 47 C.F.R.  95.71; new  1.913; 1.915; 1.923; 1.927; 1.931; 1.934; 1.949. "zT 0*@%@%"Ԍ S'190.ؠ Discussion. Burtner states that the proposed changes will allow business users to  S'encroach on what has traditionally been a personal and familyoriented service,@ yO@'ԍ Burtner Comments at 2.@ while Bollschweiler suggests that the proposed rules will allow GMRS to be overrun by business users, which will result in  S'greater interference and disrespect of the sharednature of the band.FX yO'ԍ Bollschweiler comments at 1.F We believe these concerns are somewhat overstated because the rule on permissible communications, section 95.181 of the Commission's rules, is substantially unchanged, and a nonindividual licensee who fails to abide by the GMRS rules pertaining to mitigation of interference and station identification is still subject to penalty for failure to abide by the service rules. For the benefit of PRSG, which opposes any expansion for  S'nonpersonal licenses under the current rulemaking,> yOH 'ԍ PRSG Comments at 16.> we emphasize that we are not changing the Commission's rules with respect to eligibility for GMRS licenses, and we continue to prohibit nonindividual licensees from making major modifications to their systems.  S '` ` d. Channeling Plan  S '191. CHANNELING Background. In the ULS Notice, we proposed to authorize stations to transmit on any authorized channel from any geographical location where the FCC regulates communication,  S 'eliminating the need for temporary licensing.L x {O'ԍ ULS Notice at 9709,  94.L Currently, a GMRS licensee may use seven 462 MHz interstitial channels, the 426.675 MHz/467.675 MHz nationwide channel pair for emergency communications and traveler assistance, and up to two of seven other GMRS channel pairs. The GMRS licensee is able to choose which channels will be authorized on the license. Under the allchannel operation plan we adopt, we make all seven channels pairs available to GMRS licensees who are individuals (in addition to the already available interstitial channels and nationwide channel pair), which in turn permits each GMRS system licensee to use the best channel available for its stations at any given time or place.  S'192. Discussion. Several commenters claim that allchannel operation will increase interference and degrade use of their GMRS systems. We disagree, and adopt an allchannel plan with the belief that it will provide licensees with the flexibility to reduce interference and make greater use of their GMRS systems. PRSG claims that such a policy could encourage "chitchat" and hobbytype communication, while Leef suggests that allchannel operation will result in anonymous users who  SR'float from one channel to another.UR  yO!'ԍ PRSG Comments at 78; Leef Comments at 12.U Mendelson predicts interference and inefficient spectrum use under an allchannel plan, and suggests that GMRS users will no longer have the potential for a"*U0*@%@%~"  S'working relationship that comes from licensing on specific channels.B yOh'ԍ Mendelson Comments at 2.B Under the current licensing plan where a GMRS license is authorized to use up to ten of fifteen allocated channels, users have the ability to communicate on different channels and do not have to remain within a single channel "community" if they choose. An allchannel plan will promote flexible use of GMRS by allowing users to select the channel that provides the best operational environment without having to predict during the licensing process which channels will be most suitable, and represents a natural progression  S'from the GMRS Report and Order, where we authorized selection of up to two channels (versus one channel), and authorized use of the seven interstitial channels and the nationwide channel. We adopted those changes with the belief that the additional channels would allow for "much of the flexibility we sought in advancing the allchannel concept," but we decided that "elimination of Commission assignment of channels and channel pairs would be too drastic a step to take at this time," and that retention of channel authorizations would "allow for a more gradual and useracceptable  S" 'application of existing and new technologies in the GMRS."f" X {O'ԍ GMRS Report and Order, 3 FCC Rcd. at 655859,  37.f Tellingly, no commenter disputed our tenyearold prediction that licensing of multiple channels, the interstitial channels, and the nationwide channel would promote more efficient spectrum utilization. None identified any potential for misuse or degradation of the GMRS that cannot take place under the current multiple channel licensing plan.  SZ'193.ؠAllchannel operation will also relieve the public and the Commission of unnecessary regulatory burdens. Currently, we routinely grant channel requests without further evaluation or inquiry. Although several commenters suggest that the proposed changes to the channel use policy  S'should not be undertaken because the current policy is not causing harm to the GMRS,m yOl'ԍ Leef Comments at 2; Yordan Comments at 1; PRSG Reply Comments at 5.m we believe it is appropriate for us to identify and eliminate rules that no longer serve the service, even when those rules are not actively harming use of the service. The allchannel operation plan we adopt today allows for the types of communications that were proposed in commenters' limited allchannel  SB'licensing suggestions.pBz yO\'ԍ Webber Comments at 1; Forrest Comments at 4; PRSG Reply Comments at 5.p Because we have decided to institute an allchannel use policy, we decline to adopt PRSG's suggestions that we retain rule sections relating to the licensing of specific channels and that we retain the restrictions on overlap of GMRS systems under section 95.31 of the Commission's  S'rules.D  yOt'ԍ PRSG Comments at 9 and 24.D Removal of these regulations is consistent with streamlining the GMRS, and the ready availability of an allchannel plan will give licensees additional flexibility in selecting the channel that best meets their needs. "RV0*@%@%"Ԍ S'194.ؠ Rosenthal, Yordan, and Burtner fear that the proposed changes will turn the GMRS into  S'a CBlike band, filled with interruptions, profanity, and casual communication.q yO@'ԍ Rosenthal Comments at 12; Yordan Comments at 1; Burtner Comments at 2.q We do not agree, and note that we will continue to require licenses of GMRS users, expect licensees to comply with the GMRS rules, and will use the licensing information to locate and impose sanctions against violators. We recognize that many GMRS users will consider the use of toneoperated squelch or other techniques to limit the use of a repeater to particular stations. While this may limit "the possibility of  S'other channel users from utilizing trained dispatchers to report motorist advisories and emergencies,"BX yO 'ԍ Mendelson Comments at 2.B we note that users are not presently prohibited from using these techniques. Additionally, we note that because we are not modifying the rules limiting the nationwide channel pair to emergency and traveler assistance communications, this channel pair will suit those owners who have placed repeaters on public property under the condition that they will be used solely for emergency and traveler assistance  SH 'communications.LH  {O'ԍ See Mendelson Comments at 2.L  S '195. In conjunction with the proposed allchannel use policy, we proposed to eliminate the  S 'rule limiting the use of the 467 MHz channels for transmissions through repeaters.O z {O'ԍ See 47 C.F.R.  95.29(a)(3).O We will retain this provision in our revised rules. Numerous commenters sharply disagreed with the removal of this limitation, and urged us to reconsider. Parrish suggests that interference to repeater operation caused  SX'by removal of this limitation would severely disrupt GMRS operations.BX  yO'ԍ Parrish Comments at 45.B This belief is echoed by  S0'Kobb, Forrest, Silver, and Hilke, among others.0 yOl'ԍ Kobb Comments at 1; Forrest Comments at 3; Silver Comments at 2; Hilke Comments at 1; PRSG Comments at 16; PRSG Reply Comments at 4. We originally adopted this rule after concluding that "significant interference to GMRS repeater operation is virtually inevitable due to nonrepeater  S'operations conducted on 467 MHz frequencies."|  {Ot'ԍ GMRS Report and Order, 3 FCC Rcd. at 6560,  56; Schweizer Comments at 1.| We recognize that this type of interference could still occur if these restrictions are not left in place, and we further note that retention of this provision does not affect our general allchannel use plan, nor does it lessen the administrative and licensing relief afforded by not processing applications and issuing licenses for specific channels. Finally, we take this opportunity to further clarify the section by including and defining the term "repeater." We believe that this clarification will aid licensees and potential GMRS users, and will help the Commission's rules match commonly accepted GMRS terminology. "W 0*@%@%"Ԍ S'` ` e. Information Collection  S'196.ؠINFOCOLLECT Background. In the ULS Notice, we tentatively concluded that by collecting basic contact information (such as name, address and telephone number) of individuals applying for licenses, we would be able to meet our statutory duty to license and regulate the GMRS. Accordingly, we proposed to consolidate the collection of license information into the new Part 1 rules, and to streamline the GMRS rules to eliminate technical information requirements relating to system  S'configuration and equipment.L {OR'ԍ ULS Notice at 9709,  95.L We also proposed elimination of regulations on points of communications for stations in a GMRS system (sections 95.5395.61) as part of our evaluation of our  S'information collection needs and overall streamlining of the GMRS.LZ {O 'ԍ ULS Notice at 9709,  94.L We concluded that points of communication restrictions are sufficiently removed from our licensing function that they can be  SJ 'eliminated.MJ  {O'ԍ ULS Notice at 9709,  94.M As Forrest observes, the sections' complex description of permissible and nonpermissible communication points discourages some individuals from applying for GMRS licenses,  S 'creates a burden on the Commission, and stifles innovation by manufacturers.A ~ yO'ԍ Forrest Comments at 10.A Parrish, like many commenters, claims that by no longer collecting this information, the Commission would leave GMRS users with no readily available means for users to contact other stations in order to foster frequency  S 'use, coordinate CTCSS Codes, and resolve interference problems.  yO0'ԍ Parrish Comments at 8; Forrest Comments at 67; Cochran Comments at 3; REACT Comments at 34.  S2'197.ؠDiscussion. We will adopt our basic information collection as proposed. There is no legitimate government purpose to collect more than basic information to perform our regulatory functions. Moreover, the Commission's databases will continue to provide a point of contact for licensees and because we are not eliminating the station identification requirement, GMRS users will continue to have the basic information necessary to locate other licensees. Nothing in the Commission's rules prohibits groups of GMRS users (or other third parties) from collecting and disseminating additional information about GMRS systems they have obtained from GMRS licensees. Several commenters also suggest that our proposed information collection for the GMRS will no  S'longer allow us to sufficiently regulate use of the band.v yO0 'ԍ Bollschweiler Comments at 1; Mendelson Comments at 4; Parrish Comments at 9.v We disagree. The Wireless Telecommunications Bureau will continue to accept and investigate formal and informal complaints of rule violations in GMRS. This agency has the capability to monitor GMRS transmissions and, when necessary, to conduct field investigations. We do not believe that we will jeopardize our GMRS enforcement by discontinuing much of the current technical information collection. "*X. 0*@%@%"Ԍ S'198.ؠ Because we are adopting streamlined information collection requirements under Part 1 of the Commission's rules, we also reject PRSG's suggestion that we employ a twotiered information  S'collection requirement.Y yO'ԍ PRSG Comments at 35; PRSG Reply Comments at 3.Y Such a scheme would frustrate our efforts to streamline the GMRS rules, and there is no legitimate governmental purpose served by collecting information from certain GMRS licensees but not others. We disagree with PRSG's objection to the consolidation of information collection requirements into Part 1 of the Commission's rules. We continue to believe that consolidation of our basic rules, when possible, will result in a simple and uniform approach to licensing for our wireless services.  S'199. PRSG claims that deletion of the rule sections requiring identification of the points of  Sp'communication would compromise the purpose of the GMRS to be a mobileoriented radio service.CpX yOh 'ԍ PRSG Reply Comments at 4.C We do not concur and will remove these rules as proposed. The current points of communication rules (and modifications proposed by some commenters) rest on somewhat artificial distinctions on station types. With the advent of modern radio equipment, the same piece of equipment can qualify as a different type of station based on its location and usage. The Commission's rules, however, maintain tight restrictions on permissible communication based on station types. GMRS users are better served by rules that establish general standards than rules that distinguish between how the equipment (fixed or mobile) is used or where it is located.  S'200.ؠ By eliminating the rules on points of communications, we also eliminate the rule that requires station operators of GMRS systems licensed to individuals wishing to use repeaters in other GMRS systems to first secure the repeater owner's permission. Region 20 claims that removal of the prohibition would result in interference to public safety licensees and would make it impossible for  Sh'repeater station licensees to maintain control over their equipment.Dh yO'ԍ Region20 Comments at 45.D Similarly, Parrish points to the significant investment he has made in repeater stations, and expresses concern that our proposed rule  S'changes will lead to unauthorized access to and operation of these privately owned facilities.sx yO0'ԍ Parrish Comments at 6; Webber Comments at 2; Riechel Reply Comments at 2.s The requirement that a licensee is responsible for the proper operation of the GMRS system at all times does not in itself justify retention of our points of communication rules. Rather, it underscores the fact  S'that the repeater operator is responsible for the use of his station. In GMRS Report and Order, we noted that "closing one's own repeater to prevent undesired use, such as by toneoperated squelch or digital access codes, and limiting those to whom these codes were available, would appear to be another means to establish who has permission to use a licensee's repeater station. This mechanism would avoid disputes regarding repeater operations. We consider this to be the most efficient, most costeffective and least burdensome approach to improving transient GMRS operations, and encourage"Y0*@%@%"  S'its use."c {Oh'ԍ GMRS Report and Order, 3 FCC Rcd. at 6558,  29.c These means of control we identified a decade ago remain viable options for repeater station owners who are concerned about maintaining control over their systems.  S'` ` f. Antenna Requirements  S8'201. ANTENNAREQ Background. Our examination of unnecessary and outdated rules led us to propose the elimination of distinctions based on large urban areas. Accordingly, we also proposed to eliminate power and antennadirectivity requirements within and near urban areas, and instead limit all fixed stations regardless of location of a maximum authorized transmitting power of fifteen watts.  Sp'202. Discussion. Several parties most notably PRSG support the retention of power and antennadirectivity requirements within and near urban areas for other types of stations, and suggest  S 'that the restrictions could be further expanded.A Z yO'ԍ PRSG Comments at 1415.A We disagree. The pattern of suburban sprawl and rural growth in the years since this rule was adopted blunts the effectiveness of an urban area distinction. Additionally, the present rule imposes restrictions based on undefined points, such as the "rim" of an urban area. Under the modified maximum authorized transmitting power rule (section 95.135), all fixed stations regardless of location will be limited to fifteen watts output power, while small base stations will continue to be restricted to five watts. We believe that these modifications will further our goal of simplifying and streamlining the GMRS rules while simultaneously protecting GMRS users by retaining limits on the maximum authorized transmitting power. Because urban area distinctions are unnecessary, we also eliminate Appendix B of our current GMRS rules, which lists  S'urban areas. yOB'ԍ See 47 C.F.R.  95 ("Appendix B to Subpart A to Part 95 Where the Large Urban Areas are Located").  Sh'` ` g. Permissible Communications  S'203.ؠPERMISSIBLE Background. In the ULS Notice, we proposed to retain the regulations on permissible and prohibited communications, with minor modifications, and to list permissible and prohibited communications under separate rules.  Sz'204.ؠ Discussion. Although no commenters opposed this concept, PRSG had specific  SR'reservations about our list of prohibited communications.ARz yOl 'ԍ PRSG Comments at 2426.A Because the elimination of duplicative and ambiguous rules serves the public interest, we will adopt the proposed rules with minor modifications. While we believe that the categories of prohibited communication are discrete and do not need parenthetical explanation, we will maintain the distinction that "10codes" are not included in the prohibition against coded messages because of the potential for confusion. We will also retain a"Z 0*@%@%" prohibition on advertisements for the sale of services. We decline to alter our prohibition on profane  S'speech, as suggested by PRSG.> yO@'ԍ PRSG Comments at 25.> Many commenters strongly support the GMRS because it is free of profane, indecent and obscene speech, and many of their concerns are based on the fear that the  S'proposed changes to the GMRS will alter this quality.VX yO'ԍ Burtner Comments at 2, Yordan Comments at 1.V Finally, we remove the prohibition on sounds  S`'only to attract attention.>` yO'ԍ PRSG Comments at 26.> This prohibition is ambiguous and largely unenforceable. Moreover, we envision times such as emergency situations when the broadcast of such sounds would be both necessary and proper.  S'` ` h. Rules Pertaining to Management of a GMRS System  Sp'205. MANAGE נ Background. We proposed significant changes to the rule sections broadly titled "Managing a GMRS System" (sections 95.103 95.181 and app. A and B of the Commission's rules). These changes further our efforts to streamline the GMRS rules by eliminating duplicative rules, as well as deleting those rule sections that offer general guidance but are ambiguous in application or enforcement.  S '206.ؠ Discussion. We note that some commenters, including Parrish and Vandercook, urge us to keep many of these explanatory rules because they fear that users would lack the guidelines and  S0'structure necessary to construct, operate, and maintain GMRS systems.Z0x yOH'ԍ Parrish Comments at 4; Vandercook Comments at 1.Z We disagree and adopt the changes as proposed. Although some users believe a useful contextual function is served by the complex rules and numerous restrictions on system construction, licensing, and operation contained in the current GMRS rules, we are concerned that the current rules unnecessarily keep many parties from considering and applying for licenses in the GMRS.  S@'207.ؠ Many of the rules we eliminate are duplicative. A licensee must have access to the station equipment and be able to disable it in order to maintain the proper operation of the GMRS system at all times, so it is unnecessary to retain specific access language in section 95.103(b). Similarly, in order to maintain the overarching responsibility for proper system operation, a GMRS licensee must regularly monitor and maintain his or her equipment. Many of the rules we propose to delete are ambiguous and unenforceable. For example, the specification that voice station identification in section 95.119(d)(2) be made "with each letter and digit separately and distinctly transmitted (letters may be said using a phonetic alphabet)" does not add to a licensee's understanding of the basic requirement that a station must be identified and may even raise independent questions such as whether a user must engage in a separate transmission for each letter and digit in a call sign and whether a licensee with an accent unfamiliar to the listener is in violation of the rule. Finally, the"[0*@%@%" removal of other rule sections, such as those pertaining to system records, station control point and controlling stations from a remote point, and servicing and modifying station transmitters, is wholly consistent with our efforts to institute streamlined licensing and data collection requirements under ULS, and to remove unnecessary rules. In light of our new information collection requirements for GMRS, we also do not need to collect the detailed information specified in section 95.103(c) when a licensee's information changes or when a GMRS user moves or adds a small base station or small control station.  S'  IV. PROCEDURAL MATTERS Sp'\  S ' A. ` ` Regulatory Flexibility Act  S '208.  REGFLEX  The Final Regulatory Flexibility Analysis, pursuant to the Regulatory Flexibility Act,  S 'see 5 U.S.C.  604, is contained in Appendix B.  S2' B. ` ` Paperwork Reduction Act of 1995 Analysis  S'209. PRA This Report and Order contains a modified information collection, which has been submitted to the Office of Management and Budget for approval. As part of our continuing effort to reduce paperwork burdens, we invite the general public to take this opportunity to comment on the  Sl'information collection contained in this Report and Order, as required by the Paperwork Reduction Act of 1995, Pub. L. No. 10413. Public comments should be submitted to OMB and the  S'Commission, and are due thirty days from date of publication of this Report and Order in the Federal Register. Comments should address: (a) whether the proposed collection of information is necessary for the proper performance of the functions of the Commission, including whether the information shall have practical utility; (b) the accuracy of the Commission's burden estimates; (c) ways to enhance the quality, utility, and clarity of the information collected; and (d) ways to minimize the burden of the collection of information on the respondents, including the use of automated collection techniques or other forms of information technology.  S'  S'C. ` ` Further Information  Sh'210. FURTHERINFO For further information concerning the Report and Order, contact Wilbert E. Nixon, Jr., Policy and Rules Branch, Commercial Wireless Division, Wireless Telecommunications Bureau, (202) 4187240 (voice), (202) 4187238 (TTY), or by electronic mail at wnixon@fcc.gov, or Susan Magnotti, Policy and Rules Branch, Public Safety and Private Wireless Division, Wireless Telecommunications Bureau, (202) 4180871 (voice), (202) 4187233 (TTY), or by electronic mail at smagnott@fcc.gov. For further information concerning the information collections contained in this  Sz#'Report and Order, contact Judy Boley at (202) 4180214 (voice), (202) 4182970 (TTY), or by electronic mail at jboley@fcc.gov."T$\0*@%@%>#"Ԍ  S' -V. ORDERING CLAUSES  S'  S`'211. Accordingly, IT IS ORDERED that, pursuant to the authority of sections 4(i), 11, 303(g), 303(r), and 332(c)(7) of the Communications Act of 1934, as amended, 47 U.S.C.  154(i), 161, 303(g), 303(r), 332(c)(7), 47 C.F.R. Parts 0, 1, 13, 22, 24, 26, 27, 80, 87, 90, 95, 97 and 101 of the Commission's Rules are AMENDED as set forth in Appendix F, effective sixty days after  S'publication in the Federal Register. The information collection in these rules becomes effective sixty  S'days after publication in the Federal Register, following OMB approval, unless a notice is published  St'in the Federal Register stating otherwise.  S& '212. IT IS FURTHER ORDERED that the Commission's Office of Public Affairs, Reference  S 'Operations Division, SHALL SEND a copy of this Report and Order, including the Final Regulatory Flexibility Analysis, to the Chief Counsel for Advocacy of the Small Business Administration, in  S 'accordance with section 605(b) of the Regulatory Flexibility Act, 5 U.S.C.  601 et seq.  Sb'213.ؠ IT IS FURTHER ORDERED that pursuant to section 5(c) of the Communications Act of  S:'1934,?: yO'ԍ 47 U.S.C.  155(c).? the Chief, Wireless Telecommunications Bureau, IS GRANTED DELEGATED AUTHORITY to develop, implement, modify rules and procedures for the Universal Licensing System to the extent stated herein.  S'214.ؠ IT IS FURTHER ORDERED that Petition for Rule Making RM8677 is granted as indicated herein and WT Docket No. 96188 is TERMINATED.  ` `  hhCFEDERAL COMMUNICATIONS COMMISSION ` `  hhCMagalie Roman Salas ` `  hhCSecretary