Final Evaluation Committee Meeting: RFP No. GEN2129421P1, Next Generation 911 (NG911) - Dec 18, 2025

Good morning. Good morning, everyone. This is the Purchasing Division. We will be starting the meeting momentarily. If you could please mute your device. Thank you. Good morning, everyone. Good morning. Good morning. Good morning. I am Sonia Lovett, Senior Purchasing Manager and the meeting facilitator today. I would like to call to order the final evaluation committee meeting for request for proposals, RFP, number GEN2129421P1, Next Generation 911 for the Office of Regional Communications and Technology. The time is 9.32 a.m. on December 18th, 2025. This meeting is being held through Microsoft Teams. Representatives from the county are physically here in room 430 of the Governmental Center Building East, located in Fort Lauderdale, Florida, or virtually through Teams. Attendees, please mute the microphones on your devices to limit background noise. This is a public meeting and is being recorded by Broward County. The video recording will act as the official recording of the meeting. The recording will be made available on the Purchasing Division website on the RLI RFP repository. Information reviewed by the Evaluation Committee as part of the evaluation process will also be posted on the repository. This meeting has been publicly noticed. The purpose of the purpose of the Evaluation Committee is for the Evaluation Committee to hear presentations, score, and rank the responsive, responsible vendors. At the initial Evaluation Committee meeting on October 24th, 2025, the Evaluation Committee determined all vendors to be both responsive and responsible. The following vendors, advanced to final Evaluation and ranking, taking place today. AT&T Enterprises, LLC, doing business as AT&T Enterprises, Florida, LLC. Communications Venture Corp, doing business as InDigital. Motorola Solutions Connectivity, Inc., doing business as Motorola. Meeting attendance will be recorded in the following ways. The Purchasing Division will record attendance of county staff physically here in Room 430. All virtual attendees, including county staff, please click on the link or scan the QR code that is currently listed in the Teams chat section to complete the sign-in sheet. For attendees that cannot access the link or the QR code in the Teams chat, email the Assistant Purchasing Manager, Latoya Clark-Forbes, at LClarkForbes, at Broward.org, with the subject, EC Meeting Attendance, and indicate your name, your title, and the company you represent in the email body. We have a quorum present with the following Evaluation Committee members. Committee members, please say present after your name is called. Angela Scott, Enterprise Director, Information Technology, Aviation Department. Present. Present. Antonio Saban, E911, Communications Administrator, Office of Regional Communications and Technology. Present. Daniel Canchon, Information Systems Manager, Security, Enterprise Technology Services, Finance and Administrative Services Department. Present. Michael Naren, E911, Communications Administrator, Office of Regional Communications and Technology. Present. Brandon Watson, Information Systems Manager, Transportation Onboard Systems, Transportation Department. Present. Thank you, everyone. It is the Evaluation Committee's responsibility to review the vendor's submittals to ensure solicitation requirements are met and to evaluate the submittals to make a recommendation to award a contract. Each Evaluation Committee member was appointed by the county administrator to serve on this committee based on their experience. The Evaluation Committee members are responsible for following the county's established committee procedures to select vendors which provide the services that are in the best interest of the county. At the discretion of the board, the Evaluation Committee members may be requested to substantiate their recommendation and discuss their submittal reviews. The cone of silence has been in effect since this solicitation's advertisement. Vendors are prohibited from discussing this solicitation with the commissioner's office, county staff, or a member of the Evaluation Committee. The cone of silence terminates when the awarding authority takes action which ends the solicitation. During the cone of silence, inquiries regarding the solicitation should be directed to the project manager or the director of purchasing and or his designee. Also, vendors may communicate with designated representatives from the Office of Economic and Small Business Development at any time regarding the solicitation's small business enterprise or county business enterprise participation. The summary of vendors' rights regarding Briard County competitive solicitations was issued in the solicitation. The initial Evaluation Committee meeting minutes have been distributed to the Evaluation Committee members. Evaluation Committee members, is there any discussion regarding the minutes? Hearing none, may I have a motion to approve the minutes from the initial Evaluation Committee meeting? Antonio Saban, motion. Michael Nairn, second. May I have a, okay, may I have a, you did the second, sorry. All in favor say aye. Aye. Any opposed? Motion passes unanimously. I will now like to call on the purchasing division to report on the vendor demonstrations. Thank you, Madam Facilitator. Each vendor was invited to demonstrate their solution in accordance with the final demonstration script. Demonstration meetings with the Technical Review Team, TRT, were held on November 6th and November 7th, 2025. Project staff has produced a demonstration fact-finding report. The report has been distributed to the Evaluation Committee members for their review and consideration. Thank you. As stated previously at the initial Evaluation Committee meeting, the solicitation required vendors to state whether they accept Broward County's standard terms and conditions or if they do not accept them. To identify the agreement provisions and vendors' proposed changes. The county provided vendors an opportunity to waive their exceptions prior to the final Evaluation Committee meeting. AT&T Enterprises Florida LLC advised that they are open to negotiating all of its exceptions. Motorola has withdrawn all of its exceptions. The specific expectations taken by these vendors are outlined in an exceptions matrix that has been distributed to the Evaluation Committee members for their review. The county attorney's office is available for questions by the Evaluation Committee concerning these exceptions. Are there any questions for the county attorney's office from the Evaluation Committee? Thank you. The next order of business are the vendors' presentations. In accordance with Section 286.0113 of the Florida Statutes, presentations and questions and answers are closed to the public. Only committee members, county staff, the presenting vendor, and their team will be in the closed portion of this meeting. Other vendors, their teams, and members of the public will be excused from the meeting to permit the start of the closed presentation sessions. Subconsultants partnering with multiple prime vendors are only allowed to participate in one vendor's closed presentation session. As the meeting progresses, the Purchasing Division will provide email updates to vendors ensuring that each upcoming presenter is informed when it's time to join. Once all presentations and Q&A sessions have concluded, vendors and members of the public will be invited to return to the public portion of the meeting, during which the Evaluation Committee will score and rank the vendors. Members of the public may provide an email address in the chat to be notified when to return to the public portion of this meeting. Vendors were asked to provide an electronic copy of their presentation to the Purchasing Division prior to this meeting. The presentations received have been distributed to the Evaluation Committee members. Presentation topics, length, and order were identified during the initial evaluation meeting and distributed to the presenting vendors. Each vendor has 30 minutes for presentation, followed by an unlimited question and answer session, and five minutes per setup. The timekeeper will be the assistant manager, Latoya Clark-Forbes. Vendors will be presenting in the following order. First presenter, Motorola. Second presenter, Indigital. Third presenter, AT&T Enterprises Florida LLC. At this time, we will move into the closed portion of this meeting. The first vendor presenting, Motorola, please remain in the meeting. All other presenting vendors, their accompanying teams, and members of the public are requested to leave the virtual meeting room. As a reminder, please continue to monitor your emails for when to rejoin the public portion of this meeting. This meeting is now closed. Good morning, Motorola. Good morning. As you're waiting for members to come off and for your team members to join, you can take a look at the participants panel over to the right and confirm or verify that the folks that remain are members of your team. Thank you for that. All of the Motorola's are here. Looks like some of the other parties are still making their way out of the meeting. Let's see here. And verify there's a couple of phone numbers that I'm not certain if they belong to your team. So it looks like the two phone numbers, 07 is us and 512 is also us. There is, let me see, looks like Mario Ruiz is still on the call from another party. Okay, thank you. Is there anyone else that you don't recognize? Looks like it's good now. Okay, so you can confirm that there's no other individuals in the meeting other than your team and county staff? Correct. And who will be presenting on your behalf so we can give you access? Lisa Madden. Yeah, Lisa Madden is going to be sharing her screen. So if you could give her access to present. Okay, thank you very much. I have that access now. Thank you so much. Snow is expected today. Okay. Also, there's a wind advisory in effect on Friday, December 19th from 8 a.m. to 7 p.m. Okay, your team will now have five minutes to set up. Purchasing staff, please start the timer and please advise us when you're ready to move forward. Lisa, are we good? Yeah, we are good. Okay, we're done. We're ready to start. Okay, thank you, Motorola. Purchasing agent, please start the 30-minute timer for Motorola's presentation. Thank you. Okay. Good morning, Broward County. I'm Danny Sanchez, the Territory Vice President here at Motorola Solutions Florida. And on behalf of the entire company and this team here on the line, thank you for this opportunity. I'm joined by a lot of the team members that participated in the early November demonstrations. And we're here today to answer your questions. I've been at Motorola for about 20 years, which is about the same time that I've been also a very proud Broward County resident and taxpayer. And I'm actually coming to you live today from here, the town of Davie where I live. And this is just one of the reasons why your success is our success. And this is very personal to us. There are thousands of Motorolans who live, work, and play in Broward County since the early 70s. And as you may have heard, as you may have seen, we're doubling down and renewing our investment in the county with a brand new R&D facility that's about to open its doors here early next year. Our mission today in these next 30 minutes is to answer your questions so that you can feel confident that Motorola offers the best value, the most resilient, the most reliable option for your NGCS system, your NGCS service. Lisa Madden will answer the questions that you outlined in the late October committee meeting, while also highlighting our differentiators. These are the benefits that only Motorola can provide to Broward County. You're going to hear about our resilient solution being fully compliant with your technical requirements. You already heard that we agree to all of your terms and conditions, and we're offering all of this at a very compelling turnkey price. With that, I'm going to hand it over to Lisa Madden. Good morning, everyone, and thank you so much, Danny. And I'm Lisa Madden, Regional Manager with Motorola for NextGen Core Services, 20-plus years passionate about 911 and involved in all of our Florida and East Coast projects. Thank you very much, Broward County team, for providing the agenda to review today in our presentation. As you notice, as we go through our presentation, there are quite a few gold M's in the slides. These are areas where we provide extraordinary value to Broward County, as Danny mentioned, recognizing that our collective goal is to dependably, accurately, and quickly deliver a 911 call with as much additional information as possible all the time. So, first, here's what no single point of failure looks like. Our many Florida customers have been hit by many storms, but we were able to deliver 911 calls even when components of their system were impacted. We'll show you how we do this as we dive into the heart of our solution, the architecture and call flow. The single key takeaway of our architecture is no single point of failure, and we will show you how we accomplish that. Now, I know call flow diagrams can look like a confusing jumble, and we have provided a very detailed architecture diagram in our proposal and in the subsequent material that we sent earlier this week. But for today, I will use this diagram to walk you through the requested call flows in a way that's clear, concise, and most importantly, illuminates the core philosophy of our design. I'll quickly identify the components of our solution, starting left to right, and then take you through an actual call flow. I'll point out the green vertical bars here indicate our next-gen core service, and this is all our intellectual property, all with our embedded cybersecurity. On the left, we have full carrier migration. Note the absence of the selective router. They have not been part of our call flow for years, no, eight years. The recent FCC mandate was not a problem for Motorola, as we've been doing this for years, and we're happy to talk more about that later in the Q&A. So now, next we have the ingress, the regional and national points of interconnect, then our highly diverse multi-cloud core, the ESI net with the multiple options for connectivity, and the call handling at your PSAPs. And, of course, we have the customer web portal that lets you keep track of everything going on in your system with a unique level of detail. And we also have an optional emergency backup solution that we have recently been rolling out first in Florida. It's a full-featured call handling solution that will allow calls to be delivered over the Internet or satellite, Starlink, or whatever you prefer, if your call handling or connectivity is unavailable. As part of your request today, you've asked us to show you the voice, text, and multimedia flows. Our call flow is based on NENA I3, and many of the Motorola folks that you see in this call today are on the standards development committees for NENA I3, multimedia, et cetera. We are fully committed to the I3 standards, and we participate in NENA ICE events, et cetera. So the wireless call goes directly to us, no legacy-selective router, at redundant regional or national poise. We already have connectivity to national poise for all the wireless and VoIP providers, and for wireline, we already have regional poise in West Palm, Pompano Beach, and Miami for connectivity to your local exchange carriers. The advantage to Broward County, with this direct connection, Broward is fully ready to receive expanded NENA I3 payloads and support I3 functionality as it's evolving. Other benefits, too, we'd love to talk about them later. So back to our call, from there it goes into the core. We used to have data centers in Florida, but we made the decision a few years ago that our many Florida customers needed more reliability and geographic diversity. So we now have a multi-cloud provider core with three cloud regions, both Azure and AWS, three diverse physical locations, three different power grids, three availability zones of our service. In each of the three locations, three times three is nine, any one of these nine zones is designed to handle all the calls and data. The core is where all the NENA functional elements reside, again, all our IP. The routing destination of the wireless call is determined at this point. We don't outsource any of this, and we are very flexible in the addition of features and functionality. For example, location-based routing is an example of that. In 2021, we worked with our customer in the National Capital Region, a very congested part of the country. Calls were misrouted. So together, we designed, developed, and deployed geospatial routing to make sure the call is delivered to the correct PSAP the first time. The industry for all of our customers includes location-based routing. For Broward, you'll be using the county's very accurate GIS data. So, proceeding into the ESiNet, which is powered by SD-WAN, Software-Defined Wide Area Network, which is constantly assessing the networks. We'll utilize two different MPLS networks plus terrestrial broadband to determine the best, fastest, and most resilient path to Broward's PSAP. We have customers utilize microwave, satellite, LTE, for a third leg of connectivity as well. With SD-WAN, all circuits are active, and the best path is chosen for the call to be delivered. And we are free to pick the best carriers. We are not a carrier. We always pick diverse. And you may be aware of single-carrier solutions, where an issue in the MPLS core has caused massive outages affecting 911 service across large regions of the country. We keep our customers out of the news with this incredibly researched, diverse design. So, the call is then delivered to your load balancers at the PSAP for a response by your call takers. Today, text to 911 is currently delivered through SMS. A text is received via a text control center, which sends a request to the service directly to the national POI. Of course, the FCC report an order in the fairly near future. Text will be delivered in the same way as a voice call, RTT, real-time text, with a path identical to the voice call, carriers into the Motorola routing system, delivered to the POIs, to the core, obtaining location, and then text is passed through the ESINet to the designated PSAP. Now, let's look at multimedia. This is a great topic. Motorola is very knowledgeable about streaming video over a network. We understand the requirements for bandwidth, the need for low latency, and the unique security needs. This is all from our experience across a wide range of other mission-critical products, some of which Broward County utilizes now. In the supplemental material we provided to you this week, we included a link to the past Friday's news release established with Google. Multimedia is embedded into a SIP session. The call then goes to a national POIs and then to the core. The session with the designated PSAP, once the call is delivered, a media proxy URI is sent back, and the actual multimedia is delivered. And as you likely know, the media proxy is part of Nina's NGPSAP in-process standard, not yet published. You've asked us to take you through some scenarios for alternate routing and how we recover from failures. We're happy to do this, as it is truly a core strength in our solution. Thanks to the incredible redundancy and resiliency designed into our call routing solution, we have an amazing record, near 100% availability in our service since going live. We have 10 years of call routing success. We've been delivering over 156 million 911 calls per year, and we protect over 51 million people. Now, let me tell you about the NextGen core services outages our customers have experienced. We've had zero outages. And along those lines, we were recently invited to speak at a high level with two southern states impacted by a large carrier outage this fall. We were asked how we would react to such widespread outages. And our answer, we avoid them. We prevent them from happening in the first place with a redundant design, with diverse technology, and delivering the call, and very importantly, the carrier diversity I discussed, both in the core, where almost all the big outages happen, and also local carrier diversity. Now, notice the title of this slide, Incident Mitigation. We talk about incidents. And to be clear, a piece of our solution on occasion may not operate as expected, but we've accounted for that in our design. That's an incident. Our system is designed for any and every eventuality. It's multi-cloud, multi-zone, multi-region, multi-carrier, multi-carrier type, multi-power grid. So our customers continue providing 911 services during such an incident. If there's an incident, the system is designed to communicate to you what's going on, providing situational awareness, alternate routing around the issue, and providing continuity of service so every 911 call gets answered. We follow PARC, which is prevent, alternate route, and communicate. And here's the proof point, you know, closer to home, Collier County. This image depicts the moment that Hurricane Ian made landfall in the Naples area in September of 22. It highlights the cumulative data feeds and event layers that the Collier County team utilized during the event, gaining situational awareness by aggregating 911 call data, weather feeds, and relevant GIS map data, and specialized layers in real time. They needed to alternate route to Martin County for a bit, and no calls were dropped. They then prepared for additional resilience with Leo as a third link, and we worked with them on interoperability with Leon County and Charleston, South Carolina. So you asked us about specific failure scenarios, POISE, data center, and network. We decided these failure scenarios needed the more detailed diagram. This is the design that we've been looking at, but with more detail. So we have the ingress, we have the POIS, we have the core, the ESINet, and the PSAPs. So first we'll look at the failure of a local or national POIS. Call hits the system, but if that POIS is down, no problem. The call is redirected to another functioning POIS nearby. Same with national POIS, this is redundant by design. Now we'll look at a data center failure. The cloud is in our core. This is the advantage for Broward County with Motorola and where our customers get the ultimate protection. Each region is a campus of data centers, essentially a farm of data centers. If a single zone within a region goes down, say, and the cloud provider utilizes another zone immediately, and if an entire region, say the whole East Coast data center is impacted, the call redirects to another data center, another region. Again, no single point of failure. The calls in our ESINet will look at a network failure. It's heading to Broward County's North PSAP. It's using one of our two dedicated MPLS networks. Remember, we're not a carrier, so we diversify the transport. And one MPLS network in this case has an issue. And the call automatically redirects to the alternate MPLS or terrestrial broadband. And the call comes into the same PSAP without anyone even knowing the first network was impacted. All circuits are active all the time. So what you've seen is alternate routing in an automated manner that does not require you to do anything except select the right partner. This is built into our system. But NT911 is more than just putting in a shiny new awesome network. Many of our customers are happy with that, and that's terrific. But NT911 gives you additional options on alternate call routing in specific situations. Many customers are thinking outside the box for the first time because they can. We work with our customers to jointly develop policy routing rules, which are essentially limitless, based on our customers' operational requirements. In the near future, our customers will create these PRRs and activate them themselves. Baltimore City uses geofencing often for special events in the city. They set up a geofence around the APCO Convention Center this summer and calls for deliver to the stand-up PSAP you see behind the director here and our system architect. So, Broward County, you can do things exactly as you do today, and that is fine, or we can brainstorm and what-if with you as we set up your policy routing options together. For example, do you want a geofence around the Florida boat show so any 911 calls go to a special command post on scene? We've spent a lot of time developing our customer web portal to make sure our customers have visibility and control of their systems. Our customers love the web portal. It's their window. It really ups the game on situational awareness. As you know, this year, as you may know, we acquired Rapid Deploy, and we are actively working now to integrate all our reporting, including the customer web portal, Eclipse Reports, and Data Viewer, into a seamless one-stop shop for the most comprehensive central data hub in the industry. We are committed to delivering the single platform by Broward's Go Live. So, we are just showing you a small piece of the portal today, and we hope to have the chance to show you more as we expand the end-to-end single reporting solution. We'd love to work with you on this. With the portal, you have full visibility into the health of the network, keeping you updated on your environment. We built this with our customer, Greater Harris County, Texas, to help them visibly manage their 39 PSAPs. So, you can easily do this with your six regional and non-regional PSAPs. This is also your access for end-to-end reports, and as I mentioned, we will be integrating with Eclipse, and again, we are committed to delivering the single platform by Go Live. The customer web portal has high availability with redundant configurations within the cloud architecture. A few slides ago, you had a glimpse of how Collier uses the system. The image to the right is the dashboard, providing a web-based way to see what's going on in your environment, including the routing status, the call volume, route exceptions, and the MOS, mean opinion score, measuring voice quality. Now, here's a screenshot from the November 6th demonstration showing a remote, a reroute due to a PSAP bugout, if desired. In this image, there are two Broward PSAPs that are shown, and wherever there's a route exception, it turns red and shows where the call went. This visually shows situational awareness of PSAPs experiencing exception routing, and our customers have this up on their wall monitor in the PSAPs. On this screen to the left is the menu for the web portal. We saw the dashboard recently. You can see the health of the system here, of the core regions, and the ESINet links, as well as the status of the PSAPs. On this slide, we're showing a Vestinex call handling receipt of a diverted call. For call handling equipment, you should be able to use the diversion tagging to display the diversion as well. Once the call is answered, Vyper should be able to see the reasoning. In this case, we can see the reasoning here with the congestion. And Vyper may decide to show this prior to answering the call. We tag all diverted calls with the NENA standard diversion causes. And following the theme that customers benefit from useful aggregated data, we believe that our advanced analytics capability is a real differentiator. Broward will be using our Eclipse reporting platform, which will incorporate data from call routing, call handling, CAD, and communication from responders. We are excited to show you the maps of our deployment. We've created the requested maps, clearly identifying our completed deployments and those in progress, inclusive of the Vyper sites. So we thought it good to start with the big picture. 51 million people served across North America, 100% carrier migration off the selective router. As you look at this map, the green is statewide. The dots are individual deployments. To meet your requirements for a map showing deployment status by county, we have broken down our U.S. deployments by region. First, we're out west. And to orient you, blue is fully deployed with Motorola call routing. The blue stripes indicate in progress. So let's start at the top. We have a statewide contract for Idaho. We received that recently. And we have deployed Boise, Idaho, which is the largest population center, and we're working on the other 43 counties now. We have completed the full 29 counties in Utah and 33 counties in New Mexico. We are live in the city of Las Vegas and only have the Navajo Nation with 110 chapters, which are essentially counties, left for deployment. Now, the green shows the Vyper locations. And in New Mexico, we have four completed Vyper locations, and there are two that are in progress in Idaho. Texas deserves its own map, 42 counties. Many of our customers are the districts and multiple counties together as COGS. Out of all the different customers in the state, this represents the ones that have exercised the power to choose. We have a big chunk of the population, if not the real estate. You'll notice Greater Harris County, Texas, third largest regional system in the U.S. This is essentially Houston, 6 million people. And I've included a quote from Greater Harris County's website where they point out that they have the most technologically advanced and reliable 911 system available. There is one Vyper site, McClellan County, Texas, and we've served there for years. Moving to the Midwest, again, a lot of land, but we've served the people. So Kansas City, metropolitan area, fully deployed in this large population center. We're also working on St. Louis over here. And these are the two stripes. We have these two deployments that remain. We are super proud of the city of Chicago. They had been an AT&T customer for years for Legacy, but chose to work directly with us for NextGen Core Services in the county, Greene County, Missouri, using Viper. And then looking at the Mid-Atlantic, first of all, as much as I love New York, they've done absolutely nothing for NextGen 911 at all. So the city, though, has boroughs, which are essentially counties, live using our core services, our routing service. Maryland is interspersed with some AT&T deployments. This is the national capital region here. And we are transferring calls back and forth between us and AT&T. West Virginia, which, again, lots of land, but we serve the people. There are two counties over here, one that has been deployed and one that's in the process of being deployed. Now we get to Florida. So we have a great group of customers in the western counties from Manatee to Monroe. This would give you guys a possible alternate route if a storm hits you in the east. We just brought Escambia County live last week. It was rapid, six-month successful deployment. They're putting out a press release. We're thinking maybe today on the success. Sumter's in progress. It's a recent contract. And Monroe is moving forward, a Viper site. We've designed a system for them there with satellite connectivity since both MPLS go over the same bridge. And these are customers that are of a similar size to Broward County. And here is the big picture with the total number of counties and the zero outages. I mentioned Escambia County just went live. Here's a pic of our happy team last week. I would be remiss if I don't mention that I would put our team of deployment and support folks up against anyone in the industry. They are awesome. And our NextGen Core Services group has the highest customer satisfaction rating in all of Motorola. Our customers are all references and would recommend Motorola NextGen Core Services. Lastly, I'm hoping you had a chance to read some of these testimonials. We are proud and thankful for our wonderful customer base and would love to add Broward County to the Motorola NGCS family. Danny, I'm turning this back to you. Thank you, Lisa. One of your other requests was a pricing confirmation by Motorola, and we do confirm that the pricing that we submitted in our proposal is for the entire requirements that are indicated and outlined in the statement of work. Next slide. Okay. So, in closing, thank you, Lisa. First of all, we hope, Broward County, that you saw and heard what resilience means to us. There's, if you do the math, 10 years, over 150 million calls a year, there's over a billion NGCS calls that have been delivered with zero outages. In fact, in this NGCS team, we don't talk about outages. We talk about incidents, like Lisa mentioned. We talk in terms of, we don't talk in terms of failure scenarios. We talk about resilience scenarios, right? And it's this same resilience that has created the track record that you can trust, a track record that spans from the biggest metros like New York City, Houston, Chicago, Vegas, and also to the dozen counties in Florida who have never lost an NGCS 911 call with us, even during the hurricane seasons. There's over 50 million people that we serve, but we really hope that we have given you the confidence to trust us to serve and protect the over 2 million souls here in Broward County with this NGCS system and service. So, in summary, we feel, we hope that you feel that Motorola is in the best position to deliver the system, the service, so that we can truly deliver a system that can serve as the intersection where the public safety technology meets humanity in order to save lives. And again, we can do this at the best value for Broward County. We are fully compliant with technical requirements. We agree to all the terms and conditions, and we're doing so at a very compelling turnkey price. Again, thank you for the opportunity, and now we look forward to answering any questions that you may have. Thank you. Victoria, back to you. Thank you. Hello? Just one moment, please. Okay. Thank you, Motorola, for your time. We appreciate your presentation. Just give us one moment, please. We apologize for the fire drill, but is the committee okay? Did they hear everything that the last presenter, the last few minutes when the alarm came on? Did you all hear everything correctly and clearly, or would you like anything to be restated? I heard everything. Yeah, I heard everything, too. Yeah, it was clear. Thank you. We apologize. There was a fire alarm that was going off during the last few seconds of your presentation, so we just want to make sure everyone was able to hear what was being said. Thank you once again. Okay, I'm happy to restate it. It's less than two minutes, if it's okay with you. No, we're good. The EC members have stated that they heard what you, I mean, it was literally the last two seconds of your statement, so we appreciate it. So thank you once again, Motorola, for your presentation. Are there any questions from the evaluation committee members? Please state your name before asking your question. Thank you. Good morning. My name is Angela Scott, and I just had a question regarding the emergency backup call handling. You said that was an option, but we didn't include it as a requirement, but it's an optional service we could request in the future? Yes, absolutely. And as I mentioned, we're deploying this in Florida first, so some of your neighbors will be utilizing it. It's a full-featured emergency backup solution. So absolutely, at any point that you would want, we could include that in our conversation. Is it in service now, or it's something you're developing? So it has been, so during December, it's being deployed in Martin County and a couple of the Panhandle sites. So they have it, and we have begun, we were hoping that there will be no use for it with any sort of storms or whatever right now, but it has been utilized, and they have been testing it, and we have fully deployed it. Okay, thank you. In a couple of locations, and we're moving throughout our customer base. Hello, Daniel Canchon. I have a question regarding the, you know, networks described. You know, you mentioned the SCNet and the multi-cloud core. For the third-party attestations, you know, ISO 27001, SOC 2, can you discuss, you know, what applies to each network that you currently have? Yes. I think, Mr. Zyler, would this be inappropriate? And you are on mute, sir, because I know that you... Oh, you look like I'm on mute. There you are. Okay. Got it. I'm one of those sneaky call-in people. So we are ISO 27001 certified, as well as SOC 2, type 2 reported. And the SOC 2, type 2 report and the ISO certification are obviously communicable. I believe the SOC 2 still requires a specific agreement with the auditor, but that's just normal to rigor. So we are fully reported across the NGCS solution. So the ISO 27001... Certified on the ISO, reported on the SOC. And that is fully the entire thing, the whole multi-cloud core and the web portal that we will be using, the SCNet web portal? So it's for the NGCS solution as a whole, so yes. Okay. And the SOC 2 as well, you say? It's scoped for... Yes. And out of curiosity... So the SOC 2 is mostly service... The SOC 2 is mostly service organization controls, right? So it's mostly how we manage it and control it. Again, it does cover the entire solution. And is it for all five trust principles, or which trust principles apply? All five. Thank you. This is Michael Nair, and I'll first start out with a number of questions regarding your cost. You stated that your cost proposal will cover all of the requirements that we outline in the scope of work, or the statement of work. I'd like to just ask some very specific questions regarding some of our requirements and make sure that the requirements and your ability to fulfill these requirements are a part of your cost proposal. The Motorola Vesta Next Continuity option, is that option included in your cost proposal? It's not at this time. Okay. That was identified as optional. Okay. If you do want to talk about it, we'd be happy to talk. There is a requirement. We had noted a requirement. We, obviously, here at Broward County, would like to set up a lab environment, a test environment. And there are some requirements for you to, as our next-gen core service provider, to provide integration and connectivity to our lab environment. Is the cost associated with setting up connectivity to our lab environment included in your cost proposal? So, we have been able to edit the response that we had previously, comply with exception, to a full comply for the requirements that you had for testing and connectivity. And, yes, our cost is inclusive of that. That was in your scope. Absolutely. Okay. Again, related to cost, spare parts, the spare parts depot on-site included as a part of your cost proposal. Are the spare parts depot for critical components a part of your cost proposal? They sure are. Absolutely, sir. The tertiary option as a requirement, one of our requirements, SR-NR005, calls for a tertiary connectivity option. Is the option and the ability for you to fulfill that requirement included in your cost proposal? Yes. That's the tertiary broadband that we have included in our proposal. Yes, it is. Stir-shaken. You're projecting that you'll be able to offer stir-shaken capabilities in the first quarter of 2026. Is this also included in your cost proposal? Yes, it is. And if you want to be shaken, Dan Zyler, who is the head of our NextGen Core Services cybersecurity, may be able to add some additional color, but the answer to your question is yes. Thank you. Media recording. This is related to requirement SR-CP005, media recording in the cloud. Is your ability to fulfill this requirement included in your cost proposal? Can I ask Chuck, can you verify that that is? I want to be accurate in the information that I'm... I would actually defer to the product manager, Sam Bard. Okay. Yep. We have Sam Bard, who is our NextGen Core Services product manager, on the bridge here. Sam? Yeah. So, what we support is, you know, a specific output, the ability to provide that output, you know, putting a spec to a, you know, a third-party recorder or, you know, media recording or archiving mechanism, but we are not including the mechanism in the proposal. You stated that it is not in the proposal? Yeah. And maybe a logger or an I-3 logger is not included. Check. Keep. I'm going to make sure that I'm correct, but, you know, that's not part of the proposal. Yeah. Michael, the... We can provide the output to your recorders. Okay. Just regarding your presentation, specifically regarding the architecture diagram, what you were proposed here as a solution for Broward, are there any components in your architecture diagram and the solution you're proposing for Broward that is not in production today? No, sir. Everything that we have proposed for Broward is in production today. Michael, if I could, Danny here, can you hear me? Yes. Regarding your first question about Best and Next Continuity, so, as the team stated, that was included as optional because we interpreted the requirement to be optional. If Broward County desires Best and Next Continuity, we will commit right here to include it in our price that we have provided for you. Okay. Just looking here down my list of questions here, one moment here. Regarding requirement SRDL001, have you transitioned to IPV6? And if not, when are you planning to? Sam, could I ask you to answer that, please? Yeah, we support that today. And then, you know, we're dual supporting IPV4 and IPV6 in various areas of the system. And, you know, we've been sending that option to the call handling systems, and we meet them where they are and allow them to evolve as they need to. But otherwise, we're supportive of IPV6, you know, across the service. So, we support IPV6 and the core IPV6 today. Thank you. Correct. And then, again, at the edge, we're, you know, our approach, we're not mandating that and imposing that on the parties we connect to, upstream, downstream, laterally. You know, we're allowing them to move at their pace. So, you know, we can move to operational systems from customers, and then the calling systems or the other vendors or OSPs can catch up at their, you know, at their own pace. So, we don't stall for mobile. Thank you. Moving on to requirement SR-DL-DL014B. Does your solution provide notification of functional element failures of a Broward County call when calls are not delivered to the PSAP? Absolutely, yes. Thank you. I'm moving down to requirement SR-SLA003.B. The requirement revolves around resolving issues with specific service level requirements. Given the reliability and high availability expectations, are you able to commit to SLAs in the table that we provided based on remote response? Yes, absolutely. Absolutely, we are. Okay. We have, we comply to that, and we absolutely support that. Requirement SR-SLA008, service credits. Again, you know, as you can imagine here at Broward County, we have high expectations when it comes to availability. Are you able to, if, I know you spoke quite a bit about the resiliency of your system, you, who, to date, have had no outages, we are requiring and requesting a service credit commitment here in this specific requirement. Again, this is requirement SR-SLA008. Given our requirements and expectations, are you able to commit to the service credits in the table that we outline? Yes, we are. We absolutely have committed to those, and we echo your concern about no outages, as you know. That's a core tenant of our core services. So, we do, we are, we are good with that. Thank you. Moving on down to requirement VN008. This is around mean time between failure. Based on your response, there was one failure in the last 10 years. I take it based on your presentation, this was not an outage. Was this a failure of a component? That is correct. We have incidents where there may be one piece of our solution where there's a component that fails. So, we have architected a workaround for every single leg, every single piece. It was an incident, not an outage. Thank you. One last question here, looking at requirement, in reference to requirement VN001. Would Motorola be willing to offer dedicated technicians on site, should there be a need for a dedicated technician on site? So, we have on our call, we have Jim Stowe, who is our service manager. I will answer that before I pass it to Jim, to say we have very, so if necessary, we will. We have not had that as a necessity for any of our NextGen Core Services customers, because with the cloud architecture, there is very little hardware, very little equipment that is on site. We are right here in Plantation, so we are absolutely ready to go. So, should there be any sort of an incident that requires in-person resources? Jim, is there anything that you would want to speak about? Oh, first, good morning. Jim Stowe, I've been running the operations team for the NextGen Core Services team for the last six years. To Lisa's point, the majority of the infrastructure and network is accessible remotely. And so, at the actual edge device, where your PSAPs would be, is essentially an edge device router. So, there's very little equipment. And we do have relationships, if need be, for any kind of hardware replacement or to verify power and those things. So, you know, 95%, 97% of what we can do is remote already. So, I'll leave it. If we need to, we will assign a tech to support you. Thank you. Then my last question, it's regarding RPT003.B as a requirement. You had mentioned in your presentation that you are rolling out Rapid Deploy as a reporting solution, the Eclipse solution. Is this reporting option a part of the solution that you'll be providing to Broward County? Yes, it is. And it's not even a reporting option. It will be the way of our single reporting hub that will contain all of the components, a single pane of glass, a single point for the data. So, absolutely, yes. One of the reasons that we bought Rapid Deploy is because of Eclipse and their great reporting capabilities. We felt they were the best in the business. And we are incorporating that, pulling everything together into one platform. And that is included. Yes, sir. Thank you. I have no more questions. Thank you. Thank you. Are there any other questions from the Evaluation Committee? Please proceed. Yes. Yeah. Good morning. Brandon Watson. Looking at your diagram, you have, obviously, you mentioned AT&T being an MPLS carrier. And obviously, Motorola is not a carrier. Have you looked at other solutions in Broward County? And what solution would you propose as a second MPLS carrier? Yeah. Would you like to answer that, since you are very... Certainly. So, our core delivers through AT&T MPLS and Verizon MPLS. We also have that terrestrial broadband connection through Comcast. So, all three are active all the time. There's no failover from one to the other. It's just constantly checking to see what's the best path to send the call. So, perfect. Thank you. Are there any other questions from the Evaluation Committee? Hi. This is Angela Scott again. One of the comments from the demonstration was that there was no central place to access data and reporting. But you just spoke about the Eclipse and the web portal. Is that something that's new, or is that all in one place, or is it only accessible through the web portal, or are there different interfaces to get reporting? That's a really... It's evolving. It is something we have committed to provide to Broward County by the time you go live. We would work with you to make sure that this meets your requirements. But it is a single reporting hub that, because of the acquisition with Rapid Deploy and the Eclipse product, we see the value of one single point of data collection, aggregation. We are well underway in the development of this process and product, and we would commit to having that ready for Broward County by the time that you would go live. Lisa, if I could add on to that, Eclipse will be the single platform for call recording, or call reporting, excuse me, from end-to-end, NGCS, through call handling. We do have other platforms for case management and situational awareness and system health. All are available through the customer web portal, but you can access Eclipse directly if you choose to do so for call reporting. Okay, thank you. And then just one last thing about the policy routing. Are we able to edit rules and policies, or is that only through the portal, or are there other places that can be done? Do you want to take that, Chuck? I'll take that. It's such an exciting area. It is. It is. So policy routing rules are pretty much limitless. We do conform to the NENA standards for causes for alternate routing. Currently, the policy routing rules need to be set up by us to ensure that there are no loopbacks or continuation of calls. You do have the ability to abandon a PSAP through the web portal, and we are working towards allowing customers to edit their own policy routing rules. The complexity of those, we want to make sure that they work. So we would like to be involved in those decisions, but we are moving towards allowing customers to edit their own policy routing rules. And if I could add one more thing, Broward County is in such a great position with that because of the work that's been done in the GIS team. And, you know, Ashley's on the call here for us, and we've worked closely with you guys to make sure that you have a really strong GIS layer, and that will be utilized during the policy routing rules. And as you saw with Baltimore City, putting a polygon out there that can be utilized for how you route calls. So I just wanted to add that, that you guys are in a really great position to use the policy routing rules. And you working with us to configure those, that's included in your price? Only because I'm asking because, you know, obviously at the airport, we have the ability to include some of that information when we pass the call. If someone dials 911 from a gate or a jet bridge, we can pass certain information, including GIS information. And I believe right now it's not received on the other end, so I just wanted to mention. Like bacon, egg, and cheese on a toasted brio. So, yes, that is something that we absolutely would love to work with you. It's completely included, and we have a team of folks who, what if you do this? Or, you know, I mentioned the Florida Boat Show, but I'm sure you have other, you know, concerts, other events, things that are going on locally. And we love it when our customers are creative and are open to, like, trying something a little different with how calls are routed. We make sure that we do all sorts of testing ahead of time with the polygons that you set up. So as Chuck mentioned, there's no back and forth with calls, but we are absolutely, and yes, everything involved with that is included and encouraged. Okay, thank you. I would expect that there would be a multi-day meeting to define your policy routing rules. The complexity of your routing solution today needs to be matched and enhanced. So that's going to take some time to walk through all of those. Okay, thank you. Thank you very much. Are there any other questions? Yeah, Brennan Watson, one more question. I'm sorry. In the Azure and AWS zones, are those resources available all the time so that there's a seamless rollover? Should, you know, recently there's been incidents with both AWS and with other cloud services where they've taken total failures. Is it a seamless rollover from one carrier to the other? Yes, it is a seamless rollover. Do you have anything you want to add to that as to how we're, you know, we absolutely, none of our customers have been affected by the recent cloud issue to cloud providers. All right, great. Thank you. A couple of points there. It is all essentially thick provisioned in that way. So the capacity is there. We're sending the calls across those three regions. So at any given moment, roughly 30% of that traffic is across those three regions. Michael Nairn, regarding requirement TIME 001, based on the requirements in the RFP, are you able, are you actually committed to completing an implementation for our regional dispatch centers in the 12 months from contract execution and our non-regional dispatch centers within 15 months from our contract execution? Yes, we absolutely are. And we believe our deployment team can do the entire Broward County deployment in 12 months, directly. Thank you. Thank you very much. Thank you, Evaluation Committee members. Does the project manager have any questions? No, I don't. Thank you. Thank you very much. Thank you, Motorola, for your time this morning. Thank you all very much. Appreciate the attention, and we hope we have the opportunity to speak again soon. Thank you. The first presenter, Motorola, has now completed their presentation and answered all questions. Would purchasing staff please invite the second presenter, Indigital, to join the closed portion of the meeting for their presentation? Thank you. Goodbye. Thank you. Good morning, Indigital. Good morning. Good morning. Thank you for joining. As your team members join, please review the meeting attendees in the Teams Participants panel. Please review to ensure only your team members and county staff are in attendance. We are displaying on the screen the list of county staff in attendance. While you are reviewing the list of participants panel, please advise which member of your team should be designated as a presenter in Teams to share their screen during the presentation. Who should we give access to? I will present. I will present. And can you state your name? Who is that speaking? Caleb Branch. Thank you very much. There's a phone number that just showed up. Can you verify that's a member of your team? That is. That's Holly Peacock. She's with Indigital. Okay. Indigital, you have five minutes to set up. Purchasing, please start the five-minute timer. I'm sorry. Before we get started, did you confirm the list of attendees on the participants to make sure that they're all part of your team? Yes, we have reviewed. Okay. Great. Five minutes to get set up. Thank you. Please let us know when you're ready to begin. I'll say I think we're good to go as soon as you are. Okay. Indigital, you may begin. Purchasing agent, please start the 30-minute timer for Indigital's presentation. Thank you. Well, good morning. My name is Larry Stidham, Vice President of Sales at Indigital. And on behalf of all of us at Indigital, we want to thank you for giving us the opportunity to present our final NGCS solution for Broward County. Like you see on the slide, Indigital comes prepared, proven, and ready to serve. We have extensive experience delivering NGCS services, including in some of the most complex and demanding environments. As you'll see throughout the presentation, we don't just understand the technology. We understand the mission, the responsibility, and the expectations of the communities that you serve. So today, we're going to show you how our approach, our people, and our track record uniquely positions us to support Broward County with a seamless transition and long-term success. We look forward to proving to you why Indigital is the right partner for your next-gen core services. Indigital's NGCS technology supports 76% of Florida's PSAPs, 51 of the state's 67 counties, delivering reliable 911 service to over 10 million residents, almost half the state's population. Forty counties are served directly by Indigital with another 11 through Motorola's Vesta router, which is powered by Indigital and NGCS. What's interesting for Broward County is that Motorola didn't contact Indigital for a quote on your project. We've confirmed they're proposing their new CC router, which would be the first and only deployment in Florida. Every existing Motorola customer in Florida is using the proven, fully integrated Indigital solution, not the CC router. So why Indigital? We're a company built around a single mission, NGCS. It's all we do. No distractions, no competing priorities, no other corporate divisions that divide our attention. And a lot of Indigital staff comes right from the industry. So former 911 directors, deputy directors, supervisors, they come from police, fire, EMS. I'm a former police officer myself. Many others have years of experience working with PSAPs on their technology needs. So that gives us a really deep empathy for what you face on a daily basis. We know what's needed. We anticipate the next step and we deliver with precision. We're also steady through any storm. Some storms you can see coming days away. And Indigital's proactive in executing a plan to help you manage through it. Caleb is going to highlight one of those occasions later in his presentation. Some disasters strike without warning. Indigital responds without hesitation. We help you weather any storm, keeping your agency connected, and receiving calls, even when conditions are their worst. We're quick with quality. We turn decisions into deployments faster than anyone. Leveraging our long experience with EZNet and NGCS, we've developed a streamlined, tested approach to ensure that every project succeeds. On time, on target. We're vendor neutral, meaning that you're not limited or locked into certain technology based on the NGCore service provider that you choose. We work with all of them. We're a partner that's defined by flexibility, independence, interoperability. Always ready to serve because seconds save lives. And we have proven resiliency. Other networks go down. We stay up. Your 911 calls keep coming because of our redundant, resilient, multi-route, multi-carrier network. And then Mevo is your ultimate backup. And we have Florida-focused resources. Our Florida customers benefit from a full, dedicated, and digital team, a market manager, service manager, 911 solutions architect, an engineer, and others, providing focused and responsive service 24 hours a day, 365 days a year. You don't close. We don't close. I'll turn it over to Eric, and he'll walk you through our network architecture. Good morning. Thank you, Larry. Again, my name is Eric, Chief Operations Officer at Indigital. I've been with the company for nearly 25 years. I am responsible for the teams that will install and the ongoing operations of the system once it is deployed. When I think of architecture, I focus on the network, application, and hardware service layers. Our primary objective in this section is to convey our engineering objectives to exceed 5.9's availability for NG Core services. We focus on a minimum three levels of redundancy for all of our deployments. As we go through the second section of architecture and the next call flow section, be on the lookout for the three paths, a primary, secondary, and an out-of-band tertiary path. At Indigital, we have local data centers in production today located in Florida, in Jacksonville, and Winter Haven. Our NG Core service systems are routing over 14,000 911 calls a day in the state. Unlike our competitors, we are not backhauling local 911 calls across the country for call processing. We directly connect to the carriers and other NG 911 providers via network-to-network interfaces. We leverage our national infrastructure for operations, administration, and management of the systems. We deploy a minimum of three layers of network redundancy between our data centers to exceed the 5.9's of uptime. The goal is to get the shortest, most reliable path from the carrier to the PSAP. We work collaboratively with all 911 stakeholders to achieve this, PSAPs and carriers included. Resiliency is the ability to still deliver emergency calls when redundancy fails. We've seen countless outages in this industry with service impairments of very redundant systems. There are lessons to be learned and mitigation strategies to be deployed from events like the Nashville bombing, recent AWS outages, CloudFair outages, CrowdStrike, and even our own experiences. We are constantly reviewing and improving our applications, network, and hardware deployment designs to improve the reliability of our services. On the left of the drawing, carriers ingress to our data centers via direct network-to-network interconnections, redundantly using SIP protocols. Carriers can also leverage our national employees if it provides an advantage to the 911 authority to do so. We help coordinate the best solution for all the stakeholders involved. Focusing on the NGCore service elements in the middle, we operate four active-active call chains on redundant hardware with each single chain capable of serving the entire state. We develop and maintain all major functional elements in the call flow. The BCF, ESRP, ECRF, LDB, PRF are all in digital technologies. Unique to in digital, we deploy an independent hardware and software application service for disaster recovery purposes. Our disaster recovery system allows carriers to deliver calls directly to us via the PSTN or SIP when normal trunking fails. But we still deliver the call via the EZENET with 901 priority and the location services to the PSAP. Looking at the red and blue network links coming out of the EZENET, we build our networks with a primary, secondary, and tertiary connections, selecting the best local providers serving Bower County PSAPs. We use different providers for each network link in the EZENET. Our competitors commonly use multiple network connections from the same vendor. In this particular project, we've included Starlink as a preferred tertiary path. As we have had poor experiences with LTE priority services such as FirstNet being suitable for call delivery in times of need, any two network paths can fail and we can still maintain service reliability to the PSAP. When delivering calls to the Vypr7 call handling system, we'll be doing so using I3 standards. This includes all common I3 interfaces of SIP, SIP with location, PIDA flow, and held location queries. Interfacing will be completed via TLS encryption. Kale will talk more about our non-voice and video capabilities, but MSRP, RTT, SsecureRTP for video integration are all supported directly to the call handling, not over the top. We have interfaced to 11 different call handling vendors in our production network throughout the country. Our policy routing function gives the PSAPs and us the capabilities to distribute calls and minimize impacts of major service impairments. PRF is a collaborative effort between the PSAPs and sometimes other 911 service providers and in digital to effectively prepare and respond to infrastructure outage or system failures. Kale will discuss PRF in more details in the next section. From a hardware perspective, redundancy and reliability is also built into our hardware within the data center. We utilize three independent physical servers running VMware ESXi. This allows us to quickly upgrade, backup, and secure hosted applications without disrupting NGCore services. On the right is the rack drawing of the equipment expected to be installed with PSAP. Hardware is fully redundant utilizing I3 best practices and standards relating to security and routing. Security intrusion detection, intrusion prevention licenses with BGTP and BFD routing protocols to efficiently redirect IP traffic in the event that the link goes down. The data center and PSAP hardware can be expanded to provide additional points of interface within Broward County as needed to better serve the project. The RFP showed interest in having some data center and or POI capabilities within the county. This is supportable, and we look forward to discussing this design with your engineering staff. Architecture differentiators. InDigital owns delivery and routing and applications processing and call from the carrier to the PSAP. We develop our own software, and we are responsible for the redundancy and resiliency of the models deployed. Many of our competitors are relying on third parties for carrier aggregation services, such as Cinch or NGCore services in the case of AT&T and Entrato. InDigital is not limited by any third party, and we have no hurdles to jump to implementation or to maintain your project. InDigital is ready to execute the build-out of the EziNet to your PSAPs right away. We are connected with all major 9-in-1 providers to transition your services from legacy to NG while maintaining interoperability and service reliability. We are confident in our experience that will exceed your expectations as an NG9-in-1 partner. I'd like to introduce Caleb Branch to the next section. Hey, good morning. My name is Caleb Branch. I am the Vice President of Market Management for InDigital. My responsibility at the company is to oversee our service delivery and quality, as well as our ability to be able to meet you where you are and accomplish your goals as an NG9-1 center, as you seek to service the citizens and the visitors of your county. So I'm going to answer some questions related to what you pose to us in this process, specifically around policy routing. And I'll start with just a basic diagram of the policy routing function within our network. So as Eric said, we maintain all the functional elements within the InDigital core services platform that we deploy in Florida and everywhere else. This includes the policy router. Now, the policy router gives you the ability to be able to send your calls automatically to wherever you determine, based on availability, whether that be call taker availability, capacity, if you'd like to load share between A and B sides of equipment, maybe through a geographic region. And I'll talk more about that later through geo-routing, and also in the event that you have a disaster scenario or a large-scale event that pulls resources to one portion of your county or the other. All of this is completely configurable by the 911 center in coordination with InDigital. You have extreme flexibility for not only how your calls are delivered, but also when they are delivered based on time and schedule-based routing. It is a very flexible, I3-compliant solution. So I'm going to answer some of your questions in terms of failures, but I would like to start with call flow so that we can go into the failure scenarios and maybe a wider view of how we view those different applications. So this is a normal call flow. As Eric explained earlier, there are four chains within the call flow system, too, one data center and two in the other. A call would come in from a wireless wireline or void provider and then be processed through the border control function, through the functional elements, out of the egress border control function. The ESE net would determine what host was available, and through one of those three connections would send that call to the host. Here's an example of CHE failure. One of the questions we were asked was, what's the alternate routing scenario for one side of CHE failure? The call ingresses to the network just as it would normally. The network then senses that the A side is down, and then the call is automatically delivered to the B side. There is no hesitation. There's no loss of connectivity delay based on that A side down. The network is always in an active, active mode, searching for the shortest path, as Eric said, to be able to deliver the call. In the event that the CHE, for whatever reason, is down on both the A and the B side, then we can deliver to a backup call handling application, an admin line, or, as you will see in the next slide, we can deliver it to a neighboring PSAP. So, for whatever reason, if your 911 center is unable to answer a 911 call, the policy route would be further invoked to be able to send that call to maybe a neighbor, or either through a distribution group based on geography. Maybe you want the calls in the northern part of the county to go to a PSAP to the north. Maybe the calls in the eastern part to go to the east, and so on. Or either in round-robin fashion, so that other centers get your calls in a distributed fashion, so that they're not overwhelmed. We know it's very, very interesting that during COVID, we used round-robin policy routing to be able to distribute calls for PSAPs that had to disperse as to not spread COVID, and that was very effective. And then, in addition to that, we have the ability inside the policy route to be able to deliver calls to someone else, maybe a neighbor, maybe not a neighbor, that's on an additional or another EZ-Net. The example that comes to mind is Collier County, Florida, who is on a Motorola EZ-Net, and Charleston County, South Carolina, who is service-buying digital. Inside each policy route for Collier County and for Charleston, there is the ability to automatically send calls to the other. And if you look, just in terms of geography, those PSAPs are over 500 miles apart. The goal there was, by those agencies, was to have a scenario in which, if there is a catastrophe that occurred at either 911 center, like a large weather event such as a hurricane, that a call could be delivered and that information relayed somewhere. We are very proud of that. We are the only ones to have done that type of work to be able to ensure that EZ-Nets are able to talk to one another as well as communicate very mission-critical traffic such as a 911 call. That is in production today. That is not a theory. That is not a proof of concept. That is in production today. One of the other things that differentiates in digital is our ability to be able to receive calls from originating service providers such as carriers, whether that be wireline or wireless, in the event that both their primary and secondary connection is down to the data center. So, notice that we require carriers to connect to us in two separate ways, but if, for whatever reason, they're unable to deliver the call into our data centers because both connections are down, then that call can be delivered over an 800 number that is private that we supply them to our disaster recovery core, which sits in both data centers. That call is then processed with full location ability. We're able to pick up the callback number or the PANI, process the location, and then deliver the call as normal to your Viper 7. The goal there is for the call taker or the telecommunicator to not know that there has been a service impairment on the part of the interconnection because the call arrives as normal with normal location information when it arrives to the 911 center. Our competitors would deliver that call over an admin line with no location information, and you really would not be able to distinguish whether or not that was an actual 911 call coming in on an admin line or just normal traffic. Another question that you had for us was related to data center functional element failure, and I'll simply say this, and in this drawing here, please notice that all of our functional elements are tied to one another, meaning that all the border control functions talk to one another, whether they're inside this data center or inside this one, and they know the status of the next functional element in the call chain. So, in this diagram, you see that your core service's routing proxy and routing function have gone down, and as a result of that, the border control function just sends that call immediately to call chain B. And then that call is processed through the data center out the ESI net, and then to your VIPER 7 host A. The same is the case if the data center's down. That call is immediately sent from carrier to the backup data center or to the secondary data center, and then that call is then sent into the VIPER 7. This is a very effective way to do maintenance, whether that be OSP maintenance, whether that be functional element maintenance, or whether that be a real-world scenario in which a data center goes down. We are proud of that. We are so proud of that that we undergo independent validation and verification testing in which we have third parties come in at customer's request to make sure that what the customer bought is what we, as a service provider, have deployed. So, this is a graphic about that. In each one of those four call chains, so this is per call chain, we have been independently verified and validated to be able to receive 50,000 calls concurrently, 6,000 calls in a concurrent session to the PSAP, and then 600 third-party conference calls or conference bridges over just one call chain. And remember, you have four of those. I am originally from the PSAP, was responsible for SNET deployment on Indigital's behalf in the state of Alabama, and have participated in the IV and V testing multiple times. It is always good, from just a service provider standpoint, to have a third party come in along with a customer and say, okay, what you have purchased is what Indigital is providing. You would ask us about portal failure in the event that your policy reroute tool went down or maybe your analytics platform went down. As Eric said, and what has been the theme throughout this presentation is that if one element is down, then we have a backup, and then we have a backup to a backup. So, in the case of the policy reroute tool being down, then we have the ability to, and we will just install a soft switch phone inside each 911 center so that you can affect your policy routes, whether you need to put your calls to a backup 911 system or maybe an alternate PSAP. And for whatever reason, both of these are down, our NSOC is staffed 24-7-365. You go through no-call tree. They're American-based, and they'll pick up your call and reroute your calls for you. Very, very easy. Same way with our analytics tool, multiple redundant platforms, and the fail-safe is our NOC who can go in, or NSOC who can go in and pull that data. You would ask about call flow through for text. And so, this is a very simplistic graphic to say that we have the ability to be able to, through our own TCC, deliver text to integrated CHE to an over-the-top platform like a texty application in a web window, or through our text control API to prepare to rapid SOS. All of these are functional today, and many of them are currently in the state of Florida. Well, we believe this will only be an interim step. As we continue down the I3 path, specifically as full phase two report and order comes to fruition, all these calls, whether that be text, multimedia, or voice, will appear to our network in the same way. We will take the header from the SIP message and determine if that is a text call, if that's a voice call, if that's a video call. And then, within your call handling application, a multimedia window will present. And then, you're able to conduct business all within one seamless pane of glass inside the call handling application. This is the goal of I3. I wanted to include an example to tell you that we have done something as a 911 service provider that none of our competitors have, and that is to complete three-way video, end-to-end video, with T-Mobile, into a call handling system, and then conference a responder into that video. So, no over-the-top apps, no additional screen to look at, all within the call handling application, all based on the I3 standard, no workaround. The goal is to realize the I3 standard by deploying integrative and creative applications like this GoLive project that we did with T-Mobile. We're now working with the remainder of the carriers to do that. Again, we want you to buy the most technically advanced and best-for-you solution for Broward County. I'd like to close with this story just kind of about our commitment to the state of Florida. We all are responders. Many of us that work for Indigital have backgrounds in fire law, EMS, or in the PSAP. And as a result of that, we know what it takes to be able to successfully respond to any emergency. You know, Hurricane Milton was originally forecast to be a generational storm. And so, we wanted to make sure that we went out and we served the 911 centers and anybody else that we could in the event that there is a catastrophe in the state of Florida. And so, we spun up 30 Starlink satellites, deployed 14 PSAPs in a box, we call that Mevo Anywhere Kits, and strategically deployed 25 team members all over the state of Florida in case what the original forecast was planned to occur actually happened. Very fortunately, it did not. Because of our redundancy, resiliency, and reliability, we had no network-cause PSAP impacts. In fact, you see the four PSAPs that had issues related to Milton. They were 100% power-related, not anything network-related. So, now I'm going to turn it back over to Larry Stidham for him to talk about our footprint. All right. Thanks, Caleb. Let's take a look at our footprint. We have a local pulse with a national impact. As you can see, Indigital has a considerable presence. We're in 544 counties across 21 states, serving more than 60 million citizens and growing. Our NGCS technology provides 911 service to three of the four largest cities in America. Our commitment is simple. Deliver reliability, resilience, and results every day. We have extensive Vyper 7 integration experience. We have 43 deployments across Michigan, Alabama, Florida, South Carolina. We've had Vyper 7 in our NGCS labs, and we've successfully certified it on our network. But we've also successfully completed full interoperability testing with all the major call handling providers. They're tested, proven. They're live on our EziNet today, receiving 911 calls from our core services. That includes Motorola Vesta, Vesta Next, Solicom Guardian, Carbine, Central Square, Zetron, and the others listed. Now, some providers suggest there's a proprietary magic sauce between their EziNet and specific call handling solutions that somehow unlocks special features. This simply isn't true. The reality is interoperability is standards-based. The exclusiveness comes from commercial agreements, not technology. So, in the end, it doesn't matter which call handling provider you might choose in the future. You can be confident that they already work on our network. So, don't give up your flexibility. Good morning, Evaluation Committee. My name is Lynn Hauserman. I'm the CEO of Indigital. And as an officer of the company, I personally attest that the pricing we've submitted in our response includes all of your requirements that you outlined in the NG91 RFP. We are fully committed to your long-term success through a streamlined integration, close implementation with your chosen call handling vendor, best in-class support, and partnership well beyond contract award. We would be proud to serve Broward County. Larry. Thanks, Lynn. So, why Indigital? To wrap up, NGCS is all we do. Our competitors, who you're considering, they're merely system integrators. They bundle others' technology. AT&T does the wires, and then they contract with Entrado for their NGCS. Motorola, as mentioned earlier, utilizes Indigital NGCS as part of their offering. At Indigital, we develop it. We deploy it. We deliver every day. We're the team behind the technology. So, why Indigital? While others integrate, we innovate. Our competitors assemble. We build. Storms happen. Indigital makes sure you stay connected, always ready, always reliable. We're quick with quality. We simply move faster. And that speed means precision. Our EZENET and NGCS expertise, our streamlined, proven approach, turns plans into successful deployments on time, on target. We're vendor neutral. Flexibility matters as much as reliability. With Indigital, your future technology investments will leverage the value of your EZENET and NGCS and enhance it. They don't compete with it. And we have proven resiliency. Networks fail. Ours doesn't. 911 calls keep flowing, powered by multi-route, multi-carrier resilience in Mevo. And, again, dedicated Indigital Florida staff focus solely on your daily success. Attendant, proactive, reliable. We live your mission. That's Indigital on your side. At Indigital, we build a true partnership. We're different than what you might have experienced with other companies. We're nimble, accessible, accountable. We don't quit. We don't point fingers. We don't run and hide behind voicemail or third-party call centers. We stand with you. You know not a single NGCS customer has ever left Indigital? I think that speaks volumes. Zero churn affects trust built through performance. That's Indigital, NGCS. 76% of PSAPs in Florida, 51 of 67 counties have put their trust in Indigital. 544 counties, 21 states, over 60 million citizens. One commitment, your success. Now, as you wrap up your due diligence, if you've determined that Indigital is best suited to partner with you on this critical journey, you have our commitment and our word will not let you down. We come prepared, proven, and ready to serve Broward County. Thank you for your time and consideration. Thank you very much. Thank you, please. Thank you. Thank you very much, Indigital. I will ask now for any questions from the Evaluation Committee members, and please state your name before asking your question. Thank you. Hi, my name is Angela Scott. I just had a question regarding, you had stated that if you needed to expand the number of servers or ports in your data center, that you would do that to support us. I'm just wondering, is there like an established measurable threshold, or, you know, how do you determine when that's needed, and is that included in the price? Yes. So, I was more pointing towards the need to add additional resources within the county in particular. We have existing data centers that are already built and have plenty of capacity to support the Broward County project. But from an engineering perspective, if your, you know, IT staff or consultants or anyone sees benefit for us to add additional capacity within Broward County, it is included in the price. Okay, thanks. And then I saw that your references were mainly smaller implementations than we would be. Do you, and in your presentation, you had said you had some large cities. What were the ones that would be the similar size and scope of our implementation that you've completed successfully? Well, the three or four that we mentioned are the largest cities would have been New York, Chicago, and Houston. And then we've done Hillsborough County in Florida. I would probably be the next largest to you. They're about 1.7 million. Okay, thank you. And then, of course, statewide deployments in Michigan, Alabama, Indiana, Vermont, Rhode Island, New Hampshire. Hi, Danny, Danny Canchon. Just now, during the presentation, you mentioned, you know, that you guys have your own data centers. Everything stays in house. You develop the application. The demonstrations you guys provided previously, we have notes saying that the cybersecurity are all managed through third-party vendors. Can you describe that? Yeah, we install, you know, I can't remember what the name of the, I remember the product name is Overwatch, but it's, you know, basically, you know, packet sniffers, detectors that look for, you know, fingerprints of, you know, possible, you know, changes in traffic patterns or traffic destinations. And so that's meant to be, you know, in addition to our own security, you know, standards, best practices related to our Fortinet architecture, we allow the third party to provide SOC services in rapid response. So they're monitoring not only our traffic and usage of the network, but then we have a third party that's validating the security of the network at all times. And so that's an active, you know, system that's, you know, just verifying and validating that we're following our best security practices. Okay, because it does, I do see where you comment on the, you know, the Fortinet, the IPS, but on top of that, they're also doing their own detection of, you know, DOS, things of that nature. Absolutely. Yep. Yep. We're looking for the, you know, the third party in the event that our systems miss it, or you have a third party system that detects something that our architecture doesn't detect. Just to have as complete a picture of what's coming in and out of the network is, you know, just our best operating practice. And so we do that everywhere we go. Okay. And for the, you know, the core services, the SESINet, you know, I see there was a reference in the VSQ where you didn't mention you did not have a SOC 2. Out of curiosity, what third party attestation for security? Any audits that you guys take over that can certify or discuss or, you know, attest to the security of the system? We do SOC 2. So we have a third party, you know, company that comes in and performs SOC 2 on different installation systems that we provide. And then we also do a SOC 2 audit of our, you know, change control and company operations as well. So we may have misspoke or didn't get it. No problem. Do you know what trust principles your SOC 2 has? I don't think I can accurately answer that question off the fly. Okay. I know it's SOC 2 type 2. Okay. I mean, yeah, because the VSQ, okay. What about the SOC 2? Does it cover the entire solution? Is it for just the data centers at Jacksonville and Winter Haven? Is it, you know, certain aspects of your solution? And on top of that, oh, let me, let me just finish that question. I'll follow up with that. What does the SOC 2 cover? Yeah. So the SOC 2 covers the digital infrastructure. So it'd be the digital data centers and, you know, our NSOC and, you know, other company operations. So, you know, our whole national footprint is from a company perspective. We do have customers that have extended SOC 2 operations or SOC 2 reporting into the PSAP operations. So we have customers like the state of Vermont that actively participates. So then we actively participate in the SOC 2 audit from their perspective in addition to our infrastructure as well. So it's kind of done on a customer-by-customer basis. We have other business partners, other business, the business partners that also do SOC 2 compliance checks on our work and verification. So if that's something of interest to Broward County, we can certainly talk about that. What about the vendor you mentioned? Do you have any, you know, like the MSP or Overwatch, do you have any attestation of their security practices? We do. They are included in our, you know, vendor controls and our SOC 2 audits that we go through for our, you know, best practices, company operations, change control, all those type of things. And so they have to adhere to the same standards that we operate to. So that's, you know, contractual obligation. Thank you. Michael Nairn, first question, going back to your presentation, the implementation of multimedia across T-Mobile, what call handling equipment was used or has been implemented? This is going back to slide 23 in your presentation. Yeah. So in that particular scenario, it was micro automation. But anybody that is, or any solution that is I3V3 compliant has the capability of receiving that. Regarding your footprint across the U.S. where you've rolled out your solution, are there any Viper 7 environments that are comparable to ours that you've rolled out? As far as, as far as what, like size or? Yes, size, size of the environment, population base. I would say no from a population serve perspective. We do have, you know, kind of several, I'll call them hosted Viper 7s that we interface, particularly in the state of Michigan, that serve, I think, in somewhere in the neighborhoods of, you know, kind of 10 individual agencies. I would guess that those 10 agencies combined are, you know, maybe just shy of a million people from a population perspective. But, you know, your Broward County system would be our biggest integration to Viper 7 on a single instance. But I also think it's fair to point out that the complexity of integrating with a call handling solution, in my previous life I was with Motorola and responsible for Vesta, usually isn't around its size being served. It's about the feature and functionality and just the initial integration and doing that certification testing. So, we do not have any concerns about our experience with Viper 7 not being appropriate based on population. Thank you. Are there any components in the architecture diagram that you presented here that is not currently in production? No, everything, yeah, all of the functional elements and systems are in production today and in call flow for all of our counties in Florida. And that extends nationwide outside of Florida. Everything that we've referenced as far as our call handling integrations or the number of populations served or the systems we have in other states are all in production. Based on your staffing and, you know, the size of your organization, can you share with us how many employees are really dedicated to R&D within your organization? One, and two, would you have the ability to offer a dedicated resource here to Broward if there be a need? Yeah. Go ahead, Eric. No, I'll let you go ahead, Lynn. No, I'm, you know, specific to R&D, we're about 160 employees strong. Um, I would say that 20 to 30% of our employees, if you're just talking about research and development on the, like, software engineering side and not as it pertains to ongoing support, um, would be dedicated to that particular function. And, yes, if you need a dedicated resource, um, we're happy to do that. We've done that in other, um, in other deployments. Tertiary. Our entire intent. Oh, sorry. Go ahead. I would just, I would just point out. Our entire intent is to make sure you don't need a dedicated R&D person because, um, we've, we've standardized our implementations. And we've done a tremendous amount of work integrating with all of the other call handling vendors. So there's not, you know, it would be very unusual that someone would be required to implement workarounds to just our normal, um, software implementations. Regarding requirement VN003, uh, specifically related to distinguishing characteristics, uh, that you'd be able to offer to Broward County to offer the MEVO option. Is this option included in your cost proposal? So I think what we, we included a MEVO phone in each location, and then there's a optional, in the optional page that was included in the, in the response, if you wanted to have a MEVO phone at, at each of your primary answering positions. So each PSAP will have it at least one, um, and there may be more. I don't remember off the top of my head what the exact number was, but you will have MEVO in the PSAPs, um, but there is option in the pricing for one-to-one coverage in, in each PSAP. Yeah, you can all card them. Thank you. Uh, referring to requirement SR-GN001, can you share with us the role of your subcontractors when it comes to next-gen core services overall? I, I don't believe, I think that's one of our competitive differentiators is we don't rely on subcontractors. So as a part of your overall solution, there are no subcontractors as a part of the solution? Yeah, no, I, I don't think we've, uh, included anything from the RFP response perspective or, um, um, or, um, you know, from a pricing structure perspective. Um, our intent, um, would be to add, uh, you know, dedicated local resources to, you know, help with, you know, network maintenance and, and, you know, service, uh, connections, um, those type of things. Um, in the past in Florida and in other locations, we have, uh, utilized, um, um, local IT smart hand services to help with installation and, um, and, um, those type of things. But, uh, you know, our intent with Broward County, it was large enough that we felt we would have our own resources added to the project. Thank you. Regarding requirement SR-GN011, this requirement revolves around interconnection to a lab environment that we expect to set up here at Broward County. Is the cost associated with you establishing an interconnection to this environment included in your cost proposal? Yes. Requirement SR-NR005, this is the tertiary backup for connectivity to our environment. Is the cost for either Starlink or FirstNet, whatever option is best, are these, uh, tertiary backup options included in your cost proposal? Yes. Have you just, have you deployed, and I'm referring specifically to requirement SN-S-N-009, have you deployed STIR-Shaken? We have, um, and, um, you know, STIR-Shaken is one of those things that's, um, you know, a little bit, um, you know, kind of up to the PSAP's discretion of what we do with, with the information. Um, you know, right now, um, you know, right now, most, uh, PSAP's that we work with, we pass the information on that the, you know, the call, um, um, within the pit of flow or attestation fields of, of the call that there is, you know, some likelihood that the call is spam or, you know, uh, illegitimate or those type of things. But, uh, you know, typically what we see, um, from that is that we lower the priority of the call instead of, um, you know, blocking the call. So we usually have the PSAP give us, you know, explicit instructions that they want those types of calls blocked, um, because there is false positives, um, in the STIR-Shaken, um, um, possibility there. So, um, we work with the PSAP to, to define how you want those calls delivered and, and queued or routed or, um, those types of things. Thank you. Moving on to the next requirement, SR-DL001. This is around call egress delivery, and there's a requirement in there regarding a transition to IPV6. Have you transitioned to IPV6, or if not, are there plans to? We certainly support IPV6, um, you know, thus far, um, just from a, you know, perspective of where, you know, I3 deployments are as a whole, um, you know, we haven't had the need to, um, move all of the infrastructure to IPV6, but, uh, we have tested. We do have, um, you know, uh, individual deployments that are IPV6, um, but I would say at the moment, we don't foresee the need in this project, at least in the initial turn-up for IPV6. There are two requirements, uh, regarding SLA, SR-SLA-003.B. We had outlined in the requirements a table for service level. Are you committed to the SLA and the service levels that we've outlined in the set of requirements, statement, scope of work that we presented? Uh, yes, we are, um, and that's, um, you know, that's, that's common for us to do so. We, you know, update our, um, SLA, uh, reporting and response requirements, you know, on basically our most, um, um, you know, most first, most fast acting, um, um, that we can, um, you know, possibly, uh, deploy from an operations perspective. But, uh, uh, those were, um, in line with, um, you know, all other state contracts and other large, um, you know, PSAPs from a requirement perspective. And so, um, we would, um, uh, establish those timers as, uh, within our monitoring system and then also in our, um, trouble ticketing system, um, you know, specific to this, um, RFP and, and the contract that, uh, would follow suit with it and, um, you know, make sure those are adhered to. Okay. And then the, the last question regarding the SLA is this is, this is, uh, the requirement SR-SLA008, um, where we outline, should there be a scenario where you're not able to meet the SLA, uh, that you would offer us service credits? Are you committed to the service credits that we've outlined? Yes, we are. And the last question, this is the question regarding the implementation timeframe. It's T-I-M-E-0-0-1 and what's the requirement specifically. And the question, you know, I have here is based on the requirements in the RFP, you're able to commit to completing the implementation for our regional dispatch centers within 12 months from contract execution and our non-regional, uh, dispatch centers within 15 months from contract execution. Yes, we, we believe so. Um, from a, from a project perspective that lines up with, um, you know, our past experience and, you know, getting our other systems deployed in, um, Florida. Um, you know, there is a, a transition element to it, particularly as you go through, you know, carrier conversions. It takes, you know, I always internally, I tell everybody it takes two to tango on, on that. And so, you know, we've got a partner with the carriers to be able to, um, you know, uh, coordinate those moves. But, um, as we talked about in the last presentation, I think the timing for Broward County is, is, is exceptional, uh, because we're doing the, um, phase one, um, transition with carriers to SIP now. And so a lot of our major carriers have, um, in the state have began their transition to IP and SIP integration, which is going to speed up deployments of, um, of projects like this going forward, because a lot of that trunking and, and testing and, and, um, all of those things are already been, uh, performed in production today. And so, um, I think all of that is pointing to a very successful timeline, um, to, um, meet your requirements. Thank you. Thank you. Are there any other questions from the evaluation committee? Any questions from the project manager? No, thank you. Thank you very much. Thank you for your time this morning in digital. Thank you. Thank you. Thank you. Appreciate it very much. Thank you. Bye. The second presenter in digital has now completed a presentation and answered all the questions. I just, before I want to pause, is there a need to, um, have a pause right now or do we continue going EC members? Of course. Yes, yes, yes. Right. I just want to make sure we are good to move forward with the third. And there is a time once we get to the scoring that you'll have time to do what you need to do. Okay. All right. Great. As the team is leaving the meeting with purchasing staff, invite the third presenter, AT&T Enterprises Florida LLC, to join the closed portion of the meeting for their presentation. Thank you. Good morning. AT&T Enterprises. Good morning. Good morning. Thank you for joining. Thank you. As your team members join, please review the meeting attendees in the team's participants panel. Ensure only your team members are, and county staff are in attendance. We are displaying on the screen, the list of county staff in attendance. And can you also let me know who will be presenting on your behalf so I can give them access? Sure. Um, it'll be, uh, Rich Johnston will be controlling the slides anyway. Okay. And then he and Jimmy Lichtenstein will be the primary presenters or speakers. Okay. And can you confirm that all the participants listed on the participants panel belong to your team? Yes, ma'am. Okay. We have, we have a few others that we're trying to, uh, make sure they saw the message to get them to hop on as well. Okay. We have a phone number that came on. Can you verify that's a member of your team? Four, six, nine. It's probably me, Destin. Okay. Mike, it ends in, uh, one, two? Yep. That's me. Yes. We'll, we'll let him stay. Yeah. Okay. Okay. Let's see. Mario, uh, anyone else from your team, uh, planning to hop on? Mario, I think you're on mute if you're talking. Letoia, I think, uh, we could probably proceed. Um, there was, uh, I think one more team member that may be, um, joining here shortly. Uh, looks like there's another that popped in. Uh, Mario, is that you? It is. Good morning. Sorry. And do you know if Eric's planning to, uh, rejoin or should we go ahead and proceed? Well, Toia, I think we can proceed if you guys are ready. Okay. You have five minutes to set up, so you make sure your presentation is displayed. Can you folks see the, uh, the presentation on the screen? Yes, we can. Great. I think we're ready, uh, Dustin, if you think so. Yes. I think we're ready to go, LaToya, if you guys are. Yes, we are. Purchasing agent, please start the 30-minute timer for AT&T Enterprises Florida LLC's presentation. Thank you. You may begin. Hi, folks. Um, this is Rich Johnston. Um, we're going to get, jump right into the call flows as asked for. Uh, it was our goal to present as much detail for the, for the different various call flows as we could in this period of time. Um, I will, if, if we need to circle back in the question and answer period, we're, we'd love to do that and go into more detail. So the first call flow we're going to go through is our sunny day call flow. So this is a normal voice call from a wireless, uh, VoIP wireline customer, either using a transitional method of TDM, IP, or I3. Call is placed by that, uh, end user and goes into the system. Um, the top line is the TDM. Um, so TDM, it can go directly from the carrier through dedicated links into the point of inner, uh, interconnect or through the legacy select router into an aggregation site or LMG. Uh, or the call can come in IP, that IP can come through an in-state POI, uh, or can go directly to one of, uh, one of our core sites. Uh, all carriers will have at least redundant, diverse connectivity. So at least two links into our infrastructure, they can have more. We offer many more points of interconnect, but at least two, uh, coming into our system. Um, that calls and process by one of our core sites, uh, at each core site, we have actual two cores. So we have six core locations with two core, um, uh, sets of equipment in each location, giving us a total of 12 cores. And as you can see on the screen here, we can have option one of TDM two is IP basic through either, uh, in-state POI or direct to our infrastructure or I three, which can also use an in-state POI or direct to our infrastructure. When a call comes into our infrastructure, it's processed by all the core elements. Those core elements are, as we've talked about in our RFP, things like RECRF, ESRP, uh, down below, you can see a location database that's used as a, uh, transitionary solution. If carriers cannot yet send in location information via I three, uh, but also we can retrieve, uh, I three information directly from the carrier using that location by value or location by reference. Once all that call is processed through our system, uh, the GIS location is determined and plotted within our ECRF, that call will then be sent to Broward. Broward currently has, or will, uh, our design has it set up with six total links, which are completely diverse and redundant going into the, uh, multi-node locations that serve Broward. Broward, we additionally have a tertiary route for first net. So, um, that first net route is, uh, typically only used if one of the wired, or all the wired connections are either down or, uh, has a low, um, uh, MOS score or reliability rating. That call again is sent through to the CPE, the CPE receives that call, uh, the additional information if available is sent upon, uh, delivery, initial delivery to the PSAP in the I three protocols. For any additional queries, that query will be sent out by, uh, in an I three format by the CPE that will go back to our core. Our core will redirect that query to either go out external to the carrier to retrieve that information or internal to that location database. If we're in that transitionary spot where we're, um, where we're still managing the data on behalf of the customer, then the, then that information is returned to the PSAP. A little bit more on the functional level of the sunny day call flow, just to kind of give you a better feel for it. Um, some individual elements are portrayed here as the, that the call again comes in either, um, you know, directly into our core IP through an in-state POY IP or through an aggregation site, a TDM aggregation site or LMG. Um, the next step again is either we go back to the carrier to retrieve that location information, right? For I three, they can either deliver the location information at the time of the original sending the voice. Typically all the wireless employee providers right now are doing a location by reference. So we'll go out and pull that information from their systems via I three or down below. If it's, uh, if it's a transitionary carrier, we'll pull it from our location database. We then get that information back. Uh, we plot that location information within our, um, ECRF and determine the PSAP. If that, uh, GIS information that was provided was, was bad. Um, or, um, was not provided, uh, then we do fall back to that IP selected router functionality you see in there. And then we send that call to a PSAP. We're going to go through the text call flow. So for text, um, there just to establish out there, there's two true, uh, TCC providers out there. One being in Trotto, the other being ComTech. And what I mean by true TCC providers is that they actually have interconnectivity to the wireless carriers. There are other, um, uh, third party, I would call them TCC providers, but they just coordinate, um, texts coming in from, from the ComTechs and the, uh, and the Intrato TCC process messages. So AT&T uses Intrato as the, as the primary TCC. So when a wireless, um, text is made, it goes into the TCC. That TCC processes that text, sends it out, um, to the appropriate ESI net vendor. In this case, we're, we're going to say that that is the AT&T ESI net. AT&T ESI net can make various routing decisions, um, based on that text. It can either use the information provided by the TCC, the SIP URI, and send it out to the PSAP, or can do, uh, it has the capability to do routing based off the XY given within the text message. But that is processed, determined, the PSAP is determined, and then the call is sent to the proper PSAP. At that point, as we showed during our demo, uh, Viper on your side is, and it would be integrated. So that would come through on the Viper display, um, real time, again, all that data, location information, text conversations provided over, over the AT&T ESI net. Next one is, we're going to talk about text with media call flow. Um, so same kind of front half of this, that the text and media is sent to the TCC. The TCC then does two things. One is, um, it'll send the text prior, just like the, the, the, uh, prior call flow, but it also then sends the media to the Intrata EDB. That call is then processed just like a text would be to determine the appropriate PSAP. That call would be delivered to the Viper, uh, at Broward. Um, at that point, and, and currently the only integrated solution with Viper right now is the Intrata EDB, um, solution for media. So at that point, when the call comes in, again, the text portion would, would, would look as the text portion does. As you can see up top here, uh, there is an EDB button that EDB button would light up, uh, understanding that there is a, uh, media available, whether that be pictures or video, that when that EDB is initiated from the Viper, um, from Viper application, it goes to the, uh, EDB and retrieves that information and responds with, with the, uh, appropriate, uh, information. The EDB application is then displayed. We'll show things, uh, like the additional location information, any supplemental data, if there is supplemental data, and additional media, if it's available. So pictures or video, as we demonstrated, uh, last month. We're going to go through some of the alternate routing mechanisms. We tried to, they're the ones that were provided to us. We did provide some, uh, variations of that. Uh, so I'll go through those right now. The first one, uh, is, uh, we're going to talk about if there's an interconnection failure for a TDM carrier. So this is a call, again, made by a transitional, what I would call them, is a TDM carrier. That call would come into the AT&T Poi via TDM. And if that link drops, typically, TDM, um, does not retain the call. So it would have to be regenerated. That's a, uh, that's a restriction of TDM solution. So in, in that case, most likely the caller would have to redial 9-1-1 if the link was lost mid-call. So that call would then be redialed into an aggregation site. That aggregation site would do, as we talked about in the sunny day scenario, send it to one of our core sites. Our core sites would process that and then deliver it to the Broward PSAP on either one of the diverse wired links, assuming they were good, uh, and, um, uh, and were up at the appropriate, uh, level. If not, if all of them, uh, went down, then FirstNet again is available. An additional feature functionality of the AT&T ESI Net system is once that call gets into an aggregation site, LNG, if a call is lost at any point beyond that, then the aggregation site does retain that call, does anchor that call. So if there's a TDM failure, interconnection failure between that aggregation site and our core locations, then that call is regenerated, um, from, from the LNG, the caller would not have to redial, uh, it would be regenerated and it would be represented to the CPE. At that point, it would be represented as a separate call, um, because that, that call needs to be restarted, um, from the LNG perspective, but the caller would not have to redial 911. We'll talk about from the same type of scenario, if it was an IP call. So again, we have two scenarios here for IP calls. Either they could use an in-state POY or they can be direct connected. We have a bunch of, uh, carriers that already, our top three, two, the tier three wireless carriers are already connect, interconnected to our core sites now. Uh, so if a call is generated IP through an in-state POY, that call comes into our infrastructure. If that call, if that link were to go down on either side of that, on one side of that in-state POY, then the carrier, in this case, now that we're in the IP world, there's a couple of different alternate routes that we test. And validate with our IP carriers coming into our infrastructure. One is a network reroute. So because that call was originally destined for a core IP address, if one link went down, each in-state POY has connections to all of our core IPs. So because there's still a live connection to that destination IP, then the carrier sending the call would be able to do a network reroute. Send that call back into the infrastructure, the caller wouldn't lose connectivity. The call would flow as normal, uh, and ring into the, the appropriate, uh, ring into Broward. If it did happen to also lose that connection directly to the in-state POY, same is true. The carriers will have multiple connections into the AT&T ESI net infrastructure. All of those physical network connections will have available, uh, will have an available route to all of our cores. So again, in that portion, uh, that scenario, it's a network reroute on the carrier's part. And we'll send that call in back into the infrastructure to one of our core sites, uh, from a direct connect perspective. Again, if it's IP, that, um, that OSP would send the call into the infrastructure. If that link was dropped, that, um, OSP has additional connections into our infrastructure. That is a bit that has availability to all of our cores. So that would be a network reroute on the, on the carrier side would send it into the core site. The core would, sorry, the core would process that and then send it to the appropriate PSAP. Uh, we're going to talk about an individual component failure here. So again, this is one of our AT&T ESI net dual core. So if we're looking at this from, uh, this is a one physical location with two cores. If a call is generated and sent into the BCF, that BCF would then send it to one of our cores for processing. If that core had an issue, the BCF, BCF retains that and we'll send it to the other available location. I'm sorry, the other available core. That core will then process the call as it would using the Atlas ADR to go grab the location information from the carrier. It would then get that location information back, plot that information within the ECRF and route it appropriately to Broward. Since it, since we're truly, uh, fully diverse from an equipment perspective at each location, there would be no interruption and a sub-second fail over there. So we'll talk about, uh, a complete site failure now. Uh, so if we had a, rather than a component failure, if we had a site failure, uh, via TDM, that call would come in TDM, would try one of our core sites, would send it out to the PSAP, as we've been talking about doing all that processing. If that core site, let's say core site three failed here, then the aggregation site in that case would reroute that call to a, a different available core and send that through to the PSAP. If that call had been completed and was up, um, during that core failure, uh, then, then the LNG again would reroute that call. So it wouldn't have, the caller wouldn't need to redial in that case, but it would present as a new call into the CPE because it is using a new core site. So same, same scenario here, but with IP. So assume that this is an IP that directly from the customer, um, into the core infrastructure or through an in-state COI, the call would come in here to our core site, uh, again, be delivered to the PSAP. If that core goes down, again, now we're talking about rather than a network failover, that IP, that destination IP that the, um, call was originally being processed, we're assuming is now no longer available. That core is down. That was processing the call. Now we're talking about an application level failover. So this, the carrier in that case would then re-invite a different IP address on AT&T ESI net side. That call would process and send it into the PSAP. So in that case, um, most likely the caller would not have to redial 9-1-1 because it's an application level failover within the intelligence of the carrier's, uh, network info, or sorry, application infrastructure. So, um, the caller would stay on the line as the, uh, OSP would see that the original call went down, uh, and it would re-invite to a new available IP on the AT&T assignment side. Again, all of these scenarios are tested when we bring our carriers up IP. All right. We'll talk about a network failover now. So there's different, various different network types of fail, failovers. I try to, uh, capture two of them here. So for, for these scenarios, we're going to assume the carrier's coming in IP. Carrier comes in IP to our infrastructure. We process it just like we did on the sunny day scenario. The call is then sent to Broward. If we assume then that that link that was, that was, um, communicating that call went down mid-call, uh, then in that case that the core itself, because all calls once it's through the core are anchored at the core, that core would then reroute over a different available route to the PSAP. That could be any route that is available that has a, uh, high enough MOS score, um, um, um, that is, uh, an available consistent network that we would send that call through. So that's that scenario is if one link fails mid-call, then our core retains that call, we'll resend that call into the infrastructure. Again, this is assuming the CPE is still up. So the IP address that we're sending to is the same. So it would be the same call. There would just be a brief interruption in voice from a call taking perspective with a sub-second failover. Because we, we monitor those networks, um, uh, uh, at a sub-second level. So if we see that go down and that's no longer sending IP or voice traffic, our core will automatically reroute using a network failover to the CPE. Okay. Now we're going to talk about a total network failure. So a call comes into the infrastructure, is sent, um, to the, to the PSAP and, and everything goes down. So all the wired links go down, uh, for whatever reason, the first net is not available. In this case, we take our normal alternate, uh, routing scenario at that case. So we would see that it's done. We would retain the call and then send that call to whatever the alternate route is set up for Broward. That alternate route can be a bunch of different things. It can be on that PSAPs, right? Things that are on that to AT&T ESI net. They can be legacy PSAPs that we have interconnectivity to, or it could be the PSTM. So all those routing decisions and alternate routing scenarios are set up, you know, prior to go live and tested through our, through our process there. One note is again, from a, from a delivery perspective of what's they were delivering it to a different Broward PSAP destination. We do have the capability in our system to, um, use a unique indicator when we send that message to that PSAP. So that PSAP knows that it was an alternate routed, uh, call. Um, so they can treat it separately there. And then a queue is just created within that alternate PSAP queue to, to indicate that that's a, a separate call. Uh, and that it was specifically alternate or default routed from a customer management portal perspective. So these are, this is all the connectivity that we use for when we went over a month ago, our CMP, our standard reports, executive dashboard, the GIS uploads. This is, uh, uh, currently set up through the internet using that application that we demoed. So we have multiple internet, um, providers that go into our sites that, that house that application. So multiple internet providers, multiple sites, normally it would just pass through the internet down one of those internet carriers to that site. If for some reason that site went down, it would be immediately available through the other site or through another internet connection there. If everything went down, um, and, and the Broward needed to, to upload some GIS information or change some alternate routing or get connectivity, uh, or visibility into the system, then that's then a phone call to the AT&T Res Center. The AT&T Res Center has the availability to connect to those cores via different means other than public internet, uh, and that those conversations, either the updates can happen or the information can be, uh, sent to Broward appropriately. All right. All right. I think I'm going to hand this over to Jimmy now to, to walk through the ESI net deployment map. Thanks, Rich. I appreciate it. And of course, as always, we appreciate all your, your expertise here. So if we can bring up the first map, um, I think in the, uh, requirements, there was some requests for county level maps. Um, so we've provided two maps here of county level deployments. Um, this one is everything identified in blue are counties that have AT&T live or PSAPs within that county have AT&T ESI net being live. And then the items that are shaded in black and white are PSAPs that are, or PSAPs or counties that are in progress of being deployed. Um, so as you can see, we cover, you know, a large portion of the U S, um, with our deployments. And in the following map, you'll see our Viper seven and, and Viper upgrades in progress. Um, to Rich, if we can go ahead and move on. Thanks. Thanks. So we'll see here, uh, again, in blue is, uh, PSAPs that are on our ESI net that are on Viper seven. So they are live Viper seven PSAPs on the AT&T ESI net. Um, and then again, the items shaded are PSAPs that are currently in progress. They're in some, uh, state of progress of being upgraded to Viper seven and on our AT&T ESI net. Uh, so, uh, what we wanted to represent here is that our experience and our knowledge with not only Viper seven, but with upgrades is vast. Um, we've done more Viper seven implementations than any other provider. And we have more Viper seven integrations with our ESI net. Uh, additionally, once these upgrades happen, um, you know, as you can see, there's quite a number of PSAPs that are in progress. Um, some there in Florida, Texas and all over the country. Um, so we will have all of those upgraded as well. What we wanted to additionally give you, um, so we have the map here, but we wanted to give you the deployment details. So there's quite a number of pages following here, but as a summary page, um, you'll see here that, um, we have, have identified the number of PSAPs and the population served by non Viper call handling by Viper seven call handling and Viper seven in progress call handling. Call handling. And so this is across the country. Um, as you can see, our ESI net, and we serve a little over 81 million in population, um, uh, across the country. Then we went ahead and additionally broke this down so that you all could see, um, by county what the call handling was. Again, we did non Viper because we didn't want to give you every version of every different call handling platform, but we did give you, uh, the Viper seven implementations there in the middle. And then the Viper seven implementations or the Viper seven upgrade implementations on the right. And this is again, all broken out by county also to include the number of deployments in those counties. So you can see, um, for example, under Viper seven in Connecticut, um, it's the number of deployments when within each of those and the population served. And with that, I think, um, we'll close out the presentation session and be ready for any questions. Thank you very much this morning, this afternoon AT&T for your presentation. Are there any questions from the evaluation committee members? And if so, please state your name before asking the questions. Before moving forward, uh, there seems to be someone in the lobby that I'm not certain is part of your team AT&T. Eric Lindborg. Yes, ma'am. Yes. He's the hearing vice president. Okay. All right. Thank you. Sure. Please proceed with your questions. Thank you. Hello, Danny Canchon. Um, reviewing the, um, the answers here. I see that you had, uh, the ISO 2701 that covers the AT&T global IP and customer, um, products, customer facing. Does that cause, does that cover the, uh, customer portal and the, um, AT&T Snet core? Yeah. Um, so I'll, I'll kind of be the MC here, um, and hand this off to different members of the team to respond to, but, um, I think for that Mark Titus or Jimmy, can you, one of you guys speak to that? Mark, you on mute there. And Mark is either muted or there we go. Okay. Yeah. The answer is yes. It's covered. What is covered? The portal? Yes. Okay. So that ISO 2701 is for the portal and for the, uh, ASINet, uh, core. Correct. Okay. And then, you know, there's comments that you guys have a SOC 2, uh, security. Do you have just a security? Cause then there's a little vague, uh, mention about that we'll get in 30 days. So, I mean, if you can talk about the SOC 2, um, compliance that you guys have. Dustin, you're on mute. Rich. Rich. Dustin. Sorry. Um, yes, I, we are SOC 2 compliant. Uh, we will provide that as, as, uh, you know, the full compliancy and documentation as, as, as part of the delivery. Uh, yep. Okay. Understood. Is that, and is that for the five trust principles just for security? What, what is your, what are you SOC 2 compliant with? All of the above. Yes. Okay. And that covers again, both the portal and the, uh, core services. Correct. Thank you. Hi, Brandon Watson. Um, in the diagram, it showed, um, coming from, they're coming into the MPLS. Are there, is there the two MPLS connections, um, carrier agnostic or are they both on the AT&T? Want me to take that one, Dustin? Uh, sure. Sure. Sure. So, um, they are redundant and diverse. They are both provided by AT&T. Um, what we've seen in the past and we've experienced, um, through history is that the only true way to, to verify true diversity through a system is to have it both circuits, both paths, or in this case, six along with first net is to be provided by the same carrier. Um, the carrier can then verify and plan appropriately that no, never the two shall meet. Never the two paths shall meet. When alternate carriers are you utilized, a lot of those carriers, those third party provider carriers do share infrastructure that they're not always aware of. Um, so for, for this case, it is all AT&T infrastructure, um, and we can guarantee diversity and redundancy because it is on our infrastructure. Dustin, I'm, um, sorry if I overstepped, but. And I'll just add. Sorry, Dustin. I'll just add to that, right? As, as the carrier, and I'm, I'm just gonna enhance what Rich said, right? When, when diverse and redundant circuits are ordered from an individual carrier, they are designed to be completely separate and they are tagged as diverse. So if there's any network grooming or anything that happens, um, as a single carrier, they're aware of all of that. Whereas if you have diverse carrier or different carriers, those carriers don't necessarily know what the other is doing. And if they're doing some grooming on some element, um, that affects something in the upstream world. Um, additionally, right, we not only have everything separate from the carrier on a, on an individual carrier, but there's also different, uh, AVPN cloud infrastructure. So that's also separated. Whereas if you had a, an individual, or if you had two different carriers, everything converges somewhere at some point. And so again, with the experience and knowledge that we've gained over the last 15, 20 years, um, we've definitely learned and identified that to guarantee that diversity and the resiliency necessary for public safety communications, that they should come from an individual carrier where possible. And to, to just add on to both Rich and Jimmy's comments. So we do have serving plans that we could, we can share with you all, um, to show the, the alternate paths that have been designed for the solution. Um, there's some that, that do require some additional fiber, I believe in the ground, um, to make sure we do have alternate paths. Again, so that never those two fibers shall meet, uh, in terms of being in the same conduit or ditch, uh, running back through, um, all the way from the survey wire center to the layer two pops, uh, and then onto our layer three pops. So they're again, full diversity, um, from end to end. Thank you. It's Michael Nairn. Referring back to your presentation, specifically around the architecture diagrams, are all components in the proposed solution, uh, that you presented in production today for 911 call process? Rich, you want to address that? Sure. Uh, yes, they absolutely are. Yep. Every one of them, that was part of our initial turn up, uh, for the solution. Um, and part of what we think the benefit is, is that all those core components have been, uh, integrated, tested and turned up and are live within the environment today. The only new piece parts of the solution will be the individual network out to Broward, uh, and the, the, the equipment that we provide at the, at Broward's locations, but everything else has been fully tested and is in production today. Okay. Okay. And I'll add to that and say that not only is it fully tested and in production today, but has been since 2017. And those, you know, the, the, the population of 81 million that we serve across the CNI, ESI net are, is spread across all of those live elements today. There's nothing new from a core infrastructure that we would need to build for Broward. Okay. Thank you. Referring back to specific requirements in the scope of work, requirement PS002.b, there is a questionnaire regarding your, your SOC and NOC. They, they are, can you just confirm that they are 24 by 7 by 365? Yes, they are. Okay. Moving on to the next requirement, VN 001. This requirement, uh, speaks to just general information about, uh, you as the service provider. If there is a need here in Broward for you to offer a dedicated technician on site for any reason that we may have here, um, would you be able to, uh, fulfill a request to provide a dedicated resource on site for support? Yes, absolutely. Yes. In your overall project approach, this is requirement SR-GN 001, your project approach overall. Are there any subcontractors that you will be using as a part of, uh, provisioning and, and implementing the solution for Broward? Yeah. Michael, let me, um, ask Mark Titus to speak to that, to, um, clarify our relationship with our, our partner here in Toronto. Uh, Mark, if you don't mind. Yeah. So, our, um, our subcontractor with our ESINet service is in Toronto. They've been our, um, application service provider that we've used since the beginning of ESINet. We would use them in the, some of the provisioning aspect of our system, but largely this is all managed by AT&T. And we think of in Toronto as our extended team of, of, you know, through the ESINet deployment, as well as some of the, uh, operational support capabilities. Okay. Thank you. You know, to, to add onto that, um, Michael, you know, any onsite work would be performed by AT&T technicians. So the installation of, uh, the DMARC equipment that we would install at your, your, uh, Viper nodes, those would all be handled by AT&T badged, um, employees, as well as any, you know, onsite maintenance work that was required. Uh, that would all be handled by AT&T as well. Okay. Thank you. Um, moving on down to requirement S R G N double O nine. The requirement revolves around our lab environment here at Broward. We're planning to set up a test environment, a lab, and want to confirm that in your cost proposal, you have accounted for, uh, the work services, whatever's required to interconnect to our test environment. Yeah, Michael, we have, and, uh, we've, we've done that, uh, for a number of other large customers on AT&T ESINet as well, where they do have their production system as well as a lab, um, that that's set up connected to the fully live AT&T ESINet. So it would definitely be in scope of this. Okay. Moving on to the next requirement VN double O five. This is re this requirement related to the distinguishing characteristics or options that you may be able to provide to Broward. And I speak specifically to apex and first net is apex and first net included in your cost proposal for Broward. Yes, they are. They are Mike. So I'm speaking. We're speaking over each other. Yes. Apex continuity. Uh, that option is, is included in there as is the first net wireless backup. Okay. Thank you. There is a requirement. SR dash N R N R double O five. This is related to a tertiary backup for connectivity. You included the services and requirements here, whatever activities are required to fulfill this requirement in your cost proposal. Michael, can you give me that number again? Yeah. This is the wireless connectivity. Dustin SR dash N R double zero five. And it is first. The answer is yes. Sorry. Thank you. Thank you. And then requirement S N zero one two. This is regarding system log retrieval. You referred to a trace tool that you would need to offer. Is this also included in your cost proposal? Yes, it is. And it was, uh, the, the trace tool that we showed during, um, the oral presentations last month. Moving on to the next requirement S N zero one three security information and event manager integration. You included also in your cost proposal to integrate configure and set up whatever interfacing there, there is required for the logging to our Splunk tool internally. Yes. Yes. Requirement SR dash DL zero zero one. Have you transitioned to IPv six? And if not, when, uh, rich, you want to take that? Sure. Um, we've tested it, uh, internally to our systems and we're ready to do that. We haven't had a piece up require that yet. Um, most piece ups are still using IPv four and their CPE is using IPv four, but the appropriate licensing, um, has been, uh, um, purchased and we've tested it within one of our, um, um, lab environments. So we're ready to do it. Uh, we're just ready for a customer to, to make that requirement or have the capability themselves from the CPE perspective to do it. Thank you. Moving on to S R D L double O six. This is related to E IDO. Is this support onboarding and validation included in your cost proposal for E IDO? Yes. Yes. Does your solution provide notification of functional element failures at the functional element level, uh, to Broward County for Broward County calls? Do you have for that notification? Yeah, from, um, from, uh, I, what I would say is a generalized perspective, we build our systems to be, be fully diverse and redundant. So if there is a single failure, there's multiple paths and multiple cores, uh, for that call to still be delivered. If we have an individual functional element failure, that doesn't impact call processing. Typically that that's not notified on, um, and Mark Titus, I might talk to you about our standard SLA is about what that happens. If there was a call processing issue, then absolutely. You're going to be notified, but because of the diversities and redundancies built within our system that if we have an internal network, uh, outage or an internal. Uh, specific, uh, feature or function outage that does not impact call processing, then we don't notify that on that necessarily. Thank you. Um, based on the requirement in the RFP to complete the implementation for our regional PSAPs within 12 months from contract execution and for our non-regional PSAPs within 15 months from contract execution, are you able to meet this requirement, commit to this requirement? Yes, certainly, certainly, certainly are able to do that. And, and we have, you know, a track record, um, where we we've turned up, you know, from contract execution to the first PSAP go live, um, as quickly as four months. Um, not saying that that could necessarily be the case in Broward, but, um, absolutely. Don't see any issue getting you guys, uh, up and live within 12 months. And keep, can I add to that a little bit, Dustin, just to go back to a previous question of whether or not those core elements and the 12 cores are already in production. They are, that is a huge benefit to when, when we, for deployment timeframes, right? We're not bringing up new core elements. We're not testing and turning up feature functionality or capacity. All of them are up and running and in production today. So it's from a, from a deployment perspective, it's getting the OSPs onboarded. If you, if you remember the diagram from the left side and the PSAPs connected to the right side, all those core elements are already established, which is a big long pole. Typically. There are two SLA questions in the RFP. And I just would like to reconfirm the two questions. SR dash SLA 003.B. There were response and, uh, resolution times outlined in this particular requirement. Are you committed to meeting these requirements in terms of the SLA? Yes, sir. Absolutely. Thank you. And then the last question is SR SLA 008 08. Uh, this is regarding the service credits. Should you not meet the SLAs that are outlined in the previous requirement? Would, are you committed to providing the service credits that were outlined in the RFP? Yes, sir. We are fully committed. Those are the only questions I have. Thank you. Thank you. Thank you very much. Are there any other questions from the evaluation committee members? Project manager, do you have any questions? No, thank you. Okay. That will complete our question and ask answer portion for AT&T Enterprises. Thank you very much for your time this afternoon. Thank you. We appreciate it very much. Thank you. The third presenter AT&T Enterprises Florida LLC has now completed a presentation and answered all questions. This concludes the vendor, all vendor presentations. Thank you. Okay. So let's just make it official with a recess and then we can, um, reconvene. So a recess will now be called. How long? 10 minutes. Is that okay with you? A recess will be called for 10 minutes. The time is now 12 38 PM. This meeting is in recess. Thank you. Good afternoon. Good afternoon. Once again, when purchasing staff invite all vendors and members of the public back to the open portion of the meeting, good afternoon, once again, the next order of business is the scoring of vendors. The score sheets have been distributed to the evaluation committee members. The score sheets include the unsigned points for location, which are applied based on the specific criteria stated in the solicitation. The score sheets also include points for price, which was calculated based on the formula identified in the solicitation. When all evaluation committee members have completed and submitted their score sheets, I will recess the meeting to provide time to tabulate the results. Committee members, are there any questions? Seeing none. Seeing none. Committee members may begin scoring. Purchasing will notify me when they have received all scores, score sheets and are ready to tabulate. Thank you. Good afternoon, everyone. Thank you for your patience. All the score sheets have been received. We will now take a recess to tabulate the results. The time is now 1 42 PM. We are in recess. Thank you. Good afternoon. Once again, everyone. Good afternoon. Okay. Hello. Yes. Thank you. I would like to reconvene the meeting. The time is now 2 0 3 PM. Before the results are announced, I would like to thank all of the vendors for your participation in the solicitation process. We appreciate your time and interest in working with Broward County. Thank you once again for your time today and throughout the entire solicitation. Purchasing, please announce the scores and ranking. Madam facilitator. The number one ranked vendor is the number one ranked vendor is Motorola Solutions Connectivity Inc., doing business as Motorola. The number two ranked vendor is AT&T Enterprises LLC, doing business as AT&T Enterprises Florida LLC. And the third ranked vendor is Communications Venture Corp., doing business as in digital. Thank you. The next order of business is acceptance of the scoring and ranking. May I have a motion to accept the evaluation committee's results and recommendation of ranking for approval. All in favor say aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye. Aye website repository, including the closed portions of this meeting. Committee members, is there any other business that needs to be discussed today? Hearing none, again, I would like to thank all of the vendors that responded and their presentations today. Thank you to all of you, the Evaluation Committee members. Thank you for your time today. The final Evaluation Committee meeting is adjourned. The time is now 2.07 p.m. Thank you, everyone. Thank you.