Putting BIM 360 Field Management to Work

SHIRIN ARNOLD: BIM 360 field management, the next generation. No? So the higher hands? All right. All right. So it's good at least that for some of you there'll be some new stuff here. Is everyone familiar with what field management is? No? OK. So I'll start there while we're waiting for the slides to go.

So BIM 360 field management is our next generation solution for classic fields. So what is known today has been 360 fields, we're building out our next generation solution on the BIM 360 platform. And with this next generation platform built on top of forage, we are giving each of these feature module names so they're no longer siloed products. And field management is the name that we've given to field management. As we know classic field is a large product. It encompasses issues, checklists, tasks, daily logs, a lot of functionality. So we're taking a phased approach to our release.

And before I get into any more details because I might have to do this all without anything, let me introduce myself. Totally forgotten about that. Welcome to this class. Hopefully we can get things going so I can share something with you. But my name is Shirin Arnold. I'm a senior product manager in the BIM 360 group and the product that I am working on is field management. So the next generation field solution.

All right. With that said, I'll move forward. I did have some nice, let's say, intro surveys that I wanted to do just to sort of understand the crowds. And unfortunately looking for the technical reasons I think we'll just go ahead without those and they'll be difficult without any technology.

So classic field it's a very robust tool. It's been around for years, so there are many ways in which you can customize to adhere to your workflows. So what we have today with field management, which is released today in production, is we can support issues. So issue management and checklist management, as well as daily logs, which is the next generation equivalent for daily updates. With that we have the ability to cover our quality, safety workflows, and the daily reporting.

So that's what I had wanted to share with you today and hopefully-- well now my tech guy has left. I was just going to say hopefully they're going to be able to help me out here. I do have some colleagues in the room. Do you guys have a USB? Just to take my presentation off of here and put it on somewhere else so I can share my presentation. Apologize.

So what I wanted to share with you today was how to utilize field management, how to utilize the new next generation issue management, the changes enhancements that we've made compared to classic field, as well as what we have done around checklist management. So as an example, as we'll move forward, the issue customizability--

That's a good sort of measure for the audience. How many of you are classic field users? Maybe I should say how many are not classic field users? All right. OK. So we have a couple. All right. Oh, perfect, and a gentleman sorry. All right. I got a USB. All right. Sorry, one second. All right. So are you a BIM 360 user? Yes. OK. Document management model. OK, perfect.

OK. So what I wanted to take you through today-- and I can discuss as we're getting this up. --is I wanted to take you through the quality and safety workflows, and with that take you through the customization, the abilities that we have within issue management, as well as within checklist management. So within issue management we have the ability to customize issue types. So this allows you to differentiate the issues-- you guys let me know if you need help on where it is. --to differentiate the types of issues.

So out of the box we have an issue type of quality, of safety, commissioning. These are all the various issue types that are available to you. And what you're allowed to do is come in and customize those issue types so I can add additional issue types. So there are ways in which to aggregate your issue management or group them.

So I want particular issues to cover-- maybe I let them do their thing-- I have particular issue types to cover my safety, my commissioning, my warranty, defects, or issues that I'm trying to gather. One of the advancements-- so I will touch upon some of the differences from classic to next generation for those that are classic field users-- is classic field has also out-of-the-box issue types that are available to you. Now, one difference, what we've done with field management, is we allow you to actually deactivate the out of the box, which gives you the power to full customizability.

So let's say as an example out of the box we have a warranty as an issue type. And maybe you're not good-- could easily be that warranty is not-- that's not the phase that you're currently in, or commissioning is not a phase that you're currently in, or you'd like to call it something different. So you have the ability now within field management to deactivate that issue type and add your own customized issue type. So that's one of the big advances that we've added. As well as that-- yes?

AUDIENCE: Just a question-- when you customize those, how does that affect the [INAUDIBLE] because in classic, [INAUDIBLE] customize some of that kind of stuff, it would [INAUDIBLE] break the rewards [INAUDIBLE].

SHIRIN ARNOLD: So great question-- the question was about customization. So if I go ahead and add customization, how does that affect the reporting because we do have some downsides when it comes to classic field on that. One good thing to note is the product manager who's running BIM 360 reporting for this new next generation reporting is actually Krystian Macek, the product manager for classic field. So he knows all the pains-- ins and outs-- of field very well. And on our roadmap, we are actually going to be adding the custom attributes to the report so that is something that they will no longer break the reports.

And you will be able to-- thank you. Thank you so much. A round of applause to the team. No. [LAUGHTER] Thank you, guys. [LAUGHTER] So we will ensure to take care of that and custom reports or custom attributes are something that are going to be added very shortly to the actual reports.

And that's one thing before I go any further, and I apologize this has ended up being a bit of a discussion ad hoc conversation rather than going, but sometimes it's a bit more fun, right? It is after lunch. You're probably tired. Food's starting to settle in. So we need to make sure to keep you awake on your toes.

So one thing to note as well when we went into field management, we have an advantage and a disadvantage. Our disadvantage I would say is that we're almost competing against our own product. So we have BIM 360 classic field. It's a robust product. It's out there. Those that are using it are using it very well today. You have API extensions heavily integrated into your systems.

But we also have a great advantage in the sense that we understand all of the things that you love about classic field. And we are taking all of that-- the things you love and the pain points-- all the pieces that are causing frustration today, and we're putting all of that emphasis into our next generation solution, which I hope you'll see today. So an example is the customizability. It's around the reporting. So I'm going to actually leave the slides for a second and continue on customizability.

But one piece I wanted to add there was then you can also add the custom attribute. So per issue type, I can add custom attributes. And let me-- actually, it's easier if you-- oh, is this only going by PowerPoint, so I can't show my computer? Can you open field? So what I'll do is actually show you the product itself instead of, so I'm to go off here. Now that we've started the conversation quickly on differences and custom attributes, I'll show you exactly what I mean by that. And we can just get this opened up. And we'll open field management.

So with the custom attributes, today we have four types that are available-- types of custom attributes. We'll be continuing to expand that. So for each issue type and subtype, you can define custom attributes. So maybe I want to have a particular list value for my safety issues. And I want another type for quality or for commissioning. So you have full flexibility with that.

Another piece that we've added is the ability when you add an issue type to have a particular status set associated to that issue type. So that means a quality issue might go through a different workflow than a safety issue. Now, today there are two that are out of the box that we provide for you. Where we want to go with this is the ability to actually customize that. So today, if you're familiar with document management, one set will be the basic set, which is the set that document management has-- draft open or draft open, answered, and closed, and void we added. And then we have for field the ready to inspect, work complete, so you have the broader set of status values.

So when you generate a new issue type, you can define which status set to define to that issue type, map the two together, and then you will be able to have that full flexibility. And this gets even more powerful when you have the ability to customize that actual status set. Another important piece-- I would say differentiator-- as we go through this, and this also plays a role in how best to use field management, is we have the concept of the user role company. Ow, I keep getting zapped everywhere. Let's see. One second, and I have multiple passwords. I might forget my password. So hold on.

All right, one second. Hold on. Well, that was wrong. At least it's an exciting session, right? Is that? Also wrong?

AUDIENCE: No. That seems right.

SHIRIN ARNOLD: OK, so we're just signing in here. And maybe--

AUDIENCE: [INAUDIBLE]

SHIRIN ARNOLD: Yeah, I've been having issues with Wi-Fi around here. So one other piece that I wanted to note as we're waiting for this is we went over the customization around issues. Another piece that's very important and also a large differentiator is the assignee. So everywhere within BIM 360, you'll notice not in document management, the permission settings can be done to the user role and company level of granularity. So the assignee of an issue can be at the user role or company level of granularity. So that's very advantageous.

We also have another additional attribute, a differentiator, when it comes to field management and classic field. In this case, it's the issue owner. So here's a great example. I'm walking. I'm on the site. Maybe I'm a project engineer. And I'm walking with my senior superintendent. And I'm the one capturing all of the notes for him, taking photos, generating issues.

So maybe I'm the one doing that. And so the issues-- I am the creator of the issue in that case. And I can assign somebody else as the owner. And that means maybe my senior super is the one who has full responsibility and is the one responsible for closing that issue out. I can still capture those issues and make somebody else responsible, like the architect or a senior super. I've heard that a lot from customers. They've asked me, well, I'm looking for this type of workflow. Well, now with issue owner, you can actually do that with the issue itself by using that field to assign the responsible individual.

Another example, and if this doesn't work, we'll just go to the PowerPoints. I think we're going to have--

AUDIENCE: [INAUDIBLE]

SHIRIN ARNOLD: Do you want to just get PowerPoints?

AUDIENCE: I have a question.

SHIRIN ARNOLD: Yes, please.

AUDIENCE: Do you have [INAUDIBLE]

SHIRIN ARNOLD: So a very good question-- so do we have an electronic workflow? So every time I fill out a-- I assign, let's say, an issue or a checklist, the individual is automatically notified. So today, it's an automatic notification. And what we're doing with this within the BIM 360 platform is to add more management around those notifications. So one is like a push notification. It's a safety issue, right? I want everyone to know immediately that this has occurred. These individuals should be notified immediately.

Or I want, at the end of the day, a notification to be sent out. That's something with daily logs that I'm looking at doing-- to be able to send the notification at the end of the day. Specify some timeline. Or another example with notifications is a summary of notifications. I don't want to have one every time something happens. Right now, we're adding a lot of information. So we'd rather almost over inform somebody rather than less at the moment. And then we're going to pull that back and reduce that as we move forward.

So let me now jump back into the slides. I'm not going to introduce myself. I already have. And let's see if this-- I don't know if this works. Oh, sorry. It does work. OK, we're going to forget the polls. I think we're already-- am I going the wrong direction? [LAUGHTER] That's human error.

All right, so let's see. OK, so brief overview-- let's just jump straight into it. So I sort of talked about this. It's a bit easier for me to go on this side. I talked about this already-- is what are the workflows that we support today. This is what we support today. We will be building out-- this is isn't our roadmap session. We do have a roadmap session on Thursday that I'm going to go into detail about the asset module as well as the improvements that we're going to be doing with daily logs.

What today is about is how do you use field management today with the capabilities that it has, so around quality control through the use of the templates that we have when it comes to checklists as well as issues. Punch list-- a great example for punches as I previously mentioned-- I'm doing a walk with my architect or the owner. And I have the concept of the issue owner and the issue itself. We can go through walks and generate issues. Or I can actually just have a checklist for that.

Safety as well-- my daily audits-- I can run through checklists that I can manage at an accounts' level now. So that's something exciting that I'm going to show you today-- also a big difference from classic field. Daily reporting-- I can capture weather conditions, labor, and general notes for my project.

So the first thing that I want to walk through is how to boost your QA/QC workflow. So I think we're all very aware when it comes to QA/QC, generating standards and repeatable. A lot of it is coming from standards and repeatable processes. So these are things that are done repetitively on the job site daily. There are ways in which we can place a program control around that to have better results coming from this. So as an example, digitization of checklists-- using the templates themselves-- so ensuring that each of our projects are using the same method. Of course, we have different projects. We have different teams.

But this allows us to ensure later to have better analytics from a data perspective. If I know-- let's say I self-perform concrete. And I know every time that I have my pre- [INAUDIBLE] checklist, we're going to run through the same exact check. Then I can aggregate that information at an account level later-- analyze where am I always getting nonconforming items-- why do I have issues every time at this particular step in my process and my inspection process and then have better self-reflection and see how we can have more preventative from a quality perspective.

So here, these are the proactive checklists-- measure what is going right as well as what's going wrong. And then set leading indicators, not lagging indicators. So be proactive about it. With all this, we have the reporting and analytics side as well. So we do have a-- we've started a lot of work on reporting and analytics and are even bringing out our machine learning on quality as well as safety. And we have some other dashboards that I'll share with you today.

One other piece-- I did mention customizability for the issue type and custom attributes. What we will be bringing-- I think this has a little pointer-- what we will be bringing out shortly as well is the customization of root cause. So today, we provide an out-of-the-box value. What you'll be able to do is customize that root cause list and then ensure that your projects are using the same, let's say, root cause values or need to adjust according to their specific project needs.

So taking this into consideration, what I wanted to do was actually take you through a typical workflow and how you could do this in field management today. Today was really about the how. So we have the concept of a checklist. What I've done is I've built out a QA/QC checklist. You can today, and I'm going to throw some new added functionality in here as well-- within a checklist, you can assign sections themselves to user role and company. So you can have a workflow within an inspection. That's another differentiator.

So what we're going to do is we're going to go, and we're going to run an inspection. We're going to have a nonconforming item. And then that's going to kick off the creation of an issue. We'll go through the assignment of the issue itself. And in this case, for the notification, as I'm running the inspection, that individual where the issue was generated has been contacted. So they know that they have an issue pending their action. And then we will go ahead, close the issue, so we'll put on the hat of the subcontractor-- respond to the issue. The general contractor will come back and close the issue.

And then we'll go on and continue with the checklist and then run the actual report. I might need help initiating videos if they don't work. Let's see. OK, before we do that, though, let's get into permissions. So before we go into the actual process, another great advantage-- so classic field has the roles. They have as columns, you have the roles and then the functionality that you can define who has access to create templates, to look at reporting. So within BIM 360 field management, you have full control at the user role and company level of granularity-- you'll hear me say that quite often-- around who can view and edit and create either checklists, templates themselves.

So maybe I can create a checklist. I can run an inspection or create a checklist. But I can't create the templates themselves, so the standards-- to full control, which is like a mini admin. I can edit, let's say, other templates if I have to come in and make edits to an issue, a checklist, or a template. So full granularity and functionality here.

What I do is I actually show you. Here's an example quickly of what it looks like within the project admin space. I'm adding an individual, in this case, a user. And you can see as we're doing this, there's user company role. I'm defining Basic from Basic, View All, Create, View and Create, Full Control Permissions. So I decide to give this individual View and Create.

So what I'm doing now is adding this for checklists and templates. Then we're actually going to go into issues because we just recently, for those of you that are active BIM 360 users for document management and field management, we just recently added unified issues within BIM 360. So we've pulled issues out of field management from a permissioning perspective and have it now the same, let's say, functionality, if I'm just a document management user or if I'm a document management and field management user. So we have that full capability.

And here's just a quick glimpse into the permissioning capabilities. So what this is doing is really allowing you to have a more collaborative process on your job sites. If I want particular subcontractors to come in and bring their own quality checklist templates to the table, why not give them that permission? They can only do update, create their templates. So that's the collaboration we want to allow within field management. I can move to the next slide. Thank you. [LAUGHTER]

So I touched upon this a bit. So you'll see some of this is a repeat. But now you have visual because I was flying without slides. What I wanted to note was that previously, we went through the permissions itself on the actual, let's say, object on the issue, on the checklist. Now going one level deeper, there's the actors. So let's say these are the roles that are part of, in this case, an issue.

So I mentioned before the creator. So let's say I'm a project engineer. I'm out. I'm creating issues. I have the ability to edit the issue. I cannot close the actual issue myself, as a default, though. So you don't have additional data entry because of course we're very aware, what do individuals on-site hate-- multiple clicking, finding it difficult to get to one place to the other. A very streamlined workflow is what we need to focus on.

So in that case by default, the owner equals the creator. So only in the case that you want somebody else to be the one responsible to close the issue do you change the actual issue owner to creator. And as we get issue templates in the future, this will be something that you can also predefine. So it'll be part of that.

The owner's the one who closes the issue. And then the assignee is the one who goes from the in-progress workflow. So they can change the ball in court. They can say, OK, I've done my piece. Let me hand over to the next individual. So they can only move also between the in-progress status values. So they cannot actually close an issue or set an issue to void.

And then at any given moment, you can @mention. So you can say, hey, Joe. I need some help. Can you have a look at this? I'm not quite sure. I need to find a bit more information. Have a look. And then that individual can also partake in the issue itself.

Let me just also do it because [INAUDIBLE] half an hour. All right. So building your-- spelling-- Building Your Checklist Template. So there are three ways in which you could do that today. So similar to classic field, I can either build from scratch. I did challenge-- and one of the designers is actually in the room-- I did challenge the designers to make this a fun, lovable experience because I've heard with classic field, it's not that fun and lovable. I actually did get feedback from users that it is lovable. It is a fun experience. So you will want to go in and start building checklist templates.

One way is to do it from scratch. You can import from classic field. So of course, if you have your IP, your templates, in classic field, you can export from classic field, and then import those directly into field management. I actually have a video. I'll take you through that.

And similarly to what we have-- nope-- I don't want to jump that fast. OK, similar to what we have in classic field, within field management, we also have a download a sample. You can download a sample template. You can fill that information out in Excel. One big difference we have here compared to classic as well is you can have x number of templates in one Excel. One Excel can house multiple templates. You don't need to have one Excel per template.

Now what I'm going to show you next is pretty exciting. We just released it last week. So in classic field, you have the concept of a project template. In a project template you can house all of your information-- your issue types, your custom attributes, as well as checklist templates. And when you create a project, you say I want to create one based upon this particular project.

Well, what we've done, because that's not version aware. In listening to pain points from our users, they're like, well, I update my quality checklist. And now all of a sudden, I want to make an update. I have to copy it back in every single project. Or my safety checklist-- I now have to go and copy it into every single project. And now we have different versions.

So what we introduced is the account level for field management. So if all goes well, this video, yes, will start. So you can see I'm in global construction. And this is just the base of what we will be doing with issues, with all of the functionality. I'm at the account level.

I'm building a checklist template today because I'm here to be very open and honest with you. It is a push functionality only. We will be allowing a pull, as in I have a project. I have a great project engineer that has done some cool, innovative new inspections. I want to be able to take that template and promote it up to the account level. That is something that's on our roadmap.

Here I created a template. And now, I am looking at all the projects. I in this example select only one. But you can select multiple-- as many as you'd like. At the top, you can select all of them. You can search for your project.

So here's the checklist. I can quickly identify which one was it actually assigned to. In this case, only one. Now I'm going to go down to the project level. I'll search for that particular template. And you'll see very clearly that that template is coming from the account level. So while here, first I look at it. See, it's exactly the same one. I only have one question under rebar.

So here, this little globe tells you that this is a template that's managed from the account level. Where we will be going with this is you'll be able to lock it and say I don't want anybody at the project to change it. Or better yet, lock section A and B. But let projects adjust C because that's project specific. But I want every inspection to start with A and B.

So here, I went back to the account level. I made a change. Now I'm updating the template in the project again. I added form work. I added another item. So now you can see. I'll go back down. And you can check in the project level. And you'll see that that was automatically updated. Yes, question?

AUDIENCE: When you publish a new question to an [INAUDIBLE] template, how do the reports look at that question [INAUDIBLE] completed [INAUDIBLE]

SHIRIN ARNOLD: So the way it works today is it affects only the template. Where we plan to go with this is it will push also an update to the checklist instances that were created that were not started. So if I had started already, it won't overwrite. We're not going to overwrite any information. If anything, we're looking into ways to maybe say, hey, FYI, there's a newer version that's out there. Would you like to update?

So that's going to be something-- not the user-- we don't want to do any force in that sense. And that's why even here, if when I go back, when I'm at the account level and I make my updates, I can make an update, Save, come back a couple days, make an update, and when I'm ready, I can then publish it to the projects.

All right, here's just a quick example of importing from classic field. So here's the Import view. I can select Import from classic field. One difference is in field management we differentiate-- in classic field, you have those tabs that differentiate the type of checklist. Here, we do it by type at the top. So before you import, you need to define what type it is. Here, I quickly highlight also that fun, new, lovable experience of building a template.

So very quick in-line editing, the drag and drop capabilities to move one up to the other, the automatic numbering. So right now, it's all automatic numbering. If I want to remove an item from in the middle, I don't have to renumber all of the items. So there we go. We have our checklist.

All right, I think we're about ready to get into the workflow. And looking at the time, let's do this. OK, so the first thing, this is my mobile app. While I say this, two important pieces-- I'm running a checklist. That was a list of my checklists as me, myself, Shirin.

I'm starting to run the checklist. You'll start to see differences already from a usability perspective. I'm adding notes to an item. Even though it was yes, I can add notes, any comments. I can also add photos to those particular items.

Another piece to note before I move on to the next is the fact that we do automatic sync. So you no longer have to do a manual push to say update the two. It automatically syncs for you. As long as you have a connection, it's constantly getting the latest data. So as soon as I generate an issue, it syncs with the server. And the individual who's sitting in the trailer has all that information, the latest and greatest information. Another piece as we move on to the next is that it's available in Android and iOS, on telephone-- phone-- that sounds old school-- telephone-- on mobile and tablet.

All right, so now, I hit a nonconforming item. Or we're first going to add a quick-- let's add that note again. I continue forward. And I hit a nonconforming item. The ceiling framing is not complete. You noticed as soon as I hit that item and it was nonconforming, it automatically auto-initiated an issue.

I can assign by user role or company. I'm going to quickly search for a particular individual, David Sanchez. He's my subcontractor I'm going to pick on today. I can go and add photos, define a scheduled date, mark up the photos. So these are all now part of that issue.

And the great thing is, the issue's generated, and I can continue on my workflow. So as the-- yes, question?

AUDIENCE: Will the auto-generation issue be able to be disabled by [INAUDIBLE] classic field.

SHIRIN ARNOLD: Yes, so that is on my roadmap. And that's why we also have the auto-initiate as a first. So we brought this out auto-initiate. I took it out because I thought it might be annoying. And then I had a lot of customers who were very customer-focused say, Shirin, why did you take it out? Put it back. So now it's back.

But one thing that we are working on, and you can see in the new year, is this Auto Issue Create, which is what classic field has. So I can define attributes. And we're going above and beyond what classic field does. You can do it even at the item level. So I might have a section that I don't want any issues to be automatically generated. But I have another section where they should be. And I can define the attributes at the item level. The root cause, the assignee-- all of that will be possible. Until then, we're going to have this. I guess the vote from customers was to annoy them or have this auto-initiate for a bit longer.

So now that I have the issue, now I'm coming in as my subcontractor. I'm looking at the issue. It's on my issue list. While Shirin is out still on site running the inspection, I'm adding information to the particular issue. Here, this is my activity thread. So another thing from a usability perspective that I can come in, have a communication. This is where I mentioned previously about the @mention, the capabilities that are available.

I'm then going to assign it back to Shirin, say, OK, ball's in your court. You need to take care of it now. And now it's just running in a loop. So now I come in as Shirin-- how it switches. You can see as I'm running the inspection, I can see that it's actually changed status.

So let's say Dave was super fast and took care of the issue, made the changes. While I'm out on site still running the inspection, I can review what Dave has written. And then I can come in and close the issue and continue forward. So here, I'm just reviewing everything that he's written. Go in, and I've now closed the issue and can go back and continue on running my inspection.

So here's the route two. I didn't have a nonconforming. Another piece you'll notice-- a differentiator-- is the fact that we have the concept of done and complete for our checklists. And I'm just adding a quick photo to show you can add photos as well to items that are not nonconforming or part of an issue. And then we'll continue forward.

So as soon as I finish, you can see the progress there. I get the done. And then I continue forward. You always have the progress, so you can see how far I am. We also have a quick way to jump from one to the other. So now I've completed the checklist. It's moved to complete. And now we go into running the report. So now I can select the actual checklist.

And within the checklist, it's a completed checklist. I'm going to run a detailed report in this case. What I've done is I'm also going to run a report on that particular issue just so you could see the differences between the two. And here, I just wanted to show from a web perspective while we were waiting for the report what it looked like. So I'm opening up the checklist, looking at the particular issue itself, and then I'm going to go ahead and generate a detailed report for this particular issue.

And I want to make sure we get Q&A, so let's see. Here's the checklist report. This is our detailed report. We will continue to enhance this to add additional functionality as we go. One thing that we're going to be adding is the ability to drop a pin for a checklist. So you could represent a checklist on an actual floor plan as we do with issues. And then our issue report, we'll continue to go ahead and expand that to show the push pin location on the floor plan as well, as well as adding activity thread and all that information.

All right, so the last piece from the quality perspective before we dive into safety are the dashboards that are available to you. So this is at a project level where I'm able to quickly see the status of all the quality issues that I have in this particular project. So I can see quickly how many I have that are in progress, that are open, that are ready to inspect or in dispute. So I can see all of this information very quickly.

I have this top left graphic. This is a new one. Again, for those that are field users, this is what we're calling the heartbeat of the project. So it's really allowing you to see over a time span how many issues are generated or opened versus how many are closed. And the idea is over time, we can also start to overlay more information with this. So let's say maybe, does it have to do with a particular trade coming on site or is it a particular phase in the project? Maybe it's nearing close out or I'm in the commissioning phase. That's why I see sort of a ramp-up of issues coming-- or weather related-- anything.

I can also see here root cause, so how many issues. This is a great way to see the quality of the data. If you mandate root cause, in this case, I actually have 80 issues that have no root cause associated to them. So that's not a good thing. I would want to ensure that out on site, it's a quick way to understand is this project really adhering to the standards that I've applied to them. And you can dive in deeper and try and understand.

This one, we have in classic field today, so total issues to date, active versus closed. And then another great one is around the quality checklist conformance. So this takes all the observations that were gathered when running checklists-- those inspections from a quality perspective-- and then you get a color coding of how many failed versus past. So in an ideal scenario, you would want this all to be a nice blue. And you wouldn't want to see any yellow. And it's a good way to say, hey, they're actually using checklists. If this is something that they're meant to be using from a quality perspective with my quality program, I would not want to see this chart empty.

All right, so let's jump on. And I wanted to give you-- we are a bit delayed because of the technical issues we had. But let's go ahead, and we'll jump on to safety. Safety's just a bit quick one where I'm just going to introduce a workflow. We won't go into the product because I already did that from a quality perspective. And then I'd like to share daily logs and get any additional questions you may have.

So as we know, for everyone, safety is vital. It's important. We want to get everybody home safely to their families at the end of the day. Safety is, I would say, number one in wanting to really standardize the processes that we have out on site today, and through the use of checklists and issue management, having those standard safety audits is a great way to do that. One example that I have here similar to what we had from a quality perspective, so this is just looking at how we could have a different approach or a different workflow coming from safety versus the approach that we took from a quality perspective.

So again, we can go ahead, build out our IP at the account level, build out that checklist template that represents the safety audits that I have. And what we will be doing with this as well is allowing you to say, Shirin, every Friday, you have to do this particular safety audit, so pre-scheduling these types of inspections to ensure that they occur on a weekly, daily basis. So that's something that you can see coming in the near future.

We would then initiate the checklist, so were items or any behaviors noticed that were unsafe in nature. In this case, you could then initiate the issues, again, using that customizability-- that issue functionality that I spoke to you previously about-- where now I would have the safety issue type. And then we would be able to record all the information through our custom attributes. So I had all the different custom attributes. I could define if it was a type of incident what type of incident-- gather all the information that's necessary. And what I've seen also used in practice a lot is the checklist itself to be a way in which to gather that information, so almost like a form to gather the information from a particular incident. And again, because of the permissioning level of detail that we have, you can also ensure that only the right eyes have access to that particular checklist, so it doesn't get into the eyes of any other individuals.

Close the issue, and then again-- oh, sorry. Again, as we did with the previous was complete all the sections, submit the checklist, and then all the reporting capabilities that are available to you from a checklist and issue perspective as I showed you on the quality side. All right, so why follow this workflow-- really, to track and review the job site safety issues through one central location. So I have one repository where I can see all of the issues that occurred over time. And as we continue to either-- you extract the data out of field management or as we continue to build out our dashboards and analytics capabilities within BIM 360, you'll start to understand who are those subcontractors, what are the areas or the high risk, high safety hazards that we tend to have on a more repetitive basis.

So for those of you, hopefully, you're aware of Insight and our machine learning with Project IQ. Hopefully, if you're interested in that and what we have done, there are definitely some classes here at AU that I would definitely recommend that you attend. We have done a lot that can show you what risk or safety hazard your project is at. So utilize templates and create those custom safety checklists as well as really about gaining quick visibility into the priority of the issues that you have on site.

This is-- we're just beginning. I mentioned Project IQ. We've put a lot of focus on the machine learning side of this. So we do have Project IQ. That's another piece. And I was hoping to go into the product as we were having problems. And I can't actually get the computer to work. I would've liked to share with you some of those other dashboards and what we can get.

But today, we're starting to build this out from a safety perspective. So you'll see what we did on the quality side. And here, you'll start to see on a safety perspective the observations that are being tracked as well as the issue status, so similar to what we had with quality. And we'll continue to build this out from a purely safety focus.

All right, daily reporting, so let's go into the last workflow. So daily reporting is really about where I want to showcase the tracking of the daily activities that are occurring on a project from a weather perspective as well unforeseen delays-- being able to capture progress photos-- all of that information within BIM 360. What we support today, and I mentioned previously when I was talking about the phasing aspects, that we are going to be continuing to build this out. What's supported today is the weather widget, labor widget, as well as general notes widget.

And with this, we can track-- I'll go through each of these individually, starting off with weather. So we can track the weather conditions on a daily basis, so understand as well as add any additional notes-- what was the weather on sites on a specific day. We can also log the activity or the labor, so how many workers per company and how many hours were they on site for that particular day. So this is all information that can be tracked.

And all this is, again, the daily basis-- the document notes about the day. Within the notes widget, I have the ability to add any type of just text documentation about what happened on that particular day, what areas were completed, what deliveries came in. I can add all that information here and then have my daily log for that particular day.