take me. Honourable Prime Minister, Shri Narendra Modi ji, President of France, His Excellency Emmanuel Macron, Chairman Tata Trust, Shri Ratan Tata, Chairman Air India, Shri N. Chandrasekharan, CEO Air India, Shri Campbell Wilson, and CEO Airbus, Mr. Guiyam Furi. Namaskar and greetings of the day. I am honoured to welcome you all today to this virtual event to mark the landmark partnership between Air India and Airbus for supply of 250 aircraft. Given the significance of this event, Honourable Prime Minister of India and His Excellency, the President of France, have kindly consented to grace the occasion. To commence, I would first invite Shri N. Chandrasekharan, Chairman of Air India for his remarks. Honourable Prime Minister, Shri Narendra Modi ji, His Excellency, President Emmanuel Macron, Minister Goyal, Minister Sindhya, CEO of Airbus, Guiyam Furi. I would like to make some brief remarks on behalf of Mr. Tata, myself and Campbell Wilson. It's just about a year since the government handed over Air India to the Tata group. Air India is not yet another project. In a manner of speaking, it is a national project. A lot of emotions are involved in this project. There are huge expectations and one billion people want Air India to be very successful and cheering across the country. And all the Indian diaspora globally are looking forward to Air India's success. It has got such a big history and heritage. We on our part are going through a massive transformation because we are committed to building a world-class airline known for safety, on-time performance, the best of Indian hospitality and modern fleet and a wholesome experience for every passenger, whether they are in the front row or in the last row. That's our commitment. And we have been very busy since we took over. In order to do this, there are many ingredients that are required. While I will not go into each one of them, one of the most important thing is modern fleet, fleet which is efficient and which is modern and which can perform for all routes. And in doing so, we have built a very good relationship with Airbus. The government team have been incredible in the way they have worked with us for almost two years, even before we officially won the contract of Air India. And today I'm happy to say that we have signed a letter of intent to acquire 250 aircrafts, 40 of them on the white body A350 which we will use to fly all ultra long distance across the globe and 210 narrow body. And we have also had significant options to increase the fleet order once we grow. And the relationship with Airbus is particularly important because it is developing to be a very good 360 degree relationship between Tata Group and Airbus. We already are manufacturing or able to manufacture the C295 aircrafts for our defense and we have relationships in technology services, engineering and IT. We are really working on bigger partnerships and one of our ambitions for this country is to bring in the commercial aircraft manufacturing at some point in time in the future. We have teams aligned on both sides and we see this moment as a most significant moment for the Tata Groups at India, Indian aviation and for manufacturing sector in India. I want to thank the Honorable Prime Minister, Government of India and President Macron, you and your government for all the support we continue to receive. I would really like to say that your administration here which is based in India have been extremely proactive and reaching out to us and helping us all the time. So I want to thank both of you and express my gratitude. Thank you sir. I now invite Mr. Guillaume Faury, CEO of Airbus to deliver his remarks. Honorable Prime Minister, Mr. President of the Republic of France, Emmanuel Macron, dear Ministers and dear friends from Tata Sons, dear Ratan, dear Chandra and of course dear Campbell from Air India. Today is a historic moment for India, for Air India and for Airbus and at Airbus we are very proud and grateful that the Tata Group has chosen the A350 and the A320-0 to script Air India's revival. The magnitude of the Air India order, the size of the 250 planes that Chandra just explained, demonstrates the appetite for growth in the Indian aviation industry is the fastest growing in the world. India is indeed on the verge of an international air travel revolution and we are humbled at Airbus that our partnership with the Tata Group will contribute to this new chapter. The time is right for India to turn into an international hub and we believe the Airbus A350 will trigger a change of paradigm in the long-haul travel that matches the aspiration of India and its people. The A350 will turn into the new flagship of India's transcontinental service whereas the A320-0 will remain the undisputed flagship for domestic and regional service. But we do not see India just as a growth market. At Airbus we see India as a strategic industrial and technological hub offering the right mix of competencies and competitiveness which is why we have developed a fully-fledged engineering center in Bengaluru employing a few thousands of people and growing very fast. We are constantly increasing our sourcing and our manufacturing in India. Today every Airbus, be it a commercial aircraft or a helicopter has technologies and parts designed and made in India. So while the Air India aircraft will ultimately be finally assembled in Germany and France, in Europe, many of their components and parts will come from Indian companies and critical technologies will come and we're growing in that dimension from the Airbus Indian Engineering Center in Bengaluru. We're also committed to catalyzing the growth of the local aviation ecosystem with the establishment of a state of the art engineering training, digital and MRO capabilities. Our local footprint is a testament to our commitment to developing the Indian aviation and aerospace industry. We make in India, we design in India, we innovate in India and we train also in India. Airbus has strong affinities to India and is keen to weave our destiny together. Making India is at the heart of the Airbus strategy in India and the C295 program demonstrates Airbus commitment to supporting dear Prime Minister, your vision of an Atmanir Barbarat. With the Tata Group, I'd like to say Airbus has the most trusted and respected partner. We have grown as Chandra explained a very close relationship in the last two years and this is placing the two companies in a very good place to work together and develop India as a leading and sustainable aviation market. Chandra, we believed and we continue to believe in your vision for Air India and for India. So India is well on its way to achieving its ambition in the aerospace and defense sector and Airbus will continue to be a very strong partner in this journey. Thank you very much again for your trust and looking forward to working together now. Thank you, Mr. Fauri. I would now request Honorable Prime Minister to address this special event. Your Excellency, my friend, President Emmanuel Macro, CPU's girl, commerce and industry minister, see Jyotiraditya Sindhya, Minister of Civil Aviation, Sri Ratan Tata, Chairman of Tata Trust, Sri A. N. Chandrasekharan, Chairman Tata Sons, Mr. Capwell Wilson, CEO of Air India, Mr. Geom Fauri, CEO Airbus. First of all, I would like to congratulate and congratulate you on this landmark agreement with Airbus. I would like to thank my friend, President Macro, for joining this event. This important deal, along with the deep ties between India and France, is also showing the successes and achievements of the civil aviation sector. Today, our civil aviation sector is a part of the development of India. To strengthen our civil aviation sector is an important aspect of our national infrastructure strategy. In the last eight years, the number of airports in India has increased from 74 to 147. This means that our regional connectivity scheme is connected to the air connectivity of our country through the air connectivity of our country. This is increasing the social development of our country. In the near future, India is becoming the third largest market sector in the aviation sector. According to many scholars, India will need more than 2,000 patients in the next 15 years. Today's historic engagement will help to fulfill this growing demand. India's make in India, make for the world vision, is opening up many new opportunities in aerospace manufacturing. For greenfield and brownfield airports, 100% FDI has been provided with an automatic roof. Similarly, ground handling services, maintenance, repair and overhaul, means 100% FDI has been provided with an automatic roof. India can become the hub of MROs for the entire region. Today, all the global aviation companies are present in India. I invite them to take full advantage of these opportunities. Friends, the understanding of Air India and Airbus, India, France and the strategic partnership is an important opportunity. A few months ago, in October 2022, I took part in the defense transport aircraft project. The project also includes the participation of Tata and Airbus. I am also happy to know that the biggest MRO facility is being established in India for the service of the French company. Today, the international order and multilateral system, and the international order and multilateral system, is providing the service of the French company. Whether it is the security and service of India and the Pacific, or the security and service of the Pacific, India and France are also providing the service of the French company. I am also happy to know that this year, the international order and multilateral system, will provide more opportunity to work together with India. Once again, I thank all of you. Thank you, sir. I would now request President of France, his excellency Emmanuel Macron, to deliver his remarks. Thank you very much. Thank you, dear Prime Minister, dear Narendra. I am very glad to have the opportunity to see you, even just through this VTC, but after our meeting on the sideline of the G-20 in Bali, and the great discussion we had together. And I want to congratulate you, your ministers present here, our two CEOs, dear Chandra Sekaran and dear Mr. Fori, for this new success. And thank you very much for offering us the opportunity to celebrate this strategic partnership in the aerospace sector. Once again, this achievement shows that Airbus and all its French partners, including Safran, are fully dedicated to develop new areas of cooperation with India, and we've achieved so much with India. I mean, in the wide range of sectors from space to cyber, from defence to culture, from health to energy transition, and now we have the historic opportunity to go much further, given the potential of Indian and the Indian people. I fully concur with you, Mr. Prime Minister, dear Narendra, about all the perspectives we have and about the strengths of our partnership. I will try to add two quick points. The first one is that Airbus is contributing to the outstanding development of India, and the new 250 aircrafts, which will be delivered to Air India, will be one more step in this direction. There is a deep commitment in France to provide the state of the art, the most efficient technologies available to India, and that is part of your Made in God strategy. French government has put all my energy for the last six years to reinvigorate French industry. And beyond aviation, we are building a new ambition in the sectors of nuclear energy, microchips, space, cyber, biotech, to mention a few of them, and definitely France is clearly a place to invest in and a place for engineers, researchers, and this is why we want to build more with India. And more broadly, the end of the pandemic should lead to more exchanges between our two countries, students, scientists, artists, businessmen, women, tourists. All are most welcome to France, and I encourage Indians to come and be part of this French-Indian friendship. And I'm very happy to have this type of contract being signed today, but more and more exchange between us. And I want to mention the organization of the Choose France Summit on the 15th of May, a day dedicated to all the business leaders eager to invest in France. And Dheeshon Ra, I know that how much committed you are, and we are very happy to welcome you several times. The second remark I wanted to add is that among the fights we have to face together, clearly we have a lot of regional and multilateral challenges. You mentioned them, and I think this is particularly important in this very year where India has the presidency of the G20 and I want to do my best to make this presidency a success. The French government and French companies are active to propose solutions in order to accelerate the energy transition to help India to reach the goals recently set in terms of the carbon neutrality. And we showed that our two countries can make a difference, especially I do remember Dheeshon Ra when together we launched the International Solar Alliance five years ago in India. We will also work together on biodiversity and I press your policy on plastic use and we will organize with Costa Rica the next conference on oceans in 2024-2025 and in less than one month the one for summit will be held in Libreville Gabon. Based on this common ambition we are working together for the success of India's G20 presidency in a difficult context with the Russian aggression against Ukraine and India under your leadership. Clearly can be the one to mobilize the whole world and help us to address the tremendous issues we have in front of us. In this perspective I want to thank you for co-organizing with us this new South-North partnership. A session will be held in Paris in June 2022-2023 and clearly will contribute to your G20 presidency and is for us very important. Before yielding the floor, Dheeshon Ra, I would like to thank you for organizing this event and I want to thank our companies for the great partnership and the reciprocal commitment and trust. But I want to tell everybody that for me this very important contract and this achievement today is one of the milestones of the in-depth strategic and friendly partnership we have between India and France and between both of us, Mr Prime Minister. Thank you very much. Thank you, Excellency. Before we close I take this opportunity to convey gratitude to Honourable Prime Minister and His Excellency President Macron, Honourable Ministers and leaders of the two companies for gracing this occasion with their presence. Wish you all a present evening. Namaskar.


Now, Global Peace Foundation, GPF, in collaboration with Justice Development and Peace Charities, JDPC, Cardinal Archdiocese, has conducted a one-day roundtable discussion, meeting with the stakeholders in the state to look for a lasting solution to some of the lingering issues of segregation, division among people living in a Bacbalo-Kugomen community in the state. Country coordinator Reverend Joseph Hayab says the meeting is aimed at fostering unity and dispelling fears among Christians and Muslims, as well as sustained peace in Agbakpa community and the state in particular. Hayab stated that the major courses of division and disunity in Nigeria is hunger, poverty, literacy and ignorance, stressing that they need to be addressed. When people live and allow themselves to be instigated by others, division will come. When people live and also have been exploited on political reasons, division will come. But you know the famous or the most serious problem of Nigeria is hunger is helping to expand the division. Poverty is helping to expand the division and literacy is also helping to expand the division because when people are ignorant, ignorant of faith, ignorant of how life supposed to be, someone will just manipulate their ignorance and tell them what is not true about the other person and they start looking at the other person as an enemy. The coordinator of justice development and peace characters JDPC, Reverend Father Joshua Achir, advocated stronger relationship between Christians and Muslims in order to live harmoniously. Peace is key to so many developments, in fact without peace there cannot be development anywhere. And so looking at the local community, you discover that in time past they have lived as brothers and sisters. Things have gone so well that the question of religion or tribe or race, you know, did not even arise. They saw themselves more as a family, as a community and but with time all of these things changed. The Northern Coordinator of Global Peace Foundation, Halliru Malaya says Nigeria is experienced in trying times and residents have to be their brothers' keepers to maintain and promote peace irrespective of their cultural background and religion. The insurgents and the bandits killed people without putting into consideration their identities.  The historic Abba Pak local community used to be relatively peaceful but reverse has been the case in recent time. This informed the need for the meeting.


The Centre for Human Rights and Social Economic Justice has asked the Economic and Financial Crimes Commission to speed up investigation of its petition requesting approval of the immediate past Minister of State for Petroleum Chief Timépre Silver. The group, in a petition to the Commission on 10 July, demanded that Silver be propped for alleged corruption while in office. Addressing newsmen in Friday Lakers, the converter of the group, Mr Diklan Iekare, disclosed that the petition, which contained several reports of allegations of corruption, including contract inflation and abuse of office amongst orders against Silver. We wish to inform Nigerians that there are allegations of misappropriation of forms, kickbacks and professional treatment of certain companies within the petroleum industry, including illegal takeover and reallocation of oil blocks. These allegations strike at the heart of our nation's economy. We as patriotic Nigerians demand from the Economic and Financial Crimes Commission, ELCC, a comprehensive and independent investigation into these allegations. Our nation's commitment to transparency and accountability requires that no one is above the law, regardless of position or influence. Abuse of offices should not be encouraged and corruption in all facets should be condemned. That is why we are not calling on the ELCC to do the natural and conventional and immediate investigation into this petition written to them, because justice should be served appropriately. Thank you.


Welcome everyone. My name is Pranava Dury. I'm an entrepreneur in residence at Greylock Partners. We're an early-stage venture capital firm located in the Bay area. In the past I've worked as a founding engineer in multiple infrastructure unicorn startups and most recently I was over at AWS where I led a brand new service to over $200 million in run rate. Today I wanted to share with you where we see service meshes and where I'm personally excited about the challenges and where they're going to be headed. So let's get started. Initially I'll talk a little bit about service meshes, why we have them, the motivation behind them, and the current state of service meshes and then I'll spend a little bit of time going over where I see them going next and where I'm personally excited about. So to understand why service meshes are needed we really have to start by looking at why DevOps is needed and why organizations practice DevOps. Modern DevOps is practiced for three main reasons or three main objectives. Agility, stability, and accountability slash ownership. Agility so that teams can move fast and can deploy code quickly and react to bugs or incidents quickly and iterate on what's deployed. Stability so that when they're moving quickly they have the mechanisms in place to ensure that what they're releasing passes a series of tests and whatever other qualifications are needed to ensure a quality release. And then accountability and ownership so that for a given set of functionalities or a service there is an owner that is servicing that bit of code and someone that is in charge of determining how that will change over time. One implementation of these three objectives is the microservice pattern that most organizations deploy today. Now when we talk about microservices we really have to talk about complexity especially when it comes to communication. As an example, Netflix as of this presentation has over 1,000 microservices. Now each microservice has to talk to other microservices and there will be dependencies across microservices. When you have a thousand plus microservices these dependencies can grow immensely complex and individually being aware of each dependency and how communication is happening between services explicitly becomes intractable at a certain point in time. Additionally when you have a microservice architecture some services will inherently be dealing with more sensitive data than others. As a result you might want to rope off certain services or dictate that certain services can only be accessed by other services that are privy to the data and API that those services will expose. Next we always have to assume that a service and the network can be compromised. So these are really the complexities that give rise to the way service measures have evolved to today. Namely, let's start with the communication goals. The first goal would be observability which is for the traffic that you have going on in your network you want to be able to monitor it, you want to be able to log it and logs are a great indicator and observability in general is an indicator of service help which is do I have a service that is repeatedly failing requests. Next we have security. As a goal you would like that all communication between two services or any combination of services is encrypted so that in the event that your network is compromised the communication still can be deciphered. In addition to the communication itself being encrypted you also want to ensure that a service is who the service attests it is as being so attestation and authentication the idea that a service is in fact what is reporting itself to be. Finally there's a notion of control the idea that you should be able to set policies for how your traffic behaves in your network this can be in the form of rate limiting it can be in the form of defining circuit breakers it can be in the form of authorization and ACL saying that only certain services can talk to other services so that's the control aspect of the communication goal. Now if we talk about an implementation of these goals that we've just outlined it gives rise to the service meshes that we have today and so what is a service mesh then? It's an architecture that enables the previous goals for container-based environments right and the way service meshes have been built so far is they don't require businesses change the actual underlying business logic instead they rely on proxies that sit in between business logic and the other services that they're attempting to communicate with and the proxies are where policies are implemented and enforced so let's talk a little bit more about that let's first start with a mesh architecture modern meshes are broken into two planes if you will there's the control plane and then there's the data slash proxy plane and so the control plane is where administrators and organizations will define policies again policies can be for example rate limiting they can be circuit breaking policies they can be policies around which services allowed to talk to each other services and what endpoints it's allowed to it's allowed to talk to so the control plane is really where these policies are created and the control plane will take those user defined policies and translate them into appropriate configurations for the proxies in the data plane and so the control plane is responsible for keeping all the moving parts of the data plane in sync with the user provided configurations and then I've defined data plane already in talking about a control plane but the data slash proxy plane is where policies are enforced a quick dive into the different types of meshes that we're seeing right now so there's two big patterns that we're seeing now there's the sidecar proxy which is by far the most dominant strategy that's or the type that we're seeing and then there's the node proxy so in a sidecar proxy a proxy sits alongside each service instance so in kubernetes parlance you have a pod which is which will contain an instance of your business logic and in the sidecar proxy pattern a sidecar proxy a proxy will be sitting alongside each copy of your service instance and whenever that service instance attempts to talk to the network it'll go through the proxy and all the policy enforcement that is set in the control plane gets enforced and enacted by that proxy that's sitting alongside the service instance if you have to use a tourist analogy this is akin to every tourist having their own personal translator another type of mesh that we see is a node proxy and this is where instead of the proxy sitting alongside every service instance it actually sits at the node level so multiple instances can be running at the node level and they'll all make use of that single proxy running at the node level to look at the tourist analogy again this is akin to having one translator per group of tourists and so there are some advantages to the node proxy approach one of them being if you want to upgrade the proxy that you're using for your service mesh in a sidecar proxy model every single existing pod needs to be rotated with the new version of the proxy and so there is some impact to your business objectives that you're running versus in a node proxy you still have to swap them out but the amount of instances impacted is reduced next i want to talk about the service mesh interface and why it's so important so the service mesh interface is a standard interface for container service meshes this is important because there's so many different implementations of service meshes out there and one of the core issues that'll come up with any organization that is trying to adopt the service meshes which one to use everyone has their benefits and they have their downsides as well not having lock-in to a single mesh is actually very useful for reducing an organization's friction to adopting a service mesh because they know that if they use the constructs as defined on the SMI spec they can rotate to another service mesh with with a little effort and so the service mesh interface standardizes some common mesh use cases for example traffic targets route groups and traffic metrics so now that we've taken a look at the types of service meshes the mesh architecture and where we're at right now let's take a look at what i'm excited about so spiffy is a standard for attestation of identity that is for a given service how do you how does a service prove that it is in fact who it says it is now previously spiffy was not a standard that was adopted by all meshes the good news is most meshes now have a partial implementation of spiffy i look forward to this being the standard de facto adoption for identity and meshes going forward smart nicks are another area of interest smart nicks are nicks that actually have dpu's that can be programmed now smart nicks are another area that are very exciting especially when it comes to high performance networking in containerized environments you see this with the adoption of bare metal kubernetes now what's interesting about smart nicks is you can start doing offloading compute intensive properties like crypto and you can offload them through the nicks themselves this paves the way towards high performance networking in kubernetes where you can really start unlocking speeds beyond 40 gbps next hybrid cloud is here to stay and the service mesh story really wouldn't be complete without having a comprehensive play that also allows organizations to extend two on-prem deployments and what we see is plays like kuma that are being designed both for kubernetes and container native environments but also to be working with traditional vms on-prem going off of the hybrid example within an organization different teams might have different requirements and so they might be using different service meshes as a result when you have cross-functional teams that need to work together it's good to have a unified mesh management system that will allow certain policies to be enforced org-wide and also allow you to configure these meshes or in org-wide fashion so we see mesh hub as an example someone paving the way towards that and i definitely am excited to see how mesh hub will evolve in that sense next meshes rely on proxies so if you want a certain capability to be built out in istio for example at the at the data plane level if the mesh doesn't support it istio can't do it and so enhancing proxies in terms enhances the capabilities of meshes so web assembly is a really exciting development from that standpoint that allows third-party developers to add filters presently for envoy to enhance its capabilities and so when you start allowing the proxies to take on new capabilities you can start adding functionality that is traditionally reserved for other areas of the network stack i see web assembly as a very powerful enabler of future capabilities for service meshes what i would also like to see is an open web assembly standard that is adopted across service meshes so not just envoy but for example linker d as a matter of fact linker d has mentioned that they would like to they're considering the possibility of interopping with the web assembly standard that's been established for envoy and this would lead to really cool use cases where in addition in the same way that what smi did for policies there could be an equivalent implementation for standard web assembly that multiple meshes can use next i think there's also a lot of opportunity when it comes to having existing security offerings vend web assembly extensions for service meshes an example of this could be as an organization you might be using a dlp suite the dlp suite could bend a web assembly extension that you could be incorporating into your service mesh so in this way i think the future is very bright for service meshes in terms of being composable with other services that you use in your organization so these are what i'm looking forward to and if you have any questions or any suggestions of what you would like to see i would love to hear from you so please feel free to reach out i'm at the nava on twitter looking forward to it and thank you for your time today


Welcome to All Hands Update. Here's what's happening around your Navy. Ships and aircraft participating in Valiant Shield 2016 sank the decommissioned USS Rents off the coast of Guam. The Sink X marks the first time Strike Fighter Squadron 115 successfully fired a J-Soul C-1 guided glide munition. Valiant Shield 2016 is a biannual U.S. only field training exercise but they focus on integration of joint training among U.S. forces in relation to current operational plans. September 15th marks the beginning of Hispanic Heritage Month with this year's theme Embracing and Riching in Enabling America. The 2016 theme invites us to reflect on Hispanic American's vitality and meaningful legacy in our nation's cultural framework. Today marks a milestone in many sailors' careers as roughly 2,000 newly selected Chief Petty Officers are penned around the world. Congratulations Chiefs! You can read more about what's happening around your Navy at Navy.mil.


Hello everyone. My name is Marc Hervieux. I'm IOT marketing manager in ST Microelectronics America. I'm very happy to introduce the webinar of today, getting it right the first time, Accelerate Law Implementation. This ST webinar is also sponsored by Mashinchu, a Comcast company, and Murata. In the IOT world, connectivity is critical, and LP1 standing for low-power wide-access network, is widely present. LoRa is an LP1 technology that is very all suited to support IOT use cases, especially for things that are battery-operated and need to send small amount of data on regular basis and staying in sleep mode in between. We are proposing today a webinar exposing the ST LoRa desk kit running on Mashinchu network and using Murata modules, showing how simple it is to use and create new differentiated products using that technology. The webinar agenda will consist first of a short introduction of ST Mashinchu and Murata with an emphasis on IOT. Then we will go in more detail by providing another view of the ST LoRa desk kits used for prototyping, how to get started using it, how to run the Mashinchu IOT platform called MQ Central, and then explain the go-to market strategy using the Murata modules. We will then present how to expand the ST LoRa desk kit into an asset tracker. ST has all the building blocks for IOT. These blocks allow to move a thing into a small thing. If we take a very simple example, such as a barbecue, it is a matter of sensing the environmental, the motion, controlling the farm, being able to process, manage the battery, and mainly being able to communicate all of this basic information back to the cloud. These basic blocks are the critical pieces that went but together create the IOT solutions. For this, I think a career-run ecosystem is critical, so Embed Developer can easily go to market with new innovative products. ST is a semiconductor company embracing the IOT movement. Our portfolio includes all the key building blocks, especially the processing with STM32 microcontroller, security, sensor, connectivity, motor control, power and energy management, and many others. Looking at few market data, we shipped more than three billions microcontroller STM32 and our number two worldwide. We shipped also more than 14 billion MAMS sensors, and we are number one in motion sensors, number two in pressure sensors. ST is overall number three in semiconductor for industrial segment. To reach such market level, ST has built an IOT strategy based on development kit with polished and documented solutions distributed to the mass market. This enables to help the embedded developers by accelerating their development and gaining in time to market. For that, we built a comprehensive IOT ecosystem with a wide variety of hardware development kit, a large amount of software and tools, and an ST community for support, and a partner program that extends ST capability to wider IOT use case. ST IOT ecosystem is mainly articulated around the STM32 microcontroller for the processing. STM32 includes a very large family with almost 1,000 parts, all based of the ARM Cortex M series. We have a 10 years longevity commitment and have more than 40,000 customers using it today. The ST Laura Deskit is using the STM32 L0. It is an ultra low power microcontroller that can get down to 0.3 microamp in standby mode, allowing a very long battery life with a very fast wake up time. Also, ST has a very large portfolio of MAMS sensors covering motion, environmental, interactivity, micro actuators, and even optical, allowing a very wide range of use cases. MAMS stands for Micro Electromechanical System. So MAMS manufacturing evolved from the process technology in semiconductor device revolution. Because of this, they are very small form factor and are ultra low power. In the ST Laura Deskit, we are exposing the environmental MAMS, such as temperature, humidity, pressure, and the motion MAMS, such as 3D axis, accelerometer, gyroscope, and magnometer. ST is also working on many connectivity solutions, especially local connectivity such as NFC, Bluetooth DLE, that can complement nicely the LP1 sub-registered technology, such as Laura and Sixhawks. ST is also involved in other wireless technologies, such as Wi-Fi, cellular LT, KTM, and in the IoT, but mainly through partnerships. As a summary, ST IoT ecosystem is very broad, allowing to address a very wide set of use cases across the IoT verticals. Same smart home, smart city, and smart industry. We offer to embed developers a very large variety of IoT hardware platform that are modular or form factor oriented. A large set of software packages, including the four major cloud supports. The ST Laura Deskit presented today use ST board and has been initiated using one of these software packages. Hello, everyone. My name is Maggie Bozak. I'm the technical product manager at MachineQ, and I'd like to take this opportunity to introduce you to our company and platform. MachineQ is a Comcast company focused on IoT in the global enterprise B2B market. We deliver a best in class IoT management platform that enables your company to manage and scale your own dedicated IoT networks with any Laura-based device or application. We offer fully integrated and secure Laura gateways for nearly any indoor or outdoor use case, as well as SAS-based enterprise-grade management software built to help you manage thousands of gateways and millions of devices. Let's talk about the technology in more detail. MachineQ offers an end-to-end platform that delivers highly scalable and secure dedicated Laura wireless connectivity for your business. As Mark touched on earlier, Laura technology has revolutionized IoT by enabling data communication over a long range while using very little power. Our comprehensive solution starts with the hardware. Our gateways are engineered by in-house Laura experts and have certified custom firmware for each gateway model ensuring optimal connectivity. We offer best-in-class indoor and outdoor gateways that are configurable with Ethernet, Wi-Fi, or 4G LTE backhaul options, and even arrive pre-provisioned to the MachineQ platform and activated to a simple QR scan on our mobile app. Moving on to our software and infrastructure, the MachineQ platform is built and supported by an engineering team with decades of experience building the largest ISP network in the world. It is designed for millions of units of scale and is hosted in geo-redundant data centers for high availability and minimum latency. It includes well-documented APIs to simplify interaction with your cloud application, whether it's in a public cloud like Azure or AWS or hosted privately. MachineQ Central is the centerpiece and front end of our MachineQ core architecture and is designed to provide a seamless global infrastructure anywhere. This is our cloud-based, fully integrated gateway and device management software platform and is built for enterprise-grade scalability. MachineQ Central enables users to provision devices, manage gateways on the network, understand the connectivity health of those gateways and devices, manage users, and set custom notifications. We'll be using MachineQ Central in detail during our demo later in the webinar. That's it for me for now. I'll be back with a demo later, like I said, but if you need more detail on our products, you can simply email us at info at machineq.com. Who is Murata? Who would look at Murata? It's product overview and connectivity solutions in detail. First of all, I would like to thank everyone for attending this webinar. I also want to thank ST and MachineQ for allowing Murata to participate in this webinar. To start with, a quick introduction to Murata would be covered. Murata involvement in IoT will be explained. Later on, Murata Laura Marjo will be covered in detail. As shown in the slide, Murata is an international corporation with worldwide headquarters based in Japan, with many subsidiaries all over the world. As of today, Murata revenue is approximately more than 13.7 billion US dollars. Murata has been known in the electronic industry as a passive component supplier, as many customers use capacitors and inductors from Murata. But as you can see now, Murata products has expanded to many of the component types, as shown, including wireless modules, which will be the focus of discussion today. Murata connectivity products has a focus on the market segments shown in this slide, including IoT, which we believe has a huge growth potential. And to meet the future demand in IoT and in recognition of the different product costs required for IoT market, Murata has modules that support connectivity technology, such as Bluetooth, Bluetooth Low Energy, or WI-FI, along with modules for LTE, Cat M1, NV IoT, and Laura. Murata's wireless connectivity products serve various markets and can be classified into four categories, as shown here. The first three category are modules that address short-range wireless connectivity. These are Wi-Fi, Wi-Fi plus Bluetooth combo, or Bluetooth BLE module solutions. A complete platform can be broken down into either a Linux or Android operating system-based solutions, or a non-operating system or TOS-type operating system-based solutions. Category one, module solutions are available for a microprocessor-based platform, such as IMX6 SoloX that runs Linux operating system. These solutions offer a high-throughput performance for applications such as video camcorder or digital still camera. The next category includes module solutions that can attach to a microcontroller, such as ARM Cortex-M4. These module solutions can cover many of the IoT applications that require a low-throughput performance, such as smart thermostat, as an example. For customers who want cloud-enabled solutions, Murata has modules with electric amp or ALA agent loaded into the module for ease of design. Lastly, long-range IoT connectivity applications, which is the focus of this webinar, is addressed by Murata with the LoRa modules. In addition to LoRa modules are subgeekerhurst proprietary protocol-based module solutions, like E&T modules are available from Murata. Finally, for customers who have applications requiring license-span solutions, Murata has cat-in-one and MBIT modules for this market. More information is available on wireless.murata.com, so please take a look at your convenience. Without waiting more, I propose now to look into the details of the ST-LoRa desk kit. It is behaving like a real device on the LoRa network. It is able to sense the environment holes and motion using ST-MAMS to process using the ST-M32L0 and communicate to LoRa network. It is an open hardware allowing you to add your own differentiation for wide-use cases. At system level, it communicates to the first machine-Q gateway that is in range. Once the device has joined the LoRa network, we are able to fully monitor the device on the cloud using the machine-Q MQ central tool where the device has been previously provisioned. The web link here provides you with a direct access to the guide and material that will go over today. Let's look now at what is composing the desk kit. First of all, we have the baseboard called BL072Z-L011 published on the ST.com. It is a host where all the embedded code is running. The board includes a Murata module that includes an ST-M32L0 and the Sentec radio FX1276. The ST-M32L0 has 20 k-byte RAM, 192 k-byte flash, and 6 k-byte E-Prom. The board also includes the L-STL link that allows to power up the board but mainly to debug the code instead by step. Finally, it includes another Arduino V3 connector that is critical for extensibility. Using that connector, you can either add other Arduino boards from ST or the industry offering new features or even blue wire your own added value. Then the desk kit is completed with an ST Arduino sensor shield connected using the Arduino connector. That board brings a wide range of motion sensors such as 3D accelerometer, 3D gyroscope, 3D magnometer, and environmental sensors such as temperature, humidity, pressure. Note that a DL24 connector allows to extend servers or sensors to the once new produced by ST. You can find a full list on www.ST.com and search for STEval-MKSTAR and find more than 50 active DL4 compatible extensions. Please also note that the Arduino connector is extended allowing additional shields to be connected on top of it. Regarding the firmware side, the solution is available on machine Q landing page for the ST LORADF kit, where you will be able to find a binary but also the full source code for free. The project has been built using the IDE Kyle from ARM. This is a professional grade IDE that is free for STM32L0. Please see the link below to get access to a free unlimited license. For those who are already familiar with the ST LORADF stack published on ST.com called iCube Aller 1, it is reusing it but we are adding more features. We are adding the support of the sensor driver and its capability to transmit the raw data to the cloud. We are also adding a menu to be able to manage the machine to credentials so we have to can avoid to have to recompile for any new devices and the management of the transmission duty cycle. This menu will be usable when the desk kit is connected to a computer running a serial terminal. As a summary, I invite you to go to the machine Q landing page for the ST LORADF kit where you'll be able to buy the hardware, have access to the software in binary and source code. Please note that you can also acquire the hardware boards on ST.com where all the authorized distribution channels are listed. Let's now dive into our demo using the ST LORADF kit and the machine Q platform. The first thing we'd like to do is welcome you to the machine Q platform and we'll do that by creating an account on the machine Q store at HTTPS colon double slash store.machineQ.com which will allow you to purchase the starter kit as well as log into MQ central and leverage all the tools and resources available from machine Q. Once logged into the store, navigate to the dev kit section where you'll find a special offer for our $199 starter kit that includes an MQ gateway as well as an ST LORADF kit. This offer also includes three month access to our platform after which you'll have the opportunity to continue working with machine Q on a monthly C basis that includes access to the machine Q platform with no restrictions on data or device counts. When your dev kit arrives, head to the machine Q.com slash ST LORADF kit site where you'll find detailed instructions and sample code to get you started. We'll go through that process in detail now. All right, let's cover what you need to get started. All of the hardware of course, the gateway and the two ST boards that have arrived in your box, your machine Q account that you created on the store earlier, the dev UI, app UI and app key which are printed on a card inside your package and you also need to download the Q IDE as well as a terminal emulator such as Terra Term, MiniCom or Screen, links for which you'll find on this page. Today we'll be using Terra Term. Now that we have everything we need, we'll log into MQ Central to activate the gateway. Though I'll show you how to do this here, you can also download the machine Q mobile app as I noted earlier in the introduction for your Android or iOS device and simply scan the QR code on the gateway. That will result in the same activation. To activate the MQ Central, first click on the gateways tab on the left hand nav. If you have a new account, your gateway list will be empty and you can click at a gateway either in the center of the page or the top right as I'm showing here and the details pop up will appear. Let's fill in the details. First, give your gateway a friendly name that's easily identifiable. Next, choose the model which is likely the conduit AP. The MAC address and node ID will be printed on the back of that gateway. The antenna gain can be left to zero because we'll be using the internal antenna of that gateway and not adding an external antenna to it. Your location type will be indoor. You can leave GPS enabled and cellular enabled unclicked as those features are likely not included. Please also enter the latitude and longitude of the location where you're installing this gateway as well as the height above the ground in meters. Next, let's provision your desk kit on the MQ platform so that it can successfully join the network when we have it up and running. First, click the device tab on the left hand nav. Once on the devices page, you'll again click add a device as your list will be empty here as well and you'll be presented with this pop-up where we'll enter the pertinent information. In the first field, give your device a name you can easily recognize and remember like we did with the gateway. Next, enter the DEV UI, APP UI, and APP key that were provided on a printed card in your package. From the drop-down menus, choose the service and device profiles shown here as well as the decoder type. Note that for clarity, I vaginal call out of the expanded device profile name as it didn't quite fit on my page. You can leave everything else as is as we'll discuss output profiles a bit later. Now that your gateway is up and running and your DEV kit is provisioned, let's set it up. First, make sure to plug your mini USB cable in the correct port on the board. You'll want to look for the SQ link label and then plug the other end of the USB into your computer. Second, from the instructions page we looked at earlier on machinekey.com, download the binary file which will allow you to program the board with its unique DEV UI, APP UI, and APP key that we used in the provisioning process. This will allow your device to start sending sensor data to the machine key platform. Once downloaded, unzip the file, then go to your file explorer and find devices and drives on PC or locations in Mac and the board will appear as a drive there. Drag and drop the .bin file onto your board. As it's uploading, the board's LED will flash rapidly. While that's happening, let's set up your terminal window. Launch your chosen terminal application and choose the port in which your board is connected. For me, I'm using terra term so this is what it looks like. I go to the setup menu and choose serial port and change the speed to that in figure one. Then I select setup and terminal and change the settings to those in figure two. Going back to the board, now press the black reset button which would prompt you to enter the credentials that we discussed, the DEV UI, APP UI, and APP key. Now that the board has its credentials, it will attempt to join the machine key network and once successful, we'll start sending sensor data. See the far right graphic for further information. For those of you who would like to dive deeper into the development process, we've provided the source code for the sample project that's now running on your board. That download is also available on the same instruction page that we looked at earlier. After you've downloaded and installed the keel IDE, click project in the top nav then open project. You'll need to navigate to your downloaded and unzipped project file. There you'll want to follow the file tree that I've highlighted in the box marked one above. Note that it's a fairly long file tree. Once the project is open, you'll want to build that project which will allow the necessary files to be generated and included in your entire project. That button is labeled number two. Before we go further, I'd like to point out that the credentials you entered on the terminal screen are in a file called commissioning.h which you can find via the keel search feature which is only visible after you've built the project as highlighted commissioning.h with number three. Going further into the project, let's take a quick look at the main .c file. In my case, my main file has a slightly longer name but in any case you'll find it in the file tree on the left under project slash and note. Scrolling through the file, you'll first see the commissioning procedure you went through on the terminal followed by the Laura drawing procedure. The screenshot I've taken here starts with that Laura drawing procedure. Next, you'll start seeing all the sensor readings followed by a Laura send command to get the data up to the cloud. If those packets were sent up as confirmed data, the board will wait for an act from the network server. We'll take a look at this interaction between the device and the mq platform on the next slide. Switching back to mq central, let's take a look and see all the traffic between our dev kit and the mq platform. Click the devices tab where you should see the dev kit we just provisioned and click the far right arrow in the device line which will take you to the device entity page. On the left, you'll see an example device entity page where you'll find a lot of useful information. At the top, you'll see the general device info set during the provisioning process. In the middle, there's device health information including RSI, SNR and packet error rate shown as averages on the left and graphed over time on the right. At the bottom, you'll see the log stream for this device. On the right side of the slide, I've taken some screenshots of the details of an example exchange between the device and platform as seen by the platform. First, at the top right, you'll see the device's join request followed next by the join accept sent by the network server. Next, you see the device sending confirmed data upstream and finally the downstream acknowledgement of the received packet. Lastly, you can view a time series graph of your sensor data by clicking sensor data tab next to the device log stream tab in the device entity page. Finally, I'd like to quickly cover output profiles found under the integrations tab on the left. I quickly mentioned these during the introduction. These output profiles allow you to pump data out to any cloud application you choose using MQTT or REST profiles. All you need to do is provide the proper host and credentials. Additionally, MachineQ has implemented native connections directly to Azure and AWS to make connecting to those services much easier. Complete instructions on implementing those profiles can be found at http://docs.machineq.net And with that, our demo is complete. If you'd like further information, please reach out to us at info at machineq.com. We will now explain Verano modules in more detail, including module design guidelines to help you jumpstart in developing your product. Verano Lora module that is within the ST Discovery Kit offers a quick time to market ease of implementation and a small form factor sensor product design capability. Further, Verano module offers flexibility in use and this will be explained with key specification highlights as well as different models being available with same hardware. First, let me explain the two models that are available, the MQ100 or MQ200. The key difference is that MQ100 can be used if you choose to run all software code within the module. We call this OpenMCU as customers can program their code within the module. The MQ200 on the other hand is the modem version and has a closed MCU with firmware running on it that cannot be changed. Both models will be explained in more detail in the upcoming slides. The block diagram shows the major components within the module and this includes ST micro microcontroller and Samtech Lora IIC. Verano has chosen these components to cover a wide frequency range of operation, industrial temperature range, optimal output power for long distance range coverage, power control for adaptive data rate handling in Lora WAN specification, more than enough flash and RAM available to meet sensor design and more than enough pin outs for sensor attachments to the module. Both models are footprint and pin compatible and this is all available in a small form factor. Lastly, this module is designed to allow Lora, Lora WAN channel bandwidth support which may be introduced in future Lora specifications from Lora Alliance. So the module can support even down to 7.8 kilohertz channel bandwidth. To highlight in more detail, I want to first mention the frequency range of operation in more detail. Murata has chosen SX1276 for the module as frequency range covers 860 to 900 megahertz for the module. This frequency range allows Murata module to be used in United States, Canada, EU, Japan and other Asia Pacific countries such as South Korea, Vietnam, India to name a few. Next, the output power will be discussed. Murata module is designed to bring out this separate RF transmit pad from the SX1276. This was done to allow output transmit power up to 20 DVM in one DV step or up to 14 DVM in one DV step. The RF output power adjustment capability is important since Lora WAN has adaptive data rate that includes output power adjustment from the network server. So the Murata module supports this feature allowing output power adjustment so the range coverage can be controlled and interference is minimized to other sensor devices in the same area. The regulatory certification process can be time-consuming and costly and to address this Murata module has gone through a limited module certification covering FCC and Industry Canada. GE certification is also available and Murata module is covered with RF conducted tests completed which allows in-product red certification to be completed by customer with radiation test. The limited module certification that was mentioned was completed with the reference antenna as shown here that includes PCB trace antenna, chip antenna, and external quick antenna. These options allow you to design in the lowest cost antenna solution or small antenna solution if your size constrained or sensor design constraints requiring external antenna. For more information on antenna please contact Murata. As mentioned earlier about MQ100 and MQ200 differences between the two parts will be highlighted. First let's cover the MQ100. The MQ100 comes with open MCU meaning there is no farm water loaded during module production. Customers can design the application code to be included into MCU thus eliminating the need for additional MCU outside of module along lowest component count and cost saving for in-device sensor product design. And also to highlight again the MCU on the module has 192 kilobytes of flash and 20 kilobytes of RAM. And to give you an example of how much code space you will have left to add application layer class A lower ones fact takes up roughly around 35 kilobytes of flash. Add battery for power source desired sensors such as temperature sensors or other sensors, 50 ohm antenna, and product casing to complete the sensor product design. Now MQ200 which is a modern version module and it is pre-loaded with firmware during module production. The firmware on MQ200 includes lower ones fact and a mid-layer AT command code that sends data through the UART interface. As you can see from the block diagram the host microcontroller on your product only needs to implement AT command to send data for simple operation. Just like the MQ100 all you need to add is battery, temperature sensor as an example, 50 ohm antenna. Of course keep your existing microcontroller in the design. Add a product case your design is complete. Now I also want to quickly highlight key schematic and layout design guidelines for the Mirata module. First I would like to point out that you must connect M1 to pin 48 as this will allow microcontroller within the module to turn on or off the fast clock that is within the module. By doing so you can achieve lowest current consumption during the sweep mode and as you can probably guess sweep mode current consumption is the most critical factor for battery operated sensor design due to sweep mode being significantly longer than active mode operation for sensors that sends data very few times a day. Mirata has reference schematic available to cover this as well as other recommendations for schematic design. The printed circuit board layout design is critical to optimizing the radio performance to its limit. There is not enough time to cover all layout guidelines but key points will be mentioned here as this will save you time and effort during your PCB layout design stage. First and foremost point is the layout guideline for the area underneath the module. The picture shown in this slide is a good example of a proper way to lay out underneath the module. Notice the metal ground is flooded underneath the module along with the ground vias that connects well with the main ground plane that is typically the PCB layer immediately below the main component metal layer. This ensures RF ground current to have the shortest path as possible to the main ground plane. Note also that no signal trace is underneath the module. This will help to reduce any potential noise that can reduce the sensitivity of the radio signal. Mirata will be providing schematic and layout review so contact Mirata to plan for this service. We see Lora Asset Tracker as a very interesting extension to the current ST Lora dev kit. We believe that adding an accurate device localization when in a Lora network but also when outside the network could help to bring even more value to your new product and explore new use cases. Being able to look at an asset and its environmental sensors has many advantages and application for instance for fleet management. For example a store manager adding its own Lora network can monitor its truck delivery to its store branches. In that scenario when the truck get into the Lora gateway coverage a notification can be sent to the owner and accurate location can be transmitted. When off network it is recording the position telemetry so we can rebuild the path to the truck later on. That's record being able to be transmitted only when back in a range of a gateway. Many other applications could be for asset or good tracking or even pet or child tracking. You can extend the formally presented ST Lora dev kit to become an asset tracker. For that you just have to add a new Genesis Arduino shield. Genesis stands for Global Navigation Satellite System. It allows to accurately position an asset using satellite. ST has a shield called XNucleo Genesis 1A1 that is published on ST.com. It includes an ST-Tesio Live Free As module that includes a very powerful ST-Genesis solution that is multi-consolation taking advantage of GPS, Galileo, GLONASS, Baidu, QSS to improve accuracy. It can also do geofencing on the GNSS module limiting then the amount of data required to send back to the cloud that is very interesting for Lora network and to save even further the device battery. In case some of you need a smaller phone factor for asset tracker, ST has created a compact reference design including the similar bomb to the modular solution that we saw before and adding to it battery management and even USB Type-C connector to recharge. That small phone factor is about two inches by an inch and a half and is a great example of compact design and can be easily reused for data logging. It is available in a full kit presented in a blister as shown in the lower left corner of this slide. I invite you to go to ST.com and look for ST-Eval-STOrchet T01 where you will be able to get access to all the schematic variables if you want to use it as a starting point for your own design. For those two asset tractors design, the modular one based on the ST-Lora dev kit augmented by GNSS Shield and the small phone factor reference design we just saw before, we are using the same CMW that is already published on www.st.com. You just have to search for ST-80-Lora1. That CMW is running on STM32L0 of the Murata module using Lora1 1.02 Class A and adding advanced power management features using for example the axiometer to detect if the device should go in a sweep mode or be active and track. With machine 2 we were to create a UI under M2 portal in order to map an asset. We can visualize the street address by using the last known position pin on the map. We can also monitor the altitude temperature and humidity of an asset. Using a different tab of the same M2 portal webpage we can discover the past history of an asset. Inside the network we get a near real-time accurate location. Outside of the network the device records the locations for many hours so we can rebuild the full path when the device is back online. To have access to the M2 portal solution please contact machine 2. Thanks everyone for attending that webinar today. We really hope the webinar was helpful and brought you the right level of information so you can start to use the ST-Lora dev kit and initiate prototyping your new product. As a summary of what you saw today after a first introduction of ST machine 2 and Mirata IoT value proposition we presented in great detail the ST-Lora dev kit and how to build it or to get started yet a first user experience using M2 central and how to acquire the hardware. We also presented the GNSS Lora use case based on the ST-Lora dev kit and also the small form factor reference design. These dev kits are the tools to help you to go faster to market and simplify your learning curve to create your own products. So we hope you better understand how that dev kit will help you. From the hardware product side it features a Mirata module including the ST-M32 L0. For sure ST is putting its full ST-M32 portfolio at your disposal if you need a different flavor of microcontroller to certify your specific use case. Before closing that webinar and go to the Q&A session I just want to show you again the great ongoing deal that machine 2 has put together including the ST-Lora dev kit and featuring the Mirata module. Just go to store.machine2.com create an account and order your kit. We hope most of you will take advantage of it and will create innovative new product based on it.


On Tuesday, October 10th, a ribbon-cutting event was held for Pirates Cove, Axe, Paint and Rage in South Williamson. The new family-friendly venue is offering something for everyone from Axe throwing to arcade games with more to come in the future. Mountaintop News spoke with co-owner D. Kaiser for more details. It's been great to kind of expand out and kind of get out of just an adult only thing. Now that we've got a child, he's one year old, so it makes me, I guess, more maternal. It makes me want more family-oriented places that everyone can be influenced in and have fun in. So, I'm looking forward to touching a different side of the community, a different demographic of people. Getting to see those sides that we don't necessarily get to meet inside of our smoke shops. You want to save money, and Appalachian Wireless gets that. Right now, you can get up to $650 off select devices, including the latest and the greatest on the Advantage Unlimited Plan with a trade-in. Did y'all hear me? Up to $650 off select devices, including the latest and greatest with a trade-in. I'm not a math whiz, but this deal, it's amazing, and you'll be on the region's premier network. We are you. We are Appalachian Wireless. See Appalachian Wireless.com for complete terms and conditions. While most activities are meant for ages 12 and up, Pirates Cove can offer fun experiences for younger groups. For more information and party reservations, contact Pirates Cove Axe, Paint, and Rage on Facebook. The Rage Room is going to be 12 and up, Axe Throwing's 12 and up, so unfortunately, that's the reason we've tried to find other activities for younger ages. We have the simulators that'll be of all ages, arcade games that'll be of all ages, pool tables basically of all ages, if they're tall enough to play, they can play. We will have concessions. We're going to have hot dogs and hamburgers. He's going to kind of keep it simple, but keep it party-friendly. Pizza Hut's next door also, so that's for the side of kids that don't necessarily want hamburgers and hot dogs. We are trying to make sure that we have areas for walking children up to, even though we've got 12-year-old and over, we still want to incorporate everyone if they're walking up. We have pens for them to sign the walls, that'll show up under our UV lights, so that way everybody can make their mark on our place. Reporting from Outantop News, I'm Nick Colum.