window['wistiajsonp-/embed/medias/w8w4716mei.jsonp'] = {"media":{"accountId":306212,"accountHashedId":"ac7avg9s43","accountKey":"wistia-production_306212","analyticsHost":"https://distillery.wistia.net","formsHost":"https://app.wistia.com","formEventsApi":"/form-stream/1.0.0","aspectRatio":1.875,"assets":[{"is_enhanced":false,"type":"original","slug":"original","display_name":"Original File","details":{},"width":1790,"height":956,"size":458492795,"bitrate":1159,"public":true,"status":2,"progress":1.0,"metadata":{"av_stream_metadata":"{\"Video\":{\"codec\":\"h264\",\"colorPrimaries\":\"bt470bg\",\"colorSpace\":\"bt470bg\",\"colorTransfer\":\"bt709\",\"pixelFormat\":\"yuv420p\",\"rFrameRate\":\"25/1\",\"avgFrameRate\":\"25/1\"}}"},"url":"https://embed-ssl.wistia.com/deliveries/36a611af0de3c8ac698b398861940c12.bin","created_at":1716863895},{"is_enhanced":false,"type":"iphone_video","slug":"mp4_h264_330k","display_name":"360p","details":{},"container":"mp4","codec":"h264","width":640,"height":340,"ext":"mp4","size":130597646,"bitrate":330,"public":true,"status":2,"progress":1.0,"metadata":{"max_bitrate":770104,"average_bitrate":338226,"early_max_bitrate":309048,"av_stream_metadata":"{\"Audio\":{\"Codec ID\":\"mp4a-40-2\",\"duration\":3089.004,\"frameRate\":43.066,\"sampleRate\":44100},\"Video\":{\"averageFrameRate\":\"25/1\",\"Codec ID\":\"avc1\",\"codec\":\"h264\",\"colorPrimaries\":\"bt709\",\"colorSpace\":\"bt709\",\"colorTransfer\":\"bt709\",\"duration\":3089,\"frameRate\":25,\"frameRateMode\":\"CFR\",\"pixelFormat\":\"yuv420p\",\"rFrameRate\":\"25/1\"}}","built_by":"render-pipeline","time_to_ready":42.430870696},"url":"https://embed-ssl.wistia.com/deliveries/fb3128120e1fc4f606b3d19423426300cf0c8877.bin","created_at":1716863895,"segment_duration":3,"opt_vbitrate":1200},{"is_enhanced":false,"type":"mp4_video","slug":"mp4_h264_241k","display_name":"212p","details":{},"container":"mp4","codec":"h264","width":400,"height":212,"ext":"mp4","size":95419250,"bitrate":241,"public":true,"status":2,"progress":1.0,"metadata":{"max_bitrate":436168,"average_bitrate":247120,"early_max_bitrate":235832,"av_stream_metadata":"{\"Audio\":{\"Codec ID\":\"mp4a-40-2\",\"frameRate\":43.066,\"sampleRate\":44100},\"Video\":{\"Codec ID\":\"avc1\",\"frameRate\":25,\"frameRateMode\":\"CFR\"}}","time_to_ready":756.166817751},"url":"https://embed-ssl.wistia.com/deliveries/575e87f77e3a67873cf60eb64268f48cb0bd08ee.bin","created_at":1716863895,"segment_duration":3,"opt_vbitrate":300},{"is_enhanced":false,"type":"md_mp4_video","slug":"mp4_h264_579k","display_name":"540p","details":{},"container":"mp4","codec":"h264","width":960,"height":512,"ext":"mp4","size":229281264,"bitrate":579,"public":true,"status":2,"progress":1.0,"metadata":{"max_bitrate":1385736,"average_bitrate":593800,"early_max_bitrate":528560,"av_stream_metadata":"{\"Audio\":{\"Codec ID\":\"mp4a-40-2\",\"frameRate\":43.066,\"sampleRate\":44100},\"Video\":{\"Codec ID\":\"avc1\",\"frameRate\":25,\"frameRateMode\":\"CFR\"}}","time_to_ready":1229.277792868},"url":"https://embed-ssl.wistia.com/deliveries/63ff4af0839dcb4011096e15fe28e50c9bc6832f.bin","created_at":1716863895,"segment_duration":3,"opt_vbitrate":1800},{"is_enhanced":false,"type":"hd_mp4_video","slug":"mp4_h264_848k","display_name":"720p","details":{},"container":"mp4","codec":"h264","width":1280,"height":682,"ext":"mp4","size":335595603,"bitrate":848,"public":true,"status":2,"progress":1.0,"metadata":{"max_bitrate":2130632,"average_bitrate":869137,"early_max_bitrate":763064,"av_stream_metadata":"{\"Audio\":{\"Codec ID\":\"mp4a-40-2\",\"frameRate\":43.066,\"sampleRate\":44100},\"Video\":{\"Codec ID\":\"avc1\",\"frameRate\":25,\"frameRateMode\":\"CFR\"}}","time_to_ready":1565.008044436},"url":"https://embed-ssl.wistia.com/deliveries/824b31ff12d17a2dd5d883d47ee20e677cba02bd.bin","created_at":1716863895,"segment_duration":3,"opt_vbitrate":3750},{"is_enhanced":false,"type":"storyboard","slug":"storyboard_2000x2247","display_name":"Storyboard","details":{},"width":2000,"height":2247,"ext":"jpg","size":738604,"bitrate":0,"public":true,"status":2,"progress":1.0,"metadata":{"frame_count":200,"aspect_ratio":1.8723849372384938,"frame_height":107,"frame_width":200,"time_to_ready":179.086432901},"url":"https://embed-ssl.wistia.com/deliveries/a4041962eeb05b7e34c0ddfa802b7501a7f51628.bin","created_at":1716863895},{"is_enhanced":false,"type":"still_image","slug":"still_image_1280x682","display_name":"Thumbnail Image","details":{},"width":1280,"height":682,"size":471407,"bitrate":0,"public":true,"status":2,"progress":1.0,"metadata":{"av_stream_metadata":"{\"Video\":{}}"},"url":"https://embed-ssl.wistia.com/deliveries/176f21253a8310aa48dfb4e16a4be8fd.bin","created_at":1716867283}],"branding":false,"createdAt":1716863895,"distilleryUrl":"https://distillery.wistia.com/x","duration":3089.0,"enableCustomerLogo":true,"firstEmbedForAccount":false,"firstShareForAccount":false,"availableTranscripts":[{"bcp47LanguageTag":"en","familyName":"English","familyNativeName":"English","hasCaptions":true,"hasVideoStream":false,"name":"English","nativeName":"English","wistiaLanguageCode":"eng","language":"eng","ietf_language_tag":"eng","alpha3_terminologic":"eng","alpha3_bibliographic":"eng","iso639_2_language_code":"en","english_name":"English","native_name":"English","right_to_left":false,"alpha3Bibliographic":"eng","alpha3Terminologic":"eng","ietfLanguageTag":"eng","iso6392LanguageCode":"en","genericName":"English","genericNativeName":"English"}],"hashedId":"w8w4716mei","mediaId":119802680,"mediaKey":"wistia-production_119802680","mediaType":"Video","name":"[Webinar] L2, workspaces, and more: Exploring the latest Propeller releases - APAC","preloadPreference":null,"progress":1.0,"protected":false,"projectId":5978430,"seoDescription":"a Webinars video","showAbout":true,"status":2,"type":"Video","playableWithoutInstantHls":true,"stats":{"loadCount":154,"playCount":59,"uniqueLoadCount":92,"uniquePlayCount":54,"averageEngagement":0.262518},"trackingTransmitInterval":10,"liveStreamEventDetails":null,"integrations":{"hubspot_v2":true,"google_analytics":true},"tagManager":false,"captions":[{"language":"eng","text":"Good morning, everyone, and welcome to today's webinar.\n\nWe are going to get straight into it because we have a lot of really juicy and exciting things that we want to share with you all. But today's webinar is l two lidar processing, workspaces, and more. Super keen to delve into the more because you're gonna get a little sneak peek of what's upcoming for Propeller, and we have a special guest on today. So as we jump straight into it, my name, if you haven't met me yet, my name is Angelica or Gels. I'm the marketing manager here at Propeller. I'm joined by Kent, who's our senior product manager. And our guest today is Dan Ripley, who's the central region New South Wales survey manager at Sceona.\n\nSo what's on the agenda for today? We have a mix of customers and people who might not be using Propeller before, so we'll just do a quick snippet on who is Propeller. Kent will run through our newest releases. Dan will run through a bit of what Asurion has been doing with the new Propeller releases as well as what's next for Propeller, and then we've got a dedicated q and a session at the end.\n\nSo before we jump into it, just a little bit of housekeeping. As People are jumping in. You might have a colleague that wasn't able to join today, or if you need to hop off early, this, webinar is recorded, and it will be in your email inbox within twenty four hours. So just be on a lookout for it and share it with anyone that missed out if you need to.\n\nWe also as it says, I dedicated q and a session at the end. So if you look at your Zoom box, you'll see chat and QA. Don't go into the chat. We're not looking in there.\n\nSo make sure that you're popping it in the q and a section, and we will have those answers ready for you at the end. So a little bit about Propeller. So our cloud based platform and our mission at the moment is to combine the best that GIS and survey technologies have to offer, and we're really building to make that map the central place where your teams can collaborate together. We started in twenty fourteen, and since then, we have over eighty thousand users across forty thousand sites worldwide.\n\nAnd so we're super excited that customers like Dan are joining us today as well as people that may have not be using Propeller at the moment to get to learn a little bit more about what's upcoming, and I'll shoot it over to that. So with Kent, we'll head over to our newest releases.\n\nThanks, Angelica. So we've got quite a few new releases to get through, here, and there's one that we wanna spend a little bit of extra time on. So I'm gonna move through these first few fairly quickly.\n\nWe the first up, we have some new formats for our ortho photo, exports.\n\nSo, essentially, this means when you are exporting part of your ortho photo via the measurements tab, via a polygon, you now have the option to select JPEG two PNG file or a KML as the format.\n\nIt's really simple. You can also obviously do GeoTIFF and JPEG, which were existing formats already.\n\nThe way to do this is to jump into the measurements tab, choose the polygon or create a new polygon, that you want to define the area that you're exporting.\n\nSelect export and then choose the option export via email, and then you'll get this option here. It'll just take, some time for us to process that, which is why we export via email. You'll get an email when it's ready, and you can download your export there. So, next up, we have a new integration.\n\nSo we now support Autodesk build via our, integration pushing files out of Propeller. So no more time, manually downloading files and then uploading them to Autodesk build. You can just jump into the outputs tab, choose the, select files, and then you'll see a button there that says push to. And, we already have a range of different options there. You can see them in the screenshot, and we've just added Autodesk build. So you can now export directly to Autodesk build via that integration.\n\nNext up, we have some new types of DTM and Contour file types that you can download again through the files tab in the or the outputs tab, the file selection in the outputs tab.\n\nThese are for use in third party software. These are lidar geo referenced, digital terrain models. So we have geo TIFF DTM and contour, files which come out as a DXF.\n\nThey, geo referenced the site CRS.\n\nAnd again, to access them, you just go to the outputs tab via files under the survey files category. You can select the format you need there to download those file types.\n\nNext up, we have some, improvements to the way that we've processed lidar data. Up until now, we've supported the, DJI l one, sensor, and we now support the l two, in terms of our processing.\n\nSo So it's fully integrated. We use the same process that was available before, except now that you can now if you have the l two sensor, you can upload your l two data in the same easy, scalable way, accuracy, all all the same as the previous sensor except, more options now in terms of the improved and enhanced sensor. So last of all, this is the topic that we're gonna spend a bit of time chatting about today. We have a feature which actually has, just been fairly recently released, which is workspaces.\n\nWorkspaces essentially are another layer of organization for your site.\n\nSo if you think, you have folders in your measurements and your, designs tab, Now you also have workspaces which sits above them and allows you to organize your site into any sort of, structure that suits your organization.\n\nSo the idea behind this is that it makes it easier to find the information that matters to you or to a team or to an individual on a team, or any other sort of collection of people that need to see kind of a a, a curated view of of your designs and measurements. So you can use your workspaces in a variety of ways. We're gonna chat to Dan in a in a few minutes about how how he's been using them. But you can really set up workspaces around, say, a team, like a structural team, environmental team, or a safety team. You might have a workspace for a specific set of reports, like inventory reports, monthly, accounting reports.\n\nOr potentially, you could have a workspace for your master designs.\n\nAnd that one works really nicely because we have this feature called links, which allow you to link design files from one workspace into another. And then they'll appear in the other workspaces read only, which means they can be safe and protected in your design in your master designs workspace, and people can use them in the other workspaces without you worrying that the, master design files are gonna be changed or deleted.\n\nSo what we might do is jump into having a bit of a chat about, how Dan has been using workspaces.\n\nA little bit of an introduction first.\n\nSo Ascione is the company that Dan works for. A global group develops and manages sustainable infrastructure solutions, a lot of work in renewable energy.\n\nAnd, the business really spans the entire value chain from design and construction through to operation and maintenance. And Ascione has been a big, part of Propeller's journey, I would say. But we've worked pretty closely with Dan and some of the other team members over the years in terms of developing product and, and getting feedback and and understanding as to how we can be more useful.\n\nAnd and also, Ascione has made pretty extensive use of the Propeller platform. You can see here, over two thousand users, a hundred and thirty four sites currently on the platform, Nearly one point seven million photos captured and ninety one odd thousand measurements created. So pretty extensive use. We do see lots of users in there doing lots of things in Propeller, and it's been really great to, to work so closely with the guys at Asciana and see that we're we're we're helping, you know, improve workflows on the sites there.\n\nLastly, Asciana has been a part of our early access program for a few new features that are either out now or coming out or very, very recently out. So WMTS, is one of them.\n\nSo supporting, streaming of our web map tile service out into other platforms like g GIS.\n\nWe have an API as well now that is available and also workspaces. And and and Dan and the team have been testing these features over the last few months, and we're gonna have a bit of a chat to Dan now about, workspaces and kind of, how the guys have been using that and the the value there. So maybe just to get started, dan, first of all, welcome.\n\nMaybe if you could kick us off by briefly describing your initial impression when you first sort of came across workspaces and started to interact with it?\n\nYeah.\n\nFirstly, easy to use. It was logically set up.\n\nIt was a great kind of addition to the Propeller platform.\n\nAs our company has grown over the last few years, we've hired a lot of new employees as well. So the number of users on each Propeller site grows, I didn't quite realize how many users we had until you showed that a moment ago. Like, yeah, that that's pretty impressive.\n\nAdding the workspace has really helped us to add some additional structure in our sites.\n\nSo that's that's been the biggest benefit for the most that that that brings some additional structure in.\n\nAt this point now, I guess you've been using workspaces for maybe a couple of months.\n\nHow have you integrated the the new feature into your daily operations? Like, what are some of the practical ways that you guys are using them?\n\nThem?\n\nSo so we use them to split our propeller sites into smaller project team specific sites. So that that visualization or that that plan, that strategy that you that your team had sort of envisioned as it been the solution is basically what what we've done. So, again, what we have, smaller specific sites sort of broken down that allows the independent sort of team functions to actually only give you the relevant data.\n\nAnd, do you find that you have folks who are across more than one team, or do you typically have people sort of confined to one team or or maybe one or two teams? How are you sort of setting that up?\n\nYeah.\n\nWhat we sort of how I describe it so we have obviously the the main Propeller admins who who manage the actual day to day that the back end side of Propeller.\n\nWhat what I've set up now is independent sort of sub admins that are responsible for their own workspace, And and those users have the ability that they navigate quite quickly through the other workspaces and and sort of publish cross publish between their their relevant workspaces. So sort of a tiered, user sort of permission structure at the moment with with the power users sharing the data between different worksites or workspaces.\n\nThat, that makes sense. So it's probably worth saying at this point, we have, there's two tiers of workspaces. Initially, the the the workspaces that are available to all customers, is just called workspaces, and and they're essentially public workspaces.\n\nSo everyone who's a member of the site can see all the different work spaces and interact with them. But we also have a new feature that's, coming out in the next couple of months, which is called private work spaces, which allows you to lock a work space down, and restrict it to sort of only, a certain selection of people. And, if you're not invited to that workspace, you actually won't see it in the platform, which keeps things on the left hand side panel there much tidier.\n\nHow beneficial do you see, that extra ability to control who goes into workspaces for you guys? Is that something that's important to you?\n\nYeah. I'm I'm pretty confident that a few other users would have experienced the challenges when a user goes in there and accidentally deletes something or moves something to a different folder.\n\nQuite often, we sort of spend a bit of time tracking down, re adding data back in to give us some extra control. And and Kent and I discussed this in the past. It is a word that Kent's solution is setting up folder strip workspaces that allow you purely only to share out of and and lock down who can accidentally quit with the data. It's been really beneficial.\n\nAnd in the past, we you know, you mentioned that that was a bit of a challenge. We obviously didn't have any features that weren't specifically designed to allow you to control data and protect data. Was it Propeller is, I I would say, philosophically, we're a fairly open platform. We we like the idea of data democratization and sharing data, but sometimes you have things that you just need to keep safe. How have you gone about that in the past in the absence of something like private workspaces?\n\nYeah. It hasn't hasn't been very pretty. It it it hasn't been very pretty.\n\nIn the past, it it's it's been a lot of trust and a lot of faith that people are careful.\n\nBut, again, as we've grown so much, I mean, we have some sites now that, you know, two, three hundred users on an individual site. And and the the the biggest appeal of Propeller for a lot of users is the ability to allow anyone to add their own KML or their own DXF file and treat it as almost a CAD light solution on on on in a cloud package. So we can't lock down that that that ability for that because that's the biggest appeal to Propeller is giving them the freedom. But allowing us to provide some structure, which is the workspace tool seems is, is definitely doing for us last provide some structure and restrict some of the manipulation of the data is is being really, really beneficial.\n\nRight. So I I imagine if you, if you have, you know, half your user base uploading DXFs and KMLs and random files that they've got from who knows where.\n\nTraditionally, the side panel could get a a bit cluttered, I would imagine.\n\nIf you now have the ability to give each user their own kind of sandbox private workspace, does that fill you with some confidence in terms of keeping things more under control?\n\nYeah.\n\nIn the past, we've relied heavily on the search function.\n\nAnd, okay, I have a feeling I I wanna look at something related to environmental project boundary or construction boundary or some would type a few characters of boundary and hope that the relevant data pops up. Whereas now, it's quite easy for us to set a singular workspace that has all the different boundary datasets related to that, to that workspace tag tagging their hidden away. What where workspace is also useful is it allows us to actually back up the data we would normally supersede. So we're not having to remove a bunch of the older data. We can file it away in a workspace that's for reference or for information and and then revert back to. So it allows our engineering teams to actually come and compare the newest design against the early version of the design against something even early, against earlier than that. There's quite a lot of iterations that that occurred during a project.\n\nSo it's it's giving that structure and allowing us to follow things away. It's been really useful.\n\nYeah. That's cool. That's that's actually an interesting point you make that I I hadn't quite considered, actually. It's a new concept to me.\n\nWe've been talking about internally workspaces being used for things like Teams, maybe maybe stages of project, maybe individuals. But you're talking about using workspaces kind of to segment time. You could have, like, a twenty twenty three workspace or a, you know, a h one twenty twenty three workspace to kind of keep things moving out of view and have only the stuff that's most relevant for the current time period. Is that is that a fair summary of what you described?\n\nThat that's correct. I mean, at the moment, I'm doing an awful lot of, civil design for our renewable projects, and and there's many design gates and and iterations of of these access tracks and and pads that are going through. I mean, some of our projects have up to three hundred and eighty four hundred kilometers of access track. So there's quite a lot of design tweaks and and adjustments, and we're always tracking, you know, design growth and and keeping an eye on the actual increase or decrease of quantities. So it allows us to go back through and review an earlier version of the design from three or four months ago versus a version of today. Like, some of these projects, I'm producing updated designs weekly.\n\nSo, again, understand there's a quite a lot of datasets that we would historically be staggered all the way through that one workspace. We're now filing away under under multiple workspaces. So design revision one, design revision two, design revision three, design revision four, and so on.\n\nRight? The individual workspaces we have in some of our civil packages.\n\nSpeaking of design revisions, I guess, one of the features I mentioned earlier was this idea that you can link design files from one workspace space to another, and indeed, you can link a folder and and therefore dynamically updated files within that folder from one work space to another. Have you, had a chance to make much use of the linking feature?\n\nYeah. The linking again, because we're giving sort of tiered, areas of authority. So the environmental team have the ability or the the the the understanding that, hey. We manipulate the datasets within the environmental folder.\n\nAnd if it's irrelevant updated, then when I've upgraded my new design, let's push that across through the construction team. And the construction team for the design work that I've been performing, the construction team will remove the links for the earlier versions of the designs and only push across the latest, most relevant civil design to the environmental teams. The environmental team can review, the environment team are aware whether it's a whether it's a special kind of heritage tree or where there's some, challenges and some creek. They've been doing a lot of creek investigation works to make sure that I've maintained that kind of fifty meter offset from a creek, a water body to a civil design.\n\nSo it allows the individual team leaders to actually restrict and only share the relevant data across.\n\nSo saves a lot of time. It saves a lot of, a lot of questions from the different designs or different party streams of which data asking Yeah. Cool.\n\nThat so so it sounds like and correct me if I'm wrong.\n\nIt sounds like it's having some sort of positive impact on collaboration within the teams as well as just organization. Is that is that right?\n\nYeah. That that's a huge it's a huge beneficial. It it's been something that I I guess I believe you guys first sort of spoke about this probably a few years ago now. It's how sort of the missing piece that we need, and this is before we had grown so much as well.\n\nWe're always growing. You're gonna be hiring new new new new people. So this is that missing piece that gives us that structure to help tidy up and and and kind of put in these individual buckets of information that are relevant to the actual task at hand. So it saves a lot of time as well, and it just saves a lot of a lot of miscommunication.\n\nThat's, that's good to hear having having worked on it for so many months. It's nice to hear that, it is actually helping there. Would you say that given all of that, you feel somewhat more confident to have more users in the Propeller platform?\n\nBecause I guess we were talking earlier about, how you managed it in the past that that, you know, that you said a lot a lot of trust.\n\nAnd I would say, well, the organizations I've worked with, you guys are more about invite people in and just trust and hope that things don't get deleted. Other organizations are more like, well, let's just keep the number of people in Propellr fairly restrained.\n\nI I guess maybe if you could comment on where you are on that spectrum, and do you feel now with workspaces and especially private workspaces more confident to have more people in there?\n\nWe've had exactly both of those situations. Some projects are quite often, it's only ever been used by the construction team. So some some sites I've set up have, you know, ten to fifteen users in there purely from as your pilot, you just don't want people able to interrogate certain data that's not ready for construction. If it hasn't gone through all the individual design gates yet, and there's an issue with the design that we're aware needs to be fixed, having to explain to someone who probably shouldn't have reviewed that data at this stage that we're aware of that issue is being fixed, definitely occurs. So, yes, we hugely did limit a lot of our sites, the number of users that were in there.\n\nBut but looking through, now looking at the actual well, the few of the newer sites that are using workspaces, the number of users on those sites are are a lot higher compared to traditionally how we would limit the number of users in there.\n\nPropeller Propellogy is an awful lot.\n\nI guess there's sort of two tiers or the multiple tiers. There's two main tiers of users. There's sort of the power users who are getting in there and performing all those millions of measurements that we've seen. There's also a lot of other users that just wanna log in there and just have a look at the project and the latest design that's been pushed up, and they'll only spend ten ten minutes in there a week or a month. It's just to come in, have a little look around, and get back. Yeah. But setting up those workspaces and and then and allowing that certain data to be to be locked down a little bit more and and then it's individual buckets is is hugely beneficial.\n\nI can't really state exactly how beneficial it is because it just yeah.\n\nIt just this is the last before this workspace was on labor, this guy spent quite a lot of time re adding data back in that's been moved, re adding data that's been deleted. It's, yeah, it's it's definitely gonna be a time saver for us.\n\nIt makes sense. And I I think from, you know, from what I've seen, and I I I'd be curious to see your thoughts on this. It's one of those things that when you add it to a platform like Propeller, it it actually takes a bit of time or effort from someone like you to to structure it and be thoughtful about how it is best gonna serve you. Is that fair to say?\n\nThat that is. And that's that's something that what we're working through at the moment, and we've just sat down with one of the teams in one of the projects, is putting together a default structure filing system or workspace system.\n\nWhat I see happening in our future is that we have a default workspace structure that's used across all of our sites and all of our portals. So someone who's like myself who works across four or five different projects at a time or someone in more of a senior manager type position who's not directly looking with data all the time, someone from a finance background or someone from an accounting background or someone from a project reviews background to allow them to look at multiple projects quite quickly and have that exact same file structure, workspace structure, will will be hugely beneficial. I somewhat see that being the case across not just our business, though, but across all of the Propeller users. At some stage, I think there'll be a default industry standard workspace structure.\n\nThe reason why I say that is I'm given access to many portal instances of our clients' data. Some of our clients have Propeller captures, and that food feeds down to us.\n\nA lot of our joint venture partners all use Propeller as well. Propeller is sort of so well established in the similar engineering industry at the moment that we're quite often spending different time in different portal instances of portals. So, we're allowing Workspaces industry. It would be really, really, really, really useful.\n\nI thought it's sort of sort of kinda compared to sort of how you have the the new individual subclasses in an IFC folder. Sort of all this bucket of information goes into this workspace. This style of information goes into the this workspace, and it can be somewhat semi automated in that regard. When you're dragging in a new file, to Propeller, there'd be sort of a prepopulated drop down books. We have detected these sort of, instances of data in this file. Do you wish to add to this workspace, or do you wish to add to this workspace?\n\nYeah.\n\nIt's kind of the the sky's the limit now. We have these workspaces.\n\nWell, that that's cool because it actually brings us on to what the the next topic I was gonna sort of talk about, which is is feedback and, you know, potential improvements from here now that you've been using it for a while. It sounds like, a couple of things there that I heard, and you can feel free to jump on any of these and comment on them. One is maybe some kind of a templating structure, which allows you to create a template for how each work space is structured, and you could potentially roll out different ones or potentially the same one. And and and and, actually, we could potentially create them internally at Propeller so that new organizations don't have to start from scratch or new sites. Is is that's kind of one piece there.\n\nThat's correct. That that that's exactly correct.\n\nYeah. Cool. And then the other one is maybe a little bit smarter, which is some sort of automated, way of of detecting a file that's being uploaded or a measurement type that's being made and putting it in the correct workspace.\n\nThat's correct. Yes.\n\nAnd also bidding and allowing us as part of that process as well to add to multiple workspaces at once. I mean, there may also be an instance, where you may want to even add a design dataset to multiple sites at once. I I maybe, and may I potentially.\n\nBut but definitely that work workplace, so so that work structure across workspaces and the default template background in the background would be fantastic.\n\nIs there is there anything else that's come up in terms of feedback, either from you or from people who I'm I'm curious to hear how actually folks on the you you've been very close to the interaction with us, and we've been able to walk you through how how it all works. But But then, obviously, there's a lot of people on the site who are just seeing this thing appearing in their platform and having to get used to it. Do you have any sort of feedback that's worth talking about from other people on the team or, improvements that people have suggested to you?\n\nWell, we're we're pretty lucky. Civil engineering seems to be a bit of a conservative industry where when no one really got in there and went wild with the workspaces.\n\nIf a few, individual users created their own workspace for a little while to sort of play around, but but not really no. No. No. We went wild.\n\nWhat I did benefit on one of our projects, though, and it's sort of still a a work in action, is just engaging the individual, what we nominated, sort of power leaders or power users that are responsible for each of the team streams and having them give a bit of a breakdown of the the folder structure underneath the workspaces and and getting a bit of continue that collaboration that Propeller allows is the benefit. Kind of reach out and don't feel too, too kind of rule by decree up above, and definitely just kind of be collaborative is is a house and is beneficial.\n\nThat that makes sense. And and, actually, the the the sub feature of the workspaces ecosystem that might be worth talking about is this new permission called create workspaces, which either allows a user to be able to create new ones or not. Is that something that sort of fits in with those sub leaders that you mentioned there, or do you would you do you feel like you'd give create workspaces permission to everyone and let people go completely crazy? Or how do you how are you setting that up?\n\nNo. No. That that's definitely something that that I believe will evolve a little bit more with yourself and the rest of your team is how we actually treat permissions. There's still probably a couple little tweaks that that I I would really we really approve, but still still evolving. We're still learning how how to use it exactly when it comes to permissions. But but, ideally, it's I I see the workspace as as essentially breaking the site down into subsides.\n\nSo it's the same propeller capture in the background. It's the same image. It's the same three d dataset, but using the workspaces to actually lock down the the individual streams into their their own workspace. Lockdowns are great, but limit their their their their ability to perform work in that individual workspace, and that way they can still retain their free autonomy. So the ability to give a user the free rein, the free full admin control inside of an individual work space. Whereas as soon as they navigate outside of that individual work space, then suddenly they're reverted back to a view only sort of permission set.\n\nIs how I see the future for us being be being best.\n\nYeah. No. That makes that makes sense. That's one we've definitely been considering. And I think as we continue to evolve the feature, we'll get maybe a little bit more granular with with how those permissions and access kind of control tends to work.\n\nI guess, last few questions here. First of all, in terms of your, you know, your recommendation. First of all, generally speaking, do you do you recommend that other organizations give this a try? And and and if so, what advice would you give them to both get the most out of it and also make sure that, you know, that they're not there's no traps for young players or or anything that they could avoid.\n\nI definitely, definitely, definitely recommend using the workspaces. That's something that again, I I can't remember exactly when we first started to have conversations about some some kind of private workspaces and data structure. I feel it was a while ago.\n\nHighly recommended.\n\nThat's definitely the the kind of the next logical step required to to to allow larger project teams to to access the the benefits of using Propeller and hosting data design data in Propeller.\n\nBecause I I sort of touched on earlier. Due to the the size of our projects, and the number of users, I mean, we have actually one portal, I think, has over nearly six hundred users in that singular portal.\n\nSo so it's definitely beneficial to to manage large, large use yeah. Large number of users across multiple multiple sites. Definitely, a large number of users across multiple portals. This has been really useful.\n\nSort of in the past, we would we would be duplicating data across multiple sites. In a singular portal, we were duplicating the same captured propeller data across multiple sites and using that as a way of limiting limiting the design data that individual users could could actually view. Voice of workspaces now, we we we don't really have to be doing that process. We can lock things down a little bit better that way.\n\nAdvice, as I was gonna touch on earlier, just treat it as as a way of managing data to kind of sort it into raw buckets of of information, and just try to maintain that same folder or workspace structure and then folder structure across all of your sites and portals, just to really allow Quite after, we have quite a lot of users who spend time on one one project, one of our construction projects, and they'll change it across another project. And the furthest thing they wanna go do is get access to our internal GIS, and our internal GIS has a fantastic pre nominated file structure already. But when it comes to the Propeller, our users are always asking for how do we get some structure similar to what we saw in the GIS. How do we get that that that kind of recloning of those layer structures across? So now now we're able to do that. So definitely, definitely recommend it for that. So it's reducing frustrations, reducing time, reducing a lot of questions.\n\nSo Cool.\n\nThat's great that's great to hear. That's really good to hear, and I'm I'm sure, you know, others who are thinking of using it will appreciate the the advice that you have there in terms of how to get get started.\n\nI guess just looking towards the future now, we we've sort of seen this thing that we've built in the platform as a as a starting point, I guess, and we're expanding a little bit in the in the future with, private workspaces.\n\nBut you said earlier, the sky's the limit. I'm curious if you have any sort of more specific thoughts around how you see the feature evolving into the future and and potentially new ways as you get more and more used to it, that you may integrate this or the future additions to this into your operations?\n\nI think I I definitely can't repeat it enough.\n\nI think it's just giving that uniform structure so that when anyone logs in, they know exactly where they're looking.\n\nAnd that's sort of, how it works for an example is as soon as we receive any design data from a design house, all that design data is essentially coded at a at a at a at a at absolutely granular level. So each designs, and puts it all straight away into a structure that all of us all of our surveyors, all of our users inside of our software know exactly what they're looking at, where it's stored at.\n\nIn the future, I I see Propeller doing something almost identical, where as soon as a dataset is brought in, it looks at the actual alphanumeric coding, the the the the code or the the text that's used inside of that file, and starts nominating that into different workspaces. I also see a world where Propeller brings in a singular dataset. Inside of that singular dataset, it's containing environmental data. It's containing structures data. It's containing payment data, but straightaway, so sorting that into the individual workspaces and giving them a bit more a bit more automated structure, and saving us, yeah. But especially with the AI tools, the way they are at the moment, being able to sort of sort sort things away that any user can hop into any platform, any portal, and and know exactly where to find their relevant data.\n\nThat's, that's a really good, really good point. And, it it brings up another question, which is a little off the cuff, but I'm I'm curious actually. How do you guys think about AI at the moment? It's obviously the buzzword. Everyone's talking about it. We we hadn't sort of necessarily planned to chat about this, but if you've got any thoughts, I'd be I'd be curious to hear how you're thinking about it.\n\nWell, It's another tool to utilize. Right? So so there's sort of some sort of apprehension of some people. You know?\n\nAI AI took our jobs as sort of potentially is gonna reduce, But I don't see that at that at all. The reason why I say that is surveying as an industry, we we've undergone so much innovation over the last fifteen to twenty years. And And I don't remember things like machine control systems. As soon as machine control systems come on-site, that's it.\n\nYou will no longer need any more surveyors. So no more surveyors needed. Surveyors will be redundant. But it's the exact opposite.\n\nIt's just the tools allow us to option here and and design a lot more. And why I see AI is really, really useful is at the moment, a lot of our designs are only taken everything's time poor.\n\nEverything's time constrained on time. And our designers are only given this small little window of time to push out the optimal solution.\n\nAnd and those designs aren't fully refined enough to provide a full understanding of the requirements of constructability. And what I mean by that is if we take a drainage line, for example, to install that drainage line, we need to provide some benching for an excavator to and a and a worker to safely enter that trench. I see AI tools straightaway being able to, in that situation, instantaneously, drainage lines created, then how does that benching suddenly influence the rest of this flow on effect of the construction around it? Is there a barrier that that's also scheduled to be under construction at that same moment?\n\nWith AI tools, we'll be able to bring these independent design elements together, throw in the time component, and quickly review an option here and suddenly flag an alert, that there's an issue here. So I see AI as being able to save a lot of time to allow our engineering team to focus on the biggest areas of concern as opposed to, at the moment, spending so much time trying to bring all these pieces together and figure out in their own independent silo how their work depends somebody else. And it impacts somebody else in the independent silo. So AI bringing all those independent silos together.\n\nIt's going to speed things up and and and give us a more completeness on our designs.\n\nYeah. That's that's that's a cool way to think about it, and it sounds like a way to think to to spend your, cognitive energy on the things that are important. You know? Kind of take take the small stuff off your plate and focus on, you know, the bigger challenges and the the the harder things to solve, I guess.\n\nYeah. I mean, I there's tools that I'm using at the moment that some people would define as AI, but it's, you know, it's it's a brute force, brute brute force design development, and then it'll reduce, you know, two or three million design options, configurations down to a selection of ten to twenty. And of those ten to twenty elements, I'll go through and review those ten to twenty and then decide which of the sort of three or four you then progress to the next stage. So it allows us to take a lot of those assumptions we make in our stomachs and actually put them up side by side quite quickly and discard those assumptions.\n\nThat's that's how it's it's kind of looking at probably the statistics. It's not really replacing any of us at all. It's just allowing us to do more focused focused and and important work.\n\nYeah.\n\nCool. It's, it's it's it sounds good.\n\nIt's a promising future. I know it's slightly off topic. But I guess in terms of our main topic here, workspaces, is there anything else that you would want to to say to to to to those watching? Any other thoughts or comments or or feedback, before we move on?\n\nI believe that there's that there should be no real if there's any reservations potentially about grumbling users, I did have some potential some worry at times about enabling in our portal at first. So both Rhiannon and I had some conversations with Ken about kind of which portals do we turn it on? Is it going to be a bit of a nightmare?\n\nI I was apprehensive at times. In hindsight, there's no need at all. There's no big fundamental changes. No big at first, all you'll see at the top is just a singular little workspace sensor, essentially new folder substructure.\n\nIt doesn't change anything fundamentally. It doesn't break anything. It doesn't scare anyone away. It just puts an extra little sort of button at the top.\n\nAnd then as far as setting up workspaces, I I just set them up, after hours at night or on the weekends so that when the team can make it up on Mondays, hey. I've just sort of put the few things in these other little buckets, and and, let let's see how they work from from there. And and the teams will be definitely welcoming. So but that's something we've been asking for for a while.\n\nThe teams have been a company's been screaming out for something like this, some some structure. So it's it's fantastic. Definitely no apprehensions. No no no reservations about using it.\n\nCool. Well, that's good to hear. It's it's good to hear. Well, I guess, thanks for that. That was a a great chat. As always, it's good to chat with you, Dan, and, we'll keep we'll keep moving on through here in terms of, the webinar.\n\nNext up, we're gonna have a bit of a chat about what's coming up next for Propellr. These are some projects, and features that are in, development already and that you can expect to see in the upcoming months. So, let's have a look at what's up first.\n\nSo first of all, I mentioned this earlier. We have, WMTS and the API.\n\nNow this is, along with private workspaces, will be a scale to your feature. So it's a paid premium feature.\n\nYou'll get access to those three features. WMTS web map tiles service is the ability to stream propeller map data. So the maps themselves, the ortho photo and digital train models out to other platforms using a simple URL.\n\nSo this is a quick way to get your, propeller maps into, GIS platform, for example, whether it's ArcGIS, QGIS.\n\nAnd then the API is a a little bit more of a technical feature. You need to have some development chops on your end to sync up to our API and access the endpoints. And once you do that, you can actually, access more of the Propeller data and pipe it into your systems, as you need. So we're really going here for this interoperability with Propeller. We realized that, our customers work with more than just the Propeller platform, and we wanna make it as easy as possible for data to both come into Propeller and out of Propeller to make the workflow as seamless as possible.\n\nNext up, we've got, better drawing and markup. So, this is a project that I'm actually currently working on right now.\n\nOne thing that we've realized, we've had some surveys go out. If you're a user of Propellr, you've probably occasionally had a survey where it's asked you, you know, how likely are you to recommend Propellr to a friend? And, and and then often we ask why. And one of the things that's come through in those surveys is, look, drawing measurements is a little bit clunky.\n\nYou sort of have to click new measurement and then find the measurement in this big box, and that can be a little bit awkward. And then I save it, and then I have to go and do another one. And what we want to do and what we're doing in the next couple of months is improving the way that you draw measurements. So you can see here, we have a new toolbar that we're going to be putting over the top of the map, so you'll always have access to your point line and area measurements.\n\nUnderneath of those, you'll have all the templates that you need. We're moving the measurement details across to the right there so you can scan the list of measurements or drawings on the left, or you see the details on the right.\n\nAnd there's this really cool new feature that will be, coming out, which is auto save, which basically, if you toggle that on, you create a whole bunch of measurements. It saves each one instantly, which allows you to essentially just draw or scribble on the map in the same way that you would with Paint tool, Bluebeam, that sort of thing. All those measurements, which will be gradually moving towards calling them sort of drawings as opposed to just measurements because you might wanna be doing you might be doing a markup, will be exportable as well. So you can do all your markup in the platform as well.\n\nNext up, and I think this is the last one, is alignments. So this is some feedback we've had for a pretty long time, I would say. I think from people like Dan included, those folks who build long linear projects like roads and pipelines will have be very familiar with the concept of alignments. And depending on where you are in the world, you call it either change or stationing.\n\nIn Australia here, we call it, we call it chainage. And you could get it into propeller in a way as a DXF, but there was no real way to reference the stations and offsets or the change in offset with your mouse cursor. So if you wanted to know, you know, what's the change in offset of a particular stockpile based, like, in the Propeller platform, you couldn't really do that.\n\nAnd so very, very soon, we'll be releasing the ability to import commonly accepted files. So XML files of state of, alignments, including the stations and or changes, and you'll be able to activate those, stations. You'll be able or sorry, the alignments, which will allow you to see the, station and offset change and offset of the cursor and also edit the stations as well. So you can change the tick marks or change the spacing between the stations, as well. And then following on from that down the track, we're looking at even more improvements, things like automated cross sections being generated for every station and then stored in a nice report that you can you can then look at from month to month, measure your volumes along the, along the alignment from month to month, all of that kind of stuff, is also on the road map. So does you seem reasonably pleased by that, Dan? Is that a, is that a good one for us to be working on?\n\nThat one's pretty exciting. Safa, all of those are, but definitely the, the, the staking, if you had the set of super alignments, that that'd be really useful.\n\nYeah. Cool.\n\nWe're I look forward to testing those.\n\nThat's for sure.\n\nYeah. We're we're, we're looking forward to that one. It's been on on the play on the on the on the back burner for a little while, so that's gonna be good.\n\nNext up, I think we might be into some q and a.\n\nThank you, Ken. And thank you, Dan, for telling all about work spaces. So as we mentioned before, there is a q and a box that you can drop some questions in. And then, also, like, if you have things that after you've watched the recording, you have questions like, oh, hey. I've played around with workspaces now after Dan said how he uses and structures it, and I have some feedback to give. Like, you can reply it definitely to the email.\n\nSo first one for you, Kent, this, question came actually before you mentioned private workspaces.\n\nSo maybe it will be more towards, like, the current public version. Will the measurements slash designs from workspaces be visible in the default workspace collectively for everyone else?\n\nOkay. I think I think reading between the lines, what, what this audience member is asking is, is there a sort of a unified view that shows you all the measurements and designs in a sort of a default space? So the answer to that is actually no. The whole point of Workspaces is to is to separate things out, and be able to view things based on the organizational structure that you've put in place with the workspaces.\n\nBut, that being said, I think that it's definitely one of the ideas that we've been considering.\n\nAnd the other idea that we are considering is like a universal search. Because at the moment, the search works within the workspace that you're in. But, obviously, you might be just interested in where's that file. I can't remember which workspace it's in.\n\nSo we definitely wanna improve the flow across workspaces, but maintain the organizational benefits, that we get from having things separate. Just on the default workspace, by the way, that is the default workspace, there's nothing special about that other than the fact that it's the original workspace that contains all your data. Once you move things around, you can rename that workspace. You can if you have private workspace, you can make it private.\n\nYou can delete it.\n\nAnd there's nothing sort of special in the way it behaves other than it was kind of the the original gangster workspace, that you had at the at the beginning.\n\nBrilliant. And, yes, another one that's more on the projects that you're working too on Kent, an alignment tool.\n\nWhen or if it will allow bun height calculations for quarry haul roads. Is this on the pipeline?\n\nIt's not. I see that's Phil. Phil, it's it's not yet, but we it's we're pretty early days that the with alignments, the first step for us is to literally even support really the visualization, import, proper usage of alignments.\n\nFor those of you who are really into the tech details, one of the things that we're doing with it, we're actually supporting, you know, a whole bunch of the different spirals that go into transitions on road curves and things, which in the past, we didn't do that. We sort of worked our way around that with sort of polylines. We're gonna support the proper spiral. So the intention here is to really do alignments properly, get a foundation, and then build off that. So in regards to that, Phil, if you wanna reach out to us, I'm very happy to jump on a call with you. And I'd love to ask a whole bunch of questions about allowing bund height calculations for, quarry hall roads because we we really wanna just go wide on, understanding the potential use cases for for the features that we're building. So, yeah, absolutely feel free to get in touch about that.\n\nYeah. Brilliant. And then, Ken, is exports your team or not? Because then we can just leave this question to the wider product team.\n\nYeah. Probably is one for more for the for the wider product team. I do know the road map fairly well. So, I don't think that's on the road or that question. Sorry. Which is we use vertical face imagery model function quite often.\n\nWill this ever be available as an export? It's a really good question. I think in the past, we've tended to not publicize the whole vertical face imagery piece that much. It was really only because of it it led to sort of slightly slower processing, and we we we know we we want customers to get their data as quickly as they need it.\n\nBut that's improving, and we're seeing more and more usage and and and utility in having vertical face imagery.\n\nSo I would say, I don't think it's on the road map at this point, Brett, but it's it's definitely in our minds, and it's definitely something that's on the boil as opposed to something that's sort of sitting there in the fridge.\n\nThat's probably the best answer I can give you off the top of my That's super helpful.\n\nAnd, as for everyone in this, if you do have any more questions that are, like, specific or, like, little requests that you would love to see as Dan has shared with us, please always email and reply to it. The last, question that we'll just use to round off is for you, Dan.\n\nKent did mention the use of WMTS and API. If you could talk a little to the workflow and overview of what you're using that at Asurion and what you're using that information for and what platforms you're talking to.\n\nOkay. So, we have quite a lot of myself personally, so I would connect the, WMST into, say, global mapper and and and do some sort of work in there. GlobalMap is just sort of a light GIS solution.\n\nThat that's myself, whereas the actual, we have an internal fantastic GIS team as well that has the ability to ingest. So what they've been doing is pushing across a lot of the Propeller data direct through our wider GIS packages. So it's saying if you log into a GIS suite, g GIS login on one of our project in particular. But then you will see in the back end all the Propeller data aerial imagery. In the past, what we were doing was downloading manually the data from Propeller, bringing it to global map, but converting, converting across to a different format.\n\nAll of our GIS imagery in the past was all manually uploaded then, whereas now it's saving so much more time to be able to push that across.\n\nThe API calls, I'm not too sure if our GIS team have started to use that yet, so I can't quite elaborate on that. But but I know we we do some work with the API calls into, FME bench at times.\n\nBut but I'm not too sure, but definitely the the the WST. And I think Ken mentioned something in the past. There's some additional not just WST. There's some additional, kind of ability to share vector data similar to what we do with imagery on WST. Is that something Yeah.\n\nThat's I we talk about that. That's a real sneak peek about into the future, but that's cool. We we like talking about that and sort of sharing where we're thinking.\n\nWell, that one made me really excited.\n\nThat's why I brought it up.\n\nSo Yeah.\n\nYeah. That one's called WFS, which is, I can't remember off the top of my head what WFS stands for. Web feature service, maybe. But, essentially, it's the same thing, but for the shapes that are on the map, the vector shapes that are on the map. So if you draw a polygon and it has various attributes, and as long as it's in a standardized format like GeoJSON, which is the direction that we're moving in, We can stream those shapes out as well as the map itself, which makes really helps, I guess, for the interoperability, into the platforms that you mentioned.\n\nBrilliant. So, thank you everyone for joining the webinar today. You got a lot of sneak peeks of what's coming, even super futuristic, but you can at least see, like, the journey that we have of listening to our customers. I know Dan's requested a lot of things that we've sneak peeked as well as well as workspaces. So, definitely, if you're a customer of Propeller, have a little bit of a play. As Ken said, you can rename the default workspace.\n\nYou can create your own little ones just to give your teams that and we'll also share some information about workspaces in the webinar, email after. But thank you to Dan and Ken for today's session, and I hope everyone has a great day. Thanks for joining. Bye.\n\nThanks, everyone. Thanks, Dan."}],"hls_enabled":true,"embed_options":{"opaqueControls":null,"playerColor":"#ffdd00","playerColorGradient":{"on":false,"colors":[["#08111d",0],["#6e7783",1]],"on":false,"colors":[["#08111d",0],["#6e7783",1]]},"plugin":{"captions-v1":{"on":"true"}},"volumeControl":"true","fullscreenButton":"true","controlsVisibleOnLoad":"true","bpbTime":"false","vulcan":true,"stillUrl":"https://embed-ssl.wistia.com/deliveries/176f21253a8310aa48dfb4e16a4be8fd.png","unalteredStillImageAsset":{"url":"https://embed-ssl.wistia.com/deliveries/176f21253a8310aa48dfb4e16a4be8fd.png","width":"1280","height":"682"},"roundedPlayer":12,"bodyFontFamily":"Nunito","headerFontFamily":"Montserrat","buttonFontFamily":"Nunito","pageBackgroundColor":"#ffffff","contrastIcons":true,"newRoundedIcons":true,"shouldShowCaptionsSettings":true},"embedOptions":{"opaqueControls":null,"playerColor":"#ffdd00","playerColorGradient":{"on":false,"colors":[["#08111d",0],["#6e7783",1]],"on":false,"colors":[["#08111d",0],["#6e7783",1]]},"plugin":{"captions-v1":{"on":"true"}},"volumeControl":"true","fullscreenButton":"true","controlsVisibleOnLoad":"true","bpbTime":"false","vulcan":true,"stillUrl":"https://embed-ssl.wistia.com/deliveries/176f21253a8310aa48dfb4e16a4be8fd.png","unalteredStillImageAsset":{"url":"https://embed-ssl.wistia.com/deliveries/176f21253a8310aa48dfb4e16a4be8fd.png","width":"1280","height":"682"},"roundedPlayer":12,"bodyFontFamily":"Nunito","headerFontFamily":"Montserrat","buttonFontFamily":"Nunito","pageBackgroundColor":"#ffffff","contrastIcons":true,"newRoundedIcons":true,"shouldShowCaptionsSettings":true}},"options":{}};