Md7 is Technologically Agnostic
By Tom Leddo, Vice President
At Md7, we sometimes get asked “are you familiar with ___________ (fill in the blank with any type of technology) or have you worked with ___________ (fill in the blank again with any choice) equipment before?”
Our answer is always the same: “Yes, but we are technologically agnostic”
Dictionary.com defines agnostic as:
- of or relating to agnostics or their doctrines, attitudes, or beliefs,
- asserting the uncertainty of all claims to knowledge, and
- holding neither of two opposing positions.
The third one, “holding neither of two (or in our case more) opposing beliefs” is the one that applies for Md7. In short, as a vendor in the wireless infrastructure industry we are indifferent to any and all types of technology and/or equipment manufacturers as long as they perform reliably and are both safe and legal. However, we will admit to getting excited about some of the options especially when they weigh less and use less space!
When I first started in the infrastructure industry in September of 1995, one of the first RF engineers I met was working for PrimeCo PCS in Houston, Texas. He explained Code Division Multiple Access (CDMA) to me. To be candid, I didn’t really understand the difference at that time between CDMA and Global System for Mobile Communications (GSM). But, since my two largest customers at that time were PrimeCo and Sprint PCS who were both building their new CDMA networks in Texas, I, of course, agreed with them. I preferred CDMA and kept getting work.
Over time, I began to get work from other clients who were GSM-based and so my opinion began to change. Now LTE is, of course, making this a moot point.
More importantly, what I also found was that the work I was doing was in the “wireless infrastructure industry”, not the “wireless industry” as a whole, and that I specialized in towers and real estate as part of the infrastructure. My job since 1995, and the job of everyone at Md7 today, is to get sites on air faster, regardless of technology.
If it is a new site; we are tasked with finding candidates, securing leases, A&E, zoning and permitting, environmental review/approval, NTP and construction management, all in an effort to get the latest technology that our clients have chosen to deploy on air as quickly as possible.
To take it a step further, we are also indifferent to traditional macro sites, DAS and small cells. Yes, the process and skills between the three do vary. The process and skills needed to deal with a tower or roof-top owner for a macro are very different from a major sports arena for DAS and a municipality or utility for pole mounted nodes.
But, in the end, the task for Md7 is always the same – work with and coordinate the multiple parties necessary to get the signal on air….fast. And we are getting pretty good at it.
My Washer and Dryer Are (Not) Connected
By Tom Leddo, Vice President
As noted by my colleague, Mark Christenson in his recent product review about the Schlage Sense Smart Deadbolt, whenever it is time to purchase something new for my house, I always look to see if there is a new version of whatever I am buying that is “connected” in some way. I even recently followed Mark’s lead and got a smart deadbolt, but I opted for the Kevo by Kwikset.
I’ll be candid in saying that I chose the Kevo mainly because a great friend of mine works for Kwikset and so I am partial to their products. Thus, they are on every door in my house. I must say, “I LOVE IT” and highly recommend it because my phone is always with me and I can lock and unlock my door with a touch of my finger. I can also allow others through the door remotely for either a designated period of time or on a one-off basis.
But in the rapidly expanding Internet of Things (IoT) and “smart homes,” not all devices make complete sense to connect. As I have said a number of times, “I am not sure why I’ll ever need a connected toaster, but I am sure the same was said about putting a phone in someone’s car in the 1980’s. So I remain open minded.”
With this in mind, I replaced my old washer and dryer late last year. My wife and I primarily based our purchase on the capacity size of the barrel, energy/water efficiency and ease of use. But the fact that this particular set was also “connected” and included an iPhone app helped finalize our decision. We selected a paired, Samsung washer and dryer.
I am extremely happy with our new washer and dryer. If you haven’t upgraded any of your appliances in the last five to ten years you will be surprised by the advances that have been made.
But the “connected” functionality of this particular set is really bad. Through my home Wi-Fi and an accompanying iPhone app, I am supposed to be able to monitor the status of wash/dry cycles and perform remote diagnostics that can expedite needed repairs. But I have never gotten them to connect. The app has as an average rating of 1 out of 5 stars across 17 ratings in the app store with comments such as:
- “Clearly this app wasn’t given any user testing as it is so clunky to use it’s embarrassing,”
- “I was really looking forward to using this app but it would never connect to the washer,”
- “…makes me want to return my washer and dryer out of principle,”
- “Don’t even bother. I wasted too much time trying to set up this app,”
- “Can’t get it to work… was excited to use it, now just disappointed,” and
- “Useless app.”
These comments are not about the washer and dryer itself, but rather the accompanying app that enables it to be “connected” and very accurately reflect my personal opinions.
For me, here is the bottom line – The new appliance set works great except for the wireless functions so I am not able to sit in front of the TV or in my backyard on a Sunday afternoon and know exactly when the drying cycle ends to remove my shirts with less wrinkles. I still have to do it the old fashioned way of estimating or remembering how long it has been since I started a fresh load. But this is just a small hurdle in the world of more connected devices and I am still not giving up on moving into the connected world – I remain open minded!
Best Practices for Deploying Wireless Infrastructure in the Public Right-of-Way
By Daniel Shaughnessy, Md7 Land Use
As the industry moves into the future with more creative, innovative, and technologically-advanced wireless infrastructure solutions, it is worth remembering a time when things were not so great. More than just technology has changed since the early days of wireless infrastructure deployment; the partnership between telecommunications companies and the communities they serve has also advanced. While issues may pop up every now and then, long gone are the days of reckless, hurried builds accompanied by fervent public outrage, cries of NIMBY (Not In My Back Yard) and moratoriums against new towers. More and more, local governments and players in the industry are working closely together to expedite deployment timelines and allay concerns regarding the design, location, height, and the alleged negative effects of installing antennas in the community. But, as we reach the point where the implementation of DAS and small cells in the public right-of-way (ROW) has started to become a financially-viable and necessary solution for wireless infrastructure, the relationship between local governments and the industry is in jeopardy of eroding back to how it was in the tumultuous early days of wireless deployment.
Today, there are approximately 1.4 mobile-connected devices for every person in the U.S. – that is 447 million devices clogging up the bandwidth of our current wireless infrastructure. By 2018, U.S. mobile data use is projected to increase 6-fold. In order to have a fighting chance at meeting this looming demand, more carriers and wireless infrastructure companies are looking to deploy outdoor DAS and small cells in the public right-of-way in the most time sensitive manner possible. However, fearing the unknown, a local government can curtail and sometimes even completely derail ROW installations in an effort to minimize visual impacts and preserve community character. When the industry was faced with this same dilemma in the past, the solution was to bulldoze through the deployment process and worry about public opposition later. The community distrust, expanded regulation and even further increased timelines that resulted, took us 20 years to repair so that we could obtain the relationship between local governments and the wireless industry that exists today. This cannot be the solution we use today.
Instead, we need to highlight the common goals that both parties share and develop a solution that not only solidifies the local government/wireless industry partnership, but enables the two to work together to reach these goals. Local governments are nothing more than representatives of the community that wireless companies are looking to serve. Government efforts to minimize visual impacts and protect community character during the permitting process are rooted in the overall goal of increasing community desirability which leads to economic vitality. Customers expect nothing more than the best service from their wireless carriers. As such, when seeking to enhance wireless infrastructure, wireless companies are also representatives of the same community that local governments serve. When deciding between cities during the home buying process, U.S. adults often care more about mobile phone reception than the quality of neighborhood schools. Thus a carrier’s desire to timely deploy infrastructure in the public ROW will result in increased community desirability and economic vitality. Both parties are looking for the same goal. Good mobile service is part of a city’s basic infrastructure, and local governments need wireless companies to provide this service in order to enhance the overall desirability of the community. So, if mobile companies are attempting to provide a service that local governments clearly need, why is the industry running into difficulties with deployment in the right-of-way?
Simply having a product or service available is not all that is needed to complete a deal. Like any good retail sales outfit will tell you, the other half of the equation is customer service. In my experience working closely with local governments and the communities they serve, I have found that they are not turning away from the product, they are rejecting the poor level of customer service that they have received. Too often, local governments report that comprehensive ROW installations are disorganized, community involvement is avoided, communication is infrequent, and as-builts do not reflect what was originally approved. Don’t get me wrong. I get it. The wireless infrastructure industry is fueled by hasty time-to-market metrics in multiple cities, and it is not always easy to make things perfect. Additionally, apart from power and fiber backhaul, permitting costs and procedures are cited as the main constraints that can derail a DAS project. So I can see how viewing local governments as partners in ROW deployment may be hard for some to swallow. But, as we have seen in the past, by not working with a local government as a partner, bridges will burn, regulations will only increase, and the rate of ROW deployment will continue to grind along at an excruciating pace. A customer will be hesitant to return to a store where she received paltry service. A store owner would not want poor customer service to affect her reputation and limit her ability to gain more customers. These same principles apply to the carrier/local government partnership – customer service is a necessary component.
In order to successfully sell the timely deployment of multiple nodes in various ROW locations throughout a community, a customer service-driven engagement plan is needed. The bottom line requires carriers to bolster their network in order to increase customer satisfaction. A local government is nothing more than a conglomeration of these wireless customers. By establishing a customer service-driven engagement plan with local governments during the permitting process, wireless carriers are working towards the same bottom line – albeit in a slightly different order – increasing customer satisfaction in order to bolster the network. Just like any successful customer service plan, best practices for selling a comprehensive ROW installation to a local government should consist of the following three steps: (1) learn more about the particular customer’s needs to identify the problem; (2) identify a service or product that will satisfy these needs; and (3) distinguish yourself or your product from the competition by providing a high level of customer service.
In the first step, the carrier must do the due diligence necessary to identify a community’s particular needs and service issues. In general, local governments must first be educated about the growing dependence on wireless devices, smart phones, high data consumption, and home buying preferences using facts and figures from dependable non-biased sources. Next, the particular service issues in the city must be addressed. Of course, a wireless carrier will never commit to a ROW deployment based solely on what a local government thinks it needs. The ROW needs must first be carefully evaluated in the context of the carrier’s overall network. However, this does not mean that the carrier cannot coordinate its needs with the needs of the city. The carrier should take their proposed build-out plans and compare them with the community’s general or comprehensive plan. The majority of all jurisdictions in the U.S. have a publically available comprehensive plan, an overall master plan developed through citizen participation that sets forth the city’s future development goals. Among other things, the comprehensive plan will show congested neighborhoods and roads within the city, the city’s major growing industries, and the technology and infrastructure goals that the community wishes to achieve. To the extent that your build-out lines up with any of the goals, the comprehensive plan will do wonders to strengthen your proposal to the city, as it tells government officials that this is something their citizens want. Further, in conjunction with the city’s development code, the comprehensive plan will provide an understanding of the design constraints and allow the creation of correct plans at an early stage, saving on surprise costs in the back end. In addition to the particular needs of the city found in the comprehensive plan, care should be taken to research what particular events the community has held in the past and what they have planned for the future. For example, a city that holds a large amount of festivals, or that has a desire to host collegiate or professional level sports championships, will most certainly have the type of wireless congestion issues that small cells in the ROW are designed to solve. Above all, when identifying needs to the local government, make sure that they are specific to the particular community and not necessarily universal problems that all communities face.
Only once the community’s particular needs are brought to light, can the carrier or wireless infrastructure company then identify the proposed ROW build as a tailor-made solution. Now that the community’s needs are established, the proposal will no longer look like a unilateral benefit for the carrier’s network. Instead, the plan should be framed as a necessary public service that will address particular problems and modernize the community. At this point, partnership and teamwork should be highlighted. It is not simply the local government helping the carrier deploy its network, the carrier is helping the local government achieve its ultimate goal of becoming a more desirable community. In this light, both parties will be motivated to implement an expedited and efficient permitting process.
Ultimately though, the partnership between carrier and community will fail unless the carrier is able to distinguish its build plans by providing a high level of customer service from beginning to end. Community education, an organized team, and an established relationship are required. A large majority of jurisdictions allow wireless infrastructure in the public ROW without the requirement of a public hearing or some other type of community involvement. While this seems ideal from a carrier’s prospective, it can backfire when citizens feel they have no say in whether a DAS node should be installed right outside their front window. Whether or not it is required as part of the permitting process, the carrier should consider increasing the level of public education regarding the installation process and ROW builds in general by conducting community meetings and providing informational handouts. These interactions should not only focus on the benefits to the community, but should also address the considerably low visual impact that ROW installations provide in comparison to traditional macro builds. In addition to community involvement, customer service can increase with a clear and organized build-out plan and by providing an accurate development schedule to the local government. Each community build-out plan does not exist in a vacuum, and, although ideal, it may not be possible to assign a dedicated team to each jurisdiction. However, both internal and external communications regarding all stages of the project can be streamlined by assigning one point of contact to speak as the company’s representative to the local government. This dedicated government liaison does not necessarily need to be present in the jurisdiction, so long as she has the ability to communicate and coordinate operations with all members of the carrier’s team. Lastly, efforts should be made to ensure that the partnership with the local government does not end as soon as the installation is complete. Local governments should be encouraged to reach out to the government liaison to address any post-installation issues that may arise. If as-builts do not match approved plans, the liaison will work with the local government to take responsibility for botched installs and provide quick remedies.
At first blush, deploying wireless infrastructure in the ROW by way of a customer service- driven engagement plan with local governments may seem like it will only add additional time, resources, and costs. But, reverting back to the method of bulldozing through deployment in the fastest way possible is not a viable option as history tells us this will only lead to increased resistance from local governments. Instead of working against local governments, we need to further establish the trusted partnership that we have worked so hard to obtain.
As wireless data needs continue to grow exponentially, communities need innovative services like wireless in the right-of-way that will provide an effective solution while keeping a low visual and environmental impact. What better way is there to provide that service than with a smile?
Company Profile (as Published by Inside Towers)
By Eleanor Snite, Inside Towers
Md7 North America was founded in 2003, and now has operations throughout the United States and in 13 countries in Europe. Tom Leddo, vice president and one of the four founders of Md7, said it was all about the timing. Early in Md7’s launching, cell phone companies were making major acquisitions and Md7 was asked to negotiate leases for literally thousands of sites during a very short time.
“We got good at negotiating,” Leddo said. “Out of the ability to negotiate thousands of leases, we got more business asking us to help build new sites, construction services, zoning, permitting and all that goes with new or existing sites.”
The experience also taught Md7 that the Excel sheets used to manage projects just weren’t the answer. Using their own experience, they developed a custom software system – Live Track. It provides a good workflow and is designed to manage projects for developing and managing every single step and sub-step needed in a project.
Leddo said Md7 has been planning goals for growth in 2016 and forward. One thing is working to increase its presence west of the Rocky Mountains and also in the deep South. The second goal is to significantly increase its ability to broaden the turnkey service. More DAS and engineering services have also been added.
“We also significantly beefed up our construction management division,” Leddo said. “We provide all the services related to the real estate under those towers, getting the towers constructed and getting equipment on the towers.”
Md7 North America, which is headquartered in San Diego, has 17 field offices throughout the country including Austin, Atlanta, Seattle, and Sacramento. It trades on the motto: “Centralized Efficiency, Localized Know-How.” It primarily works with Tier 1 phone companies but has also worked with smaller companies. The company works with 20 carriers in Europe and the European headquarters are in Dublin, Ireland.
Wondering what Md7 means? Leddo gets that a lot and is ready with a response:
- We are not “seven doctors” – That would be “7 MD’s”.
- We do not manufacture Cosmeceuticals – That’s “MD-7”.
- We are not located on Maryland Route 7. – That’s “MD 7”.
- We do not manufacture an Ultra Long Excursion High Power Dual 18″ Subwoofer – that is JBL.
- We are not “Moorish Delta 7” (aka MD7) – the UK Hip-Hop group from Birmingham, England.
Leddo continued, “Actually, the name comes from the initials of our Founder and CEO, Michael David Gianni, or MDG. But the “G” was changed to “7” because it is the seventh letter of the alphabet. Eric LeVine, the graphic artist who also designed our logo came up with the name.