Stacey Ryan: Thank you, Simona. Powered through that. I think it's going to be an interesting challenge. All of these multi-factor, issues that we're, we're seeing I think with the EV charging and deployment is going to be a good one. Now I'd like to introduce Jennifer from Tom Tom
Jennifer Loake: Good morning everyone. Firstly I'd like to introduce myself. My name is Jennifer. I've worked at Tom Tom for five and a half years now. I started out managing a team of engineers. We were working on finding innovative methods to build ETLs to update maps quickly. Now I've moved to the dark side. I'm working in sales, but the part that I love is solving real world problems with technology.
So a little bit about Tom, Tom on where we are right now. So, those who don't know, we were the old portable navigation device company and that's what a lot of people think that we still are, but we're not. We moved to being a software and services company a number of years ago. We've got three key focus areas. We have highly accurate maps, so we are one of four global map suppliers. So there's only four companies or organisations in the world that have a global map. And yeah, we are lucky enough to be one, we've got traffic. So we've worked with UTS with our traffic before. We don't have all vehicles on the road, but we do have around 30% in Australia on the high functional road classes. We also have traffic data, going back historically to 2008. So that's, you know, good data to, test your models out with and train your models with.
Additionally we have APIs. So our APIs help people to answer difficult questions like how long will it take me to get to a certain location, which, which route will I take? We also have SDKs. So navigation SDK is a new thing that we have, which allows you to have turn by turn, navigation instructions, from point A to point B, we've got a new app that's available free in the app store called Amigo. So if you're keen to test out where Tom Tom is at with our navigation, I encourage you to download that. So last year we had a bit of a change. We announced, a new strategy and a new approach. Our focus is on building a new Tom Tom Maps platform, which is application map ready and it allows others to build on top of it. This means that we are looking at, well, we will be decom commoditizing our road centre line. And, this also creates an environment where everyone can build on top and everyone can contribute. So what it does is it builds a, brings a pool of map content from map users around the world and it's going to be the largest geolocation database available in the market. We'll be focused on having continuous updates being fed back into the map, and it will, we hope that it will be the foundation for IOT and connected autonomous vehicle projects to build on top.
So it's going to be built from an array of sources, including osm. So that will allow Tom Tom to have improved coverage. At the moment, we don't support countries like Nepal, Bangladesh, Sri Lanka. from the second half of this year, we will, we'll have, sensor derived observations coming in from vehicles. We'll also have our probe data coming in and we'll have shared POIs. So what will we do? So we will add value by building on top of it ourselves. It’s a lot of data and we'll also be providing data validation from our multiple sources that are coming in and through our technologies. At the heart is a flexible core map. End users can also create private layers where they can hold their own content on top, which can help support their individual needs and use cases. So automating the integration of super sources allows Tom Tom to continuously capture and cons consistently produce a solid base map of the world. But not only that, so towards the latter half of last year, there were a number of press releases, and the Linux Foundation has partnered with Big Tech to develop interoperable and open map data. The Overture Map Foundation is hosted by the Linux Foundation and driven by AWS Meta, Microsoft and Tom Tom.
The ultimate mission of the Overture Maps Foundation is to power new map products through openly available data sets, which can be used and then reused across applications and businesses with each member throwing their own data and resources in the mix. Collaborative map making is central to our strategy at Tom Tom and the Overture Maps Foundation provides us with the framework to accelerate our goals. So in February this year, Esri also announced that they're getting on board and, they joined the Overture Maps Foundation as well. So Esri issued a statement saying, in an increasingly digital and automated world, geospatial data plays a critical role in understanding the physical environment, empowering the next generation of location technologies for geospatial developers and professionals. The ability to access reliable open map data is vital to understanding communities and building innovative services and solutions. So today my presentation is quite short and sweet and I wanted to leave you with a slide and get you to think about what a harmonious open data ecosystem would mean for you. Would there be less system integration costs? Could you have faster build times? Would you feel better for not being locked into one proprietary map vendor?
Would it allow you to have modularity? So I'm leaving you with this thought and welcome any questions. Thank you.
Stacey Ryan: Thank you, Jennifer. And thank you to all of our panellists today. So we've got some time before morning tea and I want to offer the microphones to you to ask some questions, but I'm going to kick that off. I think it's pretty safe to say that this is a daunting, steep learning curve for a lot of folks, especially in the decision making suite. So how do we make life easier in a world where we've already filled with jargon? I spent a lot of my time explaining what an OEM is, let alone some of the more detailed complex things that we're talking about. So in a new world of clouds and lakes and edges and APIs how do we put together an understanding for people that either at beginning of their career or in signing contracts that this is an essential requirement? I'll start with you Rita.
Rita Excell: Thanks Stacey. Look, as I said, I spent 30 years in transport planning, as a civil engineer, and six months ago I moved to AWS. Retraining and understanding some of the IT concepts and emerging, ideas and, and the evolving. Every month there's a new product released. So there's a lot of training tools, self-training, self-paced training that's available. and there's multiple providers that do that. And I would encourage everybody if you are working in this space, to really look at what sort of training you can do. I'm sure my ESTEEM colleagues from the universities, but there's a lot of micro credentials, there's a lot of, professional development that happens. But, it’s really important to look at what training's available out there, up school yourself, up school, your staff, really just to be able to have those conversations and being an informed purchaser. Thanks.
Adriana-Simona Mihaita: I'll say make, make it real. So tell them a story and the current stage and where do you want to bring them next with the new emerging technologies and how it's going to be transforming the, practice and, and then do the deep dive of the technical it ease. and therefore we also focus in a lot of our effort these days on because we use a lot of deep learning. How do we make them explainable? You know, even with this large language model that we've been using for our, for our mobility modelling. They're hardly explainable at all. So we working on that front as well. To ensure the model that we have are robust and trustworthy.
Rita Excell: Outcomes. Focus is really key. Simona.
Adriana-Simona Mihaita: I think my advice would be on two sides. One is on the personal professional preparation side, and one is on the client interfacing problem solving side from a personal preparation, side. What I tend to notice is that, a lot of people tend to jump into directly, you know, using, some models or data science, but they lack the domain knowledge of, the area in which they apply these models. Now, my first advice is first become a very good domain knowledge expert. Like, what area are you working in? Are you working in public transport? Fantastic. Then learn everything about public transport modelling. Are you working in building management? Learn everything about building management first. Have that domain knowledge, which is very hard to have because this will allow you to understand the next problems that you will need to solve.
Computer and data science is usually a tool that will help you to get your destination. It's like a boat, right? But eventually, in order to get that boat, you need to know where you're going. So if you don't know where you're going, doesn't matter what boat you choose, right? So then the second step is once you have that domain knowledge, you understand very good the area, you understand the problems, and you need to know where you will go eventually. It's about choosing, selecting the tools that you need to get you in there. And this can range. And you can learn from experts in pure computer science, experts in algorithms, experts from, cloud service providers that can help you and give you the steps to get there. but eventually know where you need to go. And when you are working on a specific project with a client, I think the most important is to understand what is the problem? Well, what do I, what am I trying to solve? If you are trying, let's say, to solve a pedestrian related problem, why would you kill, your cloud service by loading data about, I don't know, scheduling or something different? Train your models with pedestrian related data. So understand what is the problem that you want to solve? Is it pedestrian? Is it time scheduling? Is it time delay? Is it what I am trying to solve? And then eventually, look at the steps to get there. That's what I would do.
Stacey Ryan: Thanks Simona. And Jennifer, now you're on the dark side selling. How do you make sense of it for?
Jennifer Loake: So, I can tell you a story. When I started at Tom Tom, I came in with about 10 years’ experience in the GIS world. I'd have my own company and I've worked in a lot of different use cases. My first week to two weeks at Tom Tom, I had no idea what anyone was talking about. Too many acronyms, too much difficult language and terminologies. For me it's about demystification, right? Let's make it simple. Let's use less acronyms and let’s, I mean, not everyone is technical that we're going to talk to. We need to be able to engage with high level stakeholders and low-level people, throughout every organisation. So just keep it simple.
Stacey Ryan: Yeah. And I think attaching the solution, solution to a specific area of issue that the people have as well. Like, and, and keeping that simple. So we talk a lot about obviously road safety. It's a critical area for us. So we're going back to the solutions outcomes focused. What are the tools that are available now and emerging that will deliver better road outcomes? Rita?
Well, I’m a heretic in the road safety community because I think the vehicles are really the going to govern road safety, human in the loop - Human makes mistakes. robots can be trained. they can, they're not going to be perfect. but, you know, all of the research shows that, you know, the, the programming a vehicle, robots don't get tired. they generally perform exactly the same way. And that's probably one of the, detriments is that when they have unexpected incursions, they, you know, we really have to train them to be able to predict, not everything's going to be a small child. It might be a leaf. And if you've ever been in a vehicle that stops suddenly, one of the automated vehicles, in the market, that stops suddenly because a leaf flies past you realise the safety critical programming that they have.
So I think, you know, really, understanding how we move and, and, you know, really excited about what the federal governments storing with connected vehicles. We don't have to go to the full spectrum of no driver. We really can start having roads and vehicles talking to each other. How we bring the, the human, into the loop is really important as well. So I think that's really critical from a road safety perspective some of the panels have talked about iRap I was really lucky about 20 years ago to be part of the team with the motoring clubs that bought the AusRap programme to Australia from Europe. that was required a lot of data and that was really a barrier to entry for local government, for others to be able to collect enough data on the road condition to be able to feed into that model. So it's really exciting to see how that's evolved, how we're using data that, you know, third party providers are collecting for other purposes to actually inform road safety. So I think, that the data's really central to decision making, but from road safety, I think we need to see the interface between the vehicles and the infrastructure to really get to that step change.
Stacey Ryan: And Flora and Simone, the models that you're building there're focusing on massive climate disruption and road incidents. Where do you see the future of that with the, like AV’s and more connected vehicles coming on?
Adriana-Simona Mihaita: That's a very hot topic. automation right, and disruption that this will bring. there's a lot to say about automation and how this, what type of data maturity, it will need. from my perspective, I think that, adopting, let's say an autonomous vehicle, transportation system would require a lot of work from the infrastructure level. The infrastructure needs to be equipped with sensors that detect the approaching of those vehicles that respond back, send messages, so that infrastructure to vehicle and vehicle to infrastructure communication needs to go smoothly. otherwise it, it will be very, very hard to adapt to anything that is happening. So first layer would be infrastructure, equipment in order to support the automation level. second level would be to actually facilitate the interaction between autonomous vehicles and all other modes. So all vehicles need to talk to each other vehicle to vehicle, communication in a reliable way. but my feeling is that before we actually get there, we're going to have a mixed transportation mode happening. Autonomous vehicle mixed with personal driven vehicles. I don't think that is going to be a straight directly adoption of avs. AVS will be everywhere. That's, from my point of view, it's going to be a stepping curve and any type of AV system will need to communicate not only with a similar system, but also with human driven vehicles. And that's the challenge. That's going to be the real challenge to equip all vehicles with this capability to communicate.
Stacey Ryan: Yeah, not a bad thing the AVs are a few years off then I suppose, and Flora?
Flora Salim: So, I just want to add to what my colleague here is saying - one of the problems that is still being researched at the moment is, perception, perception of the environment, in even autonomous vehicle environment. And because we as human, as well as we drive, we actually perceive, perceive our environment. And if, if, you know, everything is like, while we are right now human driven, we can still perceive how things are. But when they are actually mixed environment and you, you know, your, our percep level of perception change. And the thing is, there are a couple of things that AI and powerful computation can do better than our human level perception. We need to actually leverage that. We need to enable human’s as they perceive environment, to be able to tap into that knowledge.
But at the same time just like Rita mentioned that we need to actually enable, machines to enable human in the loop. so that kind of mixed environment will be quite interesting when you have perception, especially also a lot of these AV training are trained in a very known control environment. So how would you actually adapt to unknown contexts? you know, suddenly they're, I mean, some of the, vehicles, that are know, are being trained on very flat surface, for example, as soon as it goes to high on, you know, changing elevation, you know, Sydney, it's so hilly like a lot of different places, you won't be able to see the road sign or there's a dog appearing, you know, just, on the side of road it's going to be unthinkable.
Adriana-Simona Mihaita: I just want to wrap up saying data ecosystem eventually for automation, we'll need to get there. We need to have an ecosystem of multiple datas blended together. I don’t know if it's, if anybody's in the room from Telstra or any type of telecommunications company, we need you, that won't be done without you. So it's going to be at another level of data integration.
Flora Salim: Yeah, I agree. And I think one thing to mention as well is the, going back to my presentations, the federated learning. So having a capability of self-contained learning on the edge on each of the vehicle itself, right? But you need, you know, you, you won't get a hundred percent. that's where you, that you need the federated learning where you share the model being learned across between infrastructure, unit to roadside unit, unit to vehicles and, and even, you know, maybe buildings.
Just if I can, just a shout out. I don't know if anybody's here from the Transport for New South Wales customer services team or future mobility team, but there is a survey that they're asking for feedback and they are creating an Australian data set to train models, for automated vehicles. So if you go to the transport from New South Wales website and probably put in Australian data set, they're asking questions like, what sort of road environment should we, what sort of road rules should we be putting into this data model? So shout out to that team that's running that project. So we don't want to have models that are trained overseas, on overseas conditions deployed in Australia, and there isn't an Australian data set for training and assessing automated, technology and perception systems. So those sorts of things that Flora was saying, Australian conditions, bidirectional, you know, dynamic traffic controls, all those sorts of things. Our, our language. We really need to really build the ecosystem and opportunities for Australian companies to design Australian specific tests for these technologies. So, yeah, I encourage you, it closes on Friday. so, get in there and put in your submission
Stacey Ryan: Always comes back to the kangaroos, Jennifer, a lot of this sits on the maps to make it work. How, how are we going to do that?
Jennifer Loake: Yeah, I think it's all around having the ecosystem. I think we've used that word quite a bit today. but I think it's about having people contributing, but people using and making it easy and accessible.
Stacey Ryan: We talked about the training sets. So what are the costs when you talk, looking at building up those training sets and developing a schema, and how do we get to the point where we can have this robust data sets that are easy to use and understandable?
Jennifer Loake: So I think there's always going to be the base level, right? Where we want to be able to make data accessible. And it needs to be free. It needs to be open so that everyone can start having a common, base level, base layer. And, I think anyone who's done system integration between, you know, trying to apply traffic on top of different, base geometries, yeah, it's a, it's difficult. How do you get it down to the lower functional roads? how do you make sure that it's telling you what it, you need it to be telling you a different people model, motorways, roundabouts, all of these different features differently. So standardising that and everyone working off the same their foundation, I think that allows us to then start to innovate above
Stacey Ryan: And Simona and Flora. The models that you are building, say around like road crashes, we don't have a harmonised road crash data set across Australia. So is there like a way to reverse engineer that, like from your side through to the road crash scenario or, in investigator unit
Adriana-Simona Mihaita: It will be so good to have a harmonised crash data set across the entirely of Australia. One thing for us. I'll just touch on the crash data. Transport for NSW might store incidents differently. the operational and intervention on the field are, are completely different. Once again, I mentioned the textual description that operators need to do, and once they get a call and they say, okay, accident on M7, please send two vehicles or crash collide human fatalities, yes or no. So most of the times they don't have time. things happen so far they need to be on, they need to send the intervention team. They don't have time to put all the details inside the database. That's the big issues, which means that many times we have broken records coming in, broken incident logs saying, accident M7 the location, even the location of that accident. It's somewhere in the middle of road, but it's not really exactly precise. So I think improving, first of all, the collection of the crash data from the field would be fantastic to harmonise and uniform all of that. That would be so good.
Stacey Ryan: Yes. I suppose designing tools that would be more efficient to use on scene recovery units. Flora.
Flora Salim: One thing I will say that beyond crashes, what be really, really good is to have a lot more data on near misses. Yes. That's actually the, the critical bit, you know, in what cases crashes will happen and in what cases won. Yes. Because, you know, if you only look at crashes data, then your, your model, whatever you are training on, is very biased on things that eventually did happen. And, it’ll be really good to look at near misses and, yes. Well, my PhD was on looking at, you know, machine learning all those mis near misses or 10, 10 more than 10 years ago now. But even then, you know, a lot of things are have to be simulated.
Adriana-Simona Mihaita: There is a startup company, Compass IOT, if you've heard about them, it's an Australian startup company. They are collecting telematic data from vehicles, mostly the new models that send their position every few seconds. And they are looking at the combination between the steering of the wheel, the speed, the position of the vehicle, and they classify that into near misses or breaking points, all of that. We used them last year, in the last year, they're awesome. Check them out if you haven't. It's Compass IOT.
Rita Excell: Just on that again, not harping on just about vehicles, but there's a lot of data coming from vehicles about hard breaking, those sorts of things. So I think we probably need to start having a conversation about, you know, what data matters from a road safety, from a transport planning, and what's the value of that data and how do we share that data? So AWS, we work with very sensitive data from lots of organisations, and, we’ve got these things called synthetic data sets. So it's actually, getting rid of this whole, it's anonymizing the data. we have these products called clean rooms, which are just announced, late last year. So creates a place where, organisations can share data, and they can have access to it. So we provide the room, for others to collaborate in.
So there's a number of opportunities we just need to maybe start shifting the discussion and I know Australia's been trying to get vehicle generated data consensus on, on how to get that. It's sort of, I'm not quite sure, I've been away from it for a while. But, you know, the ip, the privacy, all those sorts of things. I know in Europe, you know, there are already agreements on what data can be shared around incidents, responses and, and black ice, those sorts of things that the vehicles are detecting. So I think probably we need to have a really mature discussion about what data matters for what purpose, and then also understand there is ip, there is hacking. Vehicle manufacturers don't want, vulnerability into their system. So I think that that's one thing that I would say is really important. And AWS provides, some of these, collaboration opportunities for, sharing data.
Jennifer Loake: Yeah, I totally echo that. I think, we should build upon, what has been done in Europe and then try and, regionalize that. I think, if we start to reinvent from the ground up, it's going to take us a lot longer. We've got to deal with different state jurisdictions in Australia, whereas if we try and have a harmonious approach, I think that's going to allow us to get there faster.
Stacey Ryan: Okay. We've got 10 minutes to go, so if there's any questions, please grab the microphone and ask them. But I'm going to flag one that I think is going to be super easy to answer. How do we get more women in stem?
I think data is a really great anchor. Like when I was at Arup, we used to do lunchtime sessions in Python. We would do crowdsourcing, sort of gamified to your work, India and Nepal and other developing countries. We would, have crowdsourced maps and we would draw octagons around sheds and label parts of the maps so that we could build up a better understanding of, where things were for NGOs. And most of those sessions were filled with young women.
Rita Excell: Yeah, I've got an answer. So, another thing that I've always found is that women do like to talk. and, I find that when you're working in engineering and, and coding and those sorts of things, people put on their headset, turn it onto, aeroplane mode, and there's no conversation. So it's boring. So, for me it's about, creating an energy, creating a hum making it inclusive, and, and really making it fun.
Adriana-Simona Mihaita: Academics
Flora Salim: Such a hard question to ask. How do we get more women in? The answer is by making it look not that hard. It's not that hard if you put your heart, your head to it. Any, you can't do anything. Even if it doesn't matter. You are a female, you're a man, doesn't matter. Eventually, the most important is to be passionate about what you do. And probably we need to, from when they're very young, we need to tell them this. When I started my university degree, we were five women and 100 men in my theory, in the faculty. So, it's 5% women studying automatic control and information technology. I was one of the weird outliers for wanting to study computer science and automatic control, but I loved it. and I was just telling everyone, you can do anything as long as you're passionate about the domain that you're working in, it doesn't matter. So, yeah, that's the message I would encourage from young age.
Stacey Ryan: Yeah. Start that positive reinforcement. Very young.
Flora Salim: First thing I'll say, there's no linear career pathway into stem. You can even be an, a non-technical person and have a career in stem. And even right now just highlighting, the director of National AI Centre, St. Solar, who got, the undergrad training UNSW, but not in AI not in technology, but in arts. So I will say there's not, but the, the most important thing is, reinforce the, positive passion about what you do. and especially if we can start actually showing that STEM is actually fun since, it'll be a bit too late, you know, four kids got in year 11 or 12 because they already decided some of their, courses for, and, you know, what they want to do for hex. But starting early, even the senior primary getting, the kids excited because I, can see, even in UNSW in the moment, some of the struggles I see, with some of the female cohorts are, you know, they feel that they're left behind. But, in comparison to their male, male cohorts who've been coding, because they were coding it while gaming since they were 11, 12 13. So, you know, it's typical to do coding while you're gaming, but the, the female, they, don't game as much and they only start learning coding in, in uni. Sometimes they feel they can't catch up. But it's not, it about, someone who is better in coding, will be better in stem, not necessarily, they'll be a lot of different diverse skill sets that's needed in stem, especially the one I mentioned, responsible ai, responsible data science, responsible innovation. That is a very multidisciplinary discussion. That will need to bring every single skill set from law, from arts, from social science, anthropology, not just the human factors.
Stacey Ryan: And that ties to Jennifer's point as well, that storytelling is going to be vitally important going forward. And women can talk sometime, some of them,
Rita Excell: Just on that, I have to disclose, I have two daughters and neither of them have gone into STEM. So I, you know, as a role model for my own children, but I blame my husband because he is an engineer as well. So it must have been his fault, not mine. In a previous life, I was president of an industry association in local government and we created, an, a scholarship for women to enter and to do post-graduate studies in asset management. I was really excited, really to target, to make sure that, you know, it really targeted women, to be able to apply for this. There was a lot of flak that came. Why is it only targeted at women? You know? So, we're still having this discussion we got some amazing candidates apply.
Some of those candidates probably wouldn't have even considered applying, but because it was specifically targeted, for women, it really started the conversation with their managers with themselves, you know, around accessing that. I do think that, through my children's career at, at high school, they weren't A students in mathematics and chemistry and physics, so they got streamed straight out of that, because it was all about achieving this higher Atar, this magical number around, for the school to be able to brag about, how many people over a percentage. So I think that there's some fundamental issues and maybe we've sold, engineering, and STEM in a wrong way. We've got really intelligent people setting really high bars, but we also have normal people like me, who worked hard and really, you know, worked on the tools and, and, and developed, a career in engineering and I wasn't in the 99 percentile. so I think there's a lot of language, but these fantastic role models that are up here with me, for the next generation, I think that's really important. And making sure we have really good role models for women and also diversity and inclusion, all those things. They're not just words, they're a reality. So, it’s really important for our sector.
Stacey Ryan: Excellent. I think that's a call to action for people at this conference as well. So we want to uplift and have sort of multi-generational people to attend and talk and different folks from different backgrounds. I think that's sort of the next barrier that we need to break through so that we all come from different lived experiences and have different approaches and opportunities and face different challenges so that we understand when we are building these models that, where the biases are, so we get better and fairer outcomes for all of us. So I think that's a good note, but if we've got a question
Audience Member: So I'm Bairgia I'm a PhD student from Monash City at Department of Data Science and AI. So my question is related to Chat GPT like, navigation guidance. So what I want to ask is when chat GPT is used, it is a language based model where we use constraint to analyse the database and provide answers. But when it comes to navigations, most of the data and incidents are real time. So how do you try to process this data? Like for an example, if you want to find a reroute, we have to use a, a dynamic traffic assignment algorithm. So how do you going to integrate this to the suggested system?
Flora Salim: There's a great question. So, you know, there are different power, different AI models and algorithms for different purposes, right? So an example that we show there, it’s basically, a really powerful, language model that can actually be customised for special temporal modelling and forecasting. we show that even when, when you have zero data for training, we can use it for predicting traffic, traffic flow, pedestrian flow at see data that it has never seen before. So, it is really good for those purposes. But for things like, for example, realtime data coming in, we've shown in, briefly, very briefly in the previous, work before I mentioned about the ChatGPT1 one is we need to design a memory model.
That part may not have, have the language model component, but it needs to be able to remember, what if there's any event happening, a similar, so it can then predict even in, during unprecedented events, during incidents or disasters even. and we show that that model that module can actually be adapted to the architecture we have and we haven't tried it, but it may be able to be blocked to the, language model that we have as well. But that's a really good question, but, it’s not that okay, We think language models everything. No, there are different tools for different purposes.
Stacey Ryan: It's good to see chat GPT being used for something good. I didn't think that was going to be possible. can you join me in thanking our panel and, we’ll see you all at morning tea. Thank you.