Transcript 0:00 [upbeat music] Welcome back to another episode of Vanguard Radio. I'm your host, J. Richard Jones. Today we're gonna talk about digitization issues. It's complex. 0:17 There are a number of different challenges. Our guests today are gonna talk about practical solutions from an engineering point of view as well as a business perspective. 0:29 Our first guest, Victor Ku, is chief engineer with General Dynamics Mission Systems, Canada. 0:37 Our additional guest is Austin Douglas, infantry officer, retired, and he's also capture manager, General Dynamics Mission Systems, Canada. Gentlemen, welcome to the show. Thank you very much. Thanks, John. 0:53 Thanks for having us. Oh, it's certainly a pleasure. This, this is quite an in-depth topic to get into. 0:58 I think, uh, you know, before we started the show, uh, I think it was you, uh, Victor, who had said, "You know, it's not just about recognizing the problem, it's about finding the solutions moving forward." 1:15 And I think the first topic I'd actually like to dive into is, and we'll start with you, Victor, is what is digitization? 1:25 Yeah, I think it's really good to set some context around what digitalization is or digitization, if you will, and I like to think of it as less about translating an analog to a digital signal of ones and zeros, and it's really talking about transformation from many different aspects, whether it's people, processes, and tools, we often think about that, where in my opinion, the people piece is probably the most important and difficult portion of the conversation. 1:54 But myself as an engineer, and I take a look at the process and tools point of view, it's really how do we harness that power of technology to make our tasks and processes faster and better, to make better decisions and obtain better outcomes? 2:10 I think why is that really important? 2:13 You know, Austin and I had the opportunity to attend the Army Outlook just recently here in Ottawa, and there's a strong message of di- digitization again, and to maintain our military advantage and keep up with our adversaries and allies. 2:29 So we, if we understand what digitization is and why it's important, I think we can look to solutions for this going forward. So Austin, um, TNAS, um, solves a lot of the CAF digitization issues. 2:46 How does that relate, um, so what, what are some of the challenges, and how are you solving some of the issues of digitization within Army? So TNAS, which stands for Tactical Network As a Service, 2:59 I would say is an approach that GD, um, has used to look at that problem space, and having had been in the military for 20 years as an infantry officer and retired 10 years ago, I, I, I potentially grew up in that analog era 3:14 of joint domain command and control, and as this term digitization has been around for quite a bit of time now, you know, at least over the past 10 years, it's using that past experience as a infantry officer and, and using what I've learned in, uh, commercial industry and in the defense industry 3:31 to try to find a better way to bring that capability to, to soldiers in the battle space. 3:35 And invariably, it's about trying to bring all the sensors and effectors that, uh, soldiers need to use when they're, when they're deployed and, and having them operate off a common network, off a common capability, uh, in order to help with decision-making in, in the battle space, and invariably save Canadian soldiers' lives, 'cause soldiers deploy to hard and difficult places and try to solve hard and difficult problems. 3:58 And TNAS, that GD has coined, is part of that solution set we believe that can be a great offering to Canada and the Department of National Defense. For sure. 4:09 Uh, Victor, when we talk about digitization, is, is this really only just applying to the Army domain? Um, there's a challenge here. 4:19 Uh, I mean, we've talked a little bit about the culture already, but from a technical perspective, how do you re- reduce the complexity to the user as new technologies are coming in? 4:32 Yeah, I think that's a really great point that, that you brought up there. Well, the, first of all, you know, it's definitely not just an Army domain issue. 4:42 It's really a pan-domain issue that, you know, spot spans land, sea, and air, right? 4:47 And if, if we understand how we got here, it's really driven by a lot of these sensors and effectors that Austin had just mentioned being installed on these land, uh, naval and air platforms, and with that comes data, right? 5:01 And so you have a data consumption issue, and that demand for data and trying to weave your way and distill that data is, becomes r- really at the heart of the issue. 5:13 And when you take a look at that holistically, it breaks down to three main areas, where it's like data consolidation, data distribution, and data contextualization. 5:25 So there's lots of layers to the onion there, but you were really saying, you were, if I repeat your q- word question, is how you reduce that complexity to the end user, and that's kind of the key. 5:37 But when we go back to brass tacks is first about let's make, if we recognize we have a whole bunch of data to sift through, how do we make sure that that data is, is compiled, analyzed, and secure and accurate? 5:53 And then there's a second issue of distribution, making sure that the right information gets to the right place before the actual end user gets to see it, and that's where the data contextualization comes into play, making sure that- That end user gets the right information to make timely and accurate decisions, and there's lots of different opportunities in order to simplify that process from soup to nuts. 6:20 So when we're talking about, um, you know, at the end user perspective, there's artificial intelligence, machine learning algorithms that we can actually produce adaptive content delivery to end users to, to actually tailor the information so that the person doesn't have to actually analyze all this data all at once, and they actually get, uh, a little s- piece of the puzzle so they have a just enough information to make that decision at the right time. 6:50 Austin, how do you see it? Well, if, if I go back to it, and maybe I'll just amplify TNAS a, a little bit more, there's all this capability that is out there for, for the soldier. 7:05 Um, and the way I like to phrase it, you, you've heard the customer talk about the digital backbone and the architectural spine, and it's how do we onboard new technology, new capability as it develops. 7:16 In the past, we used to buy it as an isolated system, uh, offer it to the soldier, and then these multiple parts wouldn't... 7:23 They would talk, but it would take a lot of integration and complexity to bring them all together. 7:28 So what we're offering with, uh, TNAS and, uh, being the core of this digital backbone and, and architectural spine, it's about setting up the right infrastructure and setting up the right processes so that when new capability is onboarded, it is, it is really transparent for the user to consume that capability. 7:46 You know, the iPhone service is a good commercial example. You know, probably every couple of weeks, you know, e- every two months you have, um, a new software update to do capabilities added to your phone. 7:58 Probably 90% of it is transparent to you. You, you don't even know what has been added, but your phone doesn't slow down, it works seamlessly, and it becomes more innovative and, and more smart. 8:08 So the TNAS approach and with respect to data in the, in the battle space and respecting new capabilities, w- we look to have TNAS solve that problem space and make it easier for the customer to bring on capability, consume data, use data, and, and make it available to the end user when needed and be fit for purpose. 8:27 Austin, is, um, is the US aligned with the TNAS concept? I think by sheer size and complexity, the US leads the way i- in a bunch of these spaces, but they're trying to figure it out as well. 8:40 They have programs in the States called, uh, Project Convergence as it relates to the Army, uh, Overmatch, I believe, uh, it is a naval program, and they call these, um, campaigns of learning. 8:51 Uh, and what they're trying to do is figure out how in this JADC2 joint, all domain command control, all these different capabilities that are in the battle space that Victor alluded to before, um, 9:04 can be optimized, uh, and, and integrated so that effects can be used, uh, in, in, amongst the various elements. So yes, I think they're leading the way in, in a lot of these respects. 9:16 They're trying to get Five Eyes countries on board, uh, as part of this campaign of, uh, of learning because it is a combined arms effort, not just with a, within a country itself, but amongst Five Eyes countries and then expanding out to NATO coalitions. 9:31 But yeah, the, the US is leading the way, and as Victor said, at, um, the outlooks that, uh, that we attended, you know, General Majkowski, the deputy commander of the Army, uh, Chris Ayad, COSTRAT, they go down to the States, they, they, they understand what's being said and what's being, uh, delivered. 9:49 I think they're trying to bring those examples back to Canada and seeing how Canada can participate with them here in Canada, and then as well on Project Convergence, which will be opened up to Five Eyes partners in the near future. 10:00 So Victor, um, how do we effectively there's a, uh, consolidate this information to make sure it's accurate, trusted, and of high quality? It, it sounds like there's some opportunities here. 10:13 Yeah, there's lots of different opportunities. I'm gonna use the word data quite often [laughs] in my next example set. 10:20 You know, you hear some buzzwords like data foundation, data lakes, data, data fusion, data analytics. 10:27 I, I think a, a really emerging place is multi-level data security, and, and all those stuff, I wanna make sure that, you know, everyone realizes those aren't just buzzwords, right? 10:39 Those are existing mature technologies. 10:42 So when we consolidate that data, we can sift through a large amount, get through it, contextualize it, compile it, and analyze it, but make sure that it's secure, make sure that it's accurate, so that it's not compromised at all from a security point of view. 10:59 So those are some of the opportunities that exist and have been exploited already by a lot of industry. So Austin, um, let's talk a little bit about data distribution. 11:09 What are some of the strategies around how this information gets, uh, distributed, especially to correct locations? 11:20 As a user in the, in the battle space, um, and I'll speak to the Army writ large, there's a lot of data pushed to the soldier, whether it's something like blue positional awareness, uh, whether it's something like, um, overlays that will coordinate how an, an attack's gonna take place, um, or the information with respect to the coordination of fires, whether using artillery or, or naval gunship fire. 11:47 Uh, for the user, I, I guess it's really make sure that the data can be trusted, it's coming from a reliable source, it's not spoofed, and, and it's accurate with the main end state being, you know, the avoidance of blue-on-blue and, and fratricide. 12:01 So from that standpoint, it's about having the, the data be protected, um, from endpoint to endpoint. I, I suggest it's probably not- 12:10 Those are probably transparent problems to the, to the user, but in this day and age where there is a consumption of data on the battle space, and it is definitely used in social media, uh, after the fact, I, I think make sure the reliability of data as it, as used in the, in, in the battle space is an important topic. 12:28 And then, you know, being a, a business development person, I'd have that requirement, but then I'd definitely hand it over to the engineering team to make sure that that capability, um, takes place and that security is maintained, especially when you think of things such as cloud at the tactical edge, right? 12:44 Um, and systems can be secure and reliable, and information can move on and off of those platforms. Well, certainly in the battlefield, communication would be extremely necessary, and it has to be effective. 12:56 Austin, you've mentioned a technical, uh, component to this as well. I want to, uh, come over now to you, Victor. 13:03 I mean, in terms of distribution, how do you ensure that the information is getting to the correct locations? Yeah. I think, uh, think i- i- that is, that is the heart of the issue really, to be honest. 13:18 Um, you know, I take a look at some, some technical capabilities like quality of service or QoS type algorithms, which really adapt to whatever endpoint you're sending information to, and adapts to whether it's a low capacity or high capacity on one end, and any type of application you're using on the other end, whether it's a battle management application, et cetera. 13:45 But in the middle, the, in the mushy middle, if you will, there has to be a resilient and adaptive network that's really responsible, uh, responsive, I should say, to what is available, high or low capacity links, right? 13:58 And so no matter how big or small the pipe is, the, the network will just figure it out and scale appropriately. 14:04 We have to under- also understand the operational environment that we're living in with these tactical systems. They're not your internet service provider at home, right? They're in distressed conditions. 14:15 Um, but where we want to evolve the system to is, Austin mentioned the iPhone. 14:22 When you pull out your iPhone and you go from network and you drive across Canada, you shouldn't have to worry about which network you're transitioning to, whether it's Bell, Rogers or Telus or somewhere in between, the network will just hold up, and you'll always have comms and data at your fingertips. 14:40 Well, exactly. Um, Austin, my next question is for you. Um, is there a link with Land C4ISR modernization projects? 14:51 Well, that is, I think, at the heart of what GD is trying to offer, uh, the Department of National Defense and the Canadian Army. The, 14:59 in Land C4ISR, the Army has an operational baseline, uh, that serves to host all these capabilities, sensors, uh, and effectors. 15:10 GD is under contract to deliver that right now, and, and the capability pack that is in the, in deployment is called Capability Pack Towpath. 15:21 As well, at any given time, there's a, a baseline in development and a baseline in architecture, so the teams here are definitely, you know, looking forward to make sure we can digitize that, upgrade it, uh, make the system secure and robust. 15:35 As the Canadian Army looks to modernize a series of capital programs, whether it be Canadian Forces Land EW Modernization, Tactical Communications Modernization, or ISR, the offering and part of Tactical Network as a service, uh, and the delivery of that capability pack baseline is to build an architecture that is robust and can onboard this new capability. 15:58 Like Victor said, you know, with the iPhone, and it either updates or moves from network to network, it just becomes one thing. 16:05 So whether you're looking at sustainment programs that, uh, deliver an operational, operational baseline, or whether you're looking at capital programs that deliver new boxes, sensors, effectors, and capability, 16:18 when you start hearing these terms of Pan-Domain C2 or Joint All Domain Command and Control, that ecosystem 16:25 just becomes one thing, and GD believes it has a, a central part to play, definitely with respect to delivery of that baseline and helping, uh, the government of Canada and Department of National Defense build that architecture to bring forward the best capability. 16:40 Whether it be GD offering some of those products and capabilities, or whether it be other OEMs offering some of that capability or small, medium-sized businesses, I think there's a role to play for everybody in that defense industry, a- and GD definitely sees itself as having a central role in that. 16:55 Well, that definitely identifies the need for TNAS. That's what we like to believe. [laughs] Yeah, that's what we like to believe. 17:04 And, and, and we think it's resonated, and, and we, we think it's resonated with the customer. I'm not trying to be, uh, as an infantry officer, you know, o- of twenty years, I'm not trying to be too novel about things. 17:15 It's trying to hopefully use my experience, l- look what's available in the marketplace, piggyback off what other smart folks have done, and, and definitely use that to put GD in a good position to, to help the government of Canada and, and the Department of National Defense. 17:28 Yeah. Well, listen, at the end of the day, uh, you know, your customers have a lot of choices out there, uh, but 17:35 you've, it's got to be a solution that helps them to prepare and organize in a way that, so that they are effective on the battles, on the battlefield, correct? Correct. 17:46 And if our, you know, pr- previous chief engineer before Victor, and, uh, now the director of the P&L, Jason Trope, he would just call TNAS good systems engineering, right? 17:58 It, when you look at requirements and you look at capability, you look at testing and, and end user requirements and validation, it, it is just sound systems engineering that, that we're offering to the customer. 18:12 Nicely branded in, in, in, in an acronym called TNAS, but we believe it, it, it does offer good capability and is a good solution for the government of Canada. 18:22 And invariably, it, it, it is, it will be good for Canada, it would be, will be good for soldiers, and it will be good for industry. Victor, I want to come back to you now. 18:32 Um, how do we contextualize the data so that it's tailored to the user? Yeah. I... 18:41 Earlier on in the podcast, I did mention, you know, new and novel techniques as artificial intelligence, machine learning to adapt that content to the user. A- a- and, and really that's part of the solution for sure. 18:57 Uh, you know, working with our customer, with the Army, there's a strong drive for simplification of the user experience. I would go one further though. 19:07 If we have higher technologies and emerging technologies such as AI and ML, we can, like you just said in the question, we can actually have a tailored experience based on the user, the user profile, their user role, maybe their, their age demographic, et cetera. 19:25 There's some really neat and novel concepts out there that we can, you know, we can actually offer to tailor customize experience based on the time of day, the user role, and their demographics, et cetera. 19:39 So I think that's part of it, and, and to re- really reduce that complexity at the very beginning, like you mentioned, of so they don't have to sift through all that data, they don't have to go through Excel spreadsheets, they don't have to go through some database, but it just, uh, does that analysis for you, and, uh, enables them to get the right information at that right time. 20:00 So Victor, uh, from a technical perspective, what does success look like in the future? I would say I boil it down to two, right? 20:11 So we talked about reduction of complexity, and the second factor is flexibility for now and the future. So, you know, how would I judge con- reduction of complexity? 20:23 I use the analogy of you don't need a data scientist in the back of a lab to decipher the data. If we, if we're able to move the yardsticks on that, that's obviously a, a great thing. 20:34 But the flexibility for now and the future, that's an interesting one. 20:37 It's really talking about delivering a path and a framework for Canada to evolve really their current systems and to harness, while I should say, harnessing the power of new technologies as they mature, and realizing that flexibility portion of what technologies to adopt over time based on operational need. 20:57 And that really leads to really the TNAS narrative. And, and so maybe I'd just like to take a, a minute or two to describe from a more concrete technical perspective of what TNAS actually is. 21:09 And, and really when I try to describe TNAS to other folks, at its heart it's taking a data-centric holistic view across like the PAD domain scope, as we've discussed, and reduce the data silos that have existed and developed, you know, up until very recently. 21:27 And when we take a look at that end goal of having a truly integrated and unified information system that enables interoperability and coordinated operations across all military services, that's really the goal. 21:40 But what is it actually? You know, it's really a, we're talking about a common set of services and architectural frameworks for capabilities to be deployed and upgraded as technologies evolve. 21:52 Uh, the analogy I like to use in order to fit this all together is, is Lego. It's something that, you know, I've played with as a kid. I'm sure all three of us have. 22:02 Came out in 1949, and they came up with this system of interconnecting blocks. But the funny thing is, if you bought a set in 1949, and you bought one in 2022, those blocks would interconnect and still work together. 22:17 So if we take a look at those, each of those services that I'm talking about within the TNAS is as a Lego block. 22:24 As technologies improve, and we decide to capitalize on those technologies based on operational need, the idea is we could swap out those Lego blocks for newer and better ones, but they would still fit with the old ones and give an upgrade path to the future. 22:41 Victor, that is a, a great example. Uh, Austin, I want to give you the closing remarks. Um, what does success look like from a business perspective? Can I repeat what Victor said? 22:53 [laughs] [laughs] I, I, I do think Victor did a great job of, of, of outlining exactly what success looks like. 23:03 The only thing I would add is where we feel GD has a central role to play in that ecosystem with the Department of National Defense, the Canadian Army. We remain open for, you know, collaboration with industry. 23:16 We're, we're one part of that solution set, and in building those Lego blocks together, we wanted to find that architecture to show others how to 23:24 onboard their capability onto that TNAS so that we can offer it in a seamless way to the government of Canada. 23:29 So GD is collaborative, open with, you know, available and ready to work with others to offer, um, Canada the solutions that they need to give their soldiers to deploy effectively into the battle space. 23:43 Victor, uh, from a technical standpoint, has the Army kind of already got things underway with technical networks in terms of TNAS? Yeah. 23:54 I think we've been talking about TNAS a lot this afternoon, and I think it's important to recognize actually Canada has already started to organize, at least from a Army tactical network point of view, can't say that for Navy or Air, but around this TNAS concept already. 24:11 So we've been evolving the system throughout time over the last several years on the support contract, and putting in the groundworks, if you will, in order for us to deploy the TNAS in full. 24:25 You're listening to Vanguard Radio. Today, we have been talking about how TNAS solves the CAF digitization issues. Uh, we've talked about practical solutions. 24:37 We've broken it down from both a business perspective and a technology perspective. 24:42 I want to thank our special guests for joining us today, Victor Ku, Chief Engineer at General Dynamics Mission Systems Canada, and Infantry Officer Austin Douglas Retired, Capture Manager, General Dynamics Mission Systems Canada. 24:57 Gentlemen, thank you both for coming on the show. Thank you very much for having us. Thanks, John. 25:04 [outro music] The views, information or opinions expressed during the Vanguard Weekly Podcast Series, CGE Weekly Podcast Series, Vanguard Radio Podcast, and CGE Radio Podcast are solely those of the individuals involved and do not represent those of Vanguard or any affiliated media products, their employees or owners. 25:30 Vanguard Magazine, Canadian Government Executive Magazine and its affiliates are not responsible for and do not verify for accuracy any of the information contained in this podcast series. 25:41 This podcast may not be copied or distributed without express written approval of Promotive Communications Inc., PCI. You may not edit, modify or redistribute this podcast without consent from PCI. 25:52 PCI assumes no liability for activities in connection with this podcast or for use of this podcast with any other website, computer or playing device.