 So, Graham Orkins, my name, I'm based here in Adelaide, I'm an agronomist by trade, I've been working in the ag industry for about 30 years and I'll start to show my age. I've previously worked for Elders and for the last eight or so years I've been working for Ag World. I'll go after South Australia, Northern New South Wales, Queensland, New Zealand and as of the last couple of days I've been doing a little bit of work up in the Pacific Islands where some industries or farmers in Tonga are taking on the software, along with Fiji, so interesting life travelling around. But, Ag World is an independent global platform for the data driven future of agriculture. A lot of what people talk about in the ag game these days is around data, who owns the data, who's using the data. Now, vision of the process, it's the farmer owns the data, we're independent, sometimes refer to our competitors, we're owned still by the original founders of the business and the venture capitalists that put the money in to get us going, we have no ownership in or no ownership by a chemical company or seed companies which you'll see in a lot of the global positions. So we're independent. We don't sell data, the data that is generated by farmers and their advisers is owned by the farmers and their advisers. And I think listening to the Israeli gentlemen this morning, our aim is to simplify what farmers and their advisers do, not make their life more complicated. Everything we do is about reducing the requirements to create that information, making it simple to use, easy user interface, a day-to-day farmer or a day-to-day activities for a farmer and their advisers is complicated enough without attempting to use software that doesn't help in that process. So we aim to make it less complicated, not more complicated. So we've been going since 2009, so just made it past our 10th birthday, which for ag tech, star-wag tech companies, that's quite an achievement. We're probably not considered a start-up anymore. And as I mentioned, a lot of what we see in the ag tech or our farm management space is systems like ourselves being bought by someone. We've recently reversed that strategy and have actually bought a business in the US called Green Book, which provides label and warning rate information, which we currently use in the US. It's not here in Australia as yet, but by purchasing the business out of the US, we'll give us that capacity to change some of our library function and search functions that we have here in Australia. Our primary markets, the US started in Australia, but then expanded into the US, expanded into New Zealand in about the same time. And we've just launched in Canada back late last year, so getting our first customers in the Canadian market. But everything that we've done was, the foundation was Western Australia and moved across the rest of Australia. Each of the markets we operate, we reskin the product to suit the actual marketplace that we're operating in. 50-plus employees, half of those are programmers, so the co-drivers that drive the system in the background. The people that do the things that I've got no idea what they're doing because I operate at the user interface, which is what interacts with farmers on a day-to-day basis. The user interface is what drives the day-to-day use. 35,000 registered users, approximately half of those are here in Australia. Australia, the agronomist market, is about somewhere between 1,200 and 1,400 agronomists, and we've got over 900 agronomists advisors using the system. I should say there's approximately, shade over 2,000 subscribed farmers, another 3,000 using the system on a day-to-day view-only basis, so interacting with AgWild, but not actually subscribed. And then there's about another 10,000 farmers who have access to the system or just receiving information direct from their agronomist advisor. So digitizing farm information, it's a difficult space when people are still using Excel and paper and whiteboards. Growers use lots of different machines, lots of different monitors often get farmers saying to me, they're not tech savvy, don't use computers, and I jump into their header or tractor, and there's more computer screens in those headers and tractors than I'm sitting on the desk. Farmers are using technology every day, sometimes it's more applicable to their day-to-day activities, in that they like putting oil on a tractor, so a computer, a tractor is different to a computer that they hold in their hand, a smartphone, mobile, they only operate on Apple systems, but their farmers react differently to technology that's sitting in a tractor versus technology that they're carrying around with them. Connectivity is poor in many rural areas, as we know, our mobile devices will work both online and offline, so Growers and Agronomists can use the system all day long out in the paddock, and when they return to the office back into the kitchen, often McDonald's on the way through town, they can jump on Wi-Fi and all the information will sync together, so they can lost connectivity, maybe poor, they can still use what we provide on a day-to-day basis or throughout their working day. Lack of standardized data and APIs, and I've touched that on that in a little while, but everyone talks about moving information, integration is a big topic in the... That's the free carton of beer. Everyone talks about integrating. I want to bring my weather station information into AgWorld. I want to bring the machine data into AgWorld. I want to shift products from one spot to another, but the lack of standardized data and the lack of APIs or application program interfaces, the middleware between someone like ourselves and other pieces of software makes that an interesting task. As I say, oils ain't oils. APIs and integrations aren't as easy as we might think, but that's the challenge the industry faces. I actually support for technology, one of our strengths, but in rural communities, not the highest priority. And few farms really have a technology plan or an IT technology plan. They may have plans around what new tractor ahead or they may be buying, but are not particularly looking at what software they'll be using to help them manage their farms. So we're a collaborative platform. So we work across each of these systems in our own system and sharing the information between retailers. People, farmers, buy their day-to-day farm inputs, fertilize a seed, insecticide, herbicide. Growers themselves advisors, so potentially consultants working to advise farmers not what they do, and significantly agronomists in their applicators. We run a power aid permission system which allows each of these people to interact with Agworld and interact with the farmer, depending on how they wish to. Some instances we might have simple production data shifting between an agronomist and his other farmer. Others we might have financial information around the cost of production, shifting between the farmer and the agronomist or the farmer and his retailer. So the retailers can get an understanding of the seasonal input needs. System runs, so we have a planning and budgeting tool, precision ag, core GIS, everything operates on maps, and currently rolling out some features around NWI imagery, bringing importing layers as applied layers, yield maps, nitrogen removal maps, through integration we have with a company called PC2 or precision cropping technologies. And that's an instance where integration is working because two companies willing to talk to each other, allow the transfer of data, we have a standardised piece of information being the GIS referencing of fields. In-season agronomy, day-to-day agronomy, has to say 75% of the agronomist market in Australia use Agworld. They're providing day-to-day recommendations, plans, observations to their growers, for the growers to then act on, convert or potentially convert those activities into actual events to create their farm reculates and start producing data that they can use day-to-day in the future, referring to the past as to what they've done. And significant reporting and analytics, if you let us move around up there, but it's part of presentations. Any data entered into Agworld can be pulled out of Agworld, whether that be product information, field level information, observations, and reported on. Where it can't be or have an integration if anyone's used Power BI, an analytics dashboard that we've just done another integration, it's where mobile devices where Apple only, but it's integrations with a Microsoft company. So Microsoft Power BI, they're some amazing things. Simply pulling the information out of Agworld into Power BI, some templates built, incredible with some of the things that these systems can do. Precision planning, as I've already done, by farmers are in conjunction with their agronomist, their advisors, allows them to work at rotations, allows them to put a seasonal budget together. How much fertilizer am I going to need? How much seed will I need next year to store at harvest time? And simply, we can plan on the iPad, change crop types from week to canola, depending on the market, depending on the rainfall at start of season, and report on these things. So on the iPad, we can put a plan in place in about eight taps, which will then generate each of these aspects, product requirements for the season, work scheduling. When do I roughly need to put pre-plant fertilizer in the ground? When do I roughly need to start looking at post-emergent chemistry? All reportable, eight taps on an iPad, and you can change the varieties. So I can get planning in Agworld, or planning can be done three years in advance, five years in advance, five weeks in advance of sowing a crop, depending on how the season's changed, or five days after the crop has gone in the ground, you can plan for the rest of the season. The planning's like a budget, the crop plans that we put in, like a recipe, the activities that's sent under those plans are like the ingredients that go in to make that recipe. But as I say, collaboration. We're farmers working with advisors, advisors are doing this sort of work on a day-to-day basis. Farmers will typically plan once or twice a year. The agronomists are doing it day-to-day, so they have more experience in the planning phase, but do it in collaboration with their grow. So once we have technology here, a lot of this work can be done, or will be done, while they're sitting in ahead next to the farmer, sitting at the farmer's kitchen table, working out what he needs to do for the cunning season. In season agronomy, so this is the lifeblood of the agronomists and advisors, people like the agronomists that work for elders. Retail agronomists, agronomists working for the likes of rural directions. Consulting agronomists. We'll all operate in a similar space. Agronomists create plans, recommendations, observations, they can draw on maps. So we can see in the bottom, the pivot circle down there. I'm guessing slides. Yield information, so precision things like that we're rolling into Agworld now. We're not doing it, that's the aim of integrations, is to bring that style of information in from the experts. It's about layering and integration, as I say, but working with someone that thinks willing to work with us, commercially sound on both fronts. Top-right maps, farm apps earn the activities that go in field by field. So as I say, scheduling record, so it's complete farm management. We operate in the cropping space or the plant space essentially. Agworld's used here in Australia on anything from opium poppies in Tasmania through to pineapples in North Queensland. We're using pasture country in New Zealand and dairy farms to do forage production, spuds in New Zealand, yams and taro in Tonga, basil in Nandi and Fiji. So we operate across anything that you put in the ground, feed and water. Agworld will cover that space. There's a schedule jobs, it's a schedule workflow, keep records, determine cost of production. I often ask farmers, when I do presentations to them, how many of you can tell me how much you've spent on your farming activities for the current season? I might start on a paddock level. Very rare, unless they're using Agworld, can a farmer tell me how much he's actually spent on a field, spent on his overall farming activities for a current season? I've been with them and farmers are dealing with multi-million dollar businesses and sometimes can't tell us what the cost of production is or where they're spending is at. Agworld helps them do some of those things. Insights, I'll have a look with holding periods that I have, how much nitrogen have I applied to a particular field, how much phosphorus have I applied without, simply by doing actual events, allow some great insights into what they're doing and what's happened on their farm, as I've mentioned, reporting. Key to the process is our standardised data. Agworld controls the naming of products and the naming of pests, problems, crop varieties, we control all that, so simply that products are named the same way throughout Agworld. So on the input side there, each of those products is a different glyphosate, named differently, recorded differently, so I see free typed into any systems, except Agworld. Fields can, you see that could be called home, could be called home place, could be called a number. But once you have people free typing information like that, so non-standardised data, it's impossible to integrate it. There's no way of sharing that information around or matching it between systems. So what does that create? Creates an epic fail. So anyone that's trying to integrate systems that don't have standardised data will know the drama involved there. As I round up PowerMax in Agworld, it's just round up PowerMax and that field is home. It's one of the tricks with the field naming, particularly some of the integrations we're doing in the precision space, is that the one real common factor between a field in Agworld and a field in John Deere, John Deere tractor, is the geolocation of that field. Where that field is doesn't change, the naming may change, but so we don't match field names, we match geospatial information to work out fields that overlay each other. But standardised data allows us to play in this space, so integrating with other systems. So some of these are US based, but some of them, or half of them are Australians, so John Deere Global, John Deere approached us to start working and integrating machine data coming out of the John Deere tractor and the My John Deere system. We're bringing through start stop times, we're bringing through field maps, as applied maps coming out of John Deere headers, John Deere tractors, tractors using John Deere rate controllers. Interesting thing with John Deere, we don't share at this point in time, that's when John Deere is working on, we don't share product information. So do a recommendation in Agworld, send that to a John Deere tractor and the tractor will know, or the tractor driver will be able to see on his John Deere screen. You would think the products that he needs to put into a spray rig, but John Deere in the early days forgot to build a standardised database and only have free-titing, so I mean, John Deere, our farmer may put in, I'm gonna put a weed spray in. I mean, that weed spray is really five or six and two foot AMI and all sharpened or whatever it might be. So we can't match information at this point in time until John Deere catch up and build their own or news house product database. Power BI I've mentioned, CSBP, a fertilizer company in Western Australia, but we integrate information with their soil testing lab. APAL here in South Australia, we're integrating soil testing information. Agronomist goes out to the field, takes a soil sample, scans a barcode, he's already told the system what he's going to be, what he wants tested. Scans a barcode on his iPad, drops the sample in the box and posts it off to APAL. APAL results get fed straight back into the planning page within Agro. So the soil testing integration around the globe is working extremely well. Figured, accounting software or an add-on to the Xero accounting. Figures specifically designed for rural applications. We feed planning information into Figured or farmer feeds the planning information into Figured. That feeds into Xero and can compare cash flows with actual information in Agwell. Satyr maps that provider of the precision, some of the precision software. What makes us successful? Okay, support team. Anyone that uses Agwell and will know what the support to or how good their support crew is in Western Australia. They're every day of the week on, except for weekends, to provide support to our subscribers. And what keeps us moving along is continual updates, continual improvements that our programmers, who are all based in Perth, are far fewer in the US, but significantly our programs are based in Perth, doing work only on Agwild. Thank you. And I think we're into question time. Yeah.