-
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathsubmissions.html
427 lines (357 loc) · 22.9 KB
/
submissions.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<!-- Always force latest IE rendering engine -->
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<!-- Mobile Specific Meta -->
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="description" content="Azorian Solutions is a solutions consultant that specializes in WISP / FISP industry needs and technologies with extensive experience in software engineering and integration. I also provide FCC 477 / BDC submission processing services.">
<meta name="keywords" content="consulting wireless wisp networking wifi ptp ptmp access point software tower construction fwll fiber microwave licensed unlicensed millimeter-wave mmwave">
<meta name="author" content="Matt Scott @ Azorian Solutions">
<!-- TITLE -->
<title>FCC Submissions - Azorian Solutions</title>
<!-- FAVICON -->
<link href="img/favicon/favicon.ico" rel="icon">
<link rel="apple-touch-icon" sizes="144x144" href="img/favicon/apple-icon-144x144.png">
<link rel="apple-touch-icon" sizes="114x114" href="img/favicon/apple-icon-114x114.png">
<link rel="apple-touch-icon" sizes="72x72" href="img/favicon/apple-icon-72x72.png">
<link rel="apple-touch-icon" href="img/favicon/apple-icon.png">
<!-- BOOTSTRAP CSS -->
<link rel="stylesheet" href="css/bootstrap/bootstrap.min.css">
<!-- FONT-AWESOME & ET-LINE-FONT CSS -->
<link rel="stylesheet" href="css/font-awesome/css/font-awesome.min.css">
<link rel="stylesheet" href="css/et-line-font/et-line-font.css">
<!-- MAGNIFIC POPUP CORE CSS -->
<link href="css/magnific-popup/magnific-popup.css" rel="stylesheet">
<!-- OWL CAROUSEL -->
<link href="css/owl-carousel/owl.carousel.min.css" rel="stylesheet">
<link href="css/owl-carousel/owl.theme.default.min.css" rel="stylesheet">
<!-- MAIN STYLE CSS -->
<link rel="stylesheet" href="css/style.css">
<!-- RESPONSIVE STYLE CSS -->
<link rel="stylesheet" href="css/responsive.css">
<!-- COLORS CSS -->
<link rel="stylesheet" href="css/colors/blue.css">
</head>
<body>
<!-- ====== Preloader ====== -->
<div class="loading">
<div class="load-circle">
</div>
</div>
<!-- ======End Preloader ====== -->
<!-- ====== HEADER START ====== -->
<section class="s-header" id="home" data-scroll-index="0">
<div class="header-overlay">
<!-- ====== NAVGITION ====== -->
<nav class="navbar land-nav navbar-fixed-top">
<div class="container">
<div class="row">
<!-- Brand and toggle get grouped for better mobile display -->
<div class="navbar-header">
<button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#collapse" aria-expanded="false">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<!-- logo -->
<a class="logo navbar-brand" href="/#home" data-scroll-nav="0">
Azorian<span>Solutions</span>
</a>
</div>
</div>
</div><!-- /.container -->
</nav>
<!-- ====== END NAVGITION ====== -->
<!-- Header Content -->
<div class="middle-c text-center">
<div class="capt">
<h1><span>FCC</span> 477/BDC <span>Submission</span> Processing</h1>
<h3>My FCC submission services are designed to be easy on your time. Follow my steps below to prepare your data package for my services.</h3>
<!-- Buttons -->
<div class="header-btn">
<a class="b-act" href="#data-source" data-scroll-nav="1">Get Started</a>
</div>
</div>
</div>
<!-- End Header Content -->
</div>
</section>
<!-- ====== HEADER END ====== -->
<!-- ====== ABOUT START ====== -->
<section class="sections about" id="data-source" data-scroll-index="1">
<div class="container">
<div class="row">
<!-- ABOUT CONTENT START -->
<div class="about-con col-md-9" style="text-align: center;">
<h3>Data Requirements</h3>
<p>Below is a brief summary of what data I require to process typical BDC submissions.<br/>
Keep in mind, these are generalizations as my process can actually support a wide variety of
data source scenarios.<br/>I do have CSV templates available, but I typically work
with the client to mutate their existing templates into my format.</p>
</div>
<!-- ABOUT CONTENT END -->
<!-- FEATURES START -->
<div class="features">
<ul>
<li class="col-md-4">
<a href="#data-service-plans" title="Read More About Service Plan Data"><span
class="icon icon-speedometer"></span>
<h3>Service Plans</h3></a>
<p>I require a CSV file of service plan data that includes the following; a unique plan
identifier, the account type, the connection technology, and the advertised download and
upload throughput of the service plan.</p>
<p><a href="#data-service-plans"
title="Read More About Service Plan Data">Read more here</a></p>
</li>
<li class="col-md-4">
<a href="#data-subscriptions" title="Read More About Subscription Data"><span
class="icon icon-adjustments"></span>
<h3>Customer Subscriptions</h3></a>
<p>I require a CSV file of customer subscription data that includes one line for each
subscription sold. Each line should include the following; full address of service
location, unique service plan identifier, account type, and connection technology.</p>
<p><a href="#data-subscriptions"
title="Read More About Subscription Data">Read more here</a></p>
</li>
<li class="col-md-4">
<a href="#data-coverage-models" title="Read More About Coverage Models"><span
class="icon icon-map"></span>
<h3>Coverage Models</h3></a>
<p>Whether you sell optical of FWLL based services, I require a common form of shape data
that defines one or more polygons indicating geographic areas covered by your service.
I'm sure this sounds complicated, but it's actually not depending on what tooling you may
already use.</p>
<p><a href="#data-coverage-models"
title="Read More About Coverage Models">Read more here</a></p>
</li>
<li class="col-md-12 footer">
<p>Continue reading for more detailed information on preparing each of the aforementioned
data sets <a href="#data-service-plans" title="Continue Reading">here</a>.
</p>
</li>
</ul>
</div>
<!-- FEATURES END -->
</div>
</div>
</section>
<!-- ====== DIVIDER START ===== -->
<section class="sections section-divider">
<div class="container">
<div class="row">
</div>
</div>
</section>
<!-- ====== DIVIDER END ===== -->
<!-- ====== SERVICE PLAN START ====== -->
<section class="sections about" id="data-service-plans" data-scroll-index="2">
<div class="container">
<div class="row">
<!-- SERVICE PLAN CONTENT START -->
<div class="about-con col-md-9 secondary">
<h3>Service Plan Data</h3>
<p>Your service plans CSV file should contain one row for each unique service plan you have. See
below for a description of fields that should be present in the CSV file.</p>
<p><strong>An asterisk indicates an optional field.</strong></p>
<div class="left">
<p><strong>ID</strong>: <br/>This field should define a unique identifier that can be
used to match your customer subscriptions to service plans. Whether that's a numeric index
or an ASCII label, just about anything works so long as it's unique across your service plan
data.</p>
<p><strong>COMMENT</strong>: *<br/>This field can be used to define an ASCII label for your
service plan. It is not currently used by the process but could be used in the future for
summary reports. In many cases, this field may have an identical value to AUX_PLAN_ID.</p>
<p><strong>TYPE</strong>: <br/>This field is used to indicate what account types may
consume this service plan. A value of "R" should be used for residential only
plans, "B" should be used for business / commercial only plans, and "X"
for plans that apply to either account type.</p>
<p><strong>TECH_CODE</strong>: <br/>This field is used to indicate what connection technology
this plan is used for. If the plan is used for multiple technologies, choose the best
technology to indicate here. A value of "50" should be used for optical
connections as well as copper Ethernet connections fed by optical trunks. A value of "70"
should be used for unlicensed FWLL such as 2.4 GHz and 5 GHz. A value of "71"
should be used for fully licensed FWLL such as 2.5 GHz and 3 GHz PAL holders. A value of
"72" should be used for lightly licensed FWLL such as 3 GHz CBRS GAA users.</p>
<p><strong>TECH_CODES</strong>: <br/>This field can be used in place of the aforementioned
"TECH_CODE" field if a service plan is available under multiple technology
codes. Specify multiple tech codes, separated by a comma.</p>
<p><strong>For more information</strong> about the various technology codes, <strong><a href="https://help.bdc.fcc.gov/hc/en-us/articles/12271133620763-Technology-Codes-for-Terrestrial-Fixed-Wireless" target="_blank">see here</a></strong>.</p>
<p><strong>DOWNLOAD</strong>: <br/>This field is used to indicate the download throughput limit
of the plan in Mbps (decimal format). Do not include units of measure in this field!</p>
<p><strong>UPLOAD</strong>: <br/>This field is used to indicate the upload throughput limit of
the plan in Mbps (decimal format). Do not include units of measure in this field!</p>
</div>
</div>
<!-- SERVICE PLAN CONTENT END -->
</div>
</div>
</section>
<!-- ====== SERVICE PLAN END ====== -->
<!-- ====== DIVIDER START ===== -->
<section class="sections section-divider">
<div class="container">
<div class="row">
</div>
</div>
</section>
<!-- ====== DIVIDER END ===== -->
<!-- ====== SUBSCRIPTION DATA START ====== -->
<section class="sections about" id="data-subscriptions" data-scroll-index="3">
<div class="container">
<div class="row">
<!-- SUBSCRIPTION DATA CONTENT START -->
<div class="about-con col-md-9 secondary">
<h3>Subscription Data</h3>
<p>Your subscriptions CSV file should contain one row for each Internet service subscription you
have. If you have more than one subscription at the same geographic location, it's perfectly
okay to report the same address twice in the subscription file, and it will be counted
automatically. See below for a description of fields that should be present in the CSV file.</p>
<p>If your OSS is unable to provide a service plan association in the data export, then you may also
use the DL_* and UL_* fields below to define throughput information which will then be used to
match a plan based on defined limits. If you have a scenario more complicate than this, make
sure to reach out to me. My system supports more variations than what is documented here.</p>
<p><strong>An asterisk indicates an optional field.</strong></p>
<div class="left">
<p><strong>PLAN_ID</strong>: *<br/>This field should define a unique identifier that can be
used to match your subscription to a service plans. The value here should align exactly what
the values defined in the ID field of your service plans CSV file. Otherwise, matching
can be done based on download and upload speeds.</p>
<p><strong>TYPE</strong>: <br/>This field is used to indicate what account type this
subscription is. A value of "R" should be used for residential subscriptions and
"B" should be used for business / commercial subscriptions.</p>
<p><strong>TECH_CODE</strong>: <br/>This field is used to indicate what connection technology
this subscription uses. A value of "50" should be used for optical connections as
well as copper Ethernet connections fed by optical trunks. A value of "70" should
be used for unlicensed FWLL such as 2.4 GHz and 5 GHz. A value of "71" should be
used for fully licensed FWLL such as 2.5 GHz and 3 GHz PAL holders. A value of "72"
should be used for lightly licensed FWLL such as 3 GHz CBRS GAA users.</p>
<p><strong>TECH_CODES</strong>: <br/>This field can be used in place of the aforementioned
"TECH_CODE" field if a subscription is serviced simultaneously by multiple
technology codes. Specify multiple tech codes, separated by a comma.</p>
<p><strong>For more information</strong> about the various technology codes, <strong><a href="https://help.bdc.fcc.gov/hc/en-us/articles/12271133620763-Technology-Codes-for-Terrestrial-Fixed-Wireless" target="_blank">see here</a></strong>.</p>
<p><strong>LINE1</strong>: <br/>This field is used to provide the first line (street
address) of the subscription service location.</p>
<p><strong>LINE2</strong>: <br/>This field is used to provide the second line (unit
information, if any) of the subscription service location.</p>
<p><strong>CITY</strong>: <br/>This field is used to provide the city of the
subscription service location.</p>
<p><strong>STATE</strong>: <br/>This field is used to provide the state of the
subscription service location.</p>
<p><strong>ZIP</strong>: <br/>This field is used to provide the zip code of the
subscription service location.</p>
<p><strong>COUNTRY</strong>: <br/>This field is used to provide the country code of the
subscription service location. If this field isn't provided, a value of "US" will
be assumed.</p>
<p><strong>DOWNLOAD</strong>: *<br/>This field is used to indicate the download throughput limit
of the subscription in Mbps (decimal format). Do not include units of measure in this field! This
field is only meant to be used if your OSS can't provide some form of service plan
association in the "PLAN_ID" column of this export.</p>
<p><strong>UPLOAD</strong>: *<br/>This field is used to indicate the upload throughput limit
of the subscription in Mbps (decimal format). Do not include units of measure in this field! This
field is only meant to be used if your OSS can't provide some form of service plan
association in the "PLAN_ID" column of this export.</p>
</div>
</div>
<!-- SUBSCRIPTION DATA CONTENT END -->
</div>
</div>
</section>
<!-- ====== SUBSCRIPTION DATA END ====== -->
<!-- ====== DIVIDER START ===== -->
<section class="sections section-divider">
<div class="container">
<div class="row">
</div>
</div>
</section>
<!-- ====== DIVIDER END ===== -->
<!-- ====== COVERAGE START ====== -->
<section class="sections about" id="data-coverage-models" data-scroll-index="4">
<div class="container">
<div class="row">
<!-- COVERAGE CONTENT START -->
<div class="about-con col-md-9 secondary">
<h3>Coverage Models</h3>
<p>Your coverage models should define one or more polygon shapes to indicate which geographic areas
are covered by your service. With my system, you can provide one model, or you can provide many
which can be associated to different maximum service plan tiers, account types, and connection
technologies. The more detailed your coverage models are, the more detailed your resulting
submissions will be.</p>
<p>Coverage models are ultimately converted to Shapefile format for use in my system. If you can
provide your coverage in that directly, great. If not, I have a tool that can convert many other
formats such as KML, KMZ, and geoJSON.</p>
<p><strong>REMEMBER!</strong> Just because a piece of software creates a KML/KMZ file, that does
<strong>not</strong> mean that the file actually contains valid coverage data! Modern versions
of software such as UISP / ISP Design will create KML files that contain embedded images of a
coverage map. This is not an acceptable format for conversion as the coverage must actually be
defined as polygon data.</p>
<p>A polygon will be an array of three or more sets of geographic coordinates that define a
containing area when all sequentially connected. If you want something to compare your export
to, open Google Earth and draw a polygon shape over a map and then export that file as KML. This
is a good example of what polygon data looks like.</p>
<p>If you use TowerCoverage or cnHeat, both of those products provide direct exports in the formats
needed.</p>
<p>If you provide connectivity via hardline such as optical or copper, then you need to provide
coverage data indicating every home that can be connected through the use of containment
polygons. Many popular fiber planning tools should be able to provide an export for this.</p>
</div>
<!-- COVERAGE CONTENT END -->
</div>
</div>
</section>
<!-- ====== COVERAGE END ====== -->
<!-- ====== DIVIDER START ===== -->
<section class="sections section-divider">
<div class="container">
<div class="row">
</div>
</div>
</section>
<!-- ====== DIVIDER END ===== -->
<!-- ====== LOCATION FABRIC START ====== -->
<section class="sections about" id="data-location-fabric" data-scroll-index="5">
<div class="container">
<div class="row">
<!-- LOCATION FABRIC CONTENT START -->
<div class="about-con col-md-9 secondary">
<h3>Location Fabric Data</h3>
<p>This data set is <strong>only required if you require BDC submission processing</strong> services from me.</p>
<p>Your location fabric data is something that you must obtain from CostQuest. This is a fairly simple but tedious process to obtain the data.</p>
<p>Your first step if you haven't already, is to get registered for a support account with CostQuest. Begin by sending an email to <a href="mailto:nbfsupport@costquest.com">nbfsupport@costquest.com</a> with a simple request to setup a tier 2 location fabric license.</p>
<p>CostQuest will guide you the rest of the way through the process on obtaining the data. Once you complete this step, CostQuest will provide a download link to a Zip archive. Please provide me with that download link <strong>and not a copy of the extracted files!</strong></p>
</div>
<!-- LOCATION FABRIC CONTENT END -->
</div>
</div>
</section>
<!-- ====== LOCATION FABRIC END ====== -->
<!-- ====== JS ====== -->
<!-- JQUERY -->
<script src="js/jquery.v1.12.4.js"></script>
<!-- BOOTSTRAP JS -->
<script src="js/bootstrap.min.js"></script>
<!-- COUNT TO JS -->
<script src="js/jquery.countTo.js"></script>
<!-- ISOTOPE JS -->
<script src="js/isotope.pkgd.min.js"></script>
<!-- MASONRY JS -->
<script src="js/masonry.pkgd.min.js"></script>
<!-- Magnific Popup core JS -->
<script src="js/jquery.magnific-popup.min.js"></script>
<!-- PARSLEY file -->
<script src="js/parsley.js"></script>
<!-- OWL CAROUSEL JS -->
<script src="js/owl.carousel.min.js"></script>
<!-- SCROLLIT file -->
<script src="js/scrollIt.min.js"></script>
<!-- custom js -->
<script src="js/main.js"></script>
</body>
</html>