State 9-1-1 Office Wireless Program report

              Arizona Department of Administration
State 9- 1- 1 Office
Wireless Program Report
2007
RECEI\/ D
OFFICE OF THE Pf< ESiDENT
The State 9- 1- 1 program was established, through legislation in 1985, to provide
a funding mechanism for the deployment and on- going costs of providing 9- 1- 1
services in Arizona.
Under A. R. S. Â  Title 43, Article 6, Telecommunications Services Excise Tax, a tax
is levied for each activated wire line access and wireless service account for the
purpose of finanCing emergency telecommunications services. Current law
reduced the tax fromfhirty- seven cents per month to twenty- eight cents per
month in July 1, 2006. The. tax reduced to twenty cents per month as of July 1,
2007.
The funds collected are administered by the Arizona Department of
Administration under A. R. S. Â  41- 704 and rules have been established that
govern the allowable expenditures and funding eligibility requirements by
communities and political sub- divisions in the State.
Components eligible for funding include necessary and/ or appropriate network,
equipment and maintenance to handle the processing of 9- 1- 1 emergency calls.
Of the revenue generated, the program distributes 98% of the fund for 9- 1- 1 call
service delivery of wire line and wireless services. One percent of the revenue is
allocated for local network management of contracts through the 9- 1- 1 system
coordinators. . .
An amount not to exceed 2% of the annual revenue is used by the Arizona
Department of Administration for program oversight expenditures.
Accounting methodology is in place to track all expenditures by community
  and/ or 9- 1- 1 system. The revenue is also collected and reported separately
between the wire line and wireless services. Effective July 1, 2007, the
Department of Revenue will transition to collecting the tax as one entity and
identify this collection code as 9- 1- 1 .
All Public Safety Answering Point ( PSAP) equipment used to answer and handle
9- 1- 1 calls are budgeted under wire line expenditures, although it should be
understood that the equipmentis used to answer both wire line and wireless
9- 1- 1 calls.
The Arizona 9- 1- 1 Wireless Phase II Implementation Plan has been updated
during FY07 to expand the program moving specified sites toward deployment of
Phase II Wireless; Costs associated with legislative cost recovery and a copy of
1
the plan is enclosed. The Statewide System Project plan covering each 9- 1- 1
System for FY08 has been updated and is also attached .
. The wireless program criteria established for rollouts, stipulate that Enhanced
9- 1- 1 ( voice, telephone number and address) has been completed for either an
entire county or significant portions of a county. Each county or system must
complete a Wireless 9- 1- 1 Service Plan, utilizing the format specified in the State
gUidelines and appoint a single point of contact for each county or area. The
Geographic Information System ( GIS) data must be completed and meet the
same 95% accuracy rate as established for Enhanced Wire Line 9- 1- 1.
Equipment mapping components will be installed prior to implementation of
Wireless Phase II.
Wireless Deployment
Significant progress continues to be made in the deployment of Wireless Phase
II. The two major regions in the state, Maricopa and Pima have completed their
Phase II deployments constituting approximately 80% of the state's population.
The Northern Yavapai County area, which encompasses the City of Cottonwood,
City of Sedona, Town of Camp Verde and surrounding Yavapai County has also
completed Phase II deployment.
During FY07, funds were expended from the $ 1 million dollar Public Safety
Answering Point ( PSAP) Rea~ iness Fund grant to complete the Geographic
Information Systems ( GIS) work necessary to move three counties from Wireless
Phase I to Wireless Phase II. GIS work for Graham and Santa Cruz Counties
completed in the fall of 2006. Subsequently, mapping equipment was installed
and the Request for Phase II service letters sent to the carriers. Both Graham
and Santa Cruz Counties completed theirPhase II deployment in spring 2007.
GIS work for Pinal County completed fourth quarter FY2007 and the request for
Phase II service letter was sent on April 10, 2007. Deployment is scheduled for
first quarter FY2008
The completion of these projects will provide wireless Phase II service from
Nogales all the way to Phoenix. Recently, Pinal County was identified as the
' third fastest growing county in the nation and with this deployment, the citizens
will have an added level of public safety protection.
The GIS work for Graham, Pinal and Santa Cruz counties were completed for
significantly less then what was originally estimated under the Scope of Work. The
PSAP Readiness Fund Board is pleased that their grant dollars have been used
specifically for what it was intended. With the funds remaining, the PSAP Readiness
Board has authorized an expansion to the original Scope of Work. Preliminary
planning has identified the next areas for deployment include the southern portion of
2
Yavapai County, Cochise County and Mohave County with GIS work will be
scheduled during FY08.
During FY06, the southern portion of Yavapai County completed their Enhanced
9- 1- 1 project and with the northern portion of the county already Wireless Phase
II, it is logical to implement the remainder of the county. Cochise County
completed their Enhanced 9- 1- 1 project during FY07, developing accurate GIS
in conjunction with the addressing project making this area a logical choice.
These projects are both scheduled to be deployed with wireless Phase II service
during FY08.
In FY07, the Gila River Tribal Community completed their Enhanced 9- 1- 1
project and since they are adjacent to both Maricopa and Pinal counties, they will
move toward Wireless PII in FY08. Request for Phase II service letters have
been sent to the carriers and they will begin their deployment within the six
month time frame.
Wlreless Expenditures
During FY07, the majority of one time charges were expended for completed
Wireless Phase II projects. Both the Graham County and Santa
Cruz County Wireless Phase II projects were completed in FY07 and all one time
charges have been invoiced.
The FY07 expenditures for Wireless Phase 1& II are outlined in the table below.
PII
PII
PII
PI/ PII
PI/ PII
PI
PI
PI
It should be emphasized that the 9- 1- 1 answering equipment is fiscally allocated
to wire line equipment although this equipment handles calls for both wire line
and wireless 9- 1- 1 calls. In future years, with the reduction of wire line services,
an equitable division of equipment costs and maintenance may have to be
explored.
3
The FY08 budget includes the following expenditures for systems currently
Wireless Phase I and/ or Phase II, those adding in new systems, and those that
are close to or have completed their GIS requirements.
Expenditures include network components, both wireless carrier costs and
selective router costs.
Cochise County
Gila County
Gila River Indian Community
Graham County
Maricopa Region
Mohave County
Navajo Co/ Apache Co
Paqe
Pima County
Pinal County
SantaCruz County
Winslow
Yavapai No.
Yavapai So.
Yuma County
$ 764,531
$ 2
$ 74,585
$ 58,480
$ 3,059,468
$ 1,086,285
$ 1,800
$ 198,547
$ 1,531,653
$ 396,925
$ 81,360
$ 30,500
$ 497,979
$ 305,130
$ 424,607
$ 8,511,852
to PII
to E911
to PII
PII
PII
to PII
E911
PI to PII
PII
to PII
PII
PI
PII
to PII
toPIi
Additional expenditures budgeted for fiscal year 2008 includes the
implementation of a frame relay network for deployment of an Enterprise
Mapping System. With significant county boundary issues recognized, this.
system will allow GIS data to be distributed to the 9- 1- 1 centers within their
county or share the data with other counties. These costs are already being
expended in the Maricopa Region and Pima County because ofthe number of
9- 1- 1 centers located within that system. When a new map data is available,
information can be sent via the network and updated information can be
pUblished more efficiently.
FY07 brought significant changes within the wireless industry and thus has
positively affected the future of the Arizona 9- 1- 1 program. Several mergers and
acquisitions have reduced the number of wireless network providers. This and
with a change of carrier philosophysome of the carriers have opted to not seek
cost recovery from the State 9- 1- 1 program. They have instead opted to seek
self recovery from their customers. This does not affect the costs associated
with the selective routers, but does effect the amount billed by the individual
carriers.
4
Also, with an emphasis on Homeland Security and network restoration, the
Telecommunications Service Priority ( TSP) provisioning was added in FY07. This
federal program is designed to ensure elevated network restoration to anyone
who registers and pays for the service. In the event of a national disaster and
federal intervention is required for network continuity, the service will ensure that
Arizona's 9... 1- 1 systems will be restored in a timely manner.
. All network components including 9- 1- 1 circuits, Automatic Location Identification
circuits, emergency back circuits and circuits that run to all selective routers have
been included in the service package.
The State 9- 1- 1 Office strives to reduce costs for network and equiprnent
components. During FY07, negotiationswith Owest changed the billing structure
for the wireless selective router charges, reducing costs significantly.
Revenue - FY08 Projections
Effective July 1,2007, the Wireless Tax and Wire line Excise Tax was reduced
from $. 37/ mo. to $. 28/ mo. by statute. The reduction for FY07 in projected
revenues is based on an overall 5% increase in carrier services and the twenty
per cent reduction in the tax.
There is an additional statutory reduction to $. 20/ mo scheduled for FY08
beginning in July 2007. The overall decrease reduces the revenue by almost
40% over a two year time period..
The wireless revenue for FY07 closed at $ 11,447.131, a 2% decrease over
FY06. As previously noted, the Department of Revenue will not longer be
breaking out the wireless revenue generated and therefore, the total funds will
have to be evaluated. In the past two fiscal years, the total revenue collected
between wire line and wireless was virtually equal. In FY07, wire line services
was minimally ahead of wireless, which can possibly be equated to the opinion
by the Department of Revenue that existing statutory language includes Voice
over Internet Protocol ( VoIP) services.
In the FY06 report, there was an assumption that the wireless customer base
would continue to increase, but with the aforementioned DOR decision, the wire
line customer base actually increased by 2% in FY07. The original projections
for FY07 estimated that the wire line base would be reduced by 3%. In reality,
the base only reduced by 1%. The wire line ( Excise Tax) revenue for FY07
closed at $ 11 ,627,037. Again, we offset the wire line revenue with the wireless
revenue to come up with an overall 5% increase when preparing the projections.
5
(, 0'"",,' ',' ,"' iB( Q7;', Blidget:: FY07::; l\ cfUatt ~'::,%' of Difference:
, y 110'. ',, 0,
Wireless Tax
Excise Tax
11,522,436
11,125,184
11,447,131
11,627,037
- 1%
4%
22,647,620 23,074,168 2%
In preparing the 911 Project Plan through FY12, the tax decrease, customer
base and reduced fees has been taken into consideration indicating that the
program will reach a deficit in FY12.
One area where the reductions are immediately evident and is service affecting
is the 3% administrative fees. Of this three percent, 2% is used for ADOA
administrative services and 1% is distributed to the local level for network
contract services.
The State 9- 1- 1 Office currently has five full time staff members. These
individuals not only have fiscal oversight, but work closely with the communities
to deploy and support 9- 1- 1. With the 40% reduction in revenueS over the two
year time frame and the 2% cap on administrative spending, staff will have to be
reduced by one position during FY08. This impact may delay the deployment of
Wireless PII.
The Future of 9- 1- 1
The 911 Project Plan addresses the need to transition to a more robust and
technology forward network in coming years. The IP enabled network or Next
Generation 9- 1- 1 designs are on the drawing board today. Once industry
standards are developed, costs can be determined. The move toward a single
network that provides ubiquitous service will ensure that calls can be routed
anywhere without current boundary restrictions.
Beginning in fiscal year 2008, funds have been allocated to begin transitioning to
a Next Generation IP enabled network. The initial project plan includes
deployment of an IP network in Gila County. There is currently an issue with
transfer of calls between Gila County Sheriff's Office in Payson and the office in
Globe. The northern portion of Gila County is served out a separate selective
router then the southern portion of Gila County as a result of a LATA boundary
division. The installation of this Next Generation network including installation of
soft switches, will allow for reliable and time sensitive transfer of calls. The four
PSAPs in Gila County will be changed out to Positron Viper system designed
specifically to transition to NG technology. It should be noted that this project
may take several years to come to fruition and during this time all legacy network
components will require continued support.
6
The 9- 1- 1 system was designed to ensure that in an emergency, citizens have
one reliable number to call for public safety assistance. The State 9- 1- 1 program
strives to ensure that this goal is met in the most efficient and cost effective
manner.
7
9 Â  1" 1 PROJECT PLAN' ( wI $ 15,000,000 Funr; l Transfers $ 12m FY03, $ 3mFY04)
Assumes Change in Tax Rates
As of August 24, 2007
Includes Wireless &. Excise Taxes at a Flat Rate of $. 37 through FY 2006, a Flat Rate of $. 28 for FY 2007 and a Flat Rate of $. 20 for FY 2008 Â  2012
ANNUAL INCREASE ASSUMPTIONS: 5% Operations Cost; Wireless Tax and Excise Tax
based on tax rate reduction
Actual Actual Actual Actual lin ( i;!; i;. I~ udgeted<~ ur; lgeted::<~ udgete~
FY04 FY05 FY06 FY07 1\ uo/}' c'j';"' c+ yU~\""'" """',' FY10'" ' FY11 .. "-' FY12'
Administration $ 296.513 $ 469.822 $ 431.290 $ 426.386 ',. i'. " ,$. A12.137 $'. .423.489
PSAP Network Management $ 258,625 $ 277,526 $ 339,232 $ 316.841 $' . 206,068$' " 211,744
Sub- Total $ 555,138 $ 747.348 $ 770,522 $ 743,227 $"' 573; 711' ..'," 0<$;' ' 602.273 $. 618,205 $ 635,233
I'~;',; ,;;,;:, ;:.;. ?!~: ";.'(;'",
Wireline - ( Existing Network Technology) $ 11.087,417 $ 12.925.882 $ 10.162,966 $ 13.462.043Y;" Â  ?"\ i$ 16; 333~ 305! $ 17,149,970",$ 17.536.602
Wireline - ( Proposed transition to IP enabled network)" I$>;; nnn'nnn '' 1:;.,;", .' •. $ 5; 000,000 . $ 5,000.000 . , '$ 0
Phase I Wireless - ( Includes Cost Recovery) $ 1.948,627 $ 2,581.835 $ 1.392.829 $ 557.667 1$" .~:'::' 1,~ UIJ: P .....• ~ 40.515 $.,. 357,541 $ 375,418 $ ' 394,189
Phase 1\ Wireless - ( Includes Cost Recovery) $ 3,338.435 $ 4,341,115 $ 5,985,541 $ 4,738,719 1$ I o~', 712 IV Â  "" aa < a" $ 9.029,158 $ 9,480,616 $ 9,954.647
TOTAL PROGRAM COSTS $ 16.929,617 $ 20.596,180 $ 18.311.858 $ 19,501.656 .. a, n~."<. a .$'.: 3.3,0.82.683 $ 31,322,277$ 32.624,209 $ 28,520,671 ....
FUNDS FROM PRIOR $ 19,497,150 $ 25.736,153 $ 33,122,221 $ 44,996.452 $'" n $' 44,111; 388 $ 30,610,098 $ 19,363,599 $ 7,346,225
I;,',>,'     i '(' ij, ...• .... . .....•......
WIRELESSTAX $ 11,972.954 $ 12.927.897 $ 14.620.376 $ 11,447.131 I$:;:~"' » j:- $- $ - $ •
EXCISE TAX $ 13.748,484 $ 14.317.661 $ 14.116.318 $ 11.627.037 <" Q"" " An ,,.' O.!:' 7n $ 18,268,418 $ J8.944,062 $' 19,644,695
INTEREST INCOME $ 447.181 $ 736,690 $ 1,449395 $ 2,321,033 $ 2,135,350 $ ";.'. 1,964,522 $ 1,807,360 $ 1,662,772 $ 1,529,750
Total Collections $ 26.168,620 $ 27,982,249 $ 30.186.088 $ 25,395.201$ < a <?'> a « $ 19,581,393 $ 20,075,778 $ 20,606.834 $ 21,174,445
." ,
TOTAL FUNDS $ 45,665.770 $ 53.718,402 $ 63.308.310 $ 70,391,652 $ 70,013,907 $ 63,692,781 $ 50,685,876 $ 39,970.434 $ 28,520,670 .;., ,! ii' I Â  ..'
PRIOR PERIOD ADJ OR PROJECT CARRY   FORWARD $ - $ - $ - $ - 1$ - $ • ,$ - $ - $ •
TRANSFER TO GENERAL FUND $ 3.000,000 $ • $ - $
EXPENDiTURES $ 16,929.617 $ 20.596.180 $ 18,311,858 $ 19.501.656~, 5,9~ 2' T1~ 33.082,683 $ 31.322,277 $ 32.624,209 $ 28,520.671
FUNDS FORWARD $ 25,736,153 $ 33,122,221 $ 44,996,452 $ 50,889,996 $ 44.111.388 $ 30,610,098 $ 19,363,599 $ 7,346,225 $ ( 0)
Wireless Tax Rate $ 0.37 $ 0.37 $
• Wirelesscombined with Excise tax as one revenue category per Department Of Revenue FY08 and forward.
Pg 4 Revised 9- 1- 1 Ending Balance Forecast 102507. xls
0.37 $ 0.28 $ 0.20 $ 0.20 $ 0.20 $ 0.20 $
10/ 25/ 2007
0.20
Status of Arizona 9- 1- 1
E9 Â  1 Â  1 Phase I Phase II Pro ram Plan FYOB
X FY08 FY08 Complete GIS/ Deploy Wireless PII
Proposed Enterprise Mapping Network
FY11 FY11 Complete County Addressing
FY08 FY08 Complete GIS/ deploy Wireless PII
FY08 FY08 Upgrade Equipment
Proposed Enterprise Mapping Network
FY08 FY08 Complete GIS/ Deploy Wireless PII
FY09 FY09 Continue County Addressing
FY11 FY11 Complete Enha~ ced 9- 1- 1
FY08 FY08 Deploy Wireless PII
FY10 FY10
FY11 FY11 Complete County Addressing
Addressing Program/ Service Plan Development
FY08 FY08 Complete GIS/ Deploy Wireless PII
FY11 FY11 Equipment Replacement
Equipment Replacement
FY08 FY08 Complete GIS/ Deploy Wireless PII
E911 Service Plan Development
FY11
FY08 90mplete GIS/ Deploy Wireless PII
FY12
FY08 Complete Wireless Phase II/ Enterprise Mapping
FY08 Complete GIS/ Deploy Wireless PII
Equipment Upgrades
Service Plan Development
Proposed Enterprise Mapping Network
Eq. Wpgrades/ Complete GIS/ Deploy Wireless PII
Complete GIS/ Deploy Wireless PII
Complete Enhanced 9- 1- 1
FY08 Complete GIS/ Deploy Wireless PII/ Southem Portion
FY08 Complete GIS/ Deploy Wireless PII
The Estimated Costs and Deployment Schedule to
Implement Wireless Phase II
ADOA has worked in concertwith the political subdivision to ensure compliance
with the established requirements prior to deployment Wireless Phase I and
Phase II. PSAPs that have not completed Phase I are being encouraged to
move directly to Phase II. The 9- 1- 1 Program Office has established a 12 month
time standard for completion of a Phase I or Phase II project. Direct deployment
to Wireless Phase II has cut down on the time necessary and reduce some of the
costs.
The Wireless Phase II Systems Deployment Timeline and estimated
implementation costs are listed below in chart 1. Projections are based on
figures obtained from the Local Exchange Carrier ( LEC), equipment vendors and
the Wireless Carriers. The information in chart 2 outlines implementation and
going costs for Wireless Phase I and Phase II. Additionally, these figures were
obtained. through the cooperative effort of the Local Exchange Carriers and the
Wireless Carriers. The State 9- 1- 1 Office continues to negotiate with vendors to
reduce the costs.
The costs outlined below may not match those figures outlined in the 9- 1~ 1
Project Plan and it is possible that projects will need to be delayed until sufficient
revenue is available.
Itshould be noted that three Tribal Nations have not been included in the
projections. Service Plans for 9- 1- 1 deployment have not yet been submitted for
funding consideration by the Navajo Nation, Hopi Tribe or San Carlos Tribe..
The Navajo Nation continues to work on completing their 9- 1.,. 1 Service Plan in
an effort to be eligible for funding. Over the past year, a significant amount of
work has been accomplished within the Navajo Nation governing authority to
obtain addressing concurrence with all chapters.
The ADOA 9- 1- 1 Office has an outreach program in place designed to work with
the other tribes to help them to address deployment issues.
Chart 1
Equipment & Misc.
LEC and Wireless Products and Totals ( Tax
9- 1- 1 System FY Carrier Costs Services Included)
Apache/ Navajo FY11 $ 411,800 $ 1,220,949 $ 1,632,749
Cochise FY08 $ 247,617 $ 589,491 $ 837,108
Coconino FY09 $ 848,758 $ 848,758 $ 1,697,516
Gila FY11 $ 190,000 $ 640,631 $ 830,631
Gila River
Indian
Community FY08 $ 37,117 $ 36,388 $ 73,505
Graham -
Impletmented FY07
Greenlee FY11
La Paz FY11
Maricopa
Implemented FY06
Mohave FY08
Page FY08
Pima-
Implemented FY06
Pinal FY08
Santa Cruz
impletmented FY07
Winslow FY09
Yavapai, No-
Implemented FY06
Yavapai, So FY08 $ 164,642 $ 140,488 $
Yavapai, So FY08 $ 274,794 $ 190,240 $ 465,034
Yuma FY08 $ 730,905 $ 1,190,086 $ 1,920,991
Total $ 3,847,678 $ 5,887,705 $ 9,430,253
Chart 2 E9- 1- 1 Wireless Phase III
Actual and Projected Expenditures
FY06 - FY11
FY 9- 1- 1 System Wireless Network Equipment Etc. Totals
'-"',
if; Graham
Maricopa
Page
Pima
Pinal
Sa. nta Cruz .
Winslow
Yavapai No.
Cochise
Gila
Gila River Tribal
Graham
Maricopa
M? na~~
N~ y~ jo! A~ aclle
page   ."
Pima
Pinal
Santa Cruz
Winslow
Yavapai No.
Yavapai So.
Yuma
Cochise
Coconino
Gila
Gila River Tribal
Graham
Maricopa
Mohave
Navajo! Apache
Page
Pima
Pinal
Santa Cruz
Winslow
Yavapai No.
Yavapai So.
Yuma
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
52,740
3,044,657
62,050
1,319,105
260,852
55,921
22,907
239,040.00 $
2.00 $
37,117 $
54,700 $
3,048,668 $
819] 41$
1,890 $
91,330$
1,442,985 $
382,345 $
76,500 $
27,800 $
239,427 $
164,642 $
188140 $
129,345 $
848,758 $
150,000 $
29,530 $
58,480 $
3,036,818 $
235,053 $
411,800 $
90,250 $
1,505,733 $
363,445 $
81,360 $
85,590 $
307,225 $
95,430 $
121 $
67,557
53,573
1,921
117,442
54,472
525,491.00 "$
.. - $
37,468 $
3,780 $
10,800 $
266,544 . $ .
- $
107,217 .$
88,668 $
14,580. $.
4,860 $
2,700 $
260,712 $
140,488. Â  $
23 .. $.
30,000 $
848,758 $
20,000 $
10,500 $
17,716 $
50,000 $
35,000 $
39,599 $
35,000 $
79,387 $
31,561 $
14,309 $
107; 3.00 .$....
30,719 $
20,000 $
120,297
3,098,230
62,050
1,321.026
378,294
110,392
22,907
764,531
.2
74,5815
58,480
3,059,468
1,086,285
1800 "':,.',
198,? 47
1,531,653
396,925
81,360
30,500
500,139
. 305,13()
424,607 Â 
159,345
1,697,516
170,000
40,030
76,196
3,086,818
270,053
451,399
125,250
1,585,120
395,006
95,669
192,800
337,944
115,430
141 137
Chart 2 E9- 1- 1 Wireless Phase III
Actual and Projected Expenditures
FY06 - FY11
July 2006
487,132
314,000
115,000
50,030
104,400
4,536,818
428,778
46,800
105,250
1,905,733
411,616
179,200
45,500
269,875
115,430
271,137
Cochise
Coconino
Gila
Gila River Tribal
Graham
406,488
268,800
  259r909<  
31,000
50,000
20,000
.. Â  Â  Â  Â  Â  610,000
8,310
$
53,000 $
1,? 2Q,$ Og<$.<
35,000 $
75,000 $
50,000 $
2,500 $
2,500 $
5,300 $
8,016 $
5,000 $
3,413,658
293,216
.. /:. j, Â  ~'~ IZQgj{
129,762
1,656,019
425,947
85,660
34,528
255,068
108,217
132,193
Chart 2 E9- 1- 1 Wireless Phase I II
Actual and Projected Expenditures
FY06 - FY11
July 2006
Cochise $ 426,812 $ 450,000 $ 876,812
. Coconino $ 282,240 $ 250,000 $ 532,240
Gila $ 28,240 $ 200,000 $ 228,240
Gila River Tribal $ 32,550 $ 225,000 $ 257,550
Graham $ 70,633 $ 225,000 $ 295,633
Greenlee $ 26,080 $ 50,000 $ 76,080
La Paz $ 26,080 $ 177,909 $ 203,989
Maricopa $ 3,348,090 $ 500,000 $ 3,848,090
Mohave $ 252,226 $ 75,000 $ 327,226
Navajo/ Apache $ 34,360 $ 107,337 $ 141,697
Page $ 99,500 $ 50,000 $ 149,500
Pima $ 1,660,069 $ 400,000 $ 2,060,069
Pinal $ 394,744 $ 75,000 $ 469,744
Santa Cruz $ 87,318 $ 40,000 $ 127,318
Winslow $ 33,629 $ 30,000 $ 63,629
Yavapai No $ 262,256 $ 40,000 $ 302,256
Yavapai So $ 5,211 $ 125,000 $ 130,211
Yuma $ 133,552 $ 125,000 $ 258,552
Totals $ 40,850,405 $ 12,009,913 $ 52,651,291
. I PII Implementation
State of Arizona
9- 1- 1
Phase II Wireless
Implementation
Plan
Updated 9/ 15/ 07
Version 4
STATE OF ARIZONA
DEPARTMENT OF ADlVIINISTRATION
STATE 9- 1- 1 OFFICE
Phase II Wireless
Implementation Plan
State of Arizona
Phase I & II Wireless
Implementation Plan
Table of Contents
A.
B.
C.
D.
E.
F.
G.
Authority
History ofWire Line & Wireless 9- 1- 1 in AZ
Considerations
Rules & PSAP/ County Requirements
Network Design
Deployment Schedule
Glossary
2
3
6
8
15
16
17
Attachment A - " Standard" Phase 1Service Agreement
Senate Bill 800 & AZ Revised Statute 12- 713
Attachment B - Current FiscalYear Wireless Budget
Attachment C - Deployment Schedule
Attachment D - Arizona GIS Standards
Updated 9/ 15/ 07 1
A.
Phase II Wireless
Implementation Plan
AUTHORITY
The Federal Communications Commission ( FCC) began to explore the
possibilities of extending Enhanced 9- 1- 1 ( E9- 1- J) service to wireless
communications systems with FCC Docket No. 94- 102. In a Report and Order
issued on July 26, 1996 ( FCC 96- 264), the FCC ordered that the development and
implementation ofE9- 1- 1 service for wireless communications systems be
accomplished in two phases.
Phase I ofthe requirement specifies that wireless E9- 1- 1 calls provide Automatic
Number Identificatiqn ( ANI) and the location of the base station or cell site
receiving the call. Phase II requires that covered carriers have the capability to
identify the latitude and longitude of a mobile unit making the 9- 1- 1 call, within a
radius of no more than 125 meters in 67 percent of all cases. Wireless carriers
were to be ready to deliver Phase II calls by October of2001. However, an
extension has been given to the carriers until December 2005. To date, there are
still a handful of rural carriers that have requested an extension to their original
waIvers.
The criteria for deployment ofPhase II will be the readiness of the county, as well
as, the availability of9- 1- 1 funds.
The covered carriers are to deliver enhanced wireless service within six months of
receipt of a " Request for Service" letter from the Public Safety community, or
their representative.
In response to the FCC Report and Order, in 2001 the State of Arizona passed
legislation ( House Bill 2625) to develop parity between the wire line and wireless
excise tax and set a rate of $. 37 per month per access/ service line, and to include
cost recovery for carrier services.
Currently there are two tax reductions in the statutes. In FY07 the Excise Tax
reduced to $. 28 and in FY08 reduced again to $. 20. Our updated budget
projections indicate a deficit will occur in FY12.
Arizona's Administrative Code ( Section R2-, 1- 409) defines what costs, subject to
available monies, shall be reimbursed.
Updated 9/ 15/ 07 2
Phase II Wireless
Implementation Plan
B. HISTORY OF WIRE LINE & WIRELESS 9- 1- 1 IN ARIZONA
Wire Line E9- 1- 1
History
1975 - Arizona's first 9- 1- 1 system was installed in the City of Sierra
Vista. Safford and Sedona followed shortly thereafter.
January, 1985 - The City ofTucson was the first Arizona city to
implement Enhanced 9- 1- 1 service.
July 1985 - The Arizona State Legislature adopts the Emergency
Telecommunications Services Revolving Fund. The fund was established
for on- going implementation of emergency 9- 1- 1 systems throughout the
state.
Surcharge
2001- House Bill 2625 develops parity between wire line and wireless,
and the excise tax is increased to $. 37 per month.
Coverage
September 2003 - 100% ofthe state has 9- 1- 1 access, and 96% of
telephone service is served by Enhanced 9- 1- 1.
Wireless E9- 1- 1
History
July 1996 - In a Report and Order issued on July 26, 1996 ( FCC 96- 264),
the FCC ordered that the development and implementation ofE9- 1- 1
service for wireless communications systems be accomplished in two
phases and carriers are entitled to full cost recovery for delivering the
E9- 1- 1 call. The covered carriers were to deliver Phase I calls within six
months ofreceipt of a " Request for Service" letter from the Public Safety
community, or their representative. Covered carriers were to be ready to
deliver Phase II calls by October of 2001..
1998 - Arizona's first Phase I Wireless project is kicked off in Pima
County.
1999 - Verizon Wireless is the first Phase I compliant wireless service
provider in Pima County.
Updated 9/ 15/ 07 3
Updated 9/ 15/ 07
Phase II Wireless
Implementation Plan
2000 - As recommended by the FCC in their 1996 ruling, the State of
Arizona passed legislation allowing the wireless carriers full cost
recovery. Within a week ofthat legislation being placed into law, the
FCC reversed their cost recovery decision. They wrote, " disputes about
the meaning ofthe cost recovery mechanism have become a significant
impediment to implementation of Phase I". The agency therefore
determined to " delete from the E911 rules the condition that requires a
cost recovery mechanism for carriers to be in place before a wireless
carrier is obligated to implement E91l".
2002 - Pima County's Phase I project is completed with 8 wireless carries
providing Phase I service.
August 2002- The State's 9- 1- 1 Office begins a project to deploy Phase I
wireless statewide.
2003 - Pinal County completed implementation ofPhase I service with 8
wireless service providers.
2003 - Graham County completed implementation ofPhase I service with
2 wireless service providers.
2004 ~ Santa Cruz County completed implementation ofPhase I service
with 7 wireless service providers.
2005 - The City ofPage, E9- 1- 1 system and the City of Winslow, E9- 1- 1
system completed implementation of Phase I service.
February 2005 - Pima County completed implementation ofPhase II with
the exception ofTier III provider, Coronet.
September 2005- Maricopa completed implementation ofPhase II with
exception ofTier III provider, Coronet.
October 2005 - GIS work underway for compliance in Graham, Pinal and
Santa Cruz counties for deployment of Phase II
April 2006 - Northern Yavapai County completed implementation of
Phase II. This area consists ofthe Sedona, Camp Verde and Cottonwood
and surrounding Yavapai County.
April 2007- Santa Cruz County completed implementation ofPhase II.
June 2007 - Graham County completed implementation of Phase II
4
Updated 9/ 15/ 07
Phase II Wireless
Implementation Plan
Surcharge
1997 - Senate Bi111441 adds a $. 10 per month excise tax on wireless
servIce.
2001 - House Bi112625 develops parity between wire line and wireless,
and the excise tax is increased to $. 37 per month.
2006 - Excise tax reduced to $. 28 per month beginning July 1, 2006.
2007 - Excise tax reduced to $. 20 per month beginning July 1,2007. The
Department ofRevenue converted the collection methodology to include
wire line, wireless and Voice over Internet Protocol ( VoIP) based on their
interpretation of existing statute.
Coverage
Approximately 80% of the population base is Phase II. During fiscal year
2008, Pinal, Cochise and Southern Yavapaicounties are scheduled for
implementation to Phase II.
Phase 1-
Pinal County
City ofPage
City ofWinslow.
Phase II-Graham
County
Santa Cruz County
Maricopa Region includes Apache Junction
Pima County
Northern Yavapai County
5
Phase II Wireless
Implementation Plan
C. CONSIDERATIONS
In order to deliver or Phase II Wireless service to Arizona's public safety
community there are a number of issues that need consideration.
Funding
First and foremost, funding must be available to cover the projected costs.
Fortunately, with the signing of House Bill 2625 ( May 2001), Governor Hull
increased the wire line excise tax from 26 cents to 37 cents per access line. That
same legislation mandated that wireless service lines should be taxed at the same
rate. This increase made strides to ensure that the project would be sufficiently
funded.
Within the 2001 legislation, stipulations were also made to reduce the tax basing
the conclusion that system Phase II deployment would be completed by FY2008.
The current projections for total statewide deployment will extend the date to
FY2011 and implementation is subject to progress being made by local
jurisdictions.
Technology Platform
A second consideration is ensuring that, within budget parameters, the most
effective and efficient enhanced wireless system is deployed, A key issue is
ensuring that all wireless 9- 1- 1 calls, along with their associated data, can be
transferred without delay to other PSAPs in the state. Further, it is necessary that
the systems have the ability to transfer the wireless call to another PSAP's wire
line and! or wireless 9- 1- 1 network.
Based on expertise level and customer preference, all counties in the state ( with
the exception of Maricopa County) will utilize a network solution. That is, the
wireless platform will be built around a Local Exchange Carrier's ( LEC's)
enhanced wireless offering.
Maricopa Region decided to utilize a private switch solution which would better
serve their technical and financial needs.
Frontier Communications serves parts ofApache and Navajo County, and all of
Mohave County. In order to provide these entities with Phase II service, Frontier
is currently in the process of upgrading their platfonn around CML Selective
Routers.
Updated 9/ 15/ 07 6
Phase II Wireless
Implementation Plan
Phase I versus Phase II
If a county is ready to receive Phase II service - i. e., they have developed an
MSAG ( Master Street Address Guide) valid GIS ( Geographic Information
System) file and there are processes in place to keep it current ~ then Phase II will
be deployed ifrequested by the county ( funds permitting). If the county has not
completed that task, Phase I will be deployed.
Updated 9/ 15/ 07 7
Phase II Wireless
Implementation Plan
FCC Mandated Prerequisites
The FCC ( Federal Communications Commission) has ruled that a PSAP shall
document their ability to receive and utilize the E9- 1- l data being requested.
Therefore, the PSAP must meet, and in some cases exceed, the prerequisites set
forth.
Deployment Schedule .
Deployment can only be achieved through a phased approach. Therefore, the
sequence of deployment is also a consideration. The State's 9- 1- 1 Office has
developed a schedule ( Section 1) which uses greatest need and regional
efficiencies as the criteria for deployment. In addition, the agreement, readiness,
and cooperation of the individual PSAPs also came into play.
Project Management
The State ofArizona's 9- 1- 1 Office has resources available to provide project
management for Phase I and PhaseTI projects. Those resources will be made
available as defmed in the deployment schedule ( Section 1).
Should a County/ 9- 1- 1 jurisdiction choose to manage the project themselves, that
is acceptable. The rules and requirements stated in this document still apply.
Should a County/ 9- 1- 1 jurisdiction reject the rules and/ or requirements stated in
this document, the State of Arizona's 9- 1'" 1 Office will not provide proj ect
management support. Penalties defined or not defined, fiscal and otherwise, will
be borne by the County/ 9- 1- 1 jurisdiction.
Updated 9/ 15/ 07 8
Phase II Wireless
Implementation Plan
D. RULES & PSAP/ COUNTY REQUIREMENTS
Although the State's 9- 1- 1 Office will manage the Phase I and II projects, the
public safety community has a role and responsibilities as well. Following are the
PSAP/ county requirements that will be used to administer the project.
Qualified Applicants
Since Phase I and II technologies require an ALI display, deployment will be
offered only to those PSAPs that are fully Enhanced ( receiving both ANI and
ALI). PSAPs that have Basic or Enhanced with ANI Only service will not qualify
for enhanced wireless until they are upgraded to fully Enhanced service with their
wire line service.
9- 1- 1 Wireless Administrator
Each county/ wireless 9- 1- 1 system will identify a person that will serve as their
single point ofcontact. This person will beknown as the " 9- 1- 1 Wireless
Administrator" and will be responsible to:
• Work with PSAPs within their wireless system, and as necessary with 9- 1 1
Wireless Administrators from adjoining counties, to ensure that the
wireless needs of all PSAPs are being met.
• Organize and attend related project meetings.
• Drive/ make the decisions relevant to the project, including routing and
network design.
• Serve as the " single point of contact" to the State's 9- 1- 1 Office, wireless
service providers ( WSPs), and other individuals/ organizations involved in
delivery ofEnhanced Wireless service.
• Determine whether service agreements are appropriate; and if so, negotiate
contacts.
• Ensure that PSAP personnel are provided the information necessary to
handle Phase 1 and/ or Phase II calls.
• Complete a Wireless 9- 1- 1 Service.
• Continue to manage, on a going forward basis, the relationship with the
. wireless service providers.
Note: Some of the aforementioned tasks will need input from the respective
PSAPs in the county. It will be the 9- 1- 1 Wireless Administrator's responsibility
to work with the PSAPs to ensure decisions are made, and tasks are performed.
Updated 9/ 15/ 07 9
Phase II Wireless
Implementation Plan
Note: If the 9- 1- 1 system will not name a 9- 1'- 1 Wireless Administrator, the
State's 9.,. 1- 1 Office will not provide project management support. If the
9- 1- 1 system does fill that position, but the person fails to perform the
assigned tasks, the 9- 1- 1 Office will stop project management of that system's
enhanced wireless deployment until another person is named and gets
engaged in his/ her assigned responsibilities. In the event that the 9- 1- 1 Office
does not provide project management support, all responsibilities will fall to
the PSAP( s)/ 9- 1- 1 system. Additionally, any costs incurred because of non performance
or unreasonably slow performance by the 9- 1- 1 Wireless
Administrator, and/ or his representatives, will be the responsibility of the
county ( versus Arizona's 9- 1- 1 Fund).
Countywide Deployment
All applicable PSAPs ( those that will receive Phase I or Phase II wireless calls)
within a given county will work together so that:
• Decisions regarding routing are agreed to by all involved, and
• Implementation of enhanced wireless service can be accomplished at the
sarnetime, countywide
To facilitate this, it may be appropriate that the 9- 1- 1 Wireless Administrator
heads a working group represented by all applicable PSAPs.
Network Design Decisions
The 9- 1- 1 Wireless Administrator will facilitate decisions concerning network
design. Each PSAP has options concerning how they want to receive wireless
9- 1- 1 calls. The option is are:
• Receive wireless calls over the existing wire line EM trunks ( selective
router to PSAP) or
• Receive wireless calls over a new set of EM trunks ( selective router to
PSAP) dedicated to wireless.
Additionally, depending on the 9- 1- 1 platform being utilized, there may be the
necessity to design ALI circuits and/ or interoffice circuits.
Routing
The 9- 1- 1 Wireless Administrator will facilitate decisions concerning routing.
There should be collective agreement between all PSAPs in the county regarding:
• Which PSAPs will be a " primary" wireless PSAP, and which will serve as
" secondary" wireless PSAP. The choice of primary or secondary does not
need to follow suit with the choices made in the wire line environment.
• Which PSAP will receive the call for each cell site and/ or each cell face.
Updated 9/ 15/ 07 10
Phase II Wireless
Implementation Plan
Phase 1/ 11 Service Agreements
Each 9- 1- 1 Wireless Administrator will be responsible to work with the
appropriate people within their county to determine whether they wish to pursue
service agreements with the WSPs. If they do, the responsibility ofpresenting,
negotiating, and finalizing those agreements are the total responsibility of the
9- 1- 1 Wireless Administrator. The 9- 1- 1 Office will serve as a resource;
however, will not manage nor negotiate the c01?- tracts.
The 9- 1- 1 Office has worked with Pinal County's legal division to develop a
" standard" Phase I agreement ( Attachement A). If desired, this agreement can be
used by the County to negotiate service.
Indemnity protection has been provided to the PSAPs under federal and state
legislation. Senate Bill 800 and Arizona Revised Statute 12- 713 is provided, in
part, in Attachment A.
Non- Disclosure Agreements ( NDA)
As with the service agreement, the 9- 1- 1 Office will not manage nor negotiate a
NDA on behalf ofthe county - that will be the responsibility of the 9- 1- 1
Wireless Administrator.
It should be noted that if the county decides to pursue a service agreement and
uses the " standard" agreement in Attachment A, there is non- disclosure language
included in that agreement.
Payment Responsibility
Each 9- 1- 1 system and/ or county will be responsible to receive and process bills
with the State of Arizona's 9- 1- 1 Office in the same manner as they manage their
wire line 9- 1- 1 service.
Wireless Service Plan
Arizona's Administrative Code states that a service plan shall be submitted as part
of the County/ 9- 1- 1 jurisdiction application for funds. This process holds true for
both wire line and wireless funding. The wireless service plan should be started
prior to the Request for Service Letter being sent and should continue to be
developed ( as information becomes available) throughout the project.
Completion of the planshould coincide with the completion of the project.
Updated 9/ 15/ 07 11
Phase II Wireless
Implementation Plan
Equipment Requirements
In order for a PSAP to qualify for Phase I or Phase II service, that
communications center must ensure that: .
• TheirPSAP equipmentis capable ofreceiving Phase I ALI fields. ( Ifon
the Qwest platform ALI formats - 30B, 30C, 30D and 30W meet the
requirements.)
• Their PSAP equipment is capable ofreceiving 10- digit ANI.
• Their PSAP equipment is equipped to receive new EM trunks, ifnew EM
trunks are requested.
• A GIS ( Graphic Information System) file and mapping equipment is in
place if requesting Phase II service.
Meeting FCC Mandated Prerequisites
The FCC has established rules that must be met and documented by the PSAP
prior to the agency requesting Phase I or Phase II service. Those three rules, and
Arizona's requirements relevant to those rules, follow:
Rule # 1- Funding Mechanism
• FCC Rule:
A funding mechanism must exist for recovering the PSAP's cost for the
facilities and equipment that are necessary to receive and utilize the
E9- 1- 1 data elements'being requested.
• PSAP's Responsibility Regarding . Meeting Rule # 1
Phase I & II Wireless Implementations
A) This requirement is met for Phase I & II. The following Arizona
Revised Statues provides the funding mechanism required.
ARS Â  41 Emergency Telecommunications Services; Administration;
Revolving Fund 41- 704, B.
Rule # 2 - Equipment Requirement
• FCC Rule:
ThePSAP has ordered the equipment necessary to fulfill its obligations,
and that equipment is already installed or is scheduled to be installed and
operable by the end of the six- month period ( e. g:, provide a list of
facilities and copies of relevant purchase orders, with purchase orders
demonstrating commitment to vendor performance within six month
period or othersubstantiation ofvendor commitment to perform within six
month period).
Updated 9/ 15/ 07 12
Phase II Wireless
Implementation Plan
• PSAP's Responsibility Regarding Meeting Rule # 2
Phase I & II Wireless hnplementations
A) This implementation plan requires that a PSAP be fully Enhanced in
the wire line environment ( i. e., the PSAP receives both ANI and ALI)
before the State's 9- 1- 1 Fund will reimburse for Phase I or II costs.
Therefore, a fully Enhanced PSAP automatically meets this requirement
since the call center is already provisioned with the necessary equipment,
as well as, ALI circuits and data stream to receive Phase I features.
Phase II Wireless hnplementations
A) In order to meet this requirement certain. equipment and features
( which are not necessary fOf wire line E9- 1- 1 or Phase I Wireless) must be
provisioned. Specifically, a data stream that will allow the delivery of the
X and Y coordinates ( for PSAPs served by Qwest's 9- 1- 1 service, this is
the 30W ALI data stream). Plus, mapping equipment to capture and
pinpoint the XJY coordinates ( a. k. a. latitude and longitude).
B) There is a widely accepted interpretation regarding meeting this rule.
Some reason that the PSAP needs to be able to receive the X and Y
coordinates; but that the PSAP does not need electronic/ digital equipment
to receive and pinpoint the coordinates. It is argued that tools such as
paper maps or manually accessed web sites can serve as the equipment.
The State of Arizona's 9- 1- 1 Office, and this plan, does nottotally accept
this interpretation.. Rather, Arizona's criteria are as fgllows:
1) All call centers that serve as a Primary PSAP for wireless 9- 1- 1
calls, must have electronic/ digital equipment in place at the time
the " Request for Service" letter is sent to the WSP. This
equipment can be a component of the PSAP's 9- 1- 1 equipment, or
a component of the CAD ( Computer Aided Dispatch).
2) In addition, that Primary PSAP must also have the data stream that
receives the X and Y coordinates ( in Qwest's environment that's
30W) provisioned and working at the time the Request for Service
letter is sent.
3) Call centers that serve as a Secondary PSAP for wireless 9- 1- 1
calls, are not required to have equipment in place before the
request letter is sent. However, that PSAP must be in the
planning/ implementation stage ofprovisioning electronic/ digital
mapping equipment - with tum- up set two months prior to the end
of the WSP's 6- month window. ( In other words, the target date for
turn- up ofthis equipment should be no more than 4 months from
the date of the request letter.)
4) The same conditions that are outlined for mapping equipment in a
SecondaryPSAP ( above in section 3) apply to the implementation
of the X and Y coordinates.
Updated 9/ 15/ 07 13
Updated 9/ 15/ 07
Phase II Wireless
Implementation Plan
C) It is very important to note that if the Secondary PSAP( s) can
not receive the XN coordinates or have their mapping equipment
completely installed and operational 6 months from the date of the
request letter, there will be financial penalties. From the date that
the 6 month installation period ends, until the date that all
Secondary PSAPs have fully met the equipment and data stream
requirements, the State's 9- 1- 1 Fund will not reimburse the Qwest
Communications' or Wireless Service Providers' monthly costs
. associated with Phase II. These amounts are substantial and will
fall to the County/ 9- 1- 1 jurisdiction to pay. Additionally, should the
WSPs or FCC assign financial penalties because the 9- 1- 1 system is
not ready, these cost will also fall to the County/ 9- 1- 1 jurisdiction.
Phase II Wireless Implementations
A) Two necessary and critical equipment components of Phase I and
II service are the selective router and ALI database. When a PSAP
chooses to l\. tilize an existing 9- 1- 1 platform, such as provided by Qwest
Communications, those components   are in place and operational and
need no consideration. Should, however, a PSAP/ jurisdiction determine
that it is in their best interest to provision and/ or own their own 9- 1- 1
platform then these components must be considered. Specifically, the
selective router should be installed and accepted by the customer before
the Request for Service letter is sent, with the ALI database ready to
accept records at that time.
B) If the timeline defined above is not adhered to, and the
PSAP( s)/ jurisdiction are not ready to accept service when the
wireless service provider( s) are ready to deliver it, there will be
financial penalties. Specifically, from the. date that the 6 month
installation period ends, until the date that the selective router is
fully operational ( including all associated network components) and
the ALI database is loaded and operational, the State's 9- 1- 1 Fund
will not reimburse the Qwest Communications', Wireless Service
Providers, or other related vendors the monthly costs associated
with the service. These amounts are substantial and will fall to the
County/ 9- 1- 1 jurisdiction to pay. Additionally, should the WSPs or
FCC assign fmancial penalties because th~ 9- 1- 1 system is not ready,
these cost will also fall to the County/ 9- 1- 1 jurisdiction.
14
Phase II Wireless
Implementation Plan
Documentation ofMeeting Equipment Requirements
A) Because the wireless service providers request documentation
relevant to the PSAP's status, the 9- 1- 1 Wireless Administrator must
compile information ( per PSAP) relevant to their mapping equipment,
ALI data stream, and ( where appropriate) selective router status. ( A
form will be provided by the State's 9- 1- 1 Office to meet this need.)
Rule # 3 - LEC Trunking
• FCC Rule:
The PSAP has made a timely request to the proper LEC for the facilities
and any facility related equipment necessary to receive and utilize Phase I
and II data elements ( e. g., letter ofrequest and any pertinent
correspondence between the PSAP and the LEC).
• PSAP's Responsibility Regarding Meeting Rule # 3
Phase I & II Wireless Implementations
A) Relevant to the Qwest 9- 1- 1 platform, the only network facility
that might apply is the addition and/ or rearrangement of EM trunks ( trunks
between the selective router and the PSAP). These trunks must be ordered
shortly before, or after, the Request for Service letter, with tum- up
targete~ in the middle of the six- month implementation period. It may
also be necessary to order trunk interface cards ifthe PSAP is increasing
their total number of EM trunks.
B) Relevant to a 9- 1- 1 platform where the networking ( i. e., ALI
circuits and interoffice facilitIes) is not already in place, those facilities
must be ordered 30 days prior to the Request for Service Letter is sent
with an installation date set for 4 months prior to the six- month end date.
Addditonal State of AZ Phase II Requirements
A) A GIS file that meets all requirements set forth in Arizona
Standards ( Attaclunent D)
B) A GIS file that is complete for all areas served by Phase II
C) A process in place to maintain and distribute updates to GIS
D) An approved Wireless 9- 1- 1 Service Plan
E) Sufficient funds in the State's 9- 1- 1 Fund to cover Phase II costs
To facilitate this, it may be appropriate that the 9- 1- 1 Wireless Administrator
heads a working group represented by all applicable PSAPs.
Updated 9/ 15/ 07 15
Phase II Wireless
Implementation Plan
E. NETWORK DESIGN
Non- Call Path Associated Signaling
The network technology that will be utilized to deliver the Phase I wireless calls
in Arizona will be a form ofthe Non- CalI- Path Associated Signaling ( NCAS
solution ( the specific solution will be the call ofthe WSP). Arizona's PSAPs are
not provisioned to receive a CAS ( Call- Path Associated Signaling).
Wireless Service Providers Network
The wireless service providers will have the option of connecting to the selective
router with Signaling System Seven ( SS7) or with CAMA Enhanced MF trunks.
They will also be free to elect the Service Control Point ( SCP) vendor and
database vendor of their choice.
Routing
Routing for Phase I wireless calls will be determined by the location of the tower
receiving the E9- 1- 1 call. The call will be routed to a pre- determined PSAP based
on location of the tower within an E9- 1- 1 area. In cases where the tower isin
close proximity to two or more E9- 1- 1 service areas; and the tower has a
three- sector antenna; and if a majority of one of the sectors lies in a different
E9- 1- 1 service area, routing can be done based on tower sectors.
Routing Phase II will be determined by the location of the wireless caller. A
CRDB ( Co- ordinate Routing Database) is part of the Phase II network
configuration and will facilitate routing.
It will be responsibility ofthe public safety community to work with the carrier to
designate the appropriate routing and response boundaries.
EM Trunks ( a. k. a. 9- 1- 1 Trunks)
The trunks delivering calls from the selective router to the PSAP are known as
EM trunks~ Each PSAP has a trunk group oftwo or more trunks for their wire
line E9- 1- 1 calls. Each PSAP that will receive Phase I or Phase II calls will be
given the option to utilize the existing EM trunk group for wireless calls ( in
addition to the existing wire line calls), or to install a new set ofEM trunks that
will be used only for wireless call delivery.
With the assistance ofQwest, the provider ofthose trunks, the PSAP will also
determine the appropriate size ofthose trunk groups.
Updated 9/ 15/ 07 16
Phase II Wireless
Implementation Plan
F. DEPLOYMENT SCHEDULE
The deployment schedule, is updated annually using ( 1) greatest needs ( 2)
regional efficiencies and ( 3) , PSAP agreement, readiness and cooperation as the
criteria. Available funding is also ensured.
The most recent schedule was included with the April 2007 report and has been
reviewed and included in this report. '
Deployment is only scheduled for those areas currently, or soon to be, provisioned
, with Enhanced 9- 1- 1 service. As other 9.;. 1- 1 systems become Enhanced, they
will be added to the schedule.
Updated 9/ 15/ 07 17
Phase II Wireless
Implementation Plan
G. GLOSSARY
Following is a listing ofrelevant definitions and abbreviations that are contained
in this plan.
Access Line - means the telephone service line which connects a subscriber's
main telephone( s) or equivalent main telephone( s) to the telephone company's
switching office.
Automatic Location Identification ( ALI)- means a system capability that
enables an automatic display of information defining a geographical location of
the telephone used to place the 9- 1- 1 call.
Automatic Number Identification ( ANI) - means a capability that enables the
automatic display of the number of the telephone used to place the 9~ 1- 1 call.
Call Attendant - means the person who initially answers a 9- 1- 1 call.
Call Transfer - means the call attendant determines the appropriate responding
agency and transfers the 9- 1- 1 caller to that agency.
Central Office ( CO) - means a telephone company facility that houses the
switching and trunking equipment serving telephones in a defined area.
Centralized Automated Message Accounting ( CAMA) - An MF signaling
protocol originally designed for billing purposes, capable of transmitting a single
telephone number.
Customer Premises Equipment ( CPE) - Terminal equipment at a PSAP.
Emergency Call - means a telephone request for service which requires
. immediate action to prevent loss of life, reduce bodily injury, prevent or reduce
loss of property and respond to other emergency situations determined by local
policy.
Emergency Service Number ( ESN) - A three to five digit number representing a
unique combination of emergency service agencies designated to serve a specific
range of addresses within a particular geographical area. The ESN facilitates
selective routing and selective transfer, if required, to the appropriate PSAP and
the dispatching of the proper services.
Enhanced 9- 1- 1 ( E9- 1- 1) - means the general term referring to emergency
telephone systems with specific electronically controlled features, such as ALI,
ANI, and selective routing.
Updated 9/ 15/ 07 18
Phase II Wireless
Implementation Plan
Exchange - means a defined geographic area served by one or more central
offices in which the telephone company furnishes services.
Feature Group D ( FGD) - An MF signaling protocol, originally developed to
support equal access to long distance services, capable of carrying one or two ten
digit telephone numbers.
Implementation - means the activity between the formal product/ delivery
agreement reached by the PSAPs and the carriers, and commencement of
operations.
Integrated Services Digital Network ( ISDN) - A digital interface providing
multiple channels for simultaneous functions between the network and CPR
Mobile Directory Number ( MDN) - The callback number associated with a
wireless phone.
Mobile Switching Center ( MSC) - The wireless equivalent of a Central Office,
which provides switching functions from wireless calls.
Multi- Frequency ( MF) - A type of signaling used on analog interoffice and 9- 1Â 1
trunks.
Local Exchange Carrier ( LEC) - A telecommunications carrier under the
state/ local Public Utilities Act that provide local exchange telecommunications
servIces.
9- 1- 1 Call- means any telephone call that is made by dialing the digits 9- 1- 1.
9- 1- 1 System - means a telephone system that automatically connects acall~ r,
dialing the digits 9- 1- 1, to a PSAP.
Nonrecurring Costs - means one- time charges incurred by a joint E9- 1..; 1 service
board or operating authority including, but not limited to, expenditures for E9- 1- 1
service plan preparation, surcharge referendum, capital outlay, installation, and
initial license to use subscriber names, addresses and telephone information.
One- Button Transfer - means another term for a ( fixed) transfer which allows
the call attendant to transfer an incoming call by pressing a single button. For
example, one button would transfer voice and data to a fire agency, and another
button would be used for police, also known as " selective transfer."
Phase I, Wireless 9- 1- 1 Service - means an emergency wireless telephone system
with specific electronically controlled features such as ANI, specific indication of
wireless communications tower site location, selective routing by geographic
location of the tower site.
Updated 9/ 15/ 07 19
Phase II Wireless
Implementation Plan
Phase II, Wireless 9- 1- 1 Service - means an emergency wireless telephone
system with specific electronically controlled features such as ANI and ALI and
selective routing by geographic location ofthe 9- 1- 1 caller.
Political Subdivision - means a geographic or territorial division of the state that
would have the following characteristics: defmed geographic area, responsibilities
for certain fimctions oflocal government, public elections andpublic officers, and
taxing power. Excluded from this definition are departments and divisions of
state government and agencies ofthe federal government.
Provider - means a person, company or other business that provides, or offers to
provide, 9- 1- 1 equipment, installation, maintenance, or access services.
Pseudo Automatic Location Identification ( pALl) - An ALI record associated
with a pANI, configured to provide the location of the wireless cell of sector and
information about its coverage or serving area.
Pseudo Automatic Number Identification ( pANI) - A telephone number used
to support routing ofwireless 9- 1- 1 calls. It may identify a wireless cell, cell
sector ofPSAP to which the call should be routed.
Public or Private Safety Agency - means a unit of state or local government, a
special purpose district, or a private firm, which provides or has the authority to
provide firefighting, police, ambulance, or emergency medical services.
Public Safety Answering Point ( PSAP) - means a 24- hour, state, local, or
contracted communications facility, which has been designated by the local
service board to receive 9- 1- 1 service calls and dispatch emergency response
services in accordance with the E9- 1- 1 service plan.
Public Switched Telephone Network - means a complex of diversified channels
and equipment that automatically routes communications between the cCj. lling
person and called person or data equipment.
Recurring Costs - means repetitive charges incurred by a joint E9- 1- 1 service
board or operating authority including, but notlimited to, database management,
lease of access lines, lease of equipment, network access fees, and applicable
maintenance costs.
Selective Routing ( SR) - means an enhanced 9- 1- 1 system feature that enables all
9- 1- 1 calls originating from within a defined geographical region to be answered
at a pre- designated PSAP. .
Updated 9/ 15/ 07 20
Phase II Wireless
- Implementation Plan
Service Control Point ( SCP) - means a centralized database system used for,
among other things, wireless E9- 1- 1 service applications. It specifies the routing
of 9- 1- 1 calls from the cell site to the PSAP and includes all relevant cell site
location information.
Signaling System 7 ( SS7) - An inter- office signaling network separate from the
voice path network, utilizing high- speed data transmission to accomplish call
processmg.
Subscriber - means any person, firm, association, corporation, agencies of
federal, state and local government, or other legal entity responsible by law for
payment for communication service from the telephone utility.
Tariff - means a document filed by a telephone company with the state telephone
utility regulatory commission that lists the communication services offered by the
company and gives a schedule for rates and charges.
Telecommunications Device for the Deaf ( TDD) - means any type of
instrument, such as a typewriter keyboard connected to the caller's telephone and
involving special equipment at the PSAP which allows an emergency call to be
made without speaking, also known as a TTY.
Trunk - means a circuit used for connecting a subscriber to the public switched
telephone network.
Wireless Communications Service - means cellular, broadband pes, and SMR
that provide real- time two- way interconnected voice service, the networks of
which utilize intelligent switching capability and offer seamless handoff to
customers. This definition includes facilities- based service providers and non facilities
based resellers. For purposes ofwireless 9- 1- 1 surcharge, wireless
communications service does not include services whose customers do not have
access to 9- 1- 1, or a 9- 1- 1- 1ike service, a communications channel utilized only
for data transmission, or a private telecommunications system.
Wireless Communications Surcharge - means a surcharge imposed on each
wireless communications service number provided in this state and collected as
part of a wireless communications service provider's monthly billing to a
subscriber.
Wireless Service Provider ( WSP) - a communications carrier who provides
wireless service.
Updated 9/ 15/ 07 21
State of Arizona 9- 1- 1
GIS Standards
Updated 9- 13- 2007 .
Arizona 9- 1- 1 GIS Standards
Document Description and Purpose ,. 2
GIS Data Requirements,. .. '"'''''''''''''''''' .,... ,..~,..,. .,.,.,.,.. ,.,.,..,. ,. ,.,..,.,. 2
Required GIS Data Layers ~. 3
Street Centerline ; 3
ESNIESZ Boundaries 4
Community Boundaries 4
Other Useful GIS Layers ( not required) ; 4
Metadata ; 5
Special Situations - Native American Communities 5
Spatial Accuracy Requirements ..,..,..,.,..,. ,.,.,.,.,.; ,..; ,.,..;.,.,.;,.,.,. 6
Data Collection ; 6
Map Projection ; 6
Attribute Accuracy Requirements.,.,...,. ,..,. ,. ,. ,...,. ,.. 7
Street centerlines 7
ESN and Community boundaries 7
Testing Methods 8
Data Sharing ,. ; ; ; 8
Ongoing GIS Maintenance ,.,. .. ,. ,..,. ,.,. ..,.,..,. ,. 8
APPENDIX A ,. ,. ,..,... ,...;.,..,..;.. ,. ,. ;,. ,... ,. ,...,..,. 10
APPENDIX B ,..,. ,.,...,... ,. ,.,. ,.,. ,..,.,.,. ,.,..,... ,. ,. 23
Prepared by: Adam Iten, AZ 911 Office 1
Updated: 9- 13- 2007
Arizona 9- 1- 1 GIS Standards
Document Description and Purpose
This document contains the State of Arizona's 9- 1- 1 Geographic Infonrtation System
( GIS) standards. These standards were developed for two reasons; 1) to ensure a high
level of accuracy for State funded mapped ALI systems and 2) to assist each 9- 1- 1
system with their GIS/ mapped ALI endeavors.
The State ofArizona Phase I & II Wireless Implementation Plan states:
If a county is ready to receive Phase II service - i. e., they have developed
an MSAG and valid GIS file and there are processes in place to keep it
current - then Phase II will be deployed if requested be the county ( funds
permitting). .
The purpose ofthis document is to define a " valid GIS file". This document also
contains GIS requirements for 9- 1- 1 systems that plan to upgrade to mapped ALI ( i. e.,
mapping on wire line calls).
NOTE: 9- 1- 1 Systems that were installed prior to these standards being put in place must
still. adhere to the GIS requirements listed below. Their GIS data will be evaluated and
deadlines will be set for making modifications.
These standards have been developed during a period when no national standards are in
place. Should national standards be developed and approved, Arizona's 9- 1- 1 Office will
evaluate those standards and make modifications to AZ's standards, as deemed
appropriate.
GIS Data Requirements
In order to have an effective, fully operational Mapped ALI/ Dispatch mapping software
program, three GIS data layers are required for use with the mapped ALI software.
These data layers include the street centerlines, Emergency Service Number
( ESN)/ Emergency Service Zone ( ESZ) boundaries, and community boundaries. There
are also certain data layer attributes that are required for these data layers to be effective.
The required data attributes for these GIS data layers are listed below. In addition, the
NENA GIS Data Model can be found in APPENDIX A. This model may be helpful to
agencies that are modifying or creating new GIS layers for use in 9- 1- 1 and/ or public
safety.
Prepared by:. Adam Iten, AZ 911 Office 2
Updated: 9- 13- 2007
Arizona 9- 1- 1 GIS Standards
Required GIS Data Layers
Mapped ALI software requires three GIS data layers to function properly. The three
layers are street centerlines, ESNIESZ boundaries, and community boundaries. The
specific field requirements for these layers are outlined below.
Street Centerline
1. Must include the following fields ( see APPENDIX A for field names, type, and
length): .
a. Prefix Directional
Examples: N, S, E, W
b. Street Name
Examples: Main, 1ST, Jefferson
c. Street Type
Examples: Rd, Ave, Blvd
d. Suffix Directional
Examples: N, S, E, W
e. Left From Address
Examples: 1, 101, 1200
f. Left To Address
Examples.' 99, 199, 1298
g. Right From Address
Examples: 2, 100, 1201
h. Right To Address
Examples: 98, 198, 1299
1. LeftESN and/ or Left Community
Examples: 100, PHX
j. RightESN and/ or Right Community
Examples: 100, PHX
Other Recommended Fields:
k. Oneway ( if oneways exist)
Examples: Y, N, 1, 0
1. Alias Street Name ( if one or more streets contain multiple names)
Examples: WMarconi Ave
m. Road Classification
Examples: 1,2,3, A, B, C
n. Source ofUpdate
Examples: AI, adamiten
o. Date ofUpdate
Exampks: 20041222
Prepared by: Adam Iten, AZ 911 Office 3
l] pdated: 9- 13- 2007
Arizona 9- 1- 1 GIS Standards
ESN/ ESZ Boundaries
1. Must include the following fields ( see APPENDIX A for field type and length):
a. ESN
Examples: 100, 201, 286
b. PSAPName
Examples: Sedona FD, Yuma PD
c. Fire
Community Boundaries
1. Must include the following fields ( see APPENDIX A for field type and length):
a. Community Name
Examples: Phoenix, Page
Other Useful GIS Layers ( not required)
Address Points: point locations of all addressable sites/ structures
Parcel Boundaries: map layer ofproperty parcel boundaries
Hydrology: lines and polygons depicting water ways
Railroads: lines depicting railroads
Fire Hydrants: point locations of fire hydrants
Mile Markers: point locations ofmile markers
TownshiplRange Boundaries: map layer of township and range boundaries
Emergency Buildings: point locations of emergency buildings
Cell Towers: point locations of cell towers
Cell Coverages: pie- shaped polygons depicting cell coverage areas
Common Places: point locations ofwell known structures and/ or areas
Parks/ Cemeteries: polygons representing park and cemetery locations
Prepared by: Adam ! ten, AZ 911 Office 4
Updated: 9- 13- 2007
Arizona 9- 1- 1 GIS Standards
Metadata
Every 9- 1- 1 System will eventually exchange GIS data with surrounding 9- 1- 1 Systems.
For this reason, it is necessary for agencies to maintain metadata for each GIS data layer
used in the mapped ALI systems.
Metadata, as defined by ESRI:
Information about the content, quality, condition, and other
characteristics ofdata. Metadatafor geographic data may document its
subject matter; how, when, where, and by whom the data- was collected;
accuracy ofthe data; availability and distribution information; its
projection, scale, resolution, and accuracy; and its reliability with regard
to some standard.
A sample GIS metadata form can be found in APPENDIX B. The State of Arizona
requires that the following information be included in your GIS metadata:
Publication Data ( Author and Date): see metadata under Identification
Information
Map Projection: See metadata under Spatial Reference Information
Spatial Accuracy: see metadata under Data Quality Information
Contact Information: see metadata under Identification Information
*** Please contact the State' s 9- 1- 1 GIS Coordinator with any metadata related questions.
Special Situations - Native American Communities
In order to preserve anonymity amongst its community members, Native American
communities may develop their own unique numbering system in place of a typical postal
addressing scheme. The details oftheir unique numbering system must be included in
their 9- 1- 1 Service Plan. The State 9- 1- 1 GIS Coordinator will review the 9- 1- 1 Service
Plans on a case- by- case basis in order to allocate the required map layers. In all cases,
the map layers must be capable of automatically locating at least 95% of 9- 1- 1 callers.
Prepared by: Adam Hen. AZ 911 Office 5
Updated: 9- 13- 2007
Arizona 9- 1- 1 GIS Standards
Spatial Accuracy Requirements
The advent ofFCC Wireless Phase I and II wireless 9- 1- 1 has elevated the importance of
having spatially accurate GIS data. With the implementation of Phase II, the location of
the wireless caller is plotted on a digital map based on Latitude and Longitude ( XY)
coordinates provided to the PSAP via the Automatic Location Information ( ALI). These
XY coordinates will be determined by one ofthree technologies: 1) network- based
( location determiiling equipment on each wireless tower), 2) handset- based ( GPS receiver
on the caller's mobile phone), or 3) combination ofthe network and handset- based
solutions. The FCC has adopted accuracy requirements for the wireless caller's XY.
These requirements are listed below in an excerpt from FCC 01- 351, Fifth Report and
Order:
The FCC adopted accuracy and reliability requirements for ALI as part of
' its rules for wireless carrier enhanced 911 ( E911) service in CCDocket
No. 94- 102, Revision ofthe Commission's Rules to Ensure Compatibility
with Enhanced 911 Emergency Calling Systems. Those rules were
adopted in 1996 and revised in the Third Report and Order in that docket
( released October 6, 1999). The revised rules set the following accuracy
and reliability requirements for E911 Phase II operations:
• For network- based solutions: 100 meters for 67 percent ofcalls, 300
meters for 95 percent ofcalls;
• For handset- based solutions: 50 meters for 67 percent ofcalls, 150
meters for 95 percent ofcalls.
Data Collection
These Arizona GIS standards require that the GIS centerline file be collected at a
minimum of7.6 meters 95% of the time. The scale of vector GIS data must be 1: 24,000
or better and the scale ofraster GIS data ( digital orthoimagery, satellite imagery, etc)
must be 1: 2400 or better. It is recommended that updates to the centerline file be made
with the most spatially accurate data and/ or means available.
Map Projection
In a wireless Phase II environment, the wireless 9- 1- 1 caller's XY coordinates are
provided to the PSAP in a WGS 84 projection. Thus, aIl9- 1- 1 GIS map data must utilize
projections that are capable of displaying WGS 84 projected coordinates.
Prepared by: Adam Iten, AZ 911 Office 6
Updated: 9- 13- 2007
Arizona 9- 1- 1 GIS Standards
Attribute Accuracy Requirements
The attribute information must be accurate in order for 9- 1- 1 calls to locate properly.
Below is a list of attribution accuracy requirements:
Street centerlines
./ The ALI database must have at least a 95% match rate to the GIS centerline
layer
./ Street name elements must be MSAG- valid
./ All street segments must be broken and snapped at street intersections, ESN
boundaries, and community boundaries
./ Direction of street segment must follow real- world ranges
./ Ranges may not overlap
./ " To" range must be greater than " From" range on each street segment
./ Street segments must be free ofparity errors ( i. e. - cannot have both even and odd
ranges on the same side of a segment)
./ Left and right ESN information must match boundary files
./ Divided highways, freeways, and streets ( divided by median) must be depicted as
two line segments
ESN and Community boundaries
./ Must be free of sliver polygons ( i. e. - gaps or tiny unwanted polygons)
./ Must be snapped to street segments
./ ESN boundaries must cover the 9- 1- 1 system's entire response area
Prepared by: Adam Hen, AZ 911 Office 7
Updated: 9- 13- 2007
Arizona 9- 1- 1 GIS Standards
Testing Methods
The GIS tests andvalidations may be performed by the State's 9- 1- 1 GIS
Coordinator or the 9- 1- 1 System's GIS personnel. Before funding will be approved
from the State's 9- 1- 1 Fund, each 9- 1- 1 System ( city or county jurisdiction) will be
required to send complete copies of the following GIS layers to the State 9- 1- 1 GIS
Coordinator for validation. Tests will be run to ensure they meet Arizona's standards.
• Street centerlines
• ESNIESZ boundaries
• Community boundaries
Data.. Sharing
All shared 9- 1- 1 GIS data shall be standardized prior to distribution. Please refer to
the NENA GIS Data Model ( see APPENDIX A) for standard field names, types, and
lengths.
Ongoing GIS Maintenance
Maintaining accurate GIS data is as important as acquiring accurate GIS data.
Since up- to- date GIS data is required for 9- 1- 1 mapping, it is imperative that the data be
continually updated with new streets, sub- divisions, and annexations. Each 9- 1- 1 System
is responsible for maintaining their GIS data. Below are maintenance requirements that
must be met in order to receive State 9- 1- 1 funds to finance mapped ALI and wireless 9Â 1-
1.
• The 9- 1- 1 System must identify their GIS department or GIS data maintenance
source and MSAG Coordinator prior to installing a mapped ALI system. A GIS
maintenance procedure must be submitted to the State's 9- 1- 1 Administrator or
GIS Coordinator.
• Procedures for updating and correcting the GIS data must be developed prior to
. installing a mapped ALI system. These procedures include:
a Methods for adding new streets and subdivisions
a Timeline for adding new street data/ annexations
a Methods for collecting GPS points ( if applicable)
o Methods for adjusting ESN/ Community boundaries
Prepared by: Adam Iten, AZ 911 Office 8
Updated: 9- 13- 2007
Arizona 9- 1- 1 GIS Standards
• The following people playa key role in maintaining the 9- 1- 1 GIS data:
o 9- 1- 1 dispatchers and call takers
o MSAG Coordinators
o GIS personnel
o Addressing assignment sources such as the Planning and/ or Assessors
Office
o Outside contracted data maintenance sources
• To ensure that GIS data is accurately maintained, each 9- 1- 1 System is required to
complete an annual ALI to GIS comparison. This comparison should be
. performed by the 9- 1- 1 System's GIS personnel or the State's 9- 1- 1 GIS
Coordinator. Each county is entitled to one free ALI dump per year. 9- 1- 1
Systems may also perform a GIS to MSAG comparison to assess GIS accuracy.
• Please contact the State 9- 1- 1 GIS Coordinator if you ever need GIS
assistance.
Prepared by: Adam! ten, AZ 911 Office 9
Updated: 9- 13- 2007
Arizona 9- 1- 1 GIS Standards
APPENDIX A
EXHIBIT 22
VERSION 1.0 GIS data model format
22.1Preface
The Geographic Information System ( GIS) Data Model identifies a geospatial data standard, but it
outlines data layers forGIS data to be exchanged between neighboring public safety agencies or
jurisdictions. This standard is for spatial datasets in a GIS environment. GIS utilizes linear style
addressing technique for purposes of geocoding. Should an organization use non~ linear style
addressing such as an alphanumeric grid style system, this standard would not be effective. The
primary purpose ofthis standard is for organizations that utilize a Geographic Information System.
This Standard will identify minimal attributes required in a spatial dataset, and define the
structure of said attributes. This standard will help facilitate the development of new map
products for use in Public Safety specifically as it pertains to implementing wireless
locational technologies Longitude, Latitude and elevation are part ofthe spatial layers
that are sent along with the data layers. Data specifies the map proj ections and
coordinate system recommended for the display of the Longitude and Latitude
coordinates. The standard format for Longitude, Latitude, Elevation and Datum is the
following:
« . N4IVllf"' i\\\ LABEL MAX #       TYPE: I,~
, DATKDESCRIPTION Â  Â 
.,
( .. ,' X?'(': ......"'.'" . BYTES . .' .. ...
Longitude LON 11 AN Longitude/ X coordinate. Right Justified: pad field
with zeros to left of decimal degrees. + Long: east of
Greenwich; - long: west of Greenwich.
When Phase II location cannot be provided, Phase I
information should be reported, i. e., the cell site or
sector where the call is received. Sample:
+ 000.000000
Latitude LAT 10 AN LatitudeN coordinate. Right Justified: pad field with
zeros to left of decimal degrees. + Lat: north of
equator; - lat: south ofequator. When Phase II location
cannot be provided, Phase I information should be
reported, i. e., the cell site;: or sector where the call is
received. Sample: + 00.######
Elevation ELV 5 AN Elevation! Altitude indicated as height above mean sea
level, measured in meters. Blank record indicates data
"' .' not available. Sample: #####
Datum NAD 2 N Specifies the map projection and coordinate system
recommended for the display of the Longitude and
Latitude coordinates. Two systems are commonly
used for North America. The code 83 identifies North
American Datum for 1983 ( NAD83). Code 84
identifies the World Geodetic Systemfor 1984
( WGS84). Other codes may be added as additional
datum becomes available through authorized entities.
Wherex=
83 = NAD83
84= WGS84
Prepared by: Adam Itim, AZ 911 Office
Updated: 9- 13- 2007
10
Arizona 9- 1- 1 GIS Standards
EXHIBIT 22
VERSION 1.0 GIS data model format
22.2 METADATA
Metadata is information about the content, quality, condition, and other characteristics of data
being sent. The basic elements to be included in the metadata file are taken from the 1998 NSDI Â Federal
Geographic Data Committee Digital Geospatial Metadata Standards. The following are
the basic elements that need to be included in the metadata file:
Identification Information - basic information about the data set
Citation
Description
Time Period of Content
Status
Spatial Domain
Keywords
Access Constraints
Use Constraints
Point of Contact
Browse Graphic
Data Set Credit
Security Information
Native Data Set Environment
Cross Reference
Description - a characterization ofthe data set, including its intended use and limitations
Data Quality Information - a general assessment of the quality of the data set
Attribute Accuracy
Logical Consistency Report
Completeness Report
Positional Accuracy
Lineage
Cloud Cover
Spatial Data Organization Information - the description of the reference frame for, and
the means to encode coordinates in the data set
Indirect Spatial Reference
Direct Spatial Reference Method
Point and Vector Object Information
Raster Object Information
Spatial Reference Information..., the description of the reference frame for, and the means
to encode, coordinates in the data set.
Horizontal Coordinate System Definition
Vertical Coordinate System Definition
Distribution Information - information about the distributor of and options for obtaining
the data set. .
Distributor  
Resource Description
Distribution Liability
Standard Order Process
Custom Order Process
Technical Prerequisites
Available Time Period
Prepared by: Adam Hen, AZ 911 Office
Updated: 9- 13- 2007
11
Arizona 9- 1- 1 GIS Standards
EXHIBIT 22
VERSION 1.0 GIS data model format
Metadata Reference Information - information on the currentness ofthe metadata
information, and the responsible party.
Metadata Date
Metadata Review Date
Metadata Future Review Date
Metadata Contact
Metadata Standard Name
Metadata Standard Version
Metadata Time Conversion
Metadata Access Constraints
Metadata Use Constraints
Metadata Security Information
Metadata Extensions
Citation Information - the recommended reference to be used for the data set
Originator
Publication Date
Publication Time
Title
Edition
Geospatial Data Presentation Fonn
Series Information
Publication Information
Other Citation Details
Online Linkage
Larger Work CitatiOn
Prepared by: Adam Iten, AZ 911 Office
Updated: 9- 13- 2007
12
Arizona 9- 1- 1' GIS Standards
EXHIBIT 22
VERSION 1.0 GIS DATA MODEL FORMAT
22.3 LINE DATA
22.3A. Centerline Layer
NAME' LABE MAX TYP DATA DESCRIPTION
1: tt ! 1
...... BYTE
.... S
Left Add LLO 10 N Lowest address on left side of street in ascending order
Low
Left Add LHI 10 N Highest address on left side of street in ascending order
High
Right Add RLO 10 N Lowest address on right side of street in ascending order
Low
Rigb: tA- dd RHI 10 N
High Highest address on right side of street in ascending order
PrefIx PRD 2 AN Leading street direction prefix. Valid Entries: N SEW
Directiona NENWSESW
1
Street STN 60 AN Valid service address of the Calling PartyNumber
Name
Street STS 4 AN Valid Street abbreviation, as defined by the US Postal Service
Suffix Publication 28. ( e. g. AVB)
Post POD 2 AN Trailing street direction suffix. Valid Entries: N SEW
Directiona NENWSESW
1
Road ROC 3 AN Road Class as defmed by the USGS National Mapping Product
Class Standard for 1: 24,000- scale and 1: 25,000- scale Quadrangle
Map Products.
http:// rockyweb. cr. usgs. gov/ nmpstds/ acrodocs/ qrnaps/ 5PSYM4
99. PDF
One- way ONW 1 A One. way road classification.
B1ank= No
X = Opposite Direction of arc
Y = In direction of arc
MSAG MCL 35 A Valid service community name as identified by the MSAG on
Communit the left side ofthe street
yName
Left
MSAG MCR 35 A Valid service community name as identified by the MSAG on
Communit the right side ofthe street
yName
Right
Segment SID 8 N Unique Road Segment ID number
ID
CountyID COL ' 5 AN County Identification code ( usually the FIPS code) on the left
Left side of the street in ascending order.
Note: County Identification field is used to identify the county
ofcall origination. The Committee recommends use ofthe
FIPS code assi: r; ned to each county by the US. Census Bureau
CountyID COR 5 AN County Identification code ( usually the FIPS code) on the right
Prepared by: Adam Iten, AZ 911 Office
Updated: 9- 13- 2007
13
Arizona 9- 1- 1 GIS Standards
Right side of the street in ascending order.
Note: County Identification field is used to identify the county
ofcall origination. The Committee recommends use ofthe
FIPS code assigned to each county by the U. S. Census Bureau
Source of SOD 5 A Agency that last updated the record
Data
Date DLU 10 N Date oflast update Format: CCYY-: rvfM- DD
Updated
I[ IJ Where an MSA G eXIsts, must fit the MSA Gentry.
2 Primary address associated with the Calling Party Number
3 Must include all TN USERS information on all Multi- Line Telephone Systems that willfacilitate the
implementation ofenhanced 9- 1- 1 on all PBX, Key, Hybrid and Centrex Systems.
4 NA = not available - class ofservicefor an ESCOfailure
5 The Data Technical Committee strongly recommends that all processing edits be removedfrom this Label
due to technological changes requiring improved data security measures.
EXHIBIT 22
VERSION 1.0 GIS data model format
223B R ° 1 dL   al roa ayer
NAME LABEL MAX # TYPE DATA DESCRIPTION
..:.), BYTES ..... , '.
Line LIN 4 A Railroad Line Owner ( Code of Association of
American Railroads)
Line Name LNA 30 A Railroad Line Name
SegmentID SID 8 N Unique Railroad Segment ID
Mile Post Low MPL 5 AN Beginning Linear Reference
Mile Post High MPH 5 AN Ending Linear Reference
Source ofData SOD 5 A Agency that last updated the record
Date Updated DLU 10 N Date oflast update Format: CCYY-: rvfM- DD
223C H d I L Â  Lyl ro 0 gy ayer
, ..~ 4IVIIf' Â  ," LABEL MAX # TYPE Â  DATA DESCRIPTION
•. +;; c;'";,,, BYTES .,'
. ,. .'
Surface Water SWL 1 A Type of Surface Water ( river, stream, etc.)
Line
Surface Water SWN 30 A Name ofriver, stream etc.'
Name
SegmentID SID 8 N Unique Hydrology Segment ID
Source ofData SOD 5 A Agency that last updated the record
Date Updated DLU 10 N Date oflast update Format: CCYY- MM- DD
22.4. POINTDATA
L L A S 224 Â  A Emergency el" Vlce ency ocatlOn ayer ... Â  Â  Â  ~~; il LABEL MAX#. TYPE DATA DESCRIPTION
1:....... " ...... .. . BYTES
Agency Type ATY 1 A Law= L
Fire = F
Emergency Medical Service = E
CountyID COl 5 AN County Identification code ( usually the FIPS code).
Note: County Identification field is used to identify
the county ofcall origination. The Committee
recommends use ofthe FIPS code assigned to each
Prepared by: Adam Hen, AZ 911 Office
Updated: 9- 13- 2007
14
Arizona 9- 1- 1 GIS Standards
county by the U. S. Census Bureau
Community ID CID 10 N Unique Community ill Number i. e. FIPS,
GEOCODES, etc.
Agency ill AID 9 N Emergency Service Agency ID defmed with the fIrst
5 digits as the County ill code and the last 4 digits
as the locally assigned agency code
Agency Name ANA 35 A Name of Agency
Agency Contact ACO 25 A Agency Contact Person
Agency Address AAD 25 A Street Address of Agency Facility
MSAG MCN 35 A Valid service community name as identifIed by the
Community Name MSAG
StatelProvince STA 2 A Alpa U. S. State or Canadian province abbreviation
i. e. TX ( Texas), ON ( Ontario)
Telephone Number TEL 12 A Telephone Number of Agency Format: NPA- NXX-XXXX
Source of Data SOD 5 A Agency that last updated the record
Date Updated DLU 10 N Date oflast update Format: CCYY- MM- DD
Prepared by: Adam Iten, AZ 911 OffIce
Updated: 9- 13- 2007
15
Arizona 9- 1- 1 GIS Standards
EXHIBIT 22
VERSION 1.0 GIS data model format
224B C II S't L f L . e 1 e oca IOn aver
NAME Â  I LABEL MAX # TYPE DATA DESCRIPTION
BYTES ..
LDT Provider ID LDT 8 AN LDT Provider Identification Code. Codes to be
developed and held by NENA
TowerID TIN 10 A Tower Identification Number
Tower Address TAD 35 A Tower street address
Tower TWN 25 A Tower community
Community
Tower State TSA 2 A Tower state
Number of sectors TNO 1 N Number of sector faces ( 1= 360 deg)
Ground elevation GEL 8 N Ground Elevation ( nnnnn. nn)
Tower height THT 4 N Height of tower
Height/ elev. units ZUN 1 A F= feet, M= meters of Ground Elevation and Tower
Height
Range RNG 6 N Default range of tower based on power settings of
tower. Units: miles. Format: llllll. nn ( two decimal
places)
Antenna AOR 20 A Listof antenna orientations, separated by spaces or
Orientations commas ( i. e. compass degrees or compass
directional)
Cell Type CTP 1 A A= Analog ( 900MHz), P= Digital ( PCS), T= TDMA
( Digital AMPs) - could expand depending on needs
Comment CCM 60 A Comment
Source ofData SOD 5 A Agency that last updated the record
Date Updated DLU 10 N Date oflastupdate Format: CCYY- MM- DD
22.4C. Mile Marker Location Layer
Mile Post ID MPI 10
TYPE DATA DESCRIPTION.
N Mile Post Identification Number
Mile Marker MMT 2
Type
A Type of mile marker
RR = Railroad name
HW = Road name
SegmentID
Source ofData
SID
SOD
8
5
N Unique Road or Railroad Segment ID number
A Agency that last updated the record
Date Updated DLU 10 N Date oflast update Format: CCYY- MM- DD
22 4D SOt 1St t L f L . . 1 e rue ure oea Ion ayer
NAME I LABEL MAX # TYPE DATA DESCRIPTION
.... ..
.. BYTES ..
Community ID CID 10 N Unique Community ill Number i. e. FIPS,
GEOCODES, etc.
Site ID SIN 6 N Unique Site ID Number
Site Address SAN 10 N Site Address Number
Number
Prefix Directional PRD 2 AN Leading street direction prefix. Valid Entries: N S E
W
NENWSESW
Street Name STN 60 AN Valid service address of the Calling Party Number.
Street Suffix STS 4 AN Valid Street abbreviation, as defmed by the US
Postal Service Publication 28. ( e. g. AVB)
Prepared by: Adam Iten, AZ 911 Office
Updated: 9- 13- 2007
16
Arizona 9- 1- 1 GIS Standards
Post Directional POD 2 AN Trailing street direction suffIx. Valid Entries: N S E
W
NENWSESW
ESN ESN 5 N Emergency Service Number associated with tbis
House Number, Street Name and Community Name.
Note: The Service Provider, providing the E9- 1- 1
-. Selective RoutinJ< will assign ESN's.
Prepared by: Adam ! ten, AZ 911 Office
Updated: 9- 13- 2007
17
Arizona 9- 1- 1 GIS Standards
EXHIBIT 22
VERSION 1.0 GIS DATA MODEL FORMAT
22.4D. Site/ Structure Location Layer ( cont.)
.•   .   .. NAME I LABEL MAX # TYPE I DATA DESCRIPTION
BYTES . >
MSAG MCN 35 A Valid service community name as identified by the
Community Name MSAG
Site Type STY 2 A Type of Structure - Classification Field
LR LRS 1 A LeftJRight side of the road
Source ofData SOD 5 A Agency that last updated the record
Date Updated DLC 8 N Date of last update Format: CCYYMMDD
22.5. POLYGON LAYER
L P 225A C Â  ounty olygon a, er
"' NAME' I.. LABEL MAX # TYPE DATA DESCRIPTION
BYTES
I',.
." .. '.' .'
CountyID COl 5 AN County Identification C9de ( usually the FIPS code}
Note: County Identification field is used to identify
the county ofcall origination. The Committee
recommends use ofthe FIPS code assigned to each
county by the US. Census Bureau
County Name CNA 35 A Name of County
Source ofData SOD 5 A Agency that last updated the record
Date Updated DLU 10 N Date oflast update Format: CCYY- MM- DD
Zo B d L S 225B E Â  . merl! ency erVlce ne oun ary aver
f"; T NAME I LABEL MAX # TYPE . DATA DESCRIPTION (   l.     .\ i         i BYTES > > ,
Community ID CID 10 N Unique Community ID Number i. e. FIPS,
GEOCODES; etc.
County ID COl 5 AN County Identification code ( usually the FIPS code).
Note: County Identificationfield is used to identify
the county ofcall origination. The Committee
recommends use ofthe FIPS code assigned to each
county by the u. s. Census Bureau
PSAP ID PSI 4 AN Code identifying the PSAP associated with the
assigned ESN
AgencyID AID 9 N Emergency Service Agency ID
ESN ESN 5 N Emergency Service Number associated with this
House Number, Street Name and Community Name.
Note: The Service Provider, providing the E9- 1- 1
Selective Routin~ will assi~ n ESN's.
Source ofData SOD 5 A Agency that last updated the record
Date Updated DLU 10 N Date oflast update Format: CCYY- MM- DD
225 C M .. IB d L Â  . uDlclpa oun ary aver
NAME I LABEL MAX # TYPE DATA DESCRIPTION
BYTES
Community ID CID 10 N Unique Community ID Number i. e. FIPS,
GEOCODES, etc.
MSAG MCN 35 A Valid service community name as identified by the
Community Name MSAG
Prepared by: Adam Iten, AZ 911 Office
Updated: 9- 13- 2007
18
Arizona 9- 1- 1 GIS Standards
Source of Data
Date Updated
Agency that last u dated the record
Date oflast u date Format: CCYY- MM- DD
Prepared by: Adam Hen, AZ 911 Office
Updated: 9- 13- 2007
19
Arizona 9- 1- 1 GIS Standards
EXHIBIT 22
VERSION 1.0 GIS DATA MODEL FORMAT
B d L A S 225D E .. mergency erVlCe 1gency oun ary aver
NAME Â  I LABEL MAX # TYPE Â  DATA DESCRIPTION
BYTES Â  ...
PSAPID PSI 4 AN Code identifying the PSAP associated with the
assigned ESN
CountyID COl 5 AN County Identification code ( usually the FIPS code).
Note: County Identification field is used to identify
the county ofcall origination. The Committee
recommends use ofthe FIPS code assigned to each
county by the U. S. Census Bureau
Agency ID AID 9 N Emergency Service Agency ID
Source of Data SOD 5 A Agency that last updated the record
Date Updated DLU 10 N Date oflast update Format: CCYY- MM- DD
. e Ite overage ayer
    .   .... NAI\/\ E/ il: L~~ L MAX # . TYPE DATA DESCRIPTION
./')\', i.; Â  '\ ......... " BYTES
LDT Provider ID LDT 8 AN LDT Provider Identification Code. Codes tobe
developed and held by NENA
Cell Site ID CEL 6 AN Identification number indicating a geographic
region of wireless coverage. When Phase II
location cannot be provided, Phase I information
should be reported, i. e., the cell site or sector where
the call is received.
Sector number SNO 1 N Number of this sector ( face) 1- 9
SectorID SEC 2 AN Sub set/ section of a cell. When Phase II location
cannot be provided, . Phase I information should be
reported, i. e., the cell site or sector where the call is
received.
ESRD ESD 10 N ESRD ( P- ANI) assigned to this cell/ sector
Sector Antenna ANT 3 N Center of antenna orientation for this face ( i. e.
Orientation Compass degrees or compass directional)
Coverage angle CAG 3 N Maximum angle of coverage for this face in miles or
kilometers.
Maximum Range SRG 6 N Maximum range for this face
Comment COM 60 A
Coverage source SSR 1 A. C= Company Map, D= Digital data from Company,
P= GIS Propagation Study, L= Line of Site analysis,
R= RangeDef
Ground elevation GEL 8 N Ground ( surface) elevation ( nnnnn. nn)
Tower height THT 8 N Height oftower ( nnnnn. nn)
Observed height OHT 8 N Amount to add to each point visible from tower
Height/ elev. units ZUN 1 A F= feet, M= meters of Ground Elevation, Tower
Height, and Observed Height
Spot Elevation SPO 8 N Spot elevation for the tower
Vertical angle SV1 3 N Possible angle above the horizon compass degrees or
above compass directional.
Vertical angle SV2 3 N Possible angle below the horizon compass degrees or
below compass directional.
Inside radius RD1 8 N Starting radius ( if any - Maximum range is outside
radius) in feet or meters.
225 E C II S Â  C L
Prepared by: Adam ! ten, AZ 911 Office
Updated: 9- 13- 2007
20
Arizona 9- 1- 1 GIS Standards
Agency that last u dated the record
Date oflast update Format: CCYY- MM- DD
Prepared by: Â  Adam Iten, AZ 911 Office 21
Updated: 9- 13- 2007
Arizona 9- 1- 1 GIS Standards
EXHIBIT 22
VERSION 1.0 GIS DATA MODEL FORMAT
225F H d I L . [ VI ro 02V aver
I NAME I LABEL MAX # TYPE DATA DESCRIPTION
BYTES ..
Surface Water SWL 1 A Type of Surface Water ( pond, lake, large waterway,
Line reservoir, etc.)
Surface Water SWN 30 A Name of Pond, lake, waterway, reservoir, etc.
Name
SegmentID SID 8 N Unique Hydrology Segment ID
Source ofData SOD 5 A Agency that last updated the record
Date Updated DLU 10 N Date oflast update Format: CCYY- MM- DD
Prepared by: Adam Hen, AZ 911 Office 22
Updated: 9- 13- 2007
Arizona 9- 1- 1 GIS Standards
APPENDIXB
Sample Metadata Form
ESN Boundaries
Metadata:
• Identification Information
• Data Quality Infonnation
• Spatial Data Organization Information
• Spatial Reference Infonnation
• Entity and Attribute Infonnation
• Distribution Information
• Metadata Reference Infonnation
Identification_ Information:
Citation:
Citation jnformation:
Originator: REQUIRED: The name of an organization or individual that
developed the data set
Publicationpate: REQUIRED: The date when the data set is published or
otherwise made available for release.
Title:
ESN
GeospatiaCData_ Presentation_ Form: vector digital data
Online_ Linkage: \\ WSITENA\ C$\ Adam\ GIS Data\ Arizona. mdb
Description:
Abstract:
ESN Boundaries
Purpose:
REQUIRED: A summary ofthe intentions with which the data set was developed.
Time_ Period_ of_ Content:
Time_ Period_ Information:
Single_ Date/ Time:
Calendar Date: 11/ 16/ 2004
Currentness_ Reference:
publication date
Status:
Progress: REQUIRED: The state of the data set.
Maintenance_ and_ UpdateYrequency: REQUIRED: The frequency with which
changes and additions are made to the data set after the initial data set is
completed.
Spatialpomain:
Prepared by: Adam Iten, AZ 911 Office 23
Updated: 9- 13- 2007
Arizona 9- 1- 1 GIS Standards
Bounding_ Coordinates:
West_ Bounding_ Coordinate: - 113.334221
East_ Bounding_ Coordinate: - 110.450439
Northyounding_ Coordinate: 32.511578
South younding_ Coordinate: 31.507841
Keywords:
Theme:
Theme_ Keyword_ Thesaurus: REQUIRED: Reference to a fonnally registered
thesaurus or a similar authoritative source oftheme keywords.
ThemeJ( eyword: REQUIRED: Common- use word or phrase used to describe the
subject of the data set.
Access_ Constraints: REQUIRED: Restrictions and legal prerequisites for
accessing the data set.
Use Constraints:
• REQUIRED: Restrictions and legal prerequisites for using the data set after
access is granted.
Point_ of_ Contact:
Contact_ Information:
Contact_ Person_ Primary:
Contact Person: Adam ! ten
Contact_ Organization: State of Arizona/ 9- 1- 1 Office
Contact Position: 9- 1- 1 GIS Coordinator
Contact_ Electronic_ Mail_ Address: adam. iten@ ad. state. az. us
Native Data Set Environment: - --
Microsoft Windows XP Version 5.1 ( Build 2600) Service Pack 2; ESRI
ArcCatalog 9.0.0.535
Data_ Quality_ Information:
Positional_ Accuracy:
Horizontal_ Positional_ Accuracy:
HorizontaCPositional~ ccuracy_ Report:
< 3 meters
SpatiaCData_ OrganizationJnformation:
Direct_ Spatia( fleference_ Method: Vector
Point_ and_ Vector_ Object_ Information:
SDTS_ Terms_ Description:
SDTS_ Poineand_ Vector_ Object_ Type: G.,. polygon
Point_ and_ Vector_ Object_ Count: 850
SpatiaCReference_ Information:
HorizontaCCoordinate_ System_ Definition:
Geographic:
Latitude Resolution: 0.000000
Longitude_ Resolution: 0.000000
Prepared by: Adam Iten, AZ 911 Office 24
Updated: 9- 13- 2007
Arizona 9- 1- 1 GIS Standards
Geograp hie_ Coordinate_ Units: Decimal degrees
Geodetic Model. Â  - -
Horizontal Datum Name: North American Datum of 1927 - -
Ellipsoid_ Name: Clarke 1866
Semi- major_ Axis: 6378206.400000
Denominator_ of_ Flattening_ Ratio: 294.978698
VerticaC Coordinate_ System_ Definition:
Altitude~ ystempefinition:
Altitude Resolution: 0.000010
Altitude_ Encoding_ Method: Explicit elevation coordinate included with
horizontal coordinates
Entity_ and_ AttributeJnformation:
Detailed_ Description:
Entity_ Type:
Entity_ Type_ Label: ESN
Attribute:
Attribute Label: OBJECTID
Attribute_ Definition:
Internal feature number.
Attributepefinition_ Source:
ESRI
Attribute Domain Values: - -
Unrepresentable_ Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute~ abel: Shape
Attributepefinition:
Feature geometry.
Attribute_ Definition_ Source:
ESRl
Attribute Domain Values: - -
Unrepresentablepomain:
Coordinates defining the features.
Attribute:
Attribute_ Label: AREA _
Attribute:
Attribute Label: PERIMETER
Attribute:
Attribute Label: NAME
Attribute:
Attribute Label: ESN
Attribute:
Attribute_ Label: Shape_ Length
Attribute_ Definition:
Length of feature in internal units.
Prepared by: Adam ! ten, AZ 911 Office 25
Updated: 9- 13- 2007
Arizona 9- 1- 1 GIS Standards
Attribute_ Definition_ Source:
ESRI
Attribute Domain Values: - -
Unrepresentable_ Domain:
Positive real numbers that are automatically generated.
Attribute: .
Attribute_ Label: Shape_ Area
Attribute_ Definition:
Area of feature in internal units squared.
Attribute_ Definition_ Source:
ESRI
Attribute Domain Values: - -
Unrepresentablepomain:
Positive real numbers that are automatically generated.
DistributionJnformation:
Resource_ Description: Downloadable Data
Metadata_ Reference_ Information:
Metadata Date: 20041117
Metadata Contact:
Contact_ Information:
Contact_ Organization_ Primary:
Contact_ Organization: REQUIRED: The organization responsible for the
metadata infonnation.
Contact_ Person: REQUIRED: The person responsible for the metadata
infonnation.
Contact Address:
Address_ Type: REQUIRED: The mailing and/ or physical address for the
organization or individual.
City: REQUIRED: The city of the address.
State_ or_ Province.' REQUIRED: The state or province ofthe address.
Postal_ Code: REQUIRED: The ZIP or other postal code of the address.
Contact_ Voice_ Telephone: REQUIRED: The telephone number by which
individuals can speak to the organization or individual.
Metadata.- 8tandard_ Name: FGDC Content Standards for Digital Geospatial
Metadata
Metadata Standard Version: FGDC- STD- 001- 1998 - -
Metadata Time Convention: local time - -
Metadata Extensions:
Online_ Linkage: http:// www. esri. com/ metadataJesriprof80. html
Profile_ Name: ESRI Metadata Profile
Prepared by: Adam Iten, AZ 911 Office 26
Updated: 9- 13- 2007
State Fees and Organizatiqnal Structure
STATE Wireline Fee Structure - Wireless Fee
.. '
Structure
Idaho
, Iaska
Illinois
Hawaii
__. State feefOversight& Local
, Local
State Fee/ Overisght& Local
State FeefOversight& Loc\ l1
State FeefOversight& Local
, Local
State Program
State Fee/ Oversight& Local
Lpcel
State Fee/ Ov: rsight& LOcal
Local'
State Fee/ c> versight& Local
', Ldcal '
State Fee/ Oveg; ightg. Local
State Fee/ Oversight
..'. "., ":
State Fee/ Ove: sight&~ c, cel
Staie Fee/ Oversight& Local
State Fee/ Oversight& Local
, Locel
State Program
State Fee/ Oversight& Local
State Program
State Fee/ Oversight& U) cal
State Fee/ Oversight& Local
Local
NA
StateF'ee/ Oversight& Local
'
State Fee/ Oversight& Local
Local
Stat~ Prqgram
Stat~ Program
State Program
State FeelOverisght& Local
State Fee/ Oversight& Local
Local
Local
, LoceL
State, Fee/ Oversight& Local
State Fee/ Oversight& Local
. State Progf\' m .
State FeelOversight& Local
" LOcel,"
State'Fee/ Oversight& Local
Combination .
State Fee/ Oversight& Locel
State Program .'
State F~ e10verslghtg. Local
State F~ e/ dversight& Local
Local ,
State FeelOversight& Local
Local
Local
Local
StateFee/ Oversight& Local
Local
StateFee/ Oversight& Local
Local
State Program
StateFee/ Oversight& Local
Local
Local
Local
Local
Local
Local
LocalfCounty Level
Local
Local
Local
Local
State Program
State Fee/ Oversight& Local
State Program
Loca!
State FeefOversight& Local
Local
Local
State FeefOversight& Local
Local
Local
State Program
State Program
State Program
Local
Local
Local
Local
Locai
State Fee/ Oversight& Local
Local
State Program
Local
Local
State Fee/ Oversight& Local
Combination
Local
State Progral11
State Fee/ Local
State Fee/ Oversight& Local
. Local
Local
Local
, Iabama
, rizona
\ rkansas
; alifomia
; olorado
) elaware
; onnecticut
Georgia
) jstrict of Columbi
Florida
Indiana
5% of basic tariff rate, not to exceed $ 2,. 00.
$. 50 to $. 75
WirelineNolP - $ 0.20
5% or 12% of tariff rate
.5% of Intrastate toll
Up to $. 70
WirelineNolP - $ 0.37
$ 0.60
$. 62 to $. 76
WirelineNolP - Up to $ 0,50
WirelineNoip - Up to $ 1.50
$ 0.27
Up. to $ 1.00
$. 30 up to $ 5.00
3% to 10% of monthly access charge. Statute does
note define what makes up local telephone acces charge
f'lo;:.: w"' a=- -'- J WirelineNolP - Up to $ 1.00 plus anpther $ 1.00 for 24 months
Kansas Up to $. 75
Kentucky Up, to$ 4.00
Louisiana WirelineNolP - 5% of tariff rates
Maine WirelineNolP - $ 0.5D
Maryland WirelineNolP -$ 1.00
Massachusetts $ 0.85
Michigan $ 0 to $ 4: 00
Minnesota WirelineNolP - $ 0.65
Misissippi $ 0.85 - $ 2.05
Missouri 15% of tariff rate or $. 75
Montana WirelineiVolP $ 1.00
Nebraska $ 0.50 or higher based on conditions
Nevada $. 25 or tax base
New Hamoshire $ 0.25
New Jersey WirelineNolP - $ 0.90
New Mexico $ 0.51
New York $ 0.35 or $ 1 ,00
North Carolina $. 25 to $ 3.5D ($ 1.00 average)
North Dakota $ 1.00
Ohio Property tax andfor fee up to $. 50
Oklahoma WirelinelFolP - Varies up to 15% of tariff rates
Oregon WirelineNolP - $ 0.75
Pennsvlvania $ 1.00 to $ 1.50
Rhode Island WirelineNolP - $ 0.47
South Carolina $. 50 to $ 1.50
South Dakota $ 0.75
Tennessee WirelineNolP - Up to $ 1.50 on resid. & Upto $ 3; 00 for bus.
Texas WirelineNolP • $. 50 plus it varies by HRC & ECD
Utah $: 65 local fee plus $. 13 state fee
Vermont Universal Service Fund ( USF)
Virginia WirelineNolP - $ 0.75'
Washinaton $. 20 & $. 50
West Virainia Varies
Wisconsin Varies
Wyoming $ 0.75
Key to Classifications:
Local - This is a local program from fee imposition, collections, 911 service implementation, contracting, etc.
State Proaram - This is a state program from the fee imposition, collections, 911 service implementation, contracting, etc.
State FeefOversight& Local - This is a program where the state law authorizes the fees, and remittance is to the state who has oversiaht authority via
! plan approval, standard/ rule settinQ. and fund authorizations. Local Qovemmenl are resonsible for the implementation, contract, etc. In wireless, this means
there is a wireless board or th~ state aoencv has fundina oversioht.
Updated 912012007