Communications Suite. Product Guide

Transcription

1 Communications Suite Product Guide Product Version Area Code Info 1.0 Carrier Info 1.0 ExchangeInfo Plus 2.0 LATAInfo 1.0 MobileMarketInfo 1.0 PSAP Pro 2.0 EmergencyInfo Pro 1.0 RateCenterInfo 1.0 1

2 Information in this document is subject to change without notice and does not represent a commitment on the part of the vendor or its representatives. part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, without the written permission of Pitney Bowes Inc., 350 Jordan Rd, Troy, New York Pitney Bowes Inc. All rights reserved. AreaCodeInfo, CarrierInfo, ExchangeInfo Plus, LATAInfo, MediaPrints, MobileMarketInfo, PSAP Pro, and RateCenterInfo are trademarks of Pitney Bowes Inc. and/or its affiliates. Use of the Telcordia LERG Routing Guide (LERG) data does not imply endorsement of any Pitney Bowes product by Telcordia. Products named herein may be trademarks of their respective manufacturers and are hereby recognized. Trademarked names are used editorially, to the benefit of the trademark owner, with no intent to infringe on the trademark. Disclaimer AreaCodeInfo, CarrierInfo, ExchangeInfo Plus, LATAInfo, PSAP Pro, EmergencyInfo Pro, MobileMarketInfo, RateCenterInfo, the Communications Suite Product Guide, and the supporting data furnished by Pitney Bowes, are accepted for use by the recipient with the understanding that Pitney Bowes makes no warranties, expressed or implied, concerning the accuracy, completeness, reliability, or suitability of this program or the supporting data. Pitney Bowes shall be under no liability whatsoever resulting from the use of this program. ExchangeInfo Plus should not be relied upon as the sole basis for solving a problem in situations where an incorrect decision may result in injury to persons or damage to property. Further Information Corporate Headquarters: Pitney Bowes Inc., 350 Jordan Road, Troy, New York Phone: (518) Fax: (518) Sales: (800) Government Sales: (800) Technical Support: (518) Technical Support Fax: (518) This document was published on April 26, 2017 and is intended to reflect the products (table structures, coverage, etc.) as of this date. The actual data content (as opposed to the product content) is updated on a regular basis and does not require documentation updates. 2

3 Table of Contents Chapter 1: Installing Communications Suite Products... 6 Communications Suite File Types... 7 Installing a Product... 8 Chapter 2: AreaCodeInfo... 9 AreaCodeInfo Overview AreaCodeInfo Database Table Structure Data Source and Projection Chapter 3: CarrierInfo...12 CarrierInfo Overview CarrierInfo Database Table Structures Using CarrierInfo Compatibility with Other Communications Suite Products Merger and Acquisition Scenarios Using CarrierInfo with RateCenterInfo Using CarrierInfo with ExchangeInfo Plus Using CarrierInfo with CallingAreaInfo Data Source and Projection Chapter 4: ExchangeInfo Plus...32 ExchangeInfo Plus Overview ExchangeInfo Plus Database ExchangeInfo Plus Table Structures American Data Canadian Data Using ExchangeInfo Plus Selecting the NPA/NXXs Served by a Wire Center Boundary Selecting Sub-Sets of Central Office Points Selecting Sub-Sets of NPA/NXXs Selecting NPA/NXXs That Have Line Range Splits Selecting All Boundaries for a Local Exchange Carrier Determining Serving Wire Center Code for a Database Building Wire Center Boundary Layers for a State

4 Data Source and Projection Chapter 5: LATAInfo...53 LATAInfo Overview LATAInfo Database Data Source and Projection Chapter 6: MobileMarketInfo...56 MobileMarketInfo Overview MobileMarketInfo Features Using MobileMarketInfo in Microsoft Access Configuring MapInfo Professional to Support Microsoft Access Wireless Communications Overview Defining Cellular and Personal Communications Services Cellular Services PCS Broadband Personal Communications Services Advanced Wireless Service MHz Band Services MobileMarketInfo Database Overview Cellular Database Table Structures PCS Broadband Database Table Structures AWS Database Table Structures MHz Band Services Table Structure MobileMarketAnalyzer Using MobileMarketAnalyzer Using MobileMarketInfo Using MobileMarketInfo Queries in MapInfo Professional Selecting License or Frequency Data by CallSign Selecting License Data by Licensee Name Creating a Ranged Thematic Map of Bandwidth Assets Comparing Carrier PCS to Cellular License Areas Data Source and Projection Chapter 7: PSAP Pro...98 PSAP Pro Overview PSAP Pro Database Table Structure Data Source and Projection Chapter 8: EmergencyInfo Pro

5 EmergencyInfo Pro Overview EmergencyInfo Pro Database Using EmergencyInfo Pro Visual Differences between Spatial Layers Table Structures Data Source and Projection Chapter 9: RateCenterInfo RateCenterInfo Overview RateCenterInfo Database Table Structures American Data Canadian Data Using RateCenterInfo Data Source and Projection Appendix A: Glossary Table of Acronyms for the Communications Suite Table of Communications Suite Terminology

6 Chapter 1: Installing Communications Suite Products 1 This chapter provides an overview of the Communications Suite and instructions for installing most of the Pitney Bowes Communications Suite products. In This Chapter Communications Suite Overview Communications Suite File Types Installing a Product 6

7 Communications Suite Overview This book describes the Pitney Bowes Communications Suite, which provides comprehensive locationbased coverage of telecommunications and wireless systems and is comprised of chapters of the following products: Chapter 2: AreaCodeInfo Chapter 3: CarrierInfo Chapter 4: ExchangeInfo Plus Chapter 5: LATAInfo Chapter 6: MediaPrints Chapter 7: MobileMarketInfo Chapter 8: PSAP Pro Chapter 9: EmergencyInfo Pro Chapter 10: RateCenterInfo Each chapter in this guide describes a separately purchased product. For simplicity, all these products are described as a suite in a single book. Some products in the Communications Suite also reference the Pitney Bowes product CallingAreaInfo. While CallingAreaInfo is technically considered part of the Communications Suite, this product includes an interface and a more complicated installation procedure, and therefore the content for this product resides in a distinct guide CallingAreaInfo Product Guide. For information on how to install and use CallingAreaInfo, refer to this guide. The multiple components of Communications Suite combine to give a detailed picture of telecommunications cabilities in a given region. This will help you make more informed decisions, reduce susceptibility, control costs, and enhance profitability. Communications Suite File Types For each product Spatial Plus File Types in the Communications Suite, the file sets can contain the following file types: MapInfo Professional File Types.DAT.ID.IND.MAP.TAB Data file Identification file Index file Map file Tabular file In order to properly use file sets from any product in the Communications Suite, the following rules apply: You must have access to all of the files in the file set All files must be located in the same directory Communications Suite Product Guide 7

8 Installing a Product You can install any of the products in the Communications Suite as a standalone dataset. Products are described as a suite in the Communications Suite Product Guide for the sake of simplicity only. The Pitney Bowes Communications Suite recommends using MapInfo Professional v7 or higher. To install any of the Communications Suite products: 1. Extract the contents of the zip file to a temporary folder location. 2. Copy the contents of the Data folder to the desired destination folder. If the destination folder already contains a previous vintage of the dataset, be sure to "Replace" all files of the same name with the files from the temporary folder location. 3. Copy the contents of the Docs folder (Product Guide and Release tes) to the desired destination folder. 4. Delete the files in the temporary folder location to save disk space. 5. You are now ready to start using the Communications Suite. Communications Suite Product Guide 8

9 Chapter 2: AreaCodeInfo 2 AreaCodeInfo is Pitney Bowes map database of area code boundaries for the United States. In This Chapter AreaCodeInfo Overview AreaCodeInfo Database

10 AreaCodeInfo Overview As the demand for new telephone numbers grows, new Area Codes are created and added. Pitney Bowes updates the database quarterly to ensure the most accurate, up-to-date Area Code information available. Area Code boundaries for Indiana and surrounding NPAs By combining the information in AreaCodeInfo with other mapping data, you can see a more detailed picture of the telecommunications landscape. Applying this data in your industry or field enables you to make more informed decisions, control costs, identify marketing opportunities, and enhance profitability. AreaCodeInfo Database This section explains the AreaCodeInfo database structure and provides a description of its organization. This section explains the AreaCodeInfo database structure and provides a description of its organization. Database Structure AreaCodeInfo contains one file set for the entire coverage area (United States and Canada).

11 The table below shows the file set for the United States: AreaCodeInfo (US) AreaCodeRegions.DAT AreaCodeRegions.ID AreaCodeRegions.IND AreaCodeRegions.MAP AreaCodeRegions.TAB To use AreaCodeInfo, you must have access to all of the files in the file set. All files must be located in the same directory. Table Structure The AreaCodeInfo table structure is as follows: Field Name Description Type (Length) Indexed Area_Code Area Code Number (also known as NPA number) Character (3) Yes Data Source and Projection Pitney Bowes suite of telecom infrastructure databases i built using state PUC data, state tariff data, the Telcordia LERG Routing Guide (LERG), StreetPro, and other reference data. The AreaCodeInfo database has the following coverage, scale, coordinates, and projection Coverage United States, Guam, US Virgin Islands, US rthern Mariana Islands and Canada. Scale 1:24,000 Coordinates Latitude and Longitude Projection NAD 83

12 Chapter 3: CarrierInfo 3 CarrierInfo is Pitney Bowes database of local and wireless telephone service providers for the United States. In This Chapter CarrierInfo Overview CarrierInfo Database Table Structures Using CarrierInfo

13 CarrierInfo Overview CarrierInfo is a macro view of the communications landscape, showing the serving area region of every telecommunications operating company. The product includes a high-level parent company view of a carrier's service area as well as a medium-level operating company number (OCN) view of the service area. In particular, the product: Accurately shows the service area footprints, by rate center, of U.S. communications service providers. Allows users to determine coverage areas by service type (ILEC/CLEC/Wireless), parent company name, carrier name, or operating company number (OCN). Allows users to quickly determine and compare the overall competitive landscape of various carriers. There are three major categories of landline telecommunications carriers: Regional Bell Operating Companies (RBOC) Independent Telephone Companies (ICO) Competitive Local Exchange Carriers (CLEC) In addition to the landline telecommunications carriers, there are two major categories of wireless carriers: Personal Communication Services (PCS) Cellular Carriers The divestiture of AT&T in 1984 created seven RBOCs. Several of the original RBOCs have merged and there are now four RBOCs. The local telephone companies that serve areas not served by RBOCs are considered Independent Telephone Companies (ICO). In a given area, there is one and only one RBOC or ICO offering service. The term Incumbent Local Exchange Carrier (ILEC) is used to identify the collection of RBOCs and ICOs. The Telecommunications Act of 1996 deregulated the telecommunications landscape and for the first time allowed consumers to choose their local service provider. Competitive Local Exchange Carriers (CLECs) provide alternative service in areas served by ILECs. Unlike ILECs, CLECs are not required to provide service to all locations within their service territory, and can decline to offer service to particular regions or consumers. Consumers in a territory in which a CLEC operates have the option to receive local service from a CLEC rather than from the ILEC in the area. There can be multiple CLECs offering service in a given area. The Power of CarrierInfo CarrierInfo is used to analyze telecommunications carriers geographic presence at a high-level. Additionally, CarrierInfo may be used with other Pitney Bowes data products such as ExchangeInfo Plus and RateCenterInfo to associate parent company information with the lower-level detail provided by these products. To see examples of how CarrierInfo can be used in conjunction with other Pitney Bowes communications data products, see Using CarrierInfo. For example, users can use the parent company layer to identify the footprint of Verizon Communications through a single selection. By then adding the OCN layer from CarrierInfo, users are then able identify all of the OCNs assigned to Verizon Communications. In this example, there are 41 Communications Suite Product Guide 13

14 OCNs assigned to Verizon Communications. The results of this query would identify all of the areas in which Verizon operates as an ILEC as well as a CLEC. CarrierInfo may also be used to determine all of the CLECs that operate within a particular ILEC service territory. A selection of the ILEC s parent company territory can be made from the Parent Company layer. That geographic area can then be overlaid with the CLEC layer and a selection can be made to determine all of the CLECs that have operating territories within the ILEC footprint. CarrierInfo is useful for a variety of different users and applications, including: Mergers and Acquisitions Competitive Analysis Strategic expansion into new markets The product can be used to answer questions such as: How much does one company overlap other companies coverage area? What are all the OCNs associated with Verizon or CenturyTel? What is the parent company of an area s ILEC/CLEC? What are all the CLECs operating within a particular ILEC service area? What are all the NPA/NXXs for a specific company? te This last question requires that you have data from either RateCenterInfo or ExchangeInfo Plus to perform a complete analysis. Features CarrierInfo offers the following features: A single source for ILEC, CLEC, and Wireless carrier service areas by rate center. CarrierInfo allows users to identify the service areas for any communications service provider in the United States. Useful layers that include Parent Companies, OCNs, incumbent and competitive carriers. The Parent company layer provides a researched parent company name so that affiliates can be viewed as part of a larger parent company view. The OCN layer provides a more detailed view of a parent company's serving area in terms of the individual operating company numbers owned by the parent company Provides a critical link between Telcordia LERG based company names and an industry recognized company name. Increase the usability of additional Pitney Bowes communications data products such as ExchangeInfo Plus and RateCenterInfo that rely on Telcordia LERG based company names. CarrierInfo Database This section explains the CarrierInfo database structure and provides a description of its organization. Table Structures The CarrierInfo database consists of the following tables: Communications Suite Product Guide 14

15 UsOcn.* UsOcnIlec.* UsOcnClec.* UsOcnWireless.* UsParent.* UsParentIlec.* UsParentClec.* UsParentWireless.* Each of the four OCN tables has the following table structure: OCN Tables Column Name Description Type (Length) Indexed OCN (primary key) Operating company number for all incumbent local exchange carriers that have active NPA/NXXs Character (4) Yes OCN_Name Operating company name Character (50) Abbre_OCN_Name Abbreviated operating company name Character (20) ParentName Parent company name for this OCN Character (100) ParentID For NPA/NXXs that have line range splits (thousand block pooling), this is the last line number in the range Integer Yes Category Category for this OCN. It has one of three values: ILEC CLEC Wireless Character (10) Yes <object> Combination of rate centers that have at least one active NPA/NXX assigned to this OCN Region The four OCN tables contain the following information: UsOcn - Information for all operating companies. UsOcnIlec - Subset of the UsOcn table where Category = ILEC. UsOcnClec - Subset of the UsOcn table where Category = CLEC. UsOcnWireless - Subset of the UsOcn table where Category = Wireless. Since the ILEC, CLEC, and Wireless tables are subsets of the full RegionOcn table, all information contained in those tables are also contained in the RegionOcn table. The information in the subset tables is duplicated to improve usability of the product, since common analysis involves splitting the full table by category. Each of the four Parent tables has the following table structure: Parent Tables Column Name Description Type (Length) Indexed ParentID (primary key) Parent company identifier Integer Yes Category Category for this Parent. It has one of three values: Character (10) Yes Communications Suite Product Guide 15

16 Column Name Description Type (Length) Indexed ILEC CLEC Wireless ParentName Parent company name for this OCN Character (100) <object> Combination of OCNs that have this ParentID and Category Region Each of the four Parent tables contain the following information: UsParent Information for all operating companies. UsParentIlec Subset of the UsParent table where Category = ILEC UsParentClec Subset of the UsParent table where Category = CLEC UsParentWireless Subset of the UsParent table where Category = Wireless Since the ILEC, CLEC, and Wireless tables are subsets of the full UsParent table, all information contained in those tables are also contained in the UsParent. The information in the subset tables is duplicated to improve usability of the product, since common analysis involves splitting the full table by category. The primary key for the Parent table is both ParentID and Category, since some parent companies have operations in multiple categories. For example, Verizon Communications operates in some areas as an ILEC and others as a CLEC, so there will be two records for Verizon Communications in the Parent table. About the ParentID Field The ParentID is an arbitrary integer value that does not correspond to any industry-standard code. The ParentID value for a particular ParentName will not change between updates. There is always a one-to-one relationship between ParentID and ParentName. The OCN table may be joined to the Parent table on ParentID and Category, or on ParentName and Category. Using CarrierInfo Compatibility with Other Communications Suite Products The OCN Category values in CarrierInfo are not the same as those found in other Pitney Bowes data products such as CallingAreaInfo, ExchangeInfo Plus, and RateCenterInfo. The following table shows how the CarrierInfo Category corresponds to the OCN Category values in other Pitney Bowes data products. CarrierInfo Category Categories in other Pitney Bowes Communications Data Products ILEC RBOC ICO Communications Suite Product Guide 16

17 CLEC Wireless CarrierInfo Category Categories in other Pitney Bowes Communications Data Products CLEC ULEC L RESELLER IPES CAP WIRELESS W RESELLER PCS P RESELLER Merger and Acquisition Scenarios For users that want to look at various scenarios such as mergers and acquisitions, CarrierInfo allows users to view the service area at the parent company level and the OCN level. As an example let us take a look at the pending (as of vember 1, 2005) MCI WorldCom and Verizon Communications merger and what impact it will have on the service areas of Verizon Communications. The following procedure shows how to do this. 1. Use the SQL Select dialog box to select the parent companies from the UsParent table. In this example we are using Verizon Communications and MCI WorldCom. See the image below for the parameters we are using. Communications Suite Product Guide 17

18 2. Once the desired companies have been selected, create a thematic map to distinguish between the individual company s service areas. te It may be helpful to use a pattern in order to see through the top polygon in areas of overlapping service areas 3. Use the resulting map to compare the difference in service areas and see how the addition of the proposed merger or acquisition will affect the overall service area. In this example the MCI WorldCom footprint is being added to the Verizon Communications footprint. 4. In addition to visually comparing the service areas, you can incorporate the boundaries into TargetPro to extract detailed demographic information such as population, age, and income to better understand how the proposed coverage meets their target market. For details on performing this additional analysis refer to the TargetPro Users Guide. Communications Suite Product Guide 18

19 Using CarrierInfo with RateCenterInfo RateCenterInfo is a map database of rate centers throughout the United States. It enables users to accurately determine the rate centers and NPA/NXX combinations that a carrier serves and to create maps that show all of the rate centers for a particular parent company. Using RateCenterInfo alone, users would not know each individual OCN under which a carrier operates and would not have access to the carrier s overall footprint. By using CarrierInfo alone, users are unable to detail the individual rate centers and NPA/NXXs that a carrier serves. The relation between CarrierInfo and RateCenterInfo provides the complete picture of telecommunication carriers footprints. While the possibilities of using RateCenterInfo with CarrierInfo are limitless, the following examples are some of the most common scenarios of using two products together. Selecting the Rate Centers for a Parent Company This scenario walks through the process of selecting the rate centers served by a particular parent company. CarrierInfo provides the overall footprint, and RateCenterInfo provides the individual rate centers that can be further studied for a more detailed analysis. 1. From the UsOcn table, select all the OCNs for a particular Parent Company (for example, Sprint Communications). 2. Once the list of OCNs that the parent company operates is determined, use it to select the list of rate centers from the Us_Rc_D table from RateCenterInfo for each OCN. Communications Suite Product Guide 19

20 te the use of the Group by Columns parameter. 3. w that the discrete list of serving rate centers is selected, select all the rate center geographies from the Us_Rc_G table from RateCenterInfo. 4. Finally, display the map and listing of rate centers that the particular company serves. Communications Suite Product Guide 20

21 This image only shows the first 30 records, not the entire result of the query. Communications Suite Product Guide 21

22 Selecting the NPA/NXXs a Parent Company Operates This scenario walks through the process of identifying all of the NPA/NXXs a particular parent company operates. This information is helpful for understanding potential inventory availability of a wireless carrier. The resulting output could be used in a lookup table or as input into additional analysis using CallingAreaInfo (see Using CarrierInfo with CallingAreaInfo for more details). 1. From the UsOcn table, select all the OCNs for a particular Parent Company (for example. BellSouth Corporation). 2. Once all of the OCNs from BellSouth are selected, find all the NPA/NXXs from the Us_Rc_D table RateCenterInfo for the selected OCNs. Communications Suite Product Guide 22

23 3. Finally, list the results in a browser window. This image only shows the first 30 records, not the entire result of the query. Using CarrierInfo with ExchangeInfo Plus ExchangeInfo Plus is a map database of wire centers and Central Offices throughout the United States. It enables users to accurately determine the NPA/NXX combinations that are included in specific wire centers as well as carrier information. By working with both CarrierInfo and ExchangeInfo Plus, users can quickly create maps that show all of the wire centers for a particular parent company. By using ExchangeInfo Plus alone, users would need to know each individual OCN in order to understand the overall carrier s footprint as identified in CarrierInfo. By using CarrierInfo alone, users are unable to detail the individual wire centers, Central Offices, and NPA/NXXs that a carrier serves. Combining CarrierInfo and ExchangeInfo Plus provides the complete picture of ILECs serving areas in the US as well as ILEC, CLEC, and Wireless Central Offices. Selecting Wire Centers Serving an ILEC This scenario uses data from ExchangeInfo Plus to identify the wire centers serving a particular ILEC. Communications Suite Product Guide 23

24 1. From the UsOcnIlec table select all of the OCNs for a particular ILEC parent company (for example, BellSouth Corporation). 2. Once the list of OCNs is selected, find the list of wire centers from the UsNpaNxx table from ExchangeInfo Plus for the selected OCNs. Communications Suite Product Guide 24

25 3. w that all of the CLLI codes are identified, select all the wire center geographies from the UsWcReg table from ExchangeInfo Plus. 4. Finally, display the map and listing of wire centers served by the particular ILEC. Communications Suite Product Guide 25

26 This image only shows the first 30 records, not the entire result of the query. Selecting the NPA/NXXs Served by a Particular ILEC This scenario walks through the process of identifying all the NPA/NXXs that a particular ILEC parent company operates. The resulting output could be used in a lookup table or as input into additional analysis using CallingAreaInfo (see Using CarrierInfo with CallingAreaInfo on page 30, for more details) 1. From the UsOcnILEC table, select all the OCNs for a particular ILEC Parent Company (for example, Verizon Communications). Communications Suite Product Guide 26

27 2. Once the list of OCNs is selected, find all the NPA/NXXs in the UsNpaNxx table from ExchangeInfo Plus for the selected OCNs. 3. Finally, display the list using a browser window. This image only shows the first 30 records, not the entire result of the query. Communications Suite Product Guide 27

28 Using CarrierInfo with CallingAreaInfo CallingAreaInfo maps the local calling plans available to business and residential customers when calling from or into a location. Calling plans are the rate structures that determine which phone numbers can call which other phone numbers, and at what rates. Most Local Exchange Carriers (LECs) offer more than one calling plan for each NPA/NXX combination they serve. By using CarrierInfo and CallingAreaInfo users can determine detailed information about parent companies and their local calling area footprints, such as what areas can call into a wireless company s network without incurring additional charges, or what is the overall outbound calling coverage of an ILEC. Showing Inbound Most Restrictive Footprint for a Wireless Carrier Users, such as Mobile Virtual Network Operators (MVNOs) are able to understand the inbound coverage areas for wireless carriers. This information is useful in determining phone number inventory assignments as well as actual inbound service areas for carriers for which they are partnered. This information can also help an MVNO understand the potential of a new partner. 1. From the UsOcnWireless table, select all the OCNs for a particular wireless parent company (for example, Sprint PCS). Communications Suite Product Guide 28

29 2. Select all the NPA/NXXs from the NpaNxx table from CallingAreaInfo for the selected OCNs. 3. Save the selection as a Microsoft Access (.mdb) table. 4. Import the list of NPA/NXXs into CallingAreaInfo using the Inbound Most Restrictive options. Communications Suite Product Guide 29

30 5. From CallingAreaInfo create a database report and enable GENERATE MAPS. 6. Display the map for the resulting coverage area. In this scenario we see the rate centers that Sprint PCS has inventory, as well as areas that can access that inventory as a local call. Communications Suite Product Guide 30

31 Data Source and Projection Pitney Bowes suite of telecom infrastructure databases is built using state PUC data, state tariff data, the Telcordia LERG Routing Guide (LERG), StreetPro, and other reference data. The CallingAreaInfo database has the following coverage, scale, coordinates, and projection Coverage United States, Guam, US Virgin Islands, US rthern Mariana Islands and Canada. Scale 1:24,000 Coordinates Latitude and Longitude Projection NAD 83 Communications Suite Product Guide 31

32 Chapter 4: ExchangeInfo Plus 4 ExchangeInfo Plus is Pitney Bowes database of Wire Center serving areas and Central Offices across the United States and Canada. This chapter provides an introduction to ExchangeInfo Plus and its features. In This Chapter ExchangeInfo Plus Overview ExchangeInfo Plus Database ExchangeInfo Plus Table Structures Using ExchangeInfo Plus

33 ExchangeInfo Plus Overview ExchangeInfo Plus is a comprehensive database from Pitney Bowes for mapping and analyzing Wire Center serving areas and Central Offices across the United States. Wire Center serving areas are the basic unit of geography for the telecommunications industry in the United States. They describe the organization of the local telephone exchange system. ExchangeInfo Plus lists every LEC Landline Wire Center in the United States and Canada and graphically displaying their service areas. ExchangeInfo Plus is designed for use in the telecommunications industry. In addition to providing geographic information about the Wire Center serving area and the Central Office, it contains specific telecom data for each Wire Center serving area and Central Office, including CLLI TM (Common Language Location Identifier) Codes, Rate Centre names, Exchange names, Area Code (NPA), Prefixes (NXX), Carrier Type information, and more. Features ExchangeInfo Plus contains CLLI TM codes, LATA assignments, rate center names, exchange names, area codes (NPA), prefixes (NXX), and carrier type information for each Wire Center (Centre). Communications Suite Product Guide 33

34 ExchangeInfo Plus Database File Structure The ExchangeInfo Plus database is divided into three file sets for each state or province and two support data tables for each. The files are named in the following manner: ExchangeInfo Plus state file sets: UsWcReg.*, UsWcPt.*, UsNpanxx Support data tables: ServiceType, OCNCategory Sample File Sets In the case of ExchangeInfo Plus U.S., the file set for the state of Pennsylvania (abbreviated PA) contains the following files: ExchangeInfo Plus MapInfo PAWcReg.dat PAWcReg.id PAWcReg.ind PAWcReg.map PAWcReg.tab PAWcPt.dat PAWcPt.id PAWcPt.ind PAWcPt.map PAWcPt.tab PANpanxx.dat PANpanxx.ind PANpanxx.tab ServiceType.dat ServiceType.tab OCNCategory.dat OCNCategory.tab In the case of ExchangeInfo Plus Canada, the file set contains the following files: ExchangeInfo Plus Canda (BC) CnWcReg.dat CnWcReg.id CnWcReg.map CnWcReg.tab CnWcPt.dat CnWcPt.id CnWcPt.map CnWcPt.ind CnWcPt.tab CnNpanxx.dat CnNpanxx.id CnNpanxx.map CnNpanxx.ind CnNpanxx.tab ServiceType.dat ServiceType.tab OCNCategory.dat OCNCategory.tab The ExchangeInfo Plus database is divided into five file sets: Central Office Points (XXWcPt.*) Wire Center Boundaries (XXWcReg.*) Area Code and Prefix Data Table (XXNPANXX.*) Service Type Data Table (ServiceType.*) OCN Category Data Table (OCNCategory.*) The file sets can be opened and used individually. However, using the file sets together provides the most complete information about Wire Center (Centre) serving areas and Central Offices. Communications Suite Product Guide 34

35 ExchangeInfo Plus Table Structures American Data The Central Office Points table shows the geographic location of the Central Office for each Wire Center serving area. Central Office Points Field Name Description Type (Length) Indexed XXWcPT (Point file) Wc_Code 8-character CLLI code for the Wire Center Character(8) Yes V Vertical coordinate of Central Office Character(5) H Horizontal coordinate of Central Office Character(5) X Longitude coordinate of Central Office Float Y Latitude coordinate of Central Office Float Source Indicates how the point was created: ADDR: Geocoded LERG Central Office street address VH: LERG vertical and horizontal coordinates converted to latitude and longitude. RSCH: Point created using other research techniques. Character(4) The Wire Center Boundaries table shows the geographic borders of the Wire Center serving areas. te ExchangeInfo Plus does not contain any geographic coverage data associated with wireless phone service. ExchangeInfo Plus Canada has geographic areas that have no phone service. Each province that contains this type of area will have a WC_Code designation with the Province abbreviation followed by an _UNS (??_UNS) in the CnWcReg.tab file. These WC_Codes are PB designated codes. Communications Suite Product Guide 35

36 Wire Center Boundaries Field Name Description Type (Length) Indexed XXWcREG (Region file) WC_Code 8-character CLLI code for the Wire Center Character(8) Yes The Area Code and Prefix Data table is a data table that contains information about every NPANXX in service. Area Code and Prefix Data Field Name Description Type (Length) Indexed XXNpanxx (Data file) NPA Area Code Character(3) Yes NXX Prefix Character(3) Yes StartRange For NPA/NXXs that have line range splits (thousand block pooling), this is the first line number in the range Character(4) Yes EndRange For NPA/NXXs that have line range splits (thousand block pooling), this is the last line number in the range Character(4) Yes State State that the NPA/NXX serves* Character(2) WC_Code 8-character CLLI code for the Wire Center Character(8) Yes Switch Last three characters of the CLLI code of the Switch that serves the NPA/NXX Character(3) ServiceType Indicates the type of service provided by the NPA/NXX Character(3) LATA LATA number Character(5) OCN Operating Company number Character(4) CompanyName Name of the carrier assigned to the OCN as it appears in the LERG Character(50) OCNCategory Type of carrier Character(10) Locality City name of the NPA/NXX Character(10) Exchange Exchange served by the NPA/NXX Character(24) Rate Center Rate center served by the NPA/NXX Character(16) * NPA/NXXs do not cross state lines. The 11-character CLLI code is divided into two fields in the database: the first 8 characters are shown in the WC_Code field, and the last 3 characters are shown in the Switch field In cases of Carrier Local Number Portability, there will be some subscribers in the NPA/NXX who are served by a different OCN. The value listed in this field is the OCN that owns the NPA/NXX prior to having numbers ported to other carriers. Communications Suite Product Guide 36

37 The Service Type Data table is a data table that provides descriptions of the service types. Service Type Data Field Name Description Type (Length) Indexed ServiceType (Data file) Type Service type Character(3) Description Description of the service type Character(100) The OCN Category Data table is a data table that provides descriptions of the OCN categories. OCN Category Data Field Name Description Type (Length) Indexed OCNCategory (Data file) Category OCN category Character(10) Description Description of the OCN category Character(50) Canadian Data Central Office Points Field Name Description Type (Length) Indexed XXWcPt (Point file) Geographic location of the Central Office for each Wire Centre serving area WC_Code 8-character CLLI code for the Wire Centre Character(8) Yes V Vertical coordinate of Central Office Character(5) H Horizontal coordinate of Central Office Character(5) X Longitude coordinate of Central Office Float Y Latitude coordinate of Central Office Float Source Indicates how the point was created: ADDR: Geocoded LERG central office street address VH: LERG vertical and horizontal coordinates converted to latitude and longitude. OTHR: Point created using other method Character (4) Wire Center Boundaries Field Name Description Type (Length) Indexed XXWcReg (Territory file) - Geographic borders of the Wire Center serving areas WC_Code 8-character CLLI code for the Wire Centre Character(8) Yes Communications Suite Product Guide 37

38 Area Code and Prefix Data Field Name Description Type (Length) Indexed XXNpanxx (Data file) - Data-only table containing information about every NPANXX in service NPA Area Code Character(3) Yes NXX Prefix Character(3) Yes StartRange For NPA/NXXs that have line range splits (a.k.a. blocked), this is the first line number in the range Character(4) Yes EndRange For NPA/NXXs that have line range splits (a.k.a. blocked), this is the last line number in the range Character(4) Yes Prov Province that the NPA/NXX serves * Character(2) WC_Code 8-character CLLI code for the Wire Centre Character(8) Yes Switch Last three characters of the CLLI code of the Switch that serves the NPA/NXX Character(3) ServiceType Indicates the type of service provided by the NPA/NXX Character(3) LATA LATA number Character(5) OCN Operating Company number Character(4) CompanyName Name of the carrier assigned to the OCN as it appears in the LERG Character(50) OCNCategory Type of carrier Character(10) Locality City name of the NPA/NXX Character(10) Exchange Exchange served by the NPA/NXX Character(24) RateCenter Rate Center served by the NPA/NXX Character(16) * NPA/NXXs do not cross province lines. In cases of Carrier Local Number Portability, there will be some subscribers in the NPA/NXX who are served by a different OCN. The value listed in this field is the OCN that owns the NPA/NXX prior to having numbers ported to other carriers. te ExchangeInfo Plus Canada does not contain any geographic coverage data associated with wireless phone service. Service Type Data Field Name Description Type (Length) Indexed ServiceType (Data file): Data-only table providing descriptions of the various service types Type Service type Character(3) Description Description of the service type Character(100) OCN Category Data Field Name Description Type (Length) Indexed OCNCategory (Data file): Data-only table providing descriptions of the various OCN categories. Category OCN category Character(10) Communications Suite Product Guide 38

39 Field Name Description Type (Length) Indexed Description Description of the OCN category Character(50) Using ExchangeInfo Plus This section describes how to use ExchangeInfo Plus to select portions of the data relevant to specific uses of the product. DISCLAIMER Since Wire Center boundaries and Central Office points are defined differently by some carriers and in some parts of the United States, the queries described in these examples may not work in every situation. Open all of the ExchangeInfo Plus files in MapInfo Professional before you proceed with the examples. Selecting the NPA/NXXs Served by a Wire Center Boundary To select the NPA/NXXs served by a Wire Center boundary, follow the steps below. 1. Select a Wire Center boundary from the WcReg map using the Select tool. 2. Click the Wire Center boundary with the Info tool. The Info Tool window displays showing the eightcharacter WC_Code. 3. Select the WC_Code. 4. Choose Edit > Copy or press Ctrl + C to copy the WC_Code. 5. Choose Query > SQL Select. The SQL Select dialog displays. 6. Enter UsNpanxx in the from Tables field. 7. Enter * in the Select Columns field. 8. Enter WC_Code = XXXXXXXX in the where Condition field, where XXXXXXXX is the eightcharacter WC_Code that you copied from the Info Tool window. Press Ctrl + V to paste it into the where Condition field. 9. Leave the Group by Columns and Order by Columns fields blank. 10. Enter Selection in the into Table Named field. Communications Suite Product Guide 39

40 11. Click OK. The results of the query display in a browser window. Selecting Sub-Sets of Central Office Points This section contains examples that show how to select sub-sets of Central Office points. The examples include the following: Selecting LEC Landline Central Office Points Selecting CLEC Central Office Points Selecting Central Office Points that Serve at Least One Wireless NPA/NXX Selecting LEC Landline Central Office Points To select LEC landline Central Office points, follow the steps below: 1. Choose Query > SQL Select. The SQL Select dialog displays. 2. Enter UsWcPt, UsNpanxx in the from Tables field. 3. Enter UsWcPt.WC_Code, UsWcPt.V, USWcPt.H, UsWcPt.Source in the Select Columns field. 4. Enter UsWcPt.WC_Code = UsNpanxx.WC_Code and (UsNpanxx.OCNCategory = RBOC or UsNpanxx.OCNCategory = ILEC ) and UsNpanxx.ServiceType = EOC in the where Condition field.enter USWcPt._code in the Group by Columns field. 5. Leave the Order by Columns field blank. 6. Enter Selection in the into Table Named field. 7. Click OK. The results of the query display in a browser window. Selecting CLEC Central Office Points To select CLEC Central Office points, follow the steps below. Communications Suite Product Guide 40

41 1. Choose Query > SQL Select. The SQL Select dialog displays. 2. Enter UsWcPt, Usnpanxx in the from Tables field. 3. Enter UsWcPt.WC_Code, UsWcPt.V, USWcPt.H, UsWcPt.Source in the Select Columns field. 4. Enter UsWcPt.WC_Code = UsNpanxx.Wc_code and UsNpanxx.OCNCategory = CLEC in the where Condition field. 5. Enter UsWcPt._code in the Group by Columns field. 6. Leave the Order by Columns field blank. 7. Enter Selection in the into Table Named field. 8. Click OK. The results of the query display in a browser window. Selecting Central Office Points that Serve at Least One Wireless NPA/NXX To select Central Office points that serve at least one wireless NPA/NXX, follow the steps below. te These Central Office points are not exclusively wireless. There could be LEC landline numbers serviced by these Central Office points as well. 1. Choose Query > SQL Select. The SQL Select dialog displays. 2. Enter UsWcPt, UsNpanxx in the from Tables field. 3. Enter UsWcPt.WC_Code, UsWcPt.V, UsWcPt.H, UsWcPt.Source in the Select Columns field. 4. Enter UsWcPt.WC_Code = UsNpanxx.Wc_code and UsNpanxx.ServiceType <> EOC in the where Condition field. 5. Enter USWcPt._code in the Group by Columns field. 6. Leave the Order by Columns field blank. Communications Suite Product Guide 41

42 7. Enter Selection in the into Table Named field. 8. Click OK. The results of the query display in a browser window. Selecting Sub-Sets of NPA/NXXs This section contains examples that show how to select sub-sets of NPA/NXXs. The examples include the following: Selecting LEC Landline NPA/NXXs Selecting CLEC NPA/NXXs Selecting Wireless NPA/NXXs Selecting LEC Landline NPA/NXXs To select LEC-landline NPA/NXXs, follow the steps below. 1. Choose Query > SQL Select. The SQL Select dialog displays. 2. Enter UsNpanxx in the from Tables field. 3. Enter * in the Select Columns field. 4. Enter ServiceType = EOC and (OCNCategory = RBOC or OCNCategory = ILEC ) in the where Condition field. 5. Leave the Group by Columns and Order by Columns fields blank. Communications Suite Product Guide 42

43 6. Enter Selection in the into Table Named field. 7. Click OK. The results of the query display in a browser window. Selecting CLEC NPA/NXXs To select CLEC NPA/NXXs, follow the steps below. 1. Choose Query > SQL Select. The SQL Select dialog displays. 2. Enter UsNpanxx in the from Tables field. 3. Enter * in the Select Columns field. 4. Enter OCNCategory = CLEC in the where Condition field. 5. Leave the Group by Columns and Order by Columns fields blank. 6. Enter Selection in the into Table Named field. Communications Suite Product Guide 43

44 7. Click OK. The results of the query display in a browser window. Selecting Wireless NPA/NXXs To select Wireless NPA/NXXs, follow the steps below. 1. Choose Query > SQL Select. The SQL Select dialog displays. 2. Enter UsNpanxx in the from Tables field. 3. Enter * in the Select Columns field. 4. Enter ServiceType <> EOC in the where Condition field. 5. Leave the Group by Columns and Order by Columns fields blank. 6. Enter Selection in the into Table Named field. 7. Click OK. The results of the query display in a browser window. Selecting NPA/NXXs That Have Line Range Splits To select the NPA/NXXs that are involved in line range splits, follow the steps below. 1. Choose Query > SQL Select. The SQL Select dialog displays. 2. Enter UsNpanxx in the from Tables field. 3. Enter * in the Select Columns field. 4. Enter StartRange <> 0000 or EndRange <> 9999 in the where Condition field. 5. Leave the Group by Columns and Order by Columns fields blank. Communications Suite Product Guide 44

45 6. Enter Selection in the into Table Named field. 7. Click OK. The results of the query display in a browser window. Selecting All Boundaries for a Local Exchange Carrier To select all of the Wire Center boundaries for a particular local exchange carrier, you can base the query on the company name or on the operating company number. Instructions for both methods are provided below. Selecting Boundaries by Company Name To use the company name to select all of the Wire Center boundaries for a particular local exchange carrier, follow the steps below. 1. Choose Query > SQL Select. The SQL Select dialog displays. 2. Enter UsWcReg, UsNpanxx in the from Tables field. 3. Enter * in the Select Columns field. 4. Enter UsWcReg.Wc_code = UsNPpanxx.Wc_code and UsNpanxx.CompanyName = COMPANY X in the where Condition field, where Company X is the company name of the local exchange carrier for which you are performing the query. 5. Leave the Group by Columns and Order by Columns fields blank. Communications Suite Product Guide 45

46 6. Enter Selection in the into Table Named field. 7. Click OK. The results of the query display in a browser window. Selecting Boundaries by Operating Company Number To use the operating company number to select all of the Wire Center boundaries for a particular local exchange carrier, follow the steps below. 1. Choose Query > SQL Select. The SQL Select dialog displays. 2. Enter UsWcReg, UsNpanxx in the from Tables field. 3. Enter * in the Select Columns field. 4. Enter USWcReg.Wc_code = UsNpanxx.Wc_code and UsNpanxx.OCN = #### in the where Condition field, where #### is the operating company number of the local exchange carrier for which you are performing the query. 5. Leave the Group by Columns and Order by Columns fields blank. 6. Enter Selection in the into Table Named field. Communications Suite Product Guide 46

47 7. Click OK. The results of the query display in a browser window. Determining Serving Wire Center Code for a Database This example assumes that the customer locations are in a MapInfo Professional point table called Addresses. The Addresses table contains a column called WC_Code in which the Wire Center codes will be placed. To determine the serving Wire Center code for a customer locations database: 1. Choose Table > Update Column. The Update Column dialog appears. 2. Choose the Addresses table from the Table to Update drop-down list. 3. Choose the UsWcReg table from the Get Value From Table drop-down list. 4. Choose Value from the Calculate drop-down list. 5. Choose WC_Code from the of drop-down list. 6. Choose the WC_Code column from the Column to Update drop-down list. 7. Click the Join button. The Specify Join dialog displays. 8. Select the where object from table USWcReg radio button. 9. Choose contains from the object from table Addresses drop-down list. 10. Click OK. You are returned to the Update Column dialog. 11. Click OK on the Update Column dialog. The Addresses table now contains the Wire Center codes that serve your customer locations. Building Wire Center Boundary Layers for a State There are two ways to build a Wire Center boundary layer for a particular state: Communications Suite Product Guide 47

48 Finding Wire Center Boundaries for Central Offices Residing in a State Finding Wire Center Boundaries Serving all NPA/NXXs in a State Each method is explained below. Finding Wire Center Boundaries for Central Offices Residing in a State Finding the Wire Center boundaries for Central Offices that reside in a state is the easiest way to build a Wire Center boundary layer for the state. However, this method will exclude Wire Center boundaries for Central Offices that serve the state, but reside in a different state. Only a small percentage of Wire Center boundaries along state borders will be affected. To find the Wire Center boundaries for Central Offices that reside in a state, follow the instructions below. The state of Arkansas (AR) is used as an example. 1. Choose Query > SQL Select. The SQL Select dialog displays. 2. Enter UsWcReg in the from Tables field. 3. Enter * in the Select Columns field. 4. Enter Mid$(WC_Code, 5, 2) = AR in the where Condition field. 5. Leave the Group by Columns and Order by Columns fields blank. 6. Enter ARWcReg in the into Table Named field. 7. Click OK. The results of the query display in a browser window. 8. Save a copy of ARWcReg using File > Save Copy As A copy of the Wire Center boundaries for Arkansas is saved. Finding Wire Center Boundaries Serving all NPA/NXXs in a State To find the Wire Center boundaries that serve all of the NPA/NXXs in a state, follow the instructions below. The state of Arkansas (AR) is used as an example. 1. Choose Query > SQL Select. The SQL Select dialog displays. 2. Enter UsNpanxx in the from Tables field. Communications Suite Product Guide 48

49 3. Enter * in the Select Columns field. 4. Enter State = AR in the where Condition field. 5. Enter WC_Code in the Group by Columns field. 6. Leave the Order by Columns field blank. 7. Enter AR_WC_Codes in the into Table Named field. 8. Click OK. The results of the query display in a browser window. 9. Save a copy of AR_WC_Codes using File > Save Copy As 10. Choose File > Open Table and open AR_WC_Codes. 11. Choose Query > SQL Select. The SQL Select dialog displays. 12. Enter UsWcReg, AR_WC_Codes in the from Tables field. 13. Enter UsWcReg.Wc_code in the Select Columns field. 14. Enter UsWcReg.Wc_code = AR_WC_Codes.Wc_code in the where Condition field. 15. Leave the Group by Columns and Order by Columns fields blank. 16. Enter ARWcReg in the into Table Named field. 17. Click OK. The results of the query display in a browser window. 18. Save a copy of ARWcReg using File > Save Copy As Communications Suite Product Guide 49

50 A copy of the Wire Center boundaries for Arkansas is saved. Geocoding a Database of Phone Numbers Using Central Office Points The instructions below explain how to geocode records that contain a phone number field. You can produce a map of each record in the original table. The mapped locations are based on the locations of the Central Office points serving the NPA/NXX-X for the given phone number. To geocode a database of phone numbers using central office points: 1. Choose File > Open Table to open the database of phone numbers. The database opens in MapInfo Professional. This example uses the table Customers.TAB, which contains the fields Name and Phone. The Phone field is in the format NPA-NXX-XXXX (including the dashes). The queries below must be modified if your phone number field has a different format. 2. Choose Query > SQL Select. The SQL Select dialog displays. 3. Enter Customers in the fromtables field. 4. Enter Name, Phone, Left$(Phone,3) NPA, Mid$(Phone,5,3) NXX,Right$(Phone,4) Block in the Select Columns field. 5. Leave the where Condition, Group by Columns, and Order by Columns fields blank. 6. Enter TempCustomers in the into Table Named field. 7. Click OK. The results of the query display in a browser window. 8. Save a copy of TempCustomers using File > Save Copy As Communications Suite Product Guide 50

51 9. Choose File > Open Table and open TempCustomers.TAB. 10. Choose Query > SQL Select. The SQL Select dialog displays. 11. Enter TempCustomers, UsNpanxx, UsWcPt in the from Tables field. 12. Enter TempCustomers.Name, TempCustomers.Phone in the Select Columns field. 13. Enter TempCustomers.NPA = UsNpanxx.NPA and TempCustomers.NXX = UsNpanxx.NXX and TempCustomers.Block >= UsNpanxx.StartRange and TempCustomers.Block <= UsNpanxx.EndRange and UsNpanxx.Wc_code = UsWcPt.Wc_code in the where Condition field. 14. Leave the Group by Columns and Order by Columns fields blank. 15. Enter CustomersMap in the into Table Named field. 16. Click OK. The results of the query display in a browser window. 17. Save a copy of CustomersMap using File > Save Copy As 18. Delete the TempCustomers table using Table > Maintenance > Delete Table CustomersMap.Tab contains the original data plus a geocoded point for each row in the table. Data Source and Projection Pitney Bowes suite of telecom infrastructure databases is built using state PUC data, state tariff data, the Telcordia LERG Routing Guide (LERG), StreetPro, and other reference data. The AreaCodeInfo database has the following coverage, scale, coordinates, and projection Coverage United States, Guam, US Virgin Islands, US rthern Mariana Islands and Canada. Scale 1:24,000 Coordinates Latitude and Longitude Projection NAD 83 Communications Suite Product Guide 51

52 Communications Suite Product Guide 52

53 Chapter 5: LATAInfo 5 Local Access Transport Areas (LATAs) identify a telephone call s carrier type. LATAInfo offers a map database of these LATAs, allowing you to easily differentiate calls carried by a Local Exchange Carrier (LEC) from those carried by a longdistance provider. This Pitney Bowes database covers continental United States, Alaska, Hawaii, and Puerto Rico. In This Chapter LATAInfo Overview LATAInfo Database

54 LATAInfo Overview LATAInfo is a map database of Local Access Transport Areas (LATA) across the United States. LATAs are geographic regions unique to the telecommunications industry. They are used to determine whether a telephone call is carried by a Local Exchange Carrier (LEC) or by a long-distance provider. In general, each LATA contains a single major metropolitan area. All telephone calls within a specific LATA are routed by LECs. However, telephone calls between two parties in different LATAs must, by law, be transported by a long-distance carrier. LATAInfo converts information on the nation s local access and long-distance markets, previously available only in tabular format, into a concise, easy-to-use map. By combining the information in LATAInfo with demographic, business, and customer data you can identify the best markets for growth in local telecommunications traffic. Applying this type of data enables you to make more informed decisions, control costs, identify marketing opportunities, and enhance profitability. LATAInfo data combined with the Pitney Bowes ExchangeInfo telecom database. Showing these data layers together allows you to determine which exchange areas in Virginia can route calls to each other without the need for a long distance carrier. Communications Suite Product Guide 54

55 LATAInfo Database File Structure LATAInfo contains one file set for the entire coverage area (continental United States, Alaska, Hawaii, and Puerto Rico). The file sets are named according to the convention shown below: LATA (US) US_LATA.* The table below shows the file set for the entire United States: LATAInfo (US) - MapInfo US_LATA.DAT US_LATA.ID US_LATA.IND US_LATA.MAP US_LATA.TAB Table Structure The table below details the data set s table structure. The information contained in the data set was obtained from state and federal government agencies. Field Name Description Type (Length) Indexed LATA_ID LATA ID number Character(5) Yes LATA_NAME Name of the LATA Character(100) MAJOR_LOC Major local operating companies serving the LATA Character(100) AREA_CODES Area Codes in the LATA Character(100) Data Source and Projection Pitney Bowes suite of telecom infrastructure databases is built using state PUC data, state tariff data, the Telcordia LERG Routing Guide (LERG), StreetPro, and other reference data. The LATAInfo database has the following coverage, scale, coordinates, and projection Coverage United States, Guam, US Virgin Islands, and US rthern Mariana Islands. Scale 1:24,000 Coordinates Latitude and Longitude Projection NAD 83 Communications Suite Product Guide 55

56 Chapter 6: MobileMarketInfo 6 MobileMarketInfo is Pitney Bowes comprehensive database of cellular and FCC licensed wireless market areas across the United States. This chapter provides an introduction to MobileMarketInfo and its features. It also explains how to install the database. In This Chapter MobileMarketInfo Overview Wireless Communications Overview MobileMarketInfo Database MobileMarketAnalyzer Using MobileMarketInfo

57 MobileMarketInfo Overview MobileMarketInfo is a comprehensive database from Pitney Bowes that maps and analyzes the wireless license landscape. Complete with market partitioning and frequency disaggregation, MobileMarketInfo consists of Cellular Market Areas (CMA), Personal Communication Service Areas (PCS) and Advanced Wireless Services (AWS). Together these service areas define the geographies in which wireless carriers are licensed to provide service throughout the U.S. By bringing together the complex FCC license data, coupled with dedicated research, MobileMarketInfo delivers a concise format for accurate analyses. MobileMarketInfo Features MobileMarketInfo includes the following features: Information about FCC wireless licenses Accurate 'Doing Business As' names Complete information on buildout dates and spectrum capacity Partitioning and disaggregation information for PCS licenses Relational database design that facilitates in-depth analysis Full integration with all other Pitney Bowes data products MobileMarketAnalyzer a MapBasic Application that automates common analyses Using MobileMarketInfo in Microsoft Access You can open the MobileMarketInfo databases in Microsoft Access. Microsoft Access enables you to perform complex database manipulations with greater ease. However, the geographic features of MobileMarketInfo are only available in MapInfo Professional. Consult Microsoft Access documentation for information on using Microsoft Access. Configuring MapInfo Professional to Support Microsoft Access You do not need to install Microsoft Access to use MobileMarketInfo. However, if you have not installed Microsoft Access and you are using MapInfo Professional, you may need to configure your installation of MapInfo Professional to support Microsoft Access. If you do not configure MapInfo Professional to support Microsoft Access, you will not be able to open any of the MobileMarketInfo TAB files. To configure MapInfo Professional to support Microsoft Access: 1. Launch the MapInfo Professional Setup.exe file. 2. Click Install Products. 3. Select DBMS Support. 4. Select DBMS support (again). 5. Click Next. 6. Review and accept the license agreement. 7. Select MapInfo Professional Version 7 or later. 8. Locate your installation of MapInfo Professional. Communications Suite Product Guide 57

58 9. Select the Pitney Bowes DAO (Microsoft Access) Support check box. You do not need to check either of the following options: Pitney Bowes ODBC Connectivity Support Oracle 8i Spatial Object Support for Pitney Bowes 10. Click Next. 11. Allow the installation to complete. 12. Click Finish. 13. Restart your computer. Wireless Communications Overview This section contains background information on the wireless communications industry. The information provided here is available on the Federal Communications Commission s web site along with additional information about wireless communications in the United States. Defining Cellular and Personal Communications Services Two-way wireless communication in the United States most commonly employs either Cellular Services or Broadband Personal Communication Services technology. This section describes both technologies. Cellular Services The cellular radiotelephone service is a mobile radiotelephone service in which common carriers are authorized to offer and provide a mobile telecommunications service for hire to the general public using cellular systems. Cellular systems in the United States operate in the mhz frequency bands and have 30 khz channel spacing. Personal Communications Services Broadband Personal Communications Services (PCS) is used to provide a variety of services, such as digital mobile phones and wireless internet access. These services are also called mobile telephone services and mobile data services. PCS operates in the mhz bands. Advanced Wireless Services Advanced Wireless Services (AWS) are used for a variety of wireless services, including Third Generation ("3G") mobile broadband and advanced wireless services. AWS operate in the and MHz bands. 700 MHz The 700 MHz spectrum consists of Upper 700 and Lower 700 bands, some paired and others not. The spectrum was previously owned by broadcasters for analog television use. Currently, Block C ( and MHz) of the Upper Band, and Blocks A ( and MHz), B ( and MHz) and C ( and MHz) of the Lower Band, are available for mobile phone use. Communications Suite Product Guide 58

59 Cellular Services This section describes cellular market areas, bandplan, licensing, how to obtain spectrum, and construction requirements. Market Areas The FCC divided the United States cellular communications market into Metropolitan Service Areas (MSAs) and Rural Service Areas (RSAs) in The FCC now calls MSAs and RSAs Cellular Market Areas (CMAs). CMAs are composed of one or more counties. The image below displays CMA394 and the counties of which it is composed. Bandplan Cellular Services are licensed to operate within a CMA at an A and a B frequency block. When the FCC first established cellular service rules, cellular spectrum was allocated into 40 mhz of spectrum: a 20 mhz block, 824 to 845 mhz, was designated for transmissions made by mobile units, and a separate 20 mhz block, from 870 to 890 mhz, was allocated for base station transmissions. The 40 mhz allocation accommodated 666 channel pairs (a channel pair consists of a mobile frequency and a corresponding base frequency). Due to the growth in demand for cellular service, the FCC reevaluated the cellular bandplan in The FCC allocated an additional five mhz of spectrum to each cellular system, increasing the spectrum designated for each block to 25 mhz and the total allocation to 50 mhz. The additional spectrum increased the number of channel pairs in each block to 416 channel pairs, or to a total of 832 channel pairs. The frequency allocation for mobile transmissions now ranges from 824 to 849 mhz, and from 869 to 894 mhz for base station transmissions. The charts below show the frequencies allocated in each block. Communications Suite Product Guide 59

60 Block Channel Frequencies A Mobile mhz A Base mhz A* Mobile mhz A* Base mhz B Mobile mhz B Base mhz B* Mobile mhz B* Base mhz Cellular Services Licensing Under the original cellular licensing rules, one of the two cellular channel blocks in each market (the B block) was awarded to a local wireline carrier, while the A block was awarded by comparative hearings to a carrier other than a local wireline carrier. Comparative hearings gave competing applicants a quasijudicial forum in which to argue why they should be awarded a license over competitors, and allowed other interested parties to argue for or against an applicant. After awarding the first thirty MSA licenses, rules were adopted in 1984 and 1986 to award the remaining cellular MSA and RSA licenses through lotteries. By 1991, lotteries had been held for every MSA and RSA, and licenses were awarded to the lottery winners in most instances. On August 5, 1997, Congress amended the Communications Act to require that all Mutually Exclusive Applications for initial licenses for construction permits be auctioned, with certain exceptions. The FCC auctioned three of four remaining RSA markets in Auction 45: Cellular RSA. Obtaining Spectrum Currently, no additional cellular auctions are scheduled. However, it is possible to obtain a cellular license from a current cellular licensee. Licensees may sell all or part of their licenses, subject to FCC approval, to other entities. Spectrum can also be obtained by acquiring a company and its licenses. Construction Requirements Initial cellular licensees are given a five-year period during which to expand their systems within the CMAs in which they are licensees. During the five-year buildout period, the licensee has the exclusive right to expand within its licensed CMA. At the end of the five-year buildout period, the actual service areas of all cells in a system is the licensee's Cellular Geographic Service Area (CGSA)1. Any areas within the CMA that is not part of a licensee's CGSA at the end of the five-year period is considered unserved area. Unserved Areas The FCC s application process has two phases for all cellular markets in which the five-year buildout period has expired: Phase I: Communications Suite Product Guide 60

61 A one-time process that provides an opportunity for eligible parties to file competing applications for authority to operate a new cellular system in, or to expand an existing cellular system into, unserved areas as soon as these areas become available. Entities may file Phase I applications only on the 31st day after the close of the initial licensee's five-year buildout period. Phase II: An ongoing process that allows eligible parties to apply for any unserved areas that may remain in a market after the Phase I process is complete. The timing of the Phase II licensing process is dependent on the Phase I process. If a Phase I application is granted, Phase II applications for any remaining unserved area within the market can be filed on or after the 121st day after the Phase I application was granted. If no Phase I applications were received, Phase II applications can be filed on or after the 32nd day after the close of the relevant five-year buildout period. Mutually Exclusive Applications Mutually exclusive applications occur whenever: Two or more acceptable applications are timely filed in the same market and channel block (for Phase I). OR Two or more applications propose CGSAs that overlap one another (for Phase II). In the past, the FCC conducted lotteries to resolve any mutually exclusive applications in Phase I or Phase II. In 1993, the FCC was given express authority to use auctions to choose from among two or more mutually exclusive initial applications. The Ninth Report and Order in the competitive bidding docket adopted final auction rules to enable the Commission to complete the licensing of Phase I and Phase II cellular unserved licenses. In Auction 12: Cellular Unserved, the FCC auctioned fourteen cellular unserved licenses. System Identification Numbers (SIDs) System identification numbers (SIDs) are unique numbers that the FCC assigns to cellular systems. SIDs are transmitted by the cellular systems so that cellular mobile stations can determine whether the system through which they are communicating is a system to which they subscribe, or whether they are considered by the system to be roamers. Cellular systems may transmit only their assigned SID(s) and/or the SIDs assigned to other cellular systems. A cellular system may transmit the SID assigned to another cellular system only if the licensee of that system concurs with such use of its assigned SID. PCS Broadband Personal Communications Services This section explains Broadband PCS market areas, bandplan, licensing, partitioning and disaggregation, and construction requirements. 1. MobileMarketInfo does not provide CGSAs. CMAs are the highest level of geographic precision avail- able in MobileMarketInfo. Communications Suite Product Guide 61

62 Market Areas The United States PCS market is divided into Major Trading Areas (MTAs) and Basic Trading Areas (BTAs). BTAs are composed of one or more counties and MTAs are composed of one or more BTAs. The image below shows BTA379 and the counties of which it is composed. The image below shows MTA035 and the BTAs of which it is composed. Communications Suite Product Guide 62

63 Bandplan Broadband PCS is allocated spectrum ranging from mhz and mhz. The FCC divided this 120 mhz of spectrum into six frequency blocks A through F. MTAs are assigned an A and a B frequency block. BTAs have frequency blocks C, D, E, and F. Blocks A, B, and C are 30 mhz each and blocks D, E, and F are 10 mhz each. The table below shows the frequencies allocated in each block. Block Channel Frequencies A Mobile mhz A Base mhz B Mobile mhz B Base mhz C Mobile mhz C Base mhz D Mobile mhz D Base mhz E Mobile mhz Licensing Since 1994, the FCC has conducted auctions of PCS licenses. These auctions are open to any eligible company or individual that submits an application and up-front payment, and is found to be a qualified bidder by the FCC. The winner of a license for electromagnetic spectrum is entitled to provide wireless communication services within the geographic area and spectrum specified in the license. Obtaining Spectrum Partitions and Disaggregation Currently, no additional broadband PCS auctions are scheduled. However, it is possible to obtain a broadband PCS license from a current broadband PCS licensee. Licensees may sell all or part of their licenses to other entities, subject to FCC approval. A licensee may sell a portion of their licenses through partition or disaggregation 1. A partition is a geographic subdivision of the licensee s market area. A disaggregation is a subdivision of the licensee s spectrum. A licensee may either partition, disaggregate, or both partition and disaggregate their license. The following image displays the partitioning of BTA 321. tice that callsigns KNLG502 and WPOL311 share the same frequencies, but that they are licensed to operate in different areas of BTA321. Communications Suite Product Guide 63

64 1. Partitions and disaggregations are the highest levels of precision available in MobileMarketInfo. This image displays disaggregation in MTA001. tice that callsigns WPSL626 and KNLF202 operate in the same geographic area, but at different frequencies. WPSL625 operates from mhz, and KNLF202 operates from mhz. Construction Requirements The FCC established construction requirements for broadband PCS licenses to ensure that the broadband PCS spectrum is used effectively and made available to as many communities as possible. Communications Suite Product Guide 64

65 Licensees of 30 mhz blocks must serve with a signal level sufficient to provide adequate service to at least one-third of the population in their licensed area within five years of the original license date and two-thirds of the population in their licensed area within 10 years of the original license date. 30 mhz licenses include non-disaggregated A and B blocks and non-disaggregated C blocks prior to Auction 35. Licensees of 10 and 15 mhz blocks must serve with a signal level sufficient to provide adequate service to at least one-quarter of the population in their licensed area within five years of the original license date or make a showing of substantial service in their licensed area within five years of the original license date. 10 mhz Licenses include D, E, and F blocks and C blocks including and after Auction mhz Licenses include disaggregated A and B blocks and disaggregated C blocks prior to Auction 35. Failure by any licensee to meet these requirements will result in forfeiture of the license and the licensee will be ineligible to regain it. Licensees must file maps and other supporting documents showing compliance with the respective construction requirements within the appropriate five- and ten-year benchmarks of the grant of their initial licenses. Licensees may choose to define population using the 1990 census or the 2000 census. Carriers can use TargetPro to perform census analyses. Advanced Wireless Service Over the past several years, the wireless industry has seen an increased demand for voice and data services. To keep pace with this demand, the Federal Communications Commission (FCC) is currently working to auction and license spectrum at and mhz. This new spectrum, labeled Advanced Wireless Service (AWS), can be used for a variety of services such as Third Generation (3G) Mobile Broadband and advanced wireless services, including wireless Internet access and other information and entertainment services. For more information, visit AWS Band Plan The following table shows the AWS Band Plan adopted August 5, Block Frequency Pairings License Area # Licenses A and CMA 734 B and EA 176 C and EA 176 D and REAG 12 E and REAG 12 F and REAG MHz Band Services The Digital Television and Public Safety Act of 2005 required all U.S. television broadcasters to convert from analog transmission to digital transmission by February 17, This transition to more spectrally efficient digital transmission freed spectrum in the 700 MHz band which includes MHz. Communications Suite Product Guide 65

66 The 2005 Act also required the FCC to auction the spectrum recovered from television broadcasting. Auction 73, which closed on March 18, 2008, offered 1,099 licenses in the 700 MHz band. Upper and Lower 700 MHz Band Plan Upper 700 MHz Band Block Auction Frequency Type Use A and Paired 2 x 1 Guardband B and Paired 2 x 1 Guardband C and Paired 2 x 11 Mobile Phone D and Paired 2 x 5 t Sold Lower 700 MHz Band Block Auction Frequency Type Use A and Paired 2 x 6 Mobile Phone B and Paired 2 x 6 Mobile Phone C and Paired 2 x 6 Mobile Phone D Paired 1x 6 One-way Broadcasting E Paired 1x 6 One-way Broadcasting te The above grayed out blocks are not intended for mobile phone service and are therefore not included in the product. MobileMarketInfo Database MobileMarketInfo contains databases that describe the mobile communications landscape in the United States. These are Cellular.mdb and PCS.mdb. You can open the databases in MapInfo Professional and in Microsoft Access. Communications Suite Product Guide 66

67 Overview Cellular Database Structure Cellular.mdb is located in the [InstallationDirectory]\MobileMarketInfo\Cellular\ folder, along with the following tables and queries: Tables Cellular License Cellular Channel Block Cellular DBA CMA Queries License Expired After License Expired Before License Expired Between License for DBA License Granted After License Granted Before License Granted Between License with Market Name te Effective June 2008, SID information has been removed from the Cellular database. This information has become increasingly difficult to maintain and Pitney Bowes is no longer able to provide accurate information. PCS Database Structure PCS.mdb is located in the [InstallationDirectory]\MobileMarketInfo\PCS\, along with the following MapInfo Professional tables and queries: Tables PCS License PCS Frequency PCS DBA PCS Channel Block BTA MTA Queries License 10 year Buildout Met Between License 10 year Buildout Date not Met and Deadline Between License 5 year Buildout Met Between License 5 year Buildout Date not Met and Deadline After License 5 year Buildout Date not Met and Deadline Before License 5 year Buildout Date not Met and Deadline Between License for DBA Communications Suite Product Guide 67

68 License for DBA with Frequency Market Code PCS Frequency Total Bandwidth with License Information AWS Database Structure MobileMarketInfo contains an AWS database that describes wireless communications. You can open the database in MapInfo Professional and in Microsoft Access. The AWS files are located in the [InstallationDirectory]\MobileMarketInfo\AWS folder. Tables AWS License AWS Frequency AWS DBA AWS Channel Block AWS CMA AWS BEA AWS REA Queries All Licenses within a BEA All Licenses within a BEA with Frequency Information All Licenses within an REA All Licenses within an REA with Frequency Information License for DBA License for DBA with Frequency Market Code AWS Frequency Total Bandwidth with License Information 700 MHz Band Services MobileMarketInfo contains a database dedicated to 700 MHz Band Services. Tables U700 and L700 REA U700 and L700 BEA U700 and L700 CMA Queries U700 Database Queries All Licenses within a REA All Licenses within a REA with Frequency Information License for DBA License for DBA with Frequency Market Code U700 Frequency Total Bandwidth with License Information L700 Database Queries All Licenses within a BEA All Licenses within a BEA with Frequency Information Communications Suite Product Guide 68

69 All Licenses within a CMA All Licenses within a CMA with Frequency Information License for DBA License for DBA with Frequency Market Code L700 Frequency Total Bandwidth with License Information The table structures and queries for all of the above databases are described in the sections below. Cellular Database Table Structures This section contains information on the Cellular Database table structures. Cellular License The Cellular License table describes active Cellular licenses. Field Name Description Type (Length) Indexed CELLULAR_LICENSE ( Objects) CallSign Cellular license identifier (primary key) Character(10) Yes USI Unique System Identifier. Alternate cellular license identifier. Character(10) MarketCode Cellular Market Area (CMA) code Character(6) Yes ChannelBlock Frequency block (A or B) Character(1) SubmarketCode One character submarket code Character(1) DBA Doing Business As name Character(50) Licensee Entity that owns the cellular license Character(50) LicenseContact Contact entity for the cellular license Character(50) LicenseOwner Owner of the license Character(50) LicenseeID Licensee identification Character(50) GrantDate Date on which the license was granted. DateTime ExpiredDate Date on which the license expires DateTime AuctionID Auction identification Character(10) CellularPhaseID Cellular phase identification Integer MAPINFO_ID MapInfo Professional Identifier, which is only visible in Microsoft Access Long Integer Yes Cellular Channel Block The Cellular Channel Block table contains frequency information for cellular channel blocks. Communications Suite Product Guide 69

70 Field Name Description Type (Length) Indexed CELLULAR_CHANNEL_BLOCK ( Objects) Block Frequency block (A or B) (primary key) Character(1) Yes MobileMin Minimum frequency for mobile phone to base tower transmission in MHz Float MobileMax Maximum frequency for mobile phone to base tower transmission in MHz Float BaseMin Minimum frequency for base tower to mobile phone transmission in MHz Float BaseMax Maximum frequency for base tower to mobile phone transmission in MHz Float AdditionalMobileMin Additional minimum frequency for mobile phone to base tower transmission in MHz Float AdditionalMobileMax Additional maximum frequency for mobile phone to base tower transmission in MHz Float AdditionalBaseMin Additional minimum frequency for base tower to mobile phone transmission in MHz Float AdditionalBaseMax Additional maximum frequency for base tower to mobile phone transmission in MHz Float MAPINFO_ID MapInfo Professional Identifier, which is only visible in Microsoft Access Long Integer Yes Cellular DBA The Cellular DBA table contains all Cellular Doing Business As names that are used in the Cellular database. Pitney Bowes created this table by aggregating CMA market data for each Cellular license. Field Name Description Type (Length) Indexed CELLULAR_DBA (Region file) DBA Doing Business as name (primary key) Character(50) Yes MAPINFO_ID MapInfo Professional Identifier, which is only visible in Microsoft Access Long Integer Yes Region Object The geographic area of the DBA. t available in Microsoft Access <obj> CMA The CMA table contains all Cellular Market Areas in the United States and Puerto Rico. Field Name Description Type (Length) Indexed CMA (Polygon file) MarketCode Cellular Market Area name (primary key) Character(6) Yes MarketName CMA market name Character(50) Communications Suite Product Guide 70

71 Field Name Description Type (Length) Indexed MAPINFO_ID MapInfo Professional Identifier, which is only visible in Microsoft Access Long Integer Yes Region Object The geographic area of the CMA. t available in Microsoft Access <obj> Cellular Database Queries This section contains descriptions of the queries included with the Cellular database. License Expired After The LIC_Expired_after query finds the records in the Cellular License table where the ExpiredDate is after the date that you provide. License Expired Before The LIC_Expired_before query finds the records in the Cellular License table where the ExpiredDate is before the date that you provide. License Expired Between The LIC_Expired_between query finds the records in the Cellular License table where the ExpiredDate is between the dates that you provide. License for DBA The LIC_For_DBA query finds the records in the Cellular License table where the DBA name is similar to the DBA name that you provide. You do not need to provide the entire DBA name exactly as it appears in the DBA column. Make sure that the query returns the results that you wanted, because all DBA names that are similar to the DBA name that you entered will be returned. For example, if you enter cell, the many licenses containing the word cell will be returned. License Granted After The LIC_Granted_after query finds the records in the Cellular License table where the GrantDate is after the date that you provide. License Granted Before The LIC_Granted_before query finds the records in the Cellular License table where the GrantDate is before the date that you provide. License Granted Between The LIC_Granted_between query finds the records in the Cellular License table where the GrantDate is between the dates that you provide. License With Market Name The LIC_with_MarketName query attaches the market names to the Cellular License table. The new table is created by joining the Cellular License table to the CMA table. PCS Broadband Database Table Structures This section contains information on the PCS Broadband Database table structures. PCS License The PCS License table describes active broadband PCS licenses. Field Name Description Type (Length) Indexed PCS_LICENSE (Polygon File) CallSign PCS license identifier (primary key) Character(10) Yes Communications Suite Product Guide 71

72 Field Name Description Type (Length) Indexed USI Unique System Identifier. Alternate PCS license identifier. Character(10) MarketName MTA or BTA market name Character(50) MarketCode MTA or BTA code Character(6) ChannelBlock Frequency block (A -F) Character(4) DBA Doing Business As name Character(50) Licensee Entity that owns the cellular license Character(100) LicenseContact Contact entity for the cellular license Character(100) LicenseOwner Owner of the license Character(100) GrantDate Date on which the license was granted DateTime ExpiredDate Date on which the license expires DateTime EffectiveDate Date on which the license becomes effective DateTime LastActionDate Date of last action DateTime _5yr_Buildout_Date Date 5-year buildout requirements were met. Please see Construction Requirements on page 74 for more information. DateTime _5yr_Buildout_Deadline Deadline for meeting 5-year buildout requirements. Please see Construction Requirements on page 74 for more information. DateTime _10yr_Buildout_Date Date 10-year buildout requirements were met. Please see Construction Requirements on page 74 for more information. DateTime _10yr_Buildout_Deadline Deadline for meeting 10-year buildout requirements. Please see Construction Requirements on page 74 for more information. DateTime AuctionID Auction identification DateTime MAPINFO_ID MapInfo Professional Identifier, which is only visible in Microsoft Access Long Integer Yes Region Object The geographic area of the license. t available in Microsoft Access <obj> PCS Frequency The PCS Frequency table contains frequency information for each PCS license. Field Name Description Type (Length) Indexed PCS_FREQUENCY (Polygon File) CallSign PCS license identifier (primary key) Character(10) Yes Communications Suite Product Guide 72

73 Field Name Description Type (Length) Indexed LowerBandMin Minimum lower band frequency in MHz for this license in its geographic area (defined by RegionObject) (primary key) Float Yes LowerBandMax Maximum lower band frequency in MHz for this license in its geographic area (defined by RegionObject) (primary key) Float Yes UpperBandMin Minimum upper band frequency in MHz for this license in its geographic area (defined by RegionObject) (primary key) Float Yes UpperBandMax Maximum upper band frequency in MHz for this license in its geographic area (defined by RegionObject) (primary key) Float Yes MarketCode MTA or BTA code Character(6) ChannelBlock Frequency block (A -F) Character(4) GeographicDescription Description of the geographic area of the PCS license operating in the specified frequencies. Only visible in Microsoft Access. Memo MAPINFO_ID MapInfo Professional Identifier, which is only visible in Microsoft Access Long Integer Yes Region Object The geographic area of the license operating at this frequency range. t available in Microsoft Access <obj> PCS DBA The PCS DBA table contains all PCS Doing Business as names that are used in the PCS database. Pitney Bowes created this table by aggregating PCS licenses by DBA. Field Name Description Type (Length) Indexed PCS_DBA (Polygon File) DBA Doing Business As name (primary key) Character(50) Yes MAPINFO_ID MapInfo Professional Identifier, which is only visible in Microsoft Access Long Integer Yes Region Object The geographic area of the DBA. t available in Microsoft Access <obj> PCS Channel Block The PCS Channel Block table contains frequency information for PCS channel blocks. Field Name Description Type (Length) Indexed PCS_CHANNEL_BLOCK ( Objects) ChannelBlock Frequency block (A -F) (primary key) Character(4) Yes Communications Suite Product Guide 73

74 Field Name Description Type (Length) Indexed LowerBandMin Minimum lower band frequency in MHZ Float LowerBandMax Maximum lower band frequency in MHz Float UpperBandMin Minimum upper band frequency in MHz Float UpperBandMax Maximum upper band frequency in MHz Float MAPINFO_ID MapInfo Professional Identifier, which is only visible in Microsoft Access Long Integer Yes BTA The BTA table contains all Basic Trading Areas (BTAs) in the United States and Puerto Rico. Field Name Description Type (Length) Indexed BTA (Polygon File) MarketCode Basic Trading Area (BTA) name (primary key) Character(6) Yes MarketName BTA market name Character(50) WithinMTA MTA that contains the BTA Character(6) MAPINFO_ID MapInfo Professional Identifier, which is only visible in Microsoft Access Long Integer Yes Region Object The geographic area of the BTA. t available in Microsoft Access <obj> MTA The MTA table contains all Major Trading Areas (MTAs) in the United States and Puerto Rico. Field Name Description Type (Length) Indexed BTA (Polygon File) MarketCode Major Trading Area (MTA) name (primary key) Character(6) Yes MarketName MTA market name Character(50) MAPINFO_ID MapInfo Professional Identifier, which is only visible in Microsoft Access Long Integer Yes Region Object The geographic area of the MTA. t available in Microsoft Access <obj> PCS Broadband Database Queries This section contains descriptions of the queries included with the PCS Broadband database. License 10 year Buildout Met Between The LIC_10yr_BO_met_between query finds the records in the PCS License table where Communications Suite Product Guide 74

75 _10yr_Buildout_Date is between the dates that you provide. License 10 year Buildout Date not Met and Deadline Between The LIC_10yr_BO_NOT_met_and_Deadline_between query finds the records in the PCS License table that did not meet the 10 year buildout date and where _10yr_Buildout_Deadline is between the dates that you provide. License 5 year Buildout Met Between The LIC_5yr_BO_met_between query finds the records in the PCS License table where _5yr_Buildout_Date is between the dates that you provide. License 5 year Buildout Date not Met and Deadline After The LIC_5yr_BO_NOT_met_and_Deadline_between query finds the records in the PCS License table that did not meet the 5 year buildout date and where _5yr_Buildout_Deadline is after the date that you provide. License 5 year Buildout Date not Met and Deadline Before The LIC_5yr_BO_NOT_met_and_Deadline_before query finds the records in the PCS License table that did not meet the 5 year buildout date and where _5yr_Buildout_Deadline is before the date that you provide. License 5 year Buildout Date not Met and Deadline Between The LIC_5yr_BO_NOT_met_and_Deadline_between query finds the records in the PCS License table that did not meet the 5 year buildout date and where _5yr_Buildout_Deadline is between the dates that you provide. License for DBA The LIC_For_DBA query finds the records in the PCS License table where the DBA name is similar to the DBA name that you provide. You do not need to provide the entire DBA name exactly as it appears in the DBA column. Make sure that the query returns the results that you wanted, because all DBA names that are similar to the DBA name that you entered will be returned. License for DBA with Frequency The LIC_For_DBA_FR query finds the records in the PCS License table where the DBA name is similar to the DBA name that you provide and attaches frequency information from the PCS Frequency table. You do not need to provide the entire DBA name exactly as it appears in the DBA column. Make sure that the query returns the results that you wanted, because all DBA names that are similar to the DBA name that you entered will be returned. Market Code The MarketCode query creates a list of all MTAs and BTAs with their associated Market Names from the PCS License table. PCS Frequency Total Bandwidth with License Information The PCS_FREQUENCY_BandwidthTotal_with_LIC_info query joins the information in the PCS Frequency table to the PCS License table and calculates the total frequency for each record. The total frequency data is contained in the TotalBandwidth column. The total frequency is calculated using the following equation: (LowerBandMax - LowerBandMin) + (UpperBandMax - UpperBandMin)=TotalBandwidth AWS Database Table Structures Communications Suite Product Guide 75

76 This section covers the Advanced Wireless Services (AWS) database table structures in MobileMarketInfo AWS License The AWS License table describes active broadband AWS licenses: Field Name Description Type (Length) Indexed AWS License (Polygon File) CallSign AWS license identifier (primary key) Character(10) Yes USI Unique System Identifier. Alternate AWS license identifier. Character(10) MarketName AWS market name Character(50) MarketCode AWS market code Character(6) ChannelBlock Frequency block (A - F) Character(1) DBA Doing Business As name Character(50) Licensee Entity that owns the AWS license Character(100) LicenseContact Contact entity for the AWS license Character(100) LicenseOwner Owner of the License Character(100) GrantDate Date on which the license was granted Date ExpiredDate Date on which the license expires Date EffectiveDate Date on which the license becomes effective Date LastActionDate Date of last acton Date AuctionID Auction identification DateTime Region object The geographic area of the AWS License. t available in Microsoft Access <obj> AWS Frequency The AWS Frequency table contains frequency information for each AWS License. Field Name Description Type (Length) Indexed AWS Frequency (Polygon File) CallSign AWS license identifier (primary key) Character(10) Yes LowerBandMin Minimum lower band frequency in MHz (primary key) Float Yes LowerBandMax Maximum lower band frequency in MHz (primary key) Float Yes UpperBandMin Minimum upper band frequency in MHz Float Yes Communications Suite Product Guide 76

77 Field Name Description Type (Length) Indexed UpperBandMax Maximum upper band frequency in MHz (primary key) Float Yes MarketCode BEA, CMA or REA identifier Character(6) Yes ChannelBlock Frequency block (A - F) Character(4) Region object The geographic area of the AWS License operating at this frequency range. t available in Microsoft Access <obj> Communications Suite Product Guide 77

78 AWS DBA The AWS DBA table contains all AWS Doing Business As names that are used in the AWS database. Pitney Bowes created this table by aggregating AWS licenses by DBA. Field Name Description Type (Length) Indexed AWS DBA (Polygon File) DBA Doing Business As name Character(50) Yes Region object The geographic area of the CMA. Each CMA is composed of a collection of counties <obj> AWS Channel Block The AWS Channel Block table contains frequency information AWS channel blocks. Field Name Description Type (Length) Indexed AWS Channel Block ( Objects) ChannelBlock Frequency block (A - F) Character(4) Yes LowerBandMin Minimum lower band frequency in MHz Float LowerBandMax Maximum lower band frequency in MHz Float UpperBandMin Minimum upper band frequency in MHz Float UpperBandMax Maximum upper band frequency in MHz Float AWS CMA The AWS CMA table contains all Cellular Market Areas in the United States and Puerto Rico. Field Name Description Type (Length) Indexed AWS CMA (Polygon File) MarketCode CMA identifier (primary key) Character(6) Yes MarketName CMA market name Character(50) Region object The geographic area of the CMA. Each CMA is composed of a collection of counties <obj> AWS BEA The AWS BEA table contains all Business Economic Areas (BEAs) in the United States and Puerto Rico. Field Name Description Type (Length) Indexed AWS BEA (Polygon File) Communications Suite Product Guide 78

79 Field Name Description Type (Length) Indexed MarketCode BEA identifier (primary key) Character(6) Yes MarketName BEA market name Character(50) Region object The geographic area of the BEA. Each BEA is composed of a collection of counties <obj> AWS REA The AWS REA table contains all Regional Economic Area (REAs) in the United States and Puerto Rico. Field Name Description Type (Length) Indexed AWS REA (Polygon File) MarketCode REA identifier (primary key) Character(6) Yes MarketName REA market name Character(50) Region object The geographic area of the REA. Each REA is composed of a collection of counties <obj> AWS Broadband Database Queries This section contains descriptions of the queries included with the AWS database. You can use these queries in Microsoft Access and MapInfo Professional. For information about using the queries in MapInfo Professional, see Using MobileMarketInfo Queries in MapInfo Professional. All Licenses within a BEA The All_LIC_within_BEA query finds the records in the AWS License table that operate within the BEA that you provide. The query includes all REA licenses (C frequency blocks) operating within the BEA as well as all BEA licenses (A, E frequency blocks). All Licenses within a BEA with Frequency Information The All_LIC_within_BEA_FR query finds the records in the AWS License table that operate within the BEA that you provide and attaches frequency information from the AWS Frequency table. The query includes all REA licenses (C frequency blocks) operating within the BEA as well as all BEA licenses (A, E frequency blocks). All Licenses within a REA The All_LIC_within_REA query finds the records in the AWS License table that operate within the REA that you provide.the query includes all BEA licenses (A, E frequency blocks) operating in the REA as well as all REA licenses (C frequency blocks). All Licenses within a REA with Frequency Information The All_LIC_within_ REA_FR query finds the records in the AWS License table that operate within the REA that you provide and attaches frequency information from the AWS Frequency table. The query includes all BEA licenses (A, E frequency blocks) operating in the REA as well as all REA licenses (C frequency blocks). License for DBA The LIC_For_DBA query finds the records in the AWS License table where the DBA name is similar to the DBA name that you provide. You do not need to provide the entire DBA name exactly as it appears in the DBA column. Make sure that the query returns the results that you wanted, because all DBA names that are similar to the DBA name that you entered will be returned. License for DBA with Frequency The LIC_For_DBA_FR query finds the records in the AWS License table where the DBA name is similar to the DBA name that you provide and attaches frequency Communications Suite Product Guide 79

80 information from the AWS Frequency table. You do not need to provide the entire DBA name exactly as it appears in the DBA column. Make sure that the query returns the results that you wanted, because all DBA names that are similar to the DBA name that you entered will be returned. Market Code The MarketCode query creates a list of all REA s and BEAs with their associated Market Names from the AWS License table. AWS Frequency Total Bandwidth with License Information The AWS_FREQUENCY_BandwidthTotal_with_LIC_info query joins the information in the AWS Frequency table to the AWS License table and calculates the total frequency for each record. The total frequency data is contained in the TotalBandwidth column. The total frequency is calculated using the following equation: (LowerBandMax - LowerBandMin) + (UpperBandMax - UpperBandMin)=TotalBandwidth 700 MHz Band Services Table Structure This section contains information for the Upper and Lower 700 MHz Band database table structures. U700 and L700 License The U700 and L700 License table describes active broadband U700 and L700 licenses: Field Name Description Type (Length) Indexed U700 and L700 License (Polygon File) CallSign U700 and L700 license identifier (primary key) Character(10) Yes USI Unique System Identifier. Alternate AWS license identifier. Character(10) MarketName U700 and L700 market name Character(50) MarketCode U700 and L700 market code Character(6) ChannelBlock Frequency block (A - F) Character(1) DBA Doing Business As name Character(50) Licensee Entity that owns the AWS license Character(100) LicenseContact Contact entity for the AWS license Character(100) LicenseOwner Owner of the License Character(100) GrantDate Date on which the license was granted Date ExpiredDate Date on which the license expires Date EffectiveDate Date on which the license becomes effective Date LastActionDate Date of last acton Date _5yr_Buildout_Date Date 5-year buildout requirements were met. Please see Construction Requirements on page 74 for more information. DateTime _5yr_Buildout_Deadline Deadline for meeting 5-year buildout requirements. Please see Construction Requirements on page 74 for more information. DateTime Communications Suite Product Guide 80

81 Field Name Description Type (Length) Indexed _10yr_Buildout_Date Date 10-year buildout requirements were met. Please see Construction Requirements on page 74 for more information. DateTime _10yr_Buildout_Deadlin e Deadline for meeting 10-year buildout requirements. Please see Construction Requirements on page 74 for more information. DateTime AuctionID Auction identification DateTime Region object The geographic area of the U700 and L700 License. t available in Microsoft Access <obj> U700 and L700 Frequency The U700 and L700 Frequency table contains frequency information for each U700 and L700 License. Field Name Description Type (Length) Indexed U700 and L700 Frequency (Polygon File) CallSign U700 and L700 license identifier (primary key) Character(10) Yes LowerBandMin Minimum lower band frequency in MHz (primary key) Float Yes LowerBandMax Maximum lower band frequency in MHz (primary key) Float Yes UpperBandMin Minimum upper band frequency in MHz Float Yes UpperBandMax Maximum upper band frequency in MHz (primary key) Float Yes MarketCode BEA, CMA or REA identifier Character(6) Yes ChannelBlock Frequency block (A - F) Character(4) Region object The geographic area of the U700 and L700 License operating at this frequency range. t available in Microsoft Access <obj> Communications Suite Product Guide 81

82 U700 and L700 DBA The U700 and L700 DBA table contains all U700 and L700 Doing Business As names that are used in the U700 and L700 database. Pitney Bowes created this table by aggregating U700 and L700 licenses by DBA. Field Name Description Type (Length) Indexed U700 and L700 DBA (Polygon File) DBA Doing Business As name Character(50) Yes Region object The geographic area of the CMA. Each CMA is composed of a collection of counties <obj> U700 and L700 Channel Block The U700 and L700 Channel Block table contains frequency information U700 and L700 channel blocks. Field Name Description Type (Length) Indexed U700 and L700 Channel Block ( Objects) ChannelBlock Frequency block (A - F) Character(4) Yes LowerBandMin Minimum lower band frequency in MHz Float LowerBandMax Maximum lower band frequency in MHz Float UpperBandMin Minimum upper band frequency in MHz Float UpperBandMax Maximum upper band frequency in MHz Float U700 and L700 REA The U700 and L700 REA table contains all Regional Economic Areas (REAs) in the United States and Puerto Rico. Field Name Description Type (Length) Indexed U700 and L700 REA (Polygon File) MarketCode REA identifier (primary key) Character(6) Yes MarketName REA market name Character(50) Region object The geographic area of the REA. Each REA is composed of a collection of counties <obj> U700 and L700 BEA The U700 and L700 BEA table contains all Business Economic Areas (BEAs) in the United States and Puerto Rico. Communications Suite Product Guide 82

83 Field Name Description Type (Length) Indexed U700 and L700 BEA (Polygon File) MarketCode BEA identifier (primary key) Character(6) Yes MarketName BEA market name Character(50) Region object The geographic area of the BEA. Each BEA is composed of a collection of counties <obj> U700 and L700 CMA The U700 and L700 CMA table contains all Cellular Market Areas in the United States and Puerto Rico. Field Name Description Type (Length) Indexed U700 and L700 CMA CMA (Polygon File) MarketCode CMA identifier (primary key) Character(6) Yes MarketName CMA market name Character(50) Region object The geographic area of the CMA. Each CMA is composed of a collection of counties <obj> U700 Database Queries This section contains descriptions of the queries included with the U700 database. You can use these queries in Microsoft Access and MapInfo Professional. For information about using the queries in MapInfo Professional, see Using MobileMarketInfo Queries in MapInfo Professional. All Licenses within an REA The All_LIC_within_REA query finds the records in the U700 License table that operate within the REA that you provide. All Licenses within an REA with Frequency Information The All_LIC_within_ REA_FR query finds the records in the U700 License table that operate within the REA that you provide, and attaches frequency information from the U700 Frequency table. License for DBA The LIC_For_DBA query finds the records in the U700 License table where the DBA name is similar to the DBA name that you provide. You do not need to provide the entire DBA name exactly as it appears in the DBA column. Make sure that the query returns the results that you wanted, because all DBA names that are similar to the DBA name that you entered will be returned. License for DBA with Frequency The LIC_For_DBA_FR query finds the records in the U700 License table where the DBA name is similar to the DBA name that you provide, and attaches frequency information from the U700 Frequency table. You do not need to provide the entire DBA name exactly as it appears in the DBA column. Make sure that the query returns the results that you wanted, because all DBA names that are similar to the DBA name that you entered will be returned. Market Code The MarketCode query creates a list of all REAs with their associated Market Names from the U700 License table. U700 Frequency Total Bandwidth with License Information Communications Suite Product Guide 83

84 The U700_FREQUENCY_BandwidthTotal_with_LIC_info query joins the information in the U700 Frequency table to the U700 License table, and calculates the total frequency for each record. The total frequency data is contained in the TotalBandwidth column. The total frequency is calculated using the following equation: (LowerBandMax-LowerBandMin)+(UpperBandMax-UpperBandMin)= TotalBandwidth L700 Database Queries This section contains descriptions of the queries included with the L700 database. You can use these queries in Microsoft Access and MapInfo Professional. For information about using the queries in MapInfo Professional, see Using MobileMarketInfo Queries in MapInfo Professional on page 104. All Licenses within a BEA The All_LIC_within_BEA query finds the records in the UL00 License table that operate within the REA that you provide. The query includes all CMA licenses operating within the BEA, as well as all BEA licenses. All Licenses within a BEA with Frequency Information The All_LIC_within_ BEA_FR query finds the records in the U700 License table that operate within the REA that you provide, and attaches frequency information from the U700 Frequency table. The query includes all CMA licenses operating within the BEA, as well as all BEA licenses. All Licenses within a CMA The All_LIC_within_CMA query finds the records in the L700 License table that operate within the CMA that you provide.the query includes all BEA licenses operating in the CMA, as well as all CMA licenses. All Licenses within a CMA with Frequency Information The All_LIC_within_ CMA_FR query finds the records in the L700 License table that operate within the CMA that you provide, and attaches frequency information from the L700 Frequency table. The query includes all BEA licenses operating in the CMA, as well as all CMA licenses. License for DBA The LIC_For_DBA query finds the records in the L700 License table where the DBA name is similar to the DBA name that you provide. You do not need to provide the entire DBA name exactly as it appears in the DBA column. Make sure that the query returns the results that you wanted, because all DBA names that are similar to the DBA name that you entered will be returned. License for DBA with Frequency The LIC_For_DBA_FR query finds the records in the L700 License table where the DBA name is similar to the DBA name that you provide, and attaches frequency information from the L700 Frequency table. You do not need to provide the entire DBA name exactly as it appears in the DBA column. Make sure that the query returns the results that you wanted, because all DBA names that are similar to the DBA name that you entered will be returned. Market Code The MarketCode query creates a list of all BEAs with their associated Market Names from the L700 License table. L700 Frequency Total Bandwidth with License Information The L700_FREQUENCY_BandwidthTotal_with_LIC_info query joins the information in the L700 Frequency table to the L700 License table, and calculates the total frequency for each record. The total frequency data is contained in the TotalBandwidth column. The total frequency is calculated using the following equation: (LowerBandMax-LowerBandMin)+(UpperBandMax-UpperBandMin)= TotalBandwidth Communications Suite Product Guide 84

85 MobileMarketAnalyzer This section explains how to use the MapBasic tool MobileMarketAnalyzer that is included with MobileMarketInfo. MobileMarketAnalyzer is an easy to use MapBasic application that allows you to select and view useful subsets of the MobileMarketInfo database. MobileMarketAnalyzer demonstrates the types of analysis that can be performed using MobileMarketInfo. Starting MobileMarketAnalyzer To launch the program MobileMarketAnalyzer in MapInfo Professional, follow the steps below. 1. Choose Tools>Run MapBasic Program. The Run MapBasic Program window appears. 2. Browse to the location of MobileMarketAnalyzer.mbx. te MobileMarketAnalyzer.mbx must be located in the MobileMarketInfo installation directory for the program to operate properly. 3. Select MobileMarketAnalyzer.mbx, and click Open. MobileMarketAnalyzer launches, a MobileMarketAnalyzer menu is added to the Tools menu, and a MobileMarketAnalyzer button pad is added to the MapInfo Professional buttons. Using MobileMarketAnalyzer MobileMarketAnalyzer automates both carrier analysis and market analysis, each of which is described below. Performing a Carrier Analysis When you perform a Carrier Analysis, you enter a whole or partial Doing Business As (DBA) name and specify whether you want to retrieve data from the Cellular or PCS database. MobileMarketAnalyzer then returns complete DBA, License, and Frequency (PCS only) information from the database according to the preferences you select. To perform a Carrier Analysis, follow the instructions below. 1. Do one of the following: Choose Tools>MobileMarketAnalzer>Analyze Carrier. Click the Analyze Carrier button. Communications Suite Product Guide 85

86 The Analyze Carrier window appears. 2. Enter a whole or partial DBA name in the Enter DBA field. The DBA name does not need to be exactly as it appears in the DBA table. MobileMarketAnalyzer uses a LIKE query to locate the DBA name. For example, if you enter verizon for the DBA, the program finds the Verizon Wireless DBA name. 3. Select either the PCS or the Cellular radio button to specify whether MobileMarketAnalyzer should return PCS or Cellular data. 4. Use the check boxes in the Select Matching section to define the types of data that you want to retrieve and how you want to display them. Each type of data is described in the table PCS and Cellular Data Types, below. 5. Select either the Browse or the Show checkbox for each type of data that you want to retrieve. If you select the Browse checkbox, the data is shown in a new browser window. If you select the Show check box, the data is displayed in a map window. Use the Border Style button to set the style of the map region s borders. Use the Fill Style button to set the style of the map region s fill. 6. Check the New Mapper check box if you want to display the results in a new map window. If you do not check the New Mapper checkbox, the results are displayed in the most recently used map window. 7. Use the Reset button to clear the dialog. 8. Click OK. The MobileMarketAnalyzer displays the data you requested in the format that you specified. Browser windows are displayed in the following order: DBA data License data Frequency data The map layers are drawn in the following order: DBA data (bottom) License data (middle) Frequency data (top) te Because MobileMarketAnalyzer queries the MobileMarketInfo database, the resulting tables are Communications Suite Product Guide 86

87 not automatically saved. Additionally, if you close any of the tables that the queries are based upon, the query will also be closed. PCS and Cellular Data Types DBA data Retrieving PCS data selects all instances of the DBA name from the PCS_DBA table. The selection is named [DBA Name]_PCS_DBA, where [DBA Name] is the carrier that corresponds to the DBA name that you entered. For example, if you enter Verizon for the DBA name, the resulting table is named Verizon_Wireless_PCS_DBA. Retrieving Cellular data selects all instances of the DBA name from the CELLULAR_DBA table. The selection is named [DBA Name]_CELL_DBA, where [DBA Name] is the carrier that corresponds to the DBA name. License data Retrieving PCS data selects all licenses having the DBA name that you entered from the PCS_LICENSE table. The selection is named [DBA Name]_PCS_LIC, where [DBA Name] is the carrier that corresponds to the DBA name that you entered. Retrieving Cellular data selects all licenses that have the DBA name that you entered from the CELLULAR_LICENSE table, and the result is joined to the CMA table. The geographic area for each license is represented as the entire CMA. The selection is named [DBA Name]_CELL_LIC, where [DBA Name] is the carrier that corresponds to the DBA name that you entered. Frequency data Available only by retrieving PCS data. The PCS_FREQUENCY table is joined to the PCS_LICENSE table and all licenses that have the DBA name entered are selected. The Total_Bandwidth column is created using the following formula: (LowerBandMax LowerBandMin) + (UpperBandMax UpperBandMin). The selection is named [DBA Name]_PCS_FREQ, where [DBA Name] is the carrier that corresponds to the DBA name entered. Performing a Market Analysis When you perform a Market Analysis, you enter a Market Code (CMA, MTA, or BTA) and optionally enter a Channel Block. MobileMarketAnalyzer then returns complete License and Frequency (PCS only) information from the database according to the preferences you select. To perform a Market Analysis, follow the instructions below. 1. Do one of the following: Choose Tools>MobileMarketAnalzer>Analyze Market. Click the Analyze Market button. Communications Suite Product Guide 87

88 The Analyze Market window appears. 2. Enter a complete CMA, MTA, or BTA market code in the Market Code field. If the first three characters of the Market Code are CMA, then the data is selected from the Cellular database. If the first three characters of the Market Code are MTA or BTA, then the resulting data is selected from the PCS database. 3. Optionally enter a Channel Block in the Channel Block field. If you do not enter a Channel Block, MobileMarketAnalyzer will return information for all Channel Blocks. 4. Use the checkboxes in the Select Matching section to define the types of data that you want to retrieve and how you want to display it. Each type of data is described in the table Market Code and Channel Block Data Types, below. 5. Select either the Browse or the Show checkbox for each type of data that you want to retrieve. When you select the Browse checkbox, the data is shown in a new browser window. When you select the Show check box, the data is displayed in a map window. Use the Border Style button to set the style of the map region s borders. Use the Fill Style button to set the style of the map region s fill. 6. Check the New Mapper check box if you want to display the results in a new map window. If you do not check the New Mapper check box, the results are displayed in the most recently used map window. 7. Use Reset to clear the dialog. 8. Click OK. The MobileMarketAnalyzer displays the data you requested in the format that you specified. Browser windows are displayed in the following order: License data Frequency data The map layers are drawn in the following order: License data (bottom) Frequency data (top) te Since MobileMarketAnalyzer queries the MobileMarketInfo database, the resulting tables are not automatically saved. Additionally, if you close any of the tables that the queries are based upon, the query will also be closed. Market Code and Channel Block Data Types Communications Suite Product Guide 88

89 License data If you entered an MTA or BTA Market Code, all licenses that have the Market Code and Channel Block that you entered are selected from the PCS_LICENSE table. If you supplied a channel block, the selection is named [Market Code]_[Channel Block]_PCS_LIC, where [Market Code] is the MTA or BTA code and [Channel Block] is the Channel Block that you entered. If you did not supply a Channel Block, the selection is named [Market Code]_PCS_LIC. If you entered a CMA Market Code, all licenses that have the Market Code and Channel Block that you entered are selected from the CELLULAR_LICENSE table. If you supplied a channel block, the selection is named [Market Code]_[Channel Block]_CELL_LIC, where [Market Code] is the CMA code and [Channel Block] is the Channel Block that you entered. If you did not supply a Channel Block, the selection is named [Market Code]_CELL_LIC. All licenses with the input Market Code and Channel Block are selected from the PCS_FREQUENCY table. The result is joined to the PCS_LICENSE so that the Licensee and DBA data are available. If you supplied a channel block, the selection is named [Market Code]_[Channel Block]_PCS_FREQ, where [Market Code] is the MTA or BTA code and [Channel Block] is the Channel Block that you entered. If you did not supply a Channel Block, the selection is named [Market Code]_PCS_FREQ. Frequency data Available only when a PCS Market Code (MTA or BTA) is entered. Communications Suite Product Guide 89

90 Using MobileMarketInfo This section provides instructions on using the MobileMarketInfo Queries and demonstrates several sample applications. Using MobileMarketInfo Queries in MapInfo Professional MobileMarketInfo provides several query templates for use in Microsoft Access and MapInfo Professional. Information about these templates is provided in the following sections: Cellular Database Queries PCS Broadband Database Queries This section provides general information on using the queries in MapInfo Professional. See the Microsoft Access documentation set for instructions on using the queries in Microsoft Access. 1. Choose File>Open Table and open the tables that you are querying. 2. Choose Query>SQL Select. The SQL Select window appears. 3. Click Load Template. The Load Dialog from Query File window appears. Communications Suite Product Guide 90

91 4. Browse to the location of the query that you want to use, select it, and click Open. You are returned to the SQL Select dialog, and the query template is loaded. Some of the query templates require you to enter additional information in the where Condition window. The image below shows part of the LIC_For_DBA query. In this example, you must enter a DBA name, such as Verizon, between the quotation marks. 5. Click OK. The results of your query are displayed in a Browser window. Selecting License or Frequency Data by CallSign To select license or frequency data by callsign, follow the instructions below. 1. Choose File>Open Table and open a license or frequency table. 2. Choose Query>SQL Select. The SQL Select window appears. 3. Enter the name of the license or frequency table in the from Tables window. 4. Enter CallSign = XXXXXXX, where XXXXXXX is the desired CallSign, in the where Condition window. In the example below, CallSign KNKN392 is selected from the CELLULAR_LICENSE table. 5. Click OK The license or frequency data associated with the CallSign that you specified is returned in a Browser window. Communications Suite Product Guide 91

92 Selecting License Data by Licensee Name When an entity owns multiple licenses, their name can sometimes be spelled differently in the Licensee column of the MobileMarketInfo license tables. For example, there are two ways that Lewis and Clark Communications spells their name in the PCS_LICENSE table: Lewis and Clark Communications, L.L.C. Lewis and Clark Communications, LLC One entry uses L.L.C. and the other uses LLC. You can use the InStr command select instances of a substring from the Licensee column. Since the InStr command is case-sensitive, you should use the UCase$ function to convert the entries to uppercase for the analysis. The following example demonstrates how to use the InStr and UCase$ functions to find all instances of Lewis and Clark in the Licensee column of the PCS_LICENSE table. 1. Choose File>Open Table and open the PCS_LICENSE table. 2. Choose Query>SQL Select. The SQL Select window appears. 3. Enter PCS_LICENSE in the from Tables window. 4. Enter InStr(1,UCase$(Licensee), LEWIS AND CLARK ) in the where Condition window. The example below shows the completed SQL Select window for this query. 5. Click OK. All instance of LEWIS AND CLARK are returned in a Browser window. Creating a Ranged Thematic Map of Bandwidth Assets You can use MobileMarketInfo to create a ranged thematic map of a carrier s bandwidth assets. To do this, follow the instructions below. 1. Choose Tools>Run MapBasic Program. The Run MapBasic Program window appears. 2. Browse to the location of MobileMarketAnalyzer.mbx. Communications Suite Product Guide 92

93 te MobileMarketAnalyzer.mbx must be located in the MobileMarketInfo installation directory for the program to operate properly. 3. Select MobileMarketAnalyzer.mbx, and click Open. 4. Click the Analyze Carrier button. The Analyze Carrier window appears. 5. Enter the DBA name of the carrier that you want to analyze in the Enter DBA window. 6. Select the PCS radio button. 7. Select the Frequency data Show checkbox. 8. Click the Border Style button to set the style of the map region s borders. Do not provide a fill style. The thematic map that you create will provide the fill style. The example below demonstrates the analysis for Sprint PCS. 9. Click OK. The Carrier Analysis results are displayed in a Map window. Communications Suite Product Guide 93

94 10. Choose Map>Create Thematic Map. The Create Thematic Map - Step of 1 of 3 window appears. 11. Choose Ranges as the Type. 12. Select Region Ranges Default from the Template Name list. 13. Click Next. The Create Thematic Map - Step 2 of 3 window appears. 14. Select [DBA Name]_PCS_FREQ from the Table dropdown list, where [DBA Name] is the DBA name that you entered in the Carrier Analysis dialog. 15. Select Total_Bandwidth from the Field dropdown list. 16. Click Next. The Create Thematic Map - Step 3 of 3 window appears. 17. Use this dialog customize the thematic map if you desire to do so. Communications Suite Product Guide 94

95 18. Click OK. The thematic map is drawn and shows the bandwidth assets for the carrier that you selected. The image below shows the thematic map for the Sprint PCS analysis. Comparing Carrier PCS to Cellular License Areas You can use MobileMarketInfo to compare a carrier s PCS license area to its cellular license area. To do this, follow the instructions below. 1. Choose Tools>Run MapBasic Program. The Run MapBasic Program window appears. 2. Browse to the location of MobileMarketAnalyzer.mbx. te MobileMarketAnalyzer.mbx must be located in the MobileMarketInfo installation directory for the program to operate properly. 3. Select MobileMarketAnalyzer.mbx, and click Open. Communications Suite Product Guide 95

96 4. Click the Analyze Carrier button. The Analyze Carrier window appears. 5. Enter the DBA name of the carrier that you want to analyze in the Enter DBA window. 6. Select the PCS radio button. 7. Select the DBA data Show checkbox. 8. Click the Border Style button to set the style of the PCS region s borders. 9. Click the Fill Style button to set the style of the PCS region s fill. 10. Click OK. The carrier s PCS territory is displayed on a map. 11. Click the Analyze Carrier button. The Analyze Carrier window appears. 12. Enter the DBA name of the carrier that you are analyzing in the Enter DBA window. 13. Select the Cellular radio button. 14. Select the DBA data Show checkbox. 15. Click the Border Style button to set the style of the Cellular region s borders. Select a border style that is different from the style that you selected for the PCS region s borders. 16. Click the Fill Style button to set the style of the Cellular region s fill. Select a fill style that is different from the style that you selected for the PCS region s fill. 17. Click OK. The carrier s Cellular map is drawn over the carrier s PCS map, allowing you to compare the carrier s PCS and Cellular territories. Data Source and Projection Pitney Bowes suite of telecom infrastructure databases are built using state PUC data, state tariff data, the Telcordia LERG Routing Guide (LERG), StreetPro, and other reference data. Communications Suite Product Guide 96

97 The MobileMarketInfo database has the following coverage, scale, coordinates, and projection Coverage United States and US Virgin Islands. Scale 1:24,000 Coordinates Latitude and Longitude Projection NAD 83 Communications Suite Product Guide 97

98 Chapter 7: PSAP Pro 7 8 PSAP Pro is a comprehensive compilation of Public Safety Answering Point (PSAP) agencies throughout the United States. PSAP Pro assists users determine PSAP communication center boundaries and contact information for emergency response services. In This Chapter PSAP Pro Overview PSAP Pro Content Table Structure

99 PSAP Pro Overview PSAP Pro provides contact information related to agencies that receive calls twenty-four hours a day, 7 days a week. These agencies may dispatch emergency response services or transfer the calls to other public safety agencies. PSAP Pro includes coverage areas and detailed contact information related to contacting a PSAP for emergency response planning. As an important note, it is always prudent to contact each authority and verify the information is correct for the intended use. Use cases specific to communications from alarm companies should refer to the product EmergencyInfoPro. The following figure illustrates detailed information that is typically available for each PSAP record. The PSAP service is regulated by the Federal Communications Commission (FCC). It is a part of the nation s emergency response and disaster preparedness system, and handles calls from both landline and wireless communications. A PSAP is a physical call center location which may have Basic or Enhanced capabilities. The Integrated Public Alert and Warming System (IPAWS) is also related to these capabilities as described below. Basic systems may include ANI/ALI information (Automatic Number Identification/Automatic Location Identification). Enhanced systems have ANI/ALI plus selective routing capabilities. Selective routing provides Communications Suite Product Guide 99

100 greater accuracy in routing a call to the appropriate PSAP responsible for a geographic jurisdiction. Selective routing also permits calls to be quickly transferred from the primary public safety answering point to emergency service providers or to backup or secondary PSAPs. Enhanced can provide the PSAP with the telephone number of the originator of a wireless 911 call, the location of the cell site or base station transmitting the call, and the latitude and longitude of the caller. Enhanced systems now include both wireless and VoIP technology. IPAWS, maintained by the Federal Emergency Management Agency (FEMA), is an integrated gateway through which an authorized public safety entity (such as a PSAP) may alert the public to emergencies such as a wildfire or an AMBER alert for a missing child. Using IPAWS, authorized users may send alerts through the Emergency Alert System (EAS), which delivers the information via radio, television, and other media, and/or Wireless Emergency Alerts (WEA) to consumers cell phones. PSAP Pro Database PSAP Pro contains the following main types of data: PSAP Agency Information, such as Agency Name, ID, Type and FCC ID Coordinator Contact Information (if applicable) Site Contact Information The following table entitled PSAP includes the table structure, to include a description of each field. Communications Suite Product Guide 100

101 Table Structure PSAP Column Name Description Type (Length) Indexed PSAP_Agency Public Safety Answering Point (PSAP) communications center name Char(120) PSAP_ID Pitney Bowes persistent unique identification number for PSAP record Integer Yes PSAP_FCCID Federal Communications Commission (FCC) identification number for PSAP Record Integer PSAP_Type Basic, Enhanced, Military or n Char(25) PSAP_EmergencyPhone Emergency phone number to call if an alarm is handled by the PSAP Char(15) PSAP_GeneralComments General comments regarding the PSAP record Char(254) PSAP_CoordContactName Coordinator name (a Coordinator may be responsible for multiple PSAP sites) Char(100) PSAP_CoordTitle Coordinator title Char(100) PSAP_CoordPhone Coordinator phone number Char(15) PSAP_CoordFax Coordinator fax number Char(15) PSAP_Coord Coordinator address Char(254) PSAP_CoordStreet Coordinator street Char(80) PSAP_CoordCity Coordinator city Char(40) PSAP_CoordState Coordinator state Char(2) PSAP_CoordZip Coordinator zipcode Char(10) PSAP_SiteContactName Site contact name (PSAP sites may report to a coordinator) Char(100) PSAP_SitePhone Site contact phone number Char(15) PSAP_SiteFax Site fax number Char(15) PSAP_Site Site address Char(254) PSAP_SiteStreet Site street Char(80) PSAP_SiteCity Site city Char(40) PSAP_SiteState Site state Char(2) PSAP_SiteZip Site zipcode Char(10) PSAP_SiteCounty Site county Char(40) PSAP_SiteCountyFIPS Site county Federal Information Processing Standard (FIPS) code Char(5) Communications Suite Product Guide 101

102 Data Source and Projection PSAP Pro is based on data from PSAP Pro Data Resources, Inc. and Pitney Bowes. The PSAP Pro database has the following coverage, scale, and coordinates: Coverage United States Scale 1:24,000 Coordinates Latitude and Longitude Projection NAD 83 Communications Suite Product Guide 102

103 Chapter 8: EmergencyInfo Pro 8 EmergencyInfoPro is a compilation of Public Safety Answering Point (PSAP) and Authority Having Jurisdiction (AHJ) agencies throughout the United States, to assist alarm companies determine Emergency Medical Service (EMS), Fire and Police contact information. In This Chapter EmergencyInfo Pro Overview Using EmergencyInfo Pro Visual Differences Between Spatial Layers Table Structures

104 EmergencyInfo Pro Overview EmergencyInfoPro is a compilation of Public Safety Answering Point (PSAP) and Authority Having Jurisdiction (AHJ) agencies throughout the United States, to assist alarm companies determine the primary contact information for an Emergency Medical Service (EMS), Fire or Police emergency. When an EMS, fire, or police alarm is activated for a specific location, a Public Safety Answering Point (PSAP) communications center is notified if the PSAP is the primary contact for a location. The alarm is then dispatched to an Authority Having Jurisdiction (AHJ) such as an EMS, fire or police agency. The AHJ then responds accordingly. If the PSAP is not the primary contact for a location (through agreement between the PSAP and an AHJ), the AHJ should be notified directly. EmergencyInfo Pro provides information as to which agencies should be contacted regarding an alarm, to include geographic coverage of the respective entities. As an important note, it is always prudent to contact each authority and verify the information is correct for the intended use. EmergencyInfo Pro Database EmergencyInfo Pro includes the following spatial layers: PSAP_EmergencyInfoPro Public Safety Answering Point contact information for all areas of the country. EMS_EmergencyInfoPro EMS contact information for those areas of the country where the EMS AHJ is the primary contact instead of the PSAP. Fire_EmergencyInfoPro Fire contact information for those areas of the country where the Fire AHJ is the primary contact instead of the PSAP. Police_EmergencyInfoPro Police contact information for those areas of the country where the Police AHJ is the primary contact instead of the PSAP. EmergencyInfoPro An aggregate layer containing all of the above 4 layers of information in a single flat layer. Using EmergencyInfo Pro Use Case A business is located at longitude and latitude An alarm company is installing an alarm system for the business and is investigating EMS, fire and police contact information for this location. The alarm company is also determining if the PSAP or the AHJ is the primary contact for each type of emergency. Communications Suite Product Guide 104

105 Option 1 Solution (Recommended for Single Point Query) Query the EmergencyInfoPro aggregate layer and use the contact information in fields prepended with EMS_, Fire_ and Police_. Example syntax would be as follows to request the information: Select * from EmergencyInfoPro where obj Intersects(CreatePoint( , )) Use the contact information for EMS, Fire and Police from the fields prepended with the respective AHJ names (EMS_, Fire_ and Police_). te for this example location, the PSAP is the primary contact and would be the appropriate agency to contact in the event of an EMS emergency. te if the EMS_EmergencyInfoPro layer (not the aggregate layer) was visualized at this location, there would be an intentional hole. However, in the aggregate EmergencyInfoPro layer the EMS contact information is populated as the same as the PSAP contact information. In other words, the EMS fields reflect the PSAP contact information, since the PSAP has jurisdiction to handle the call. The EmergencyInfoPro aggregate layer eliminates the need for multiple query tool actions across each of the EMS, Fire and Police layers to arrive at the same determination, as is the case for Option 4. Communications Suite Product Guide 105

106 Option 2 Solution (Recommended for Visual Analysis of Boundaries) Visualize the EMS_EmergencyInfoPro, Fire_EmergencyInfoPro, Police_EmergencyInfoPro and PSAP_EmergencyInfoPro individual layers in GIS software, find the business location in a map window and visualize each layer to find the boundaries of nearby EMS, Fire, Police and PSAP agencies. Unlike Option 1, this solution would require multiple query tool actions and logic to determine the appropriate entity to contact for each emergency. However, the full extents of each emergency agency are easily determined. te for this example location, a primary contact is not available in the EMS layer (there is an intentional hole for this area in the EMS layer). A primary contact can, however, be found in the PSAP layer for the location. This indicates that the PSAP is the primary contact and would be the appropriate agency to contact in the event of an EMS emergency. Communications Suite Product Guide 106

107 Visual Differences between Spatial Layers A greater number of objects exist in the EmergencyInfoPro aggregate layer than in the individual EMS, Fire, Police and PSAP layers. The EmergencyInfoPro aggregate layer represents the smallest boundaries in which the EMS, Fire, Police and PSAP are the same across each layer. For example, the yellow areas in the following figure represent the EmergencyInfoPro aggregate layer in which the EMS, Fire, Police and PSAP are the same across each layer. In order to view the complete boundary of the primary FIRE AHJ (in which the EMS, Police and/or PSAP would differ), the red areas can be overlayed from the FIRE_EmergencyInfoPro layer. Each red boundary from the Fire_EmergencyInfoPro layer shows contiguous coverage areas for Fire AHJs being the primary contact point for alarm incidents in these locations. Communications Suite Product Guide 107

108 Table Structures EmergencyInfoPro (Aggregate Layer) Column Name Description Type (Length) Indexed PSAP_Agency Public Safety Answering Point (PSAP) communications center name Char(120) PSAP_ID Pitney Bowes persistent unique identification number for PSAP record Integer PSAP_FCCID Federal Communications Commission (FCC) identification number for PSAP Record Integer PSAP_Type Basic, Enhanced, Military or n Char(25) PSAP_EmergencyPhone Emergency phone number to call if an alarm is handled by the PSAP Char(15) PSAP_GeneralComments General comments regarding the PSAP record Char(254) PSAP_CoordContactName Coordinator name (a Coordinator may be responsible for multiple PSAP sites) Char(100) PSAP_CoordTitle Coordinator title Char(100) PSAP_CoordPhone Coordinator phone number Char(15) PSAP_CoordFax Coordinator fax number Char(15) PSAP_Coord Coordinator address Char(254) PSAP_CoordStreet Coordinator street Char(80) PSAP_CoordCity Coordinator city Char(40) PSAP_CoordState Coordinator state Char(2) PSAP_CoordZip Coordinator zipcode Char(10) PSAP_SiteContactName Site contact name (PSAP sites may report to a coordinator) Char(100) PSAP_SitePhone Site contact phone number Char(15) PSAP_SiteFax Site fax number Char(15) PSAP_Site Site address Char(254) PSAP_SiteStreet Site street Char(80) PSAP_SiteCity Site city Char(40) PSAP_SiteState Site state Char(2) PSAP_SiteZip Site zipcode Char(10) PSAP_SiteCounty Site county Char(40) PSAP_SiteCountyFIPS Site county Federal Information Processing Standard (FIPS) code Char(5) EMS_Agency Emergency Medical Service agency name Char(120) EMS_ID Pitney Bowes persistent unique identification number for EMS record Integer Communications Suite Product Guide 108

109 Column Name Description Type (Length) Indexed EMS_FCCID Federal Communications Commission (FCC) identification number for EMS Record Integer EMS_Type Examples include: City, County, Military, State, University, Regional Char(25) EMS_EmergencyPhone Emergency phone number to call if an alarm is handled by the EMS Char(15) EMS_GeneralComments General comments regarding the EMS record Char(254) EMS_SiteContactName Site contact name (EMS sites may report to a coordinator) Char(100) EMS_SitePhone Site contact phone number Char(15) EMS_SiteFax Site fax number Char(15) EMS_Site Site address Char(254) EMS_SiteStreet Site street Char(80) EMS_SiteCity Site city Char(40) EMS_SiteState Site state Char(2) EMS_SiteZip Site zipcode Char(10) Fire_Agency Fire agency name Char(120) Fire_ID Pitney Bowes persistent unique identification number for Fire record Integer Fire_FCCID Federal Communications Commission (FCC) identification number for Fire Record Integer Fire_Type Examples include: City, County, Military, State, University, Regional Char(25) Fire_EmergencyPhone Emergency phone number to call if an alarm is handled by the Fire Char(15) Fire_GeneralComments General comments regarding the Fire record Char(254) Fire_SiteContactName Site contact name (Fire sites may report to a coordinator) Char(100) Fire_SitePhone Site contact phone number Char(15) Fire_SiteFax Site fax number Char(15) Fire_Site Site address Char(254) Fire_SiteStreet Site street Char(80) Fire_SiteCity Site city Char(40) Fire_SiteState Site state Char(2) Fire_SiteZip Site zipcode Char(10) Police_Agency Police agency name Char(120) Police_ID Pitney Bowes persistent unique identification number for Police record Integer Communications Suite Product Guide 109

110 Column Name Description Type (Length) Indexed Police_FCCID Federal Communications Commission (FCC) identification number for Police Record Integer Police_Type Examples include: City, County, Military, State, University, Regional Char(25) Police_EmergencyPhone Emergency phone number to call if an alarm is handled by the Police Char(15) Police_GeneralComments General comments regarding the Police record Char(254) Police_SiteContactName Site contact name (Police sites may report to a coordinator) Char(100) Police_SitePhone Site contact phone number Char(15) Police_SiteFax Site fax number Char(15) Police_Site Site address Char(254) Police_SiteStreet Site street Char(80) Police_SiteCity Site city Char(40) Police_SiteState Site state Char(2) Police_SiteZip Site zipcode Char(10) MI_PRINX Unique identifier Integer Yes PSAP_ EmergencyInfoPro Column Name Description Type (Length) Indexed PSAP_Agency Public Safety Answering Point (PSAP) communications center name Char(120) PSAP_ID Pitney Bowes persistent unique identification number for PSAP record Integer Yes PSAP_FCCID Federal Communications Commission (FCC) identification number for PSAP Record Integer PSAP_Type Basic, Enhanced, Military or n Char(25) PSAP_EmergencyPhone Emergency phone number to call if an alarm is handled by the PSAP Char(15) PSAP_GeneralComments General comments regarding the PSAP record Char(254) PSAP_CoordContactName Coordinator name (a Coordinator may be responsible for multiple PSAP sites) Char(100) PSAP_CoordTitle Coordinator title Char(100) PSAP_CoordPhone Coordinator phone number Char(15) PSAP_CoordFax Coordinator fax number Char(15) PSAP_Coord Coordinator address Char(254) PSAP_CoordStreet Coordinator street Char(80) Communications Suite Product Guide 110

111 Column Name Description Type (Length) Indexed PSAP_CoordCity Coordinator city Char(40) PSAP_CoordState Coordinator state Char(2) PSAP_CoordZip Coordinator zipcode Char(10) PSAP_SiteContactName Site contact name (PSAP sites may report to a coordinator) Char(100) PSAP_SitePhone Site contact phone number Char(15) PSAP_SiteFax Site fax number Char(15) PSAP_Site Site address Char(254) PSAP_SiteStreet Site street Char(80) PSAP_SiteCity Site city Char(40) PSAP_SiteState Site state Char(2) PSAP_SiteZip Site zipcode Char(10) PSAP_SiteCounty Site county Char(40) PSAP_SiteCountyFIPS Site county Federal Information Processing Standard (FIPS) code Char(5) EMS_EmergencyInfoPro Column Name Description Type (Length) Indexed EMS_Agency Emergency Medical Service agency name Char(120) EMS_ID Pitney Bowes persistent unique identification number for EMS record Integer Yes EMS_FCCID Federal Communications Commission (FCC) identification number for EMS Record Integer EMS_Type Examples include: City, County, Military, State, University, Regional Char(25) EMS_EmergencyPhone Emergency phone number to call if an alarm is handled by the EMS Char(15) EMS_GeneralComments General comments regarding the EMS record Char(254) EMS_SiteContactName Site contact name (EMS sites may report to a coordinator) Char(100) EMS_SitePhone Site contact phone number Char(15) EMS_SiteFax Site fax number Char(15) EMS_Site Site address Char(254) EMS_SiteStreet Site street Char(80) EMS_SiteCity Site city Char(40) EMS_SiteState Site state Char(2) Communications Suite Product Guide 111

112 EMS_SiteZip Site zipcode Char(10) Fire_EmergencyInfoPro Column Name Description Type (Length) Indexed Fire_Agency Fire agency name Char(120) Fire_ID Pitney Bowes persistent unique identification number for Fire record Integer Yes Fire_FCCID Federal Communications Commission (FCC) identification number for Fire Record Integer Fire_Type Examples include: City, County, Military, State, University, Regional Char(25) Fire_EmergencyPhone Emergency phone number to call if an alarm is handled by the Fire Char(15) Fire_GeneralComments General comments regarding the Fire record Char(254) Fire_SiteContactName Site contact name (Fire sites may report to a coordinator) Char(100) Fire_SitePhone Site contact phone number Char(15) Fire_SiteFax Site fax number Char(15) Fire_Site Site address Char(254) Fire_SiteStreet Site street Char(80) Fire_SiteCity Site city Char(40) Fire_SiteState Site state Char(2) Fire_SiteZip Site zipcode Char(10) Police_EmergencyInfoPro Column Name Description Type (Length) Indexed Police_Agency Police agency name Char(120) Police_ID Pitney Bowes persistent unique identification number for Police record Integer Yes Police_FCCID Federal Communications Commission (FCC) identification number for Police Record Integer Police_Type Examples include: City, County, Military, State, University, Regional Char(25) Police_EmergencyPhone Emergency phone number to call if an alarm is handled by the Police Char(15) Police_GeneralComments General comments regarding the Police record Char(254) Police_SiteContactName Site contact name (Police sites may report to a coordinator) Char(100) Police_SitePhone Site contact phone number Char(15) Communications Suite Product Guide 112

113 Police_SiteFax Site fax number Char(15) Police_Site Site address Char(254) Police_SiteStreet Site street Char(80) Police_SiteCity Site city Char(40) Police_SiteState Site state Char(2) Police_SiteZip Site zipcode Char(10) Data Source and Projection EmergencyInfo Pro is based on data from PSAP Pro Data Resources, Inc. and Pitney Bowes. The EmergencyInfo Pro database has the following coverage, scale, and coordinates: Coverage United States Scale 1:24,000 Coordinates Latitude and Longitude Projection NAD 83 Communications Suite Product Guide 113

114 Chapter 9: RateCenterInfo 9 RateCenterInfo is a map database of rate centers throughout the United States and Canada. In This Chapter RateCenterInfo Overview RateCenterInfo Database Table Structures Using RateCenterInfo

115 RateCenterInfo Overview RateCenterInfo provides a comprehensive list of NPA/NXXs in each rate center. You can use RateCenterInfo to determine the Area Code/Exchange (NPA/NXX) combinations that are included in specific rate centers. RateCenterInfo also includes a map of the rate center points across the United States and Canada. By combining the information in RateCenterInfo with geographic, business, and customer data, you can make more informed decisions, control costs, identify potential marketing opportunities, and enhance profitability. RateCenterInfo Database File Names The RateCenterInfo database is divided into three file sets. Each file set is divided into the entire United States or into individual states. The file sets are named as follows, where XX is the state abbreviation: Area Code and Prefix Data Table XX_RC_D.* Rate Center Boundaries XX_RC_G.* Rate Center Points XX_RC_P.* The table below shows the complete RateCenterInfo database for the United States. Area Code and Prefix Data Table Rate Center Boundaries Rate Center Points US_RC_D.DAT US_RC_G.DAT US_RC_P.DAT US_RC_D.IND US_RC_G.ID US_RC_P.ID US_RC_D.TAB US_RC_G.IND US_RC_P.IND US_RC_G.MAP US_RC_G.TAB US_RC_P.MAP US_RC_P.TAB Communications Suite Product Guide 115

116 Table Structures American Data The tables below show the table structures the datasets included in RateCenterInfo for the U.S. Area Code and Prefix Data Field Name Description Type (Length) Indexed xx_rc_d.* Tabular file that contains information on the NPA/NXX combinations served in each rate center Pitney Bowes Communications Data products now incorporate NPA/NXXs with LERG effective dates (planned changes) thru the end of the release month. This change provides our customers with the most up-to- date content upon receipt of the products. NPA Area Code Character (3) Yes NXX Exchange prefix Character (3) Yes START_RANGE For NPA/NXXs that have line range splits (thousand block pooling), this is the first line number in the range. Character (4) Yes END_RANGE For NPA/NXXs that have line range splits (thousand block pooling), this is the last line number in the range Character (4) Yes STATE State abbreviation Character (2) Yes RATE_CENTER Rate center name Character (10) Yes ALT_NAME Alternate name for the rate center Character (50) RC_ID Rate center identification number Character (14) LOCALITY Locality name Character (10) OCN Operating company number Character (4) COMPANY_NAME Name of carrier Character (50) OCN_CATEGORY Type of carrier Character (10) LATA LATA number Character (5) Communications Suite Product Guide 116

117 Rate Center Boundaries Field Name Description Type (Length) Indexed xx_rc_g.* Tabular file that contains rate center ID information STATE State abbreviation Character (2) Yes RATE_CNTR Rate center name Character (10) Yes ALT_NAME Alternate name for the rate center Character (50) RC_ID Rate center identification number Character (14) Rate Center Points Field Name Description Type (Length) Indexed xx_rc_p.* Rate center point file STATE State abbreviation Character (2) Yes RATE_CNTR Rate center name Character (10) Yes ALT_NAME Alternate name for the rate center Character (50) V Vertical coordinate of the rate center Character (5) H Horizontal coordinate of the rate center Character (5) X Longitude Float Y Latitude Float Canadian Data The tables below show the table structures the datasets included in RateCenterInfo for Canada. Area Code and Prefix Data Field Name Description Type (Length) Indexed Can_RC_D.* Tabular file that contains information on the NPA/NXX combinations served in each rate center NPA Area Code Character (3) Yes NXX Exchange prefix Character (3) Yes START_RANGE For NPA/NXXs that have line range splits (thousand block pooling), this is the first line number in the range. Character (4) Yes END_RANGE For NPA/NXXs that have line range splits (thousand block pooling), this is the last line number in the range Character (4) Yes PROVINCE Province abbreviation Character (2) Yes RATE_CENTER Rate center name Character (10) Yes ALT_NAME Alternate name for the rate center Character (50) Communications Suite Product Guide 117

118 Field Name Description Type (Length) Indexed RC_ID Rate center identification number Character (14) LOCALITY Locality name Character (10) OCN Operating company number Character (4) COMPANY_NAME Name of carrier Character (50) OCN_CATEGORY Type of carrier Character (10) LATA LATA number Character (5) Rate Center Boundaries Field Name Description Type (Length) Indexed Can_RC_G.* Tabular file that contains rate center ID information PROVINCE Province abbreviation Character (2) Yes RATE_CNTR Rate center name Character (10) Yes ALT_NAME Alternate name for the rate center Character (50) RC_ID Rate center identification number Character (14) Rate Center Points Field Name Description Type (Length) Indexed Can_RC_P.* Rate center point file PROVINCE Province abbreviation Character (2) Yes RATE_CNTR Rate center name Character (10) Yes ALT_NAME Alternate name for the rate center Character (50) V Vertical coordinate of the rate center Character (5) H Horizontal coordinate of the rate center Character (5) X Longitude Float Y Latitude Float Communications Suite Product Guide 118

119 Using RateCenterInfo Searching the RateCenterInfo Database This section explains how to use MapInfo Professional to search the RateCenterInfo database and generate a list of the NPA/NXXs operating within a specific rate center. 1. Open all of the RateCenterInfo tables (xx_rc_d, xx_rc_g, and xx_rc_p). 2. Choose Query > Select. The Select dialog box displays. 3. Select the xx_rc_d table from the Select Records from Table drop-down list.click A 4. Assist. The Expression dialog box displays. 5. Select RATE_CNTR from the Columns drop-down list. 6. Select = (equals) from the Operators drop-down list. 7. Type the name of the rate center in quotation marks. An example is shown below: 8. Click Verify to make sure that the query was correctly entered. 9. Click OK. You are returned to the Select dialog box. 10. Check the Browse Results box. 11. Click OK. MapInfo Professional will create a new Browser window that shows the results of the query. The browser window below displays all the NPA/NXXs that operate within the Manchester rate center, east of Hartford, Connecticut. Communications Suite Product Guide 119

120 Data Source and Projection Pitney Bowes suite of telecom infrastructure databases are built using state PUC data, state tariff data, the Telcordia LERG Routing Guide (LERG), StreetPro, and other reference data. The RateCenterInfo database has the following coverage, scale, coordinates, and projection Coverage United States, Guam, US Virgin Islands, US rthern Mariana Islands, and Canada. Scale 1:24,000 Coordinates Latitude and Longitude Projection NAD 83 Communications Suite Product Guide 120