[HamWAN PSDR] Bill of Materials for Cell Site

[Dylan Ambauen]

Jamie,
As a Kitsap resident, I am also interested in your project, and would like
to help.
Let's meet up in Bremerton. I can help with your Bill of Materials
questions... weighing the various options will certainly be easier in a 30
minute discussion, and I can give you a visual on the HamWAN gear we use to
host a server for PNW DMR. I have some spare gear too, for field tests.
Please contact me off-list.

KI7SBI
Dylan

---
Dylan Ambauen
360-850-1200


On Tue, Apr 23, 2019 at 1:08 PM Rob Salsgiver <rob at nr3o.com> wrote:

> Jamie,
>
>
>
> Good to meet you.  It is entirely possible and authorized – even
> encouraged.  I just held a discussion on the topic at Comm Academy this
> year, and part of the focus was on building communications “communities”.
>
>
>
> Most of the initial focus is usually getting a location connected to the
> HamWAN “backbone” – or one of the high level mountain-top sites.  This is
> almost never possible when looking at an entire community, so it makes
> sense to build local cells to connect facilities within the community.  In
> an ideal world your local community would create 2 or 3 cells, allowing
> each key facility with town to be connected to 2 sites for redundancy.  In
> turn, the community “hub” if you will, would also have 2 or more
> connections out to the Puget Sound HamWAN backbone for connections to the
> rest of the world.
>
>
>
> In the event that the trunks out to the Puget Sound HamWAN backbone are
> taken down, you still have communications within your community between
> fire, police, city hall, school district, public works, shelter sites, or
> whomever else you want to add.
>
>
>
> Because each site and case is different, a fixed Bill of Materials is hard
> to nail down.  We can easily give you a few examples, but your needs will
> be unique to who(m) you want to connect, and how you want to connect them.
>
>
>
> I would encourage you to start gathering a list of points you would like
> to connect (names, phone numbers, addresses, GPS coordinates).  With this
> you can start doing some ground-work on good starting sites to explore and
> how many facilities can be covered by them.
>
>
>
> You may already be a mile ahead of me on some of this, if so I apologize.
> Even so it may be good for others on the list.
>
>
>
> If you have a list of potential client and cell sites you are focused on,
> let me know and I can help look at coverage maps to see how it lays out.
>
>
>
> General ball-park costs are as follows:
>
>
>
> 1)      Single-dish connected client site - $600 (includes uplink dish
> and radio, access point and site router, and VOIP phoe)
>
> 2)      Dual-dish connected client site - $900-$1100 (similar to above,
> connecting to 2 or more other sites)
>
> 3)      Fully populated cell site - $2500-$4500, depending on number of
> links, sectors, etc.
>
>
>
> Give a shout if you have more questions.
>
>
>
> Cheers,
>
> Rob Salsgiver – NR3O
>
>
>
> *From:* PSDR [mailto:psdr-bounces at hamwan.org] *On Behalf Of *Jamie Hughes
> *Sent:* Tuesday, April 23, 2019 10:16 AM
> *To:* Puget Sound Data Ring
> *Subject:* [HamWAN PSDR] Bill of Materials for Cell Site
>
>
>
> Good Morning,
>
>
>
> The Kitsap Auxiliary Radio Service (KARS), DEM affiliate organization,
> would like to investigate the deployment possibility of a low altitude ring
> between sites, yet to be identified. The idea would be to build out a few
> cell sites just at lower altitudes that hopefully create a backup/redundant
> data ring if possible.
>
>
>
> If this is possible and authorized, may I please get a bill of materials
> and approximate cost of those materials.
>
>
>
> Thanks,
>
>
>
> *Jamie Hughes*
>
> WA7JH
>
> Mobile: (360) 340-8886 <+13603408886>
>
>
> _______________________________________________
> PSDR mailing list
> PSDR at hamwan.org
> http://mail.hamwan.net/mailman/listinfo/psdr
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.hamwan.net/pipermail/psdr/attachments/20190423/18db15ce/attachment.html>