Export Asset Data from BIM 360 Field and Revit to Create Value at Handover

KATIE: We do have a portfolio to invite you to join-- our Autodesk University, 2017 portfolio. You can request a coffee beverage from Adrian. You can send us notes, ask us questions, get a feel for what the occupant side of the app looks like. So there are the instructions and if you don't catch them now, we'll help you afterwards.

This is what we're here to talk about today, which is exporting asset data from BIM 360 Field and Revit. So in today's class, we're going to be talking strictly about how to populate Ops. We're going to show you briefly how to assign a ticket and what a ticket looks like from a technician standpoint. Tomorrow, we have a class in the morning that's all about ticket management.

So today, not talking a whole lot about ticket management, technician management-- just talking about asset handover. But if you're interested in ticket management, I highly encourage-- 10 Ways to Rock with Ops, tomorrow. So why did we decide to do Ops? Well, we went out and we spoke with hundreds of building owners and many of them looked at us like this when we asked them-- what happens after handover? How do you know what you have in your building? How do you know if you're hitting your PMs. And they didn't. There wasn't a good way-- consistent way to hand over the asset data.

And then furthermore, when we spoke of them, half of them didn't have a software solution, and this half includes spreadsheets. So there's a whole bunch of owners out there managing their buildings and their PMs with their Outlook calendar and spreadsheets. And I said, well, there's got to be a better way to do this. And when you're using these other methods, it's not uncommon for it to be two years-- after getting the keys to the building-- that you finally have a populated system.

So so I said, well, Autodesk has all this great design data. There should be a way to press a button and just send that data over to your asset management solution. It shouldn't take two years. So this is one of the problems we think about when we design Ops.

Another problem that we think about is when we were out there doing this research, talking to these building owners, we said, why are your technicians still working on little notebooks? Why are you still handing out sheets of printed paper in the morning with the tickets? And we found that over half of workers already had phones in their pockets and they were using them to take pictures of their kids and they were emailing around and posting to Facebook and other social media sites.

And we said, well if can do that, you can absolutely update the status of a ticket and comment on the conditions of your asset. We just need to enable you and give you a software that will allow that. So out of that came BIM 360 Ops. So Ops is all about-- mobile first asset and maintenance management.

And what we think about is, just like BIM 360 really focused on bringing the iPads out to the construction site and tracking that, well, bringing your asset data and your ticketing data into the building with your technicians. And when you can focus on the technicians, you can capture what's really going on in the building, you can get the most accurate information, which then enables your owners, through their reports, to better manage the building.

And finally, we have these really great models that have been developed throughout construction that have all this very accurate information about the asset data, and if you have a way to reuse that information and simply have it flow into your asset management system, it can be so much better for all of us.

So those are the benefits we think about when we think about handover is how to improve our experience, how to shorten that 18 months to two year delay, how we can enable owners to start their PMs on the first day so that they are maintaining their assets within the warranty expectations, they have all the documentation for those assets. And then ultimately, how that enables them to have a more efficient building and a more efficient team.

So today, I'm up here with Adrian. Adrian is our chief architect on the BIM 360 Ops team. And I am our product manager and we're going to show you about how to export assets from Revit. Then we're going to show you about how to export assets from Field. Once you've done that, you're going to find do you want to make some changes to the data. So we're going to talk about how to do that using a spreadsheet-- to either add data from buildings that don't have the model and aren't in-field, or how to modify the data that's already in Ops.

We're going to create a preventive maintenance schedule for an asset. We're going to assign that to our lovely technician who is then going to show us the workflow. And then finally, we'll circle around and look at some reports. So if there-- yes?

AUDIENCE: Will this session be recorded?

KATIE: This session is recorded. Yep, that's why we're wearing this lovely microphones up here. All right, and then I'll pop this slide up again at the end of the session, but these are other classes if you're interested in BIM 360 Ops, so grab a shot of him quickly. Come up and ask us afterwards.

Again, the 10 things your Facilities Team Must Do to Rock with Ops-- highly recommended. That's going to be the second half of this presentation about how to manage your tickets. So with that, that's the end of our slides. Let's go into-- all right-- so first, we have a portfolio that we've created in Ops. You'll notice, I'm at the portfolio dashboard and I can easily swipe through and look at my other buildings in this portfolio.

Now today, we are in a conference center on 201 Sand's Avenue, Las Vegas. And what we want to do is we want to bring in the assets. So we have our Revit model. Now first thing I will tell you in bringing in a Revit model, please do not export the entire model. And do not export all of the elements in the model, because you will very quickly have 20,000 to 30,000 assets that do not need to be maintained in your asset management system.

So what we're going to do-- always start with one. Today, we're going to start with a couple of more. But what you'll do is you'll select your assets and then filter. Please, please filter. We're going to bring in mechanical equipment today.

So now that we have our much more manageable solution, we're going to go to our BIM 360 Ops add-in. Now we downloaded that from the portfolio settings down here in the lower right, just at the bottom. But we need a code for our building. And the nice thing about this code is it's one time use, it expires in an hour and you don't have to have access-- there we go-- you don't have to have access to Ops to get access to the code.

So if someone has a model and I don't want them to have access to Ops, I just sent them the code. And then they come up here and they hit Export with their handful of assets selected. They simply paste in the code and then they hit Submit and Confirm.

So what assets do you want to export? You want to export assets that will be maintained, ideally assets that have a maintenance schedule of a year or more frequently. If it doesn't require a maintenance schedule, don't export it. That's just more data that your technicians have to carry around on the phone, more data that has to be maintained that won't be maintained, which makes it harder to keep the facility operating over time.

So our Wi-Fi in here is sucking wind. All right, well, our export failed. Yes, our Wi-Fi is not doing well. But we're going to come back over here. I believe Adrian has popped in an asset for us. So we have a couple that came on over here, our model might not have made it. And we can see, here's our asset record with-- yeah, our model is still coming-- our location information, our category, so that we can help with filtering, and then additional data that you may collect during the commissioning phase about that asset.

Next, I'm going to hand this over to Adrian. And Adrian is going to show how to bring in assets from Field.

ADRIAN: OK, so we've just completed a building-- we're doing hand over. We designed with Revit, but we built it with BIM 360. We used Field-- we've got lots of information in there from the installation commissioning of assets. And we want to get as much of that information into Ops as we can.

So we're going to start by-- I don't want to reuse the same building, so I'm going to create a new building. We'll just do that very quickly. We'll call this one the Venetian. And--

AUDIENCE: You are using that same [INAUDIBLE]?

ADRIAN: You can export repeatedly and it will update existing data. So if you decide, if things change, or if you want to add some additional assets and maybe you actually re-duplicate one, you don't get lots of duplicates. It does update.

I don't know what the Venetian's address is, so I'm going to call it onestrip. OK. All right, so it used geolocation to suggest a address, we'll go with that. So we're all set over here. And we're going to go over and look at Field. And with Field, we've got ourselves lots of assets. And if we look under More Actions, you'll see that there's an export to BIM 360 Opt's menu item right there. And at this point, I'm going to stop and remember the advice that Katie just gave us-- don't export everything.

I want to tell us a story about a customer I talked to just a few weeks ago. They had done, the GC had done a huge dump of information for Field Ops-- far more stuff than the facilities team needed. One of the things that came up was, chairs. The thinking was, well, chairs break, chairs need to be replaced, so we should have an asset so we could use that to maintain it. And I asked the facilities team, is it enough just to have a ticket that says, please replace my chair? And the facilities team said, yeah, that's all we really need. We don't need chairs as assets.

So with that in mind, I'm not going export this entire list. I'm going to shrink this way down and we're going to do this by using these filters. If you use filters, you know that you can filter your view here. And this is how we control what gets exported.

So if I filter by name, of course you can filter by type or bar code or any sorts of thing here. We've got a much more narrow list-- we've got pumps here, we know that pumps do need to be maintained, so that's exactly the kind of thing we do want to send over. So everything that's viewed here on this list, that's what's going over.

So if you tweaked your filters, you just look at the list, you say, this is the right list, check with our facilities team, they say it's right list-- let's go ahead and export it. Now this of course is going to look similar to what we just saw. We're going to generate a code here. And let's just hit the old Export button there. Oh, it's Windows, I'm not used to Windows. I'm doing this too fast.

There, that is the right code, I think. OK, it verifies the name, that's what we want. So we can go ahead and we'll export that. And let's see if-- this isn't going through with a Wi-Fi here, so this should hopefully behave a little bit better. And one thing we will do while we're waiting, this does take a couple of minutes, not 12 to 18 months, but a couple of minutes. So let's look at one of these assets that we are--

KATIE: Hit down there.

ADRIAN: How do you double click? Oh, there it is. So here's some of the information that is in field that we probably do want to hand over to the facilities team-- things like some photos, some manuals, PDFs-- great stuff for the facilities team, it would be great if we could just hand over all of this really easily to the facilities team. So let's go take a look in Ops and see how our export is doing. And we've got a bunch of them, it's not quite done, but we do see that P10-- the one we we're just looking at has arrived.

And if we expand that, you can see that we've exported a-- we've imported a bar code, so that's useful. The bar code that we added in Field is already there, so the facilities team can use their device to scan it and find it. We've got photos. And there are those manuals-- they've already been exported right here. So everything is ready for the facilities team to use.

We've got-- OK.

AUDIENCE: [INAUDIBLE]

KATIE: They'll come from Field. Yeah, so these attachments will be exported from Field. So these attachments are in the Field library.

AUDIENCE: [INAUDIBLE]

ADRIAN: Yeah, links--

KATIE: So the links can be here.

ADRIAN: Links get exported as links, so they will appear as links within Ops. We've exported a bunch of other information-- warranty information, things like that, manufacturer. There is no model number. And that's not because we failed to export it, it's because in Field, we just never entered that, because maybe they just didn't think they needed it.

So sometimes after you do an export, you discover that, it's not exactly what you want. The facilities team needs information, either some additional information, or it needs to be presented a little bit differently. So we want to maybe massage the information a little bit to make it a little bit better for facilities. And I'm going to turn it over to Katie who's going to show us how to do that.

KATIE: All right. Thanks, Erin. So we're in our asset list. And there's a couple of reasons for a spreadsheet import. One, on a lot of campuses, there's this brand new building with this great model, but there's also the building right next to it that was built a long time ago and has drawings, the actual old blueprint drawings and that's how that building was built. So we can bring in that information through a spreadsheet, or we can export out of another system to a spreadsheet and bring that in.

And so you will find the template that you need under Add. And you'll just download it, have it downloaded here. And the nice thing about this template is we just need the headers. So you don't even have to copy the data back and forth, because it's easy to lose track of a cell. Just copy our headers to the other spreadsheet, and that's how well do the matching.

And then what you'll want to do is you'll want to save it as a CSV. So we have here, what we're going to do is we're going to create some new assets through this update. Then we're going to modify this asset that just came in from Field-- it's P10. And we're going to add the model number-- AU2017. We can create any additional fields on the asset record by just appending another column at the end.

So we're creating a field called AU2017 and we're putting, hello world, into it. And then another common thing to do is to give the asset a new name, because we didn't like the way the name exported, especially if it comes from Revit, we might not like the way the name is. So I've already saved this as a CSV. And our new name is, Shiny New Pump, and you can see, we lost all of our formatting, because we're now in a CSV. But this is what we'll use for the import.

So we'll come back over here and we'll do, Import from CSV. And we'll go to here and we'll do our-- there we go. And then we'll see, P10 has now been updated as, A Shiny New Pump. The model number, AU2017 has been added to the record. And we've added the additional field of Autodesk University, hello world. So we updated that in that CSV sheet.

So this is how, the different ways that you can create assets within Ops through the Revit export, the BIM 360 Field export, or through the import from a spreadsheet. You can also create it manually just by clicking on Add. And when you're setting up your first portfolio, we highly recommend, just create one. See what all the fields are, get familiar with how it looks, then do your export again. The first time, just do one asset, it makes it much easier to clean up the data and then start bringing over your assets.

Next, we're going to look at scheduling maintenance. Are there any questions about this? We probably have time for one or two before we go on to scheduling maintenance.

AUDIENCE: You update information from the team?

KATIE: Yes, you can absolutely update information from the device and Adrian will show that in a little bit. Yep. Any other questions? All right, so we'll move on to scheduled maintenance for our pump. So on the asset record, we have scheduled maintenance and we just select that and we can add our maintenance right here and you can add as many schedules as you want.

And so we're going to do some bearing maintenance. And we need it to repeat. For this purpose, we're going to repeat every day. For the purposes according to the maintenance manual, it's every year, which if we just scroll down, we have every year. But for demo purposes, we'll do every day. We'll do a start date and we will also do an end date so we don't get a flood of tickets.

And what's nice about the scheduled maintenance is, once you set the schedule, it just creates a ticket for you automatically. You don't have to worry about it. And you can tell it how far in advance you want the ticket. So I want to see the ticket a week before, or I need to see it a month before for planning my team. And then I can assign a checklist. And we don't--

ADRIAN: We switched buildings.

KATIE: Yep, that's OK. So we can simply create a checklist with our-- we need to stop the pump, grease the pump. And you have the ability to have a library and transfer them. I did not do that. But you do have that ability. And go ahead and submit this. And now we have two tickets that were automatically created for this bearing maintenance.

And so it's-- scheduling your maintenance on your assets is as simple as that. And again, you can have as many maintenance schedules as you need for this asset. So next up, we're going to assign a ticket to Adrian. So we're going to come back over here and we're going to jump back over to our beautiful conference center. And we're going to assign this one to Adrian. [INAUDIBLE], sorry. Adrian is masquerading today. And then we need to switch the screen to you.

[SIDE CONVERSATION]

ADRIAN: How's that? We mentioned earlier that this was mobile first, that we were working with the technicians with the phones out in the field in mind, so we're going to demo on the phone. So I'm starting my day, I come in, I want to see what work there is for me. And so I can see on the Dashboard that I have a new ticket. So I'm going to start by taking a look at that. And there it is.

There's the ticket that was just assigned to me. So I'm going to get right to work on that. I'm going to open that up. And so I notice that this is associated with an asset. And all that asset information is right here available to me on my phone. So if I open this up, there's the asset. And so I've got lots of information about the asset. You can see that, when we export the documents--

AUDIENCE: [INAUDIBLE]

ADRIAN: OK, I mean, you could just sit here and do this occasionally. OK, let me jump back. So here's the record of the asset on my phone. All the documents that we exported, they're all available to me. So when I'm standing knee deep in water, I can just pull out my phone and take a look at the instruction manual. All the various custom attributes we might have exported from Field or Revit are available to me-- the manufacturer, all that information is right here. Photos, everything I need is right here.

There's also the bar code, which can be useful if I'm not sure what asset I'm looking at and I can just scan it. So I'm going to get right to work. Just so I have everything I need that I know what I need to do. So I'm going to go back to the ticket and I'm going to start with that checklist. And this is the checklist that we didn't see before. This is the checklist that we set up.

I'm going to get started on this and I'm just going to check off a couple of things as I do them. And if I go back to the ticket, you may notice appear under status, it's automatically been moved from assigned, which meant it was assigned to me, but I haven't started working on it. Because I started working on the checklist, it's now in progress. So if someone's sitting in the office scanning those two tickets can look at this and see, oh good, someone started working on this already.

So I'm going to spend some time dealing with it. And so I've wrapped it all up. Well, it wasn't a hard task. I spent 45 minutes on it. I'm going to enter that so that we can keep track of that. And I'm also going to add a comment just to let everyone know exactly what it was that I did. So go over here, and I told them that their bearings were all greased up.

So I've added a comment so we have a nice record of what happened. And I'm going to go back to the status. And I'm going to mark that it's completed. And now the people back at the office can see that this is completed and I can move on. And now I'm going to go on to my next task for the day and I'm going to hand the platform back over to Katie. Oh, and I forgot something-- well, I don't know-- this wasn't working a minute ago. Let me try it with one of these other ones.

This seems to be not cooperating either. I can access the 3D model right from here, but I pulled down a development build that's supposed to have some performance improvements. And hopefully-- it was working great this morning, and now that when a demo, it's not working. But yes, you have complete access to the model on here as well, as long as you're not using a development build that just came from the developers device two hours ago.

KATIE: Also, we had that question about how to edit an asset.

ADRIAN: Oh, yes, I meant to deal with that. If you're out in the field and you discover that the asset was mislabeled, there's some information about it that needs to be added, I can just hit the Edit button. So I can go here. So for example-- there you go-- I'm going to take the model number while I'm here. I'm going to take a photo of it. There we go. Now the next person to come along will have a photo for this asset. All this information can be edited by someone out in the field so that you constantly make sure that you're keeping your records of your assets up to date.

AUDIENCE: [INAUDIBLE]

ADRIAN: In the upper right corner of the asset record, you can see that there's a button that says, Edit.

AUDIENCE: [INAUDIBLE]

ADRIAN: So anything here, if you look at the very bottom, there's the thing that says, more detail. And in this case, I just have one custom field. The warranty end date is not a custom field-- warranty start date is. So if there's any custom fields that come in through Revit or through Field, they're going to show up underneath that more detail bar right there.

AUDIENCE: [INAUDIBLE]

ADRIAN: Right, if I were looking at that asset, we'd see the AU2017 there, or anything else that we wanted to add.

AUDIENCE: My question, also, most of our clients [INAUDIBLE].

KATIE: That's a good question. So options [INAUDIBLE] ticketing system. We do have an API available so that you can create tickets from outside of box using IT Devices. Tomorrow, we'll be showing using an AWS dash button. [? Six ?] box was mentioned today. One of our customers was looking at using [? six ?] box buttons, file the tickets. And we also have an API available from tenant portals for candidates to be able to file tickets. And then what customers are doing are exporting completed and closed--

AUDIENCE: Is you mic on?

KATIE: No.

AUDIENCE: Thank you.

KATIE: Exporting completed and closed ticket information to billing and ERP systems. But they're not trying to-- Ops isn't intended to be used in conjunction with another ticketing system where you'd be trying to keep the tickets synchronized. Yep.

AUDIENCE: [INAUDIBLE]?

KATIE: Absolutely.

AUDIENCE: [INAUDIBLE] so far?

KATIE: Yep. So we'll go into the reporting as our next step. Yep. Other questions?

AUDIENCE: [INAUDIBLE]

KATIE: Yes.

ADRIAN: So I'm going to go right here. Electrical box-- is it showing?

KATIE: Let's make sure.

ADRIAN: Electrical box-- we can add a category, call it, electrical. And do whatever else I want. Let's give it a better name. Can I do the name from here? Yes, because I have to hit the Edit button. And there you go. I just created a new asset in the system.

AUDIENCE: I have a question regarding, that if you have conflicting data between say, something that you just added in Ops versus something in Field, what does it-- who wins, I guess? If you were to re-import field data, but you changed the model number in Ops, is there some kind of fact check, or does one just override the other, back and forth?

KATIE: So if the field has been changed in Ops, then it should not be changed. If the field has not been changed and you're doing a second export from field with new data, then it'll be updated. But we definite-- again, we don't recommend trying to keep the data synchronized. So work in field, do the construction and then when the project's over, do a handover. But don't try to keep going back and forth, because questions like that come up and it does create opportunities for error absolutely.

AUDIENCE: [INAUDIBLE]

KATIE: Yes. So one of the other things I show quickly on the phone, Adrian, are locations. And Adrian touched briefly on bar codes. So in Ops, we have the ability to have multiple bar codes per asset. How is that helpful? Well, you can bar code the individual asset, but you can also bar code the system. So if I capture the bar code of the system, it will filter the assets that make up that system.

Our locations also have a bar code. So if you have bar codes on the door jambs, especially like a mechanical room, then you can go up and scan that bar code and you'll get a filtered list of the assets in that room, or you can see the other information for that location in there.

ADRIAN: I just tried now to use this bar code, but apparently we lost that bar code on-- when I-- so never mind that. Yeah, we can look over here at locations. This one here I think has locations. And so we can see from here how many tickets were in a given location, how many assets are in a location, and so on.

KATIE: And a good thing to put in your location record are your light fixtures. Please do not create assets for every single light fixture or electrical fixture. Just put one copy in the room, or one copy in the building and treat them as a consumable where they need the reference information, but they don't need every instance of it. It will make it much easier for the facilities team to work with the data.

AUDIENCE: Can we export the [INAUDIBLE]?

KATIE: So we have what are called, inspections, that can be associated with the locations. So if you flip back over to this machine, so when we come into the conference here, we have inspections and you can just add them. And the form is very similar to the preventive maintenance where you just schedule, this is the inspection that needs to be done on this room. Absolutely. Good question.

AUDIENCE: So you're saying that [INAUDIBLE]?

KATIE: Yes.

AUDIENCE: Can you link that and say it's in multiple locations, and that one asset type basically is in [INAUDIBLE]?

KATIE: Yeah, so typically what we would say is just like, create a record for the floor and just say, these are the fixtures, these are the type of chairs on this floor. When you're in a stadium, right, it makes sense to have instances of chairs. But in rooms like this, or buildings like this, you just need a reference. And so you can put that at like a building level or a floor and just say, this is what we use. Yeah, no, go ahead.

AUDIENCE: And it sounds like that's kind of a manual thing, like you have a room you need to add that asset. Or a lot of these things you're importing directly from Revit [INAUDIBLE]. I guess it's not really possible to just import one instance of a light and have it assigned to every room that it's in--

KATIE: Right.

AUDIENCE: --in a smart way.

KATIE: Right, so today it's not. So today, you'd only, you'd filter and select the assets that need to be maintained. And they will bring the light fixtures as context, so when you view the model, you'll be able to see them. But for every asset that's selected, whether it's Field or Revit, you will get an asset record. And you only want asset records if there's a maintenance schedule.

AUDIENCE: [INAUDIBLE]

KATIE: So if you have a special light, a special fixture, special bulbs, create an asset record for it, by all means. If it's your standard light in your building, then just put the information in like the floor record-- create a record for the floor and put it, or create one asset if you want.

AUDIENCE: [INAUDIBLE]

KATIE: Sure. Yep. Yep.

AUDIENCE: [INAUDIBLE]

KATIE: Yeah, just the documentation of, what type of light bulb and where do I get it? Right, but--

AUDIENCE: [INAUDIBLE]

KATIE: Right, the team knows where they are. They just need-- I just need the sheet. Yep. So anything that's consumable like that-- one instance.

ADRIAN: So as an example, I put up here with-- I just took out of room record and I just added a couple of comments about what kind of lights might be useful in there. So that might be sufficient for the facilities team to know how to deal with that room and the light within it.

AUDIENCE: Sure, [INAUDIBLE].

KATIE: Perfect. Let's move on to reporting. So we're going to come back to our portfolio dashboard. And so when we look at a portfolio dashboard, we see a snapshot of the portfolio-- how many open tickets, how many new, what's upcoming, what's overdue? Well, we're going to click through. And the nice thing about Ops is, any list can be pivoted into a graph.

And so all I need to do is switch over here to a graph. And now I'm looking at that same list in a graph view. So these tickets are by status, they're broken down by priority. But we could change it and look at them by technician. And if we had a question about Leopold's urgent tickets, we can click on it and we'll be immediately taken to that filtered list. And we can drill into those three tickets.

And then we can clear our search and go back over here. We do have the ability to export. So we can print this, we can download the spreadsheet, which will have the full information of tickets. So the ticket ID, any comments, the technician, the hours worked. So this would be how you-- so we track hours worked, but we don't track time and rates. So you would export your spreadsheet and put that into wherever you're paying out of.

You can download your image, you can save it. And then I can come back to it, I can schedule an email to be sent to me with a link to this report. So if I need to look at it monthly, I'll just get a nice little reminder. We can change the breakdown of our graph by category, by building, by overdue. So I can see how my team is doing. And I can drill in, I can turn off my on-time and say, just show me my overdue tickets.

I can also look at my hours worked, I don't think I have a lot of interesting data there, and all time. So one of the nice things about Ops is, everything's very clickable, very interactive, and it's designed to give you that graphical view of your information and your assets as well as those list views and just make it really easy to toggle back and forth.

Any questions about the reporting? And with that, I'm going to bring back up this last slide, these last two slides. Get started now. The portfolios are free to create you can create as many as you need. We absolutely encourage you to create sandbox test portfolios before working in your clients. The other thing that we recommend is, you can't move buildings between portfolios, so set up a sandbox, play with it, get it all set up. But then you will need to create the building in your owner's portfolio. So you want a portfolio per client.

Sometimes, we see contractors that will create a portfolio for warranty. And so they'll have two portfolios-- after the warranty period, they'll go into the owner's portfolio, but for the warranty period, they'll just manage it within one. But it is an important distinction that you cannot move those buildings. For more information about ticket management, again, tomorrow-- 10 Things Your Facilities Team Must do to Rock with Ops.

We will have Adrian co-presenter with someone from our facilities team who's been using it for the last year to manage our offices and share lots of lessons learned. And then we have a case study also presented by our facilities team. And Charles, who is with us in the room, will be talking about what they've been doing. And then on Thursday, there's a class that we highly recommend. Any other questions? Yeah?

AUDIENCE: What I want to get rid of [INAUDIBLE].

KATIE: Send us a note. So when you log into Ops, there's a little Contact Us. So you send an email through Contact Us. That comes directly to the team, most likely Adrian or myself will respond, and we will be happy to delete any buildings from you, or portfolios. Yep.

AUDIENCE: So we're not able to [INAUDIBLE]?

KATIE: Correct, yep, we do it. But just send us a note and we'll be happy to do it for you.

AUDIENCE: [INAUDIBLE]

KATIE: So Navis to Glue to Field.

AUDIENCE: And then some [INAUDIBLE].

KATIE: Send us a note and we'd be happy to help you figure out the best way to do it. Yep, absolutely.

AUDIENCE: Creating a [INAUDIBLE].

KATIE: Not today, but currently working on some very cool new enhancements to schedule maintenance. So stay tuned.

AUDIENCE: Can we [INAUDIBLE]?

KATIE: No, we can't share road maps. Yeah.

AUDIENCE: And are you planning to have a validator or [INAUDIBLE]?

KATIE: No, we don't presently have plans for a validator, although there are some partners who've been working on that. But I don't think there's anything available yet.

AUDIENCE: [INAUDIBLE]

KATIE: Right, so Glue can take the Navis model. And then what you'll do is create the equipment sets in Field from the Glue model. And so that will create the equipment linked back to the model so that when you do that export, you'll bring that model with you when you create the assets in the Ops. So Field doesn't have any model ability without Glue. So Glue would take in that Navis model.

AUDIENCE: This is a general question. For operations [INAUDIBLE]. Is there a best standard in terms of [INAUDIBLE]? What are the attributes that you recommend that [INAUDIBLE]?

KATIE: Yes. It's a great question. So when we did our survey, what we found-- let me go back over here. If we look at an asset record--

AUDIENCE: Like, I just want to be able to [INAUDIBLE].

KATIE: These core six fields are the absolute must haves. Then we would encourage you to sit down with the facilities team and ask them, by major group of asset, what are the core fields that you need? And typically, there's only a handful of fields for the different asset categories. But sit down with the technicians and ask them, what do you need when you're out there doing the work? And if they don't need it, don't gather it. But these six are the common must haves.

AUDIENCE: [INAUDIBLE]

KATIE: No, it's not-- so how we support devices other than the iPhone are through a responsive mobile website. And so that'll support any size screen. That's what we recommend on the iPads. That will support any device-- Windows phones, Android phones. Yep?

AUDIENCE: [INAUDIBLE]

KATIE: No, so because Ops is designed for the facilities team during operations, its role based. And the roles are based around an operations team. So the admin role is the owner and the co-owner of the portfolio. Then the next level role is managers. So--

AUDIENCE: [INAUDIBLE]

KATIE: Absolutely. So when we come into here and you can-- so you can add contacts at a building level or a portfolio level. If you add someone at a portfolio level, they will have access to all the buildings. If you're working in a warranty scenario, or if you were an owner and you're working with a contractor on a specific building, you can add them to just that building. And so you would add them at the building contacts, not the portfolio contacts. The manager of the building will be able to add assets, make changes to the building, assign tickets out, close tickets.

The next roll down is a technician. Technicians receive tickets. Technicians can view and update assets. Technicians can't close tickets. So they need to go to a manager and the manager checks that we have hours worked and we have all the information that we need. And then the fourth role is-- we do have the vendor role. It's a little more limited than the technician role, a little bit more focused around just that specific asset and those specific tickets.

And then the final rule is the occupant. And the occupant experiences-- if he'd joined that AU2017 portfolio, you'll see the occupant experience, which is just quick tickets, I'm hot, I'm cold, open up a ticket form. I think Adrian might be bringing it up for us. And it's a really limited view of the essential information to complete the ticket.

AUDIENCE: We as users here [INAUDIBLE] based on a portfolio, talk about how able to add themselves to [INAUDIBLE] building and how those permissions work [INAUDIBLE].

KATIE: Well, so anyone can join as an occupant. Because buildings can have thousands of occupants. There's no point to burden a facilities team with, who can-- I mean, you can restrict it down to the standpoint of, only email addresses with your corporate email address can join. We do have SSO integrations, especially we work with a lot of schools and so we do-- and we at Autodesk, we use our Autodesk credentials to log in and file tickets.

So that's how you would restrict it down, but otherwise, it's just open and any occupant can come and file a ticket and go on their merry way. Otherwise, within the building or the portfolio, you just come to that contacts-- we're back over? Nice. And we create a new contact and we just pick their role. And I can't add a contact above me. So as a manager, I can add technicians and vendors to my building, but I can't add co-owners or owners to the portfolio. Any other questions? Well, Thank you very much and I hope to see you at another session soon.