Revolutionizing the Submittal Log Creation Workflow

SATYAM VERMA: All right, guys, thank you for bearing with us through some of these technical difficulties. We've tried a couple of different things. Doesn't seem like any of those things are really working out for us, so it might be a little flashing blinking up here. I apologize ahead of time.

But hopefully, we can get through it. I'll do my best to talk through as many of these points as well. Most of this stuff, I think you guys will get, and we'll be able to talk through it. So not to worry but once again, apologies.

What we're here to discuss today is revolutionizing the submittal log workflow. And it seems like we have a good sized group here and to make it somewhat interactive conversation as well because there's so many different pieces of this puzzle that come together when we talk about how and why we create some of the logs, the type of impact it really can have on a project and the different processes that take place, and how important it is to realize that submittal logs are an integral part of our project. They drive contract compliance. They ensure that everyone knows what's going on, how we're supposed to be building things, what we're supposed to be including, and all the different pieces that come into that.

And what I wanted to start off by talking about is what are the different processes and how this process works and looks like in the world in the industry today, what challenges we're coming across, and how do we break through some of the kind of things that are holding us back when it comes to submittal logs. A lot of that is the amount of time we spend on that, the level of accuracy we can actually generate from that, and the efficiencies that we can really drive once we start addressing some of the issues that we see when it comes to building and generating submittal logs. So let's talk about what that process is today.

First of all, we'd just like to get with a show of hands, how many people here have ever had to interact with a spec book and pulling submittals out of that and generating some type of log-- just by a show of hands. Awesome. Now, building off of that, how many of you enjoyed the process of building and going through these spec documents and pulling out submittals? Raise of hands-- who enjoyed that process? That's what I was expecting because it's not very fun.

The first time I got to work, my CEO Sunil, who's sitting right there. He used to be a project manager in DC. He showed me his spec book for it's just a safe way. This is nothing really complicated. That spec book was this big.

His job and many people's job today is to sit down and go page by page and read these documents to understand what the requirements are. Now this is a very, very important and critical part of the entire project, and it's something that honestly people leave to do just the way it's been. And there have been so many breakthroughs technologically that allow us to address the inefficiencies with this process, excuse me, and that's really what we're going to talk about today.

But if we look at the process today, it is highly trained individuals. Everyone in this room has went through a lot to get to where they are today. You don't just learn inherently how to accurately go through a document and understand what submittals are. We're asking these highly trained individuals to spend their time doing manual data entry.

This is just not very efficient. People don't enjoy it. And with the labor shortage and the talent shortage, this is not something we can continually expect to ask our project teams to be doing and expect them to be happy about that, especially when there are solutions available on the market to address some of these issues.

Another big piece of that puzzle is accuracy. And accuracy is extremely important because that's what drives contract compliance. When you're architects put together these spec books and you guys win that bid, what is in that book is what you are contractually obligated to build upon or to build to words or to deliver documentation upon. And a lot of times, we miss a lot of those requirements.

What we can say after working with thousands and thousands of different project teams is on almost every project, there is at least one critical requirement that has been missed. This can be an addict stock requirements. This can be a mock up. This can be some sort of test or inspection that needs to be done.

And on average, that's going to cost about $10,000. And a lot of times, you're not even going to realize that you've missed that until 6, 8, 10, 12, 18 months into the project when that's just a sunk project cost now. With some of the new tools and techniques and processes we have, you can address those upfront on day one of those projects to ensure that you really have-- that the information, the documentation, and the actual stuff that you need to get this stuff done properly accurately, and efficiently.

Now beyond that, collaboration is also a big issue. Right now, this is a very siloed process. A project engineer, project manager, project executive-- they're sitting there with their documents. They have a nice Excel sheet, maybe a highlighter. Maybe they're uploading it into Blue Beam running some OCR and doing a word search.

But unless you're searching for every variation of the word mock up, mock ups, mock dash up, mock dash ups, mock up with the S, without the S, in parentheses-- there's probably 50 different variations. You've got to search for every single one every single time to ensure that you're capturing all of those. That is not happening across the industry as a whole. By being able to bring in the architect, bring in the owner, bring in the design team, bring in your other product team members into this process, and make it be truly collaborative, that's really when we're going to get to a stage where we feel comfortable and confident that the information we have in our submittal logs is not only accurate, but includes the input of everyone from the owner from the architect from the contractor as well so that we have a unified document that lets us maximize the level of efficiency when it comes to project delivery.

Another one of those pieces and one of the biggest problems in today's industry is that there is a real lack of standardization-- the amount of times where you can come to one company. You'll have 15 different PMs who are running 35 different projects, and each one of those projects' log looks different. They have different levels of information, different levels of details.

Some might include a full description of every last piece of information for that some middle. Some are going to narrow that down and only include the first sentence and ask you to go reference suspect book. And then you got to go to flip to page 732, paragraph four, line six to find out what that actual requirement is. That might take 20, 30 minutes.

And if you have to do that 400 times for each submittal and your requirement, who has the time to do this stuff? Nobody has the time to do this stuff. That's what the real realization is and what we've come to and what people are really starting to address today. And that's what we really need to be moving towards as an industry to understand that, hey, it shouldn't come down to one person who has to sit there with a book and a highlighter and some coffee to be able to get through this. Let's empower these employees, these engineers, these architects, these owners to get the data that they need and use their expertise and that time to do stronger quality control processes, do stronger quality assurance processes, get more familiar with the projects themselves, and not make them want to pull their hair out going through these documents.

Now there are still additional challenges that come into what that process is today. One of the main one is resource challenges. I'm sure everyone here has at one point or the other either heard someone talking about experiencing firsthand and is probably experiencing right now this shortage of talented, qualified labor in the market. Now, if we're all competing for those same people, do you think a new project engineer is going to want to come to a company that's going to ask them to spend 80 hours every month going through these documents or to an organization that's going to equip them with the tools that they need to get them to where they need to be in order to drive strong workflows and processes and understand where they need to be investing their time?

We already talked about standardization and accuracy, but contract compliance is another big aspect of that. The amount of times where with a platform where-- we're going to talk about Pype here in a second-- where we pull out every last submittal versus what they pull out is a big discrepancy. Most product teams, let's say, will pull out 300 submittals middles on a given project. A platform that is available today might pull out 1000 submittals.

Well, everyone jumps out of there see like, wow, I've never seen 1,000 submittals in my life. This is way too much. What am I supposed to do with this data? Well, the reality of the fact is that's what your contract is requiring of you. Now, yes, it is true 700 of those submittals, no one ever wants to look at or see.

Nothing's ever going to get submitted upon. And once you have that conversation with your design team and your owners, they're going to realize that as well. And some people want to say, hey, well, that should be on the architect. They should make better specs, and they should do this.

And guys, the reason why we're here talking to you and not the architects is because you guys are. The ones who have the impact. You guys are the ones have to deal with these issues on a daily basis, and you have the ability to really change the way these processes are and so by driving contract compliance, you are allowed to be upfront and tell the people that you're working with, hey, this is what we are contractually obligated to. Why is this in here if we don't need to address it, if we don't need to submit upon it. If this is not important to you, let's cross it out.

Let's make sure we all agree upon that right now, as opposed to at the end of the project, you're saying oh, well, we didn't know we needed to submit that, or you never put that in the document. Or hey, we never have had to submit this in the past.

Why do you want this to be submitted now? Those questions can be brought up and answered at the beginning of the process where you're not worried about, hey, whose money is this costing, whose pocket is this coming out of, how long is this going to delay the delivery of this project now. That provides much stronger relationships, much better owner delivery. They're driving much more value. And in general, everyone is now in a win-win situation because you understand what's expected of you.

You've clarified any discrepancies, and you can move forward with the best possible plan of action. And that kind of drives into money is lost and going back to on pretty much every project that we've been on, we've seen one critical requirement missed. The average cost of that is $10,000. And that's direct sunk project costs. It's not identified until a couple of months into the project.

Let's start identifying those up front. Let's be very clear with our owners, with our design teams, our architects that, hey, these are issues we have. Let's make sure we address them upfront once again. These are very basic simple concepts.

But with the time that's being spent with this, a lot of times, it's not something that we are actually able to address. And it's something that is extremely important. The second is quality of work, and it should say also quality of life.

We got to stop having these manual tasks, data entry highlighting that we are asking project engineers, project admins, project managers to do because that's not what they want to be doing. They didn't go to school and become a certified project engineer to sit there and analyze and highlight your spec book for 80 hours at a time for four hours a day for the next four weeks. That's not what they want to be doing. Let's make them happy by giving them the tools that they need, giving them the data that they need so that they can do their job and do it effectively as well.

So with that, what are the different tools that are available out there? And today, we're going to talk about what Pype Autospecs is. Now, I work for Pype. We have built a couple of different platforms. The first one of them being Pype Autospecs. And what this does is it really focuses on the process of pulling out your data from your spec book.

What does that look like exactly? It's as simple as having a spec book that's in PDF format-- native or scanned. That doesn't really matter. And what we focus on are addressing all those issues we talked about, pulling out all of your data from those documents up front, organizing them for you in an efficient manner, so you understand within five minutes of getting that spec book what are all your action and information submittals broken down into individual categories-- all of your lead requirements, meetings, conferences, special warranties, operating manuals, owner's manuals, whatever that may be, testing, inspection, mockup, all of that is broken down for you within a matter of minutes.

So now, your project teams can focus on diving into that data, doing strong QA processes, doing strong QC processes, and getting familiar with the project data themselves. That's what's important. That's what these guys were trained on. That's what they know how to do best, and that's where they can really drive value.

Identify-- knowing all those product requirements-- once again, going back to the same aspects that we've already talked about, contract compliance, standardization, understanding requirements, collaborating with all of your entire team, and not waiting until you get halfway into a ditch when you have problems and then saying, oh, why didn't we address this earlier. Those are some very basic things.

Now one question that always comes up when we start bringing technology into processes that have always been manual is, hey, I don't want another system in my tech stack. Great, I got Blue Beam. I got Autodesk. I got a Smart Bit.

I got instructions. I got cameras. I got drones. All of these are different logins coming in different places, and we understand that. That's why seamless integration is something that every platform that you're working with today should be a major focus on.

Wherever your data should live, we should be able to speak with that. We see a very large trend-- I mean, you can see that. We're here today at the Autodesk conference. It's been wonderful, but people spend millions and millions of dollars to buy data management systems, project management systems, but they fill these data management project management systems with inaccurate data.

So how effective is your $5 million project management system when the data that's in that system is not accurate? It's something that we really need to take control over and ensure that we have strong data, accurate data and that it's getting into the right systems, and that's an easy process to do. We can't expect everyone to be working in 5, 6, 7, 8 different systems every day and expect them to get any more value than they are when they're doing this manually because, at that point, you might as well do it manually.

So understanding the connections and the flow of information between these different systems is something that important. And it does not only apply to submittal logs. That's something that we should be thinking about when it comes to any process that we're bringing technology into as well.

Once again, going back to time management, what if we can take a project manager's time and instead of spending 40 hours doing this, they can spend five hours? That opens up 35 hours for them to do other tasks that just have never happened on the project site before. They can sit down with their PE and actually help them understand why we are looking for certain things and are not looking for certain things.

They can actually now build QA processes, build QA reports so that they can go out. They can enter interface with the super now because they have 10 extra hours to go out on the field and make sure the super has a very good understanding of their procurement log and their material expediting log to understand when they can expect things. Then the super can get more in-depth because they generally don't even have this information. So we're providing now new data, new workflows that didn't exist anymore because we are getting time back. And we're getting much more accurate data which we're able to build these reports with.

And reporting and dashboarding is also another very important aspect of this. There is so much data in construction. If we had the ability to take all of the submittals that we had for the past 10 years of projects, aggregate that, and understand what we did the best at and what we did the worst at, we can then reallocate their resources, our time, and our money to the areas that we need to focus on.

But right now, with the lack of standardization and the lack of data aggregation, it is extremely tough for companies to really look at what is impacting their overall bottom line because they don't have the ability to aggregate that data. And so what we're able to do is build strong dashboards, build strong reporting with that information to inform companies, hey, this is what overall in this entire year you've worked with these types of submittals. You've had this many different types of manufacturers specified in your projects.

You had this many sole source requirements. These were all of your requirements that you had. You can then take that up and do a lot of data analysis with that, which is just going to help drive more metrics, which is going to lead to better and stronger decision making.

Now what type of effect can this have in real life? And if you get the chance in between the blinking screens to read anything up here, I apologize. We will send this out here. I understand it it's probably not ideal.

This all comes down to real numbers. I can come up here and talk about how great data is and how much stuff you can do with it. But when it comes down to the bottom line, those that's where decisions get made. And so here's a very simple just a fact about how much time was able to be saved and the accuracy at which we're able to do it with.

So, typically, it took almost over 80 to 90 hours or about three weeks to generate a submittal log in this one specific scenario. With these new systems, that 80 to 90 hours or three weeks of kind of working time, we're able to bring that down to three hours with a 99% level of accuracy. Once again, I'm sure all of you can think of at least 50 different things that you could do that would help add value to your project, that would help make your life a little bit more sane, that would allow you to go help other people on your project teams that might actually need it, who haven't learned as much as they need to are newer to the game.

Whatever else that may be, you're getting that time back, and you're actually getting much more efficient and effective data out of that, which is why it's so important. So on average, once again, just going back to the bottom line stats-- how much time are we able to save and this is on the lower end of the scale on your smaller products-- on average, 40 to 80 man hours per project. Once again, let's just think about the different tools, the different processes, the different workflows that you can now create, implement, dissect, evaluate when you get this time back on your projects. And we can even look back and say we don't maybe we don't want to do more.

Let's say you did 10 products a year. If you're saving 90, 100, however many hours per project, what we're seeing is that's letting you do more projects. You can restart people you can get someone off of one project and onto another project much more quickly, much more efficiently.

And a lot of people don't really think of this in the realm of, hey, this is when we have a product at hand. But it has an even bigger impact when it comes to estimating. When companies-- let's say, nice round numbers-- a company that wins 100 projects a year, they're bidding on at least 300 projects a year. That's about what the industry average could be.

Most of those estimating teams, most of those preconstruction teams, when they get these bid packages, these bids sets, these bids specs documents, more often than not, they're taking a very educated guess. And this is there's nothing wrong with that. It's kind of the data that they have available. They have to do what they can do with that.

They're saying, OK. I'm using what we have in this bid package. I'm taking a snapshot of a similar project we did in the past that had similar divisions here.

And then I'm piecing that together with another project where I remember we had a scope that was similar there. And we're throwing in a number that we think is more or less accurate. Well, now, if we're able to process these documents with a matter of minutes, your estimating teams can understand the scope of the projects that you're bidding on within two minutes. That means you're going to have extremely accurate bids, and you're going to start winning more projects.

So now, not only are we saving time, we're winning more projects. We're increasing our bottom line. And that's just off of one tiny change in efficiency, which is pushing these documents into these systems that can start automating a lot of this and giving teams a strong base level to begin once again doing QA and QC, as opposed to doing copy and paste and highlighting in Excel.

Another major aspect of this comes back to, let's say, liability is a good way to put it. One out of three projects in general are going to end up in litigation in one form or another. One of the top three things that courts are looking at when it comes to litigation is your submittal log and what that looks like. With a manual process today, when this is being pasted in Excel, that Excel is being e-mailed to the design team.

The design team maybe is deleting five things, adding eight things, and manipulating for other things, there is no insight into who's doing that, when that's happening, what those changes are, what was deleted, what was added. But with these new systems, there are audit logs. There are history, you can understand what changed, when it changed, why it changed.

And you can go back to that whether it's two years ago, or whether it's two months ago. You actually have an understanding of what the evolution of these documents were, and you can now hold someone responsible for what those changes were. Hey, this was architecting that made that. Or yeah, we actually deleted that.

The amount of times where I've seen someone said, oh, that was in my log. I must have saved the wrong version, or I must have emailed you the wrong version. That's really not acceptable in these day and age. You need to have a strong flow of information.

And also, people need to be held liable. When those mistakes are made, it's no longer, oh, it got lost my email, or Excel didn't save the right version. Or it deleted it by accident, and I forgot to hit Undo. I mean, those are things that can help us save time, save money, and save our sanity as well.

Now how does this all come together with platforms like Autodesk BIM 360? It's very straightforward. We, as I said, appreciate and understand the importance of the flow of information and not having to work between 4, 5, 6 different systems. So what we'll do is eliminate the process of teams having to go in. You have one big massive spec book.

And right now, someone is tasked with, OK, here is a big spec book. Go in and break this down into each individual division, then each individual section. Make sure you have the right naming convention. Make sure that naming convention is standardized across all of them and make sure that gets into BIM 360 accurately. It's a very manual task today.

Now we have systems in place where you can as upload it. They will break everything down for you, do the naming conventions, create the folder structures, and push that into BIM 360 for you automatically. As well, they can do the same with your submittal logs. They can do the same with material expediting logs, for terminal logs, whatever that may be.

Once again, you don't need to focus on these manual tasks. Let the technology take care of those workflows and get back to spending your time doing what you enjoy doing-- the reason why everyone is in the industry today, which is getting down and dirty with these documents and figuring out how to get this job done and delivered above schedule, above budget, or I guess below budget is what would make more sense. And that's what we really want to see. Those the outcomes that we are really trying to drive.

The plan here was to show the actual live demo. Let's see how effectively we can make that happen here with this wonky screen. Just so you guys can really see firsthand how effective and how much data you can pull out of these systems. I do think it might be a little bit of a futile effort to try to go through that here today, so I will just leave that up and then see if there are any questions right now that you guys want to ask or also any concerns about technology. We all know that there's concerns of automation and things like that.

So is there anything that you guys have to ask? Sure, sir.

AUDIENCE: [INAUDIBLE]

SATYAM VERMA: Correct. So it is a slow evolution. It is something that we are testing today.

It is in beta mode where we will be able to have that functionality. I think a lot of that comes back to a big piece that is understanding where gaps exist in data. A big issue are change orders and RFIs. We get products, and there's 5, 10, 15,000 change orders on some ridiculously large projects.

What is our ability to identify where the gaps are and show that to you upfront as well as pull out a lot of information? So short answer-- that that is not available to the public market today. It is something that you will see in the very near future. Sir, I think you had a question.

AUDIENCE: [INAUDIBLE]

SATYAM VERMA: Let's try. So I won't even let me. I mean, right now, I have the right view up here, and it's not even showing anything.

AUDIENCE: [INAUDIBLE]

SATYAM VERMA: Oh, that's a good idea. Let's let's try that. I have my own HDMI cable. Let's just use that-- exactly.

They might get mad at me for unplugging their stuff, but that is OK. I don't mind. Greg [INAUDIBLE] with the great ideas here today. Thank you, Greg.

I've got to get the connector. It's short. I appreciate it. Thank you.

Hey, you've got a winner. Yeah, I mean, it wasn't really recording much in the first place and then a flashing screens. So yeah, I mean, it was it's been flashing the whole time.

All righty, then should've just done this from the beginning. So it's a very basic platform. And that's something that I think is actually what drives a lot of uses. There's not a lot of bells and whistles.

Generally, we get people up and running under 10 minutes. We see adoption rates. And if you think about average technology adoption, you think 20, 30% generally in the first year of people are actually going to get it implemented in their projects.

What we're seeing is closer to 60% to 80% of average adoption within the first year, number one, because nobody likes actually doing this manually. So when you give them an option, they really do jump on it. And number two, we're providing much more accurate and much more efficient data, so it really makes sense.

So let's go through and do AU 18 demo. We captured some different product. Now, we'll do product number one, and we'll talk about versioning.

So once again, we spoke about how most teams don't really start this process until they get issued for construction sites, ut it's really a final set. What really should be happening is you guys should be understanding and looking into your scope of cost and schedule and everything starting from the design phase, then the bid phase. And how does this scope change from one version to the next?

And how does that impact your cost and schedule, which is why we capture a version name? So we'll go in here and throw in and IFC. We also capture some just basic project information. So what is your completion date, the type of project, and the average value of that project? And we hit Create.

Now there are really only two rules that you've got to keep in mind when you're using the Pype Autospecs specs system. Rule number one is that your document needs to be in PDF format. Now, this can be a native PDF file, but it can also be a scanned document as well. And rule number two is that for the most part, it needs to follows standard CSI rules.

Now CSI has the 16, 32, the 64. There's probably so many out there I can't even keep track of them. Doesn't matter which one of those. We can even have a document that includes multiple different formats in the same one in the same document, and we'll be able to take care of that as well. So it's not an issue at all.

What we're going to do for today's purposes is use a hospital renovation document. It's a fairly smaller document. It's about 500 pages. I believe it took a PE about seven to eight hours to really get to a strong basis where they can then go review, hey, what do we need? What do what do we not need?

I can upload the document as a whole, individual sections, individual volumes, however I like. I hit upload. It's going to push that system that document onto our system. We go through validation, which will then validate the document, which is just ensuring that it is, in fact, a PDF document and we generate submittals.

So once again, this process with this little spinning circle took an actual person seven to eight hours to do with, let's say, 70% accuracy is what we see as kind of the industry average. With this sized document, I would estimate-- sometimes it depends on the Wi-Fi how long that might take. A scanned document is going to take slightly longer as well. This one I'd say 30 to 45 seconds, maybe a minute at most until we're able have gone through everything and understand what all the requirements are.

And then we'll be able to see exactly and toggle on and off certain aspects to really drive what we want to look at. So as you can see, by default, we have our action information in close out. And I'm going to toggle on some of our QA, QC requirements.

We have your fields QC, your mockups, your QA, your test inspections, as well as all of your Division I requirements I'm going to give it a second to load. And what you're looking at here is what we call a smart register. It looks a lot like Excel. There's a lot of added functionality, and we'll get back to this screen in just a moment.

Where I'd like to start, though, is on our dashboard because within a minute of having this document, I understand and have a very clear idea of the full scope of my project requirements. I have all of my action and information requirements here. I have all of my close our requirements, as well as all my, as I said, test inspection, QA, QC, and mockups.

Many times, we see project teams that they're under such a time crunch that the whole right hand of this screen, the closeout and everything else, they're like we'll do this later. That's crazy. You need to understand what your closeout requirements are on day one.

If we wonder why 90% of products don't close out on time, it's because we don't even know what the closeout requirements are until halfway through the project because we don't have the time to really get into it. And so this alleviates that pain of the time crunch, gives you this data upfront, and provides a strong basis for you to get familiar with them. One of the biggest pushbacks is, hey, we need project teams to get familiar with these documents, and that's an extremely important point. And it's a valid piece of concern.

But what we're doing-- we're not automating everything. You still 150% need to have your product teams getting familiar with these documents. You're just giving them tools to make that process easier. I can dive into any specification or any specific group here, so I chose samples for this example. And then I can also, by clicking on one of these PDF icons, open up what we call spec view.

Spec view is going to give you a view that shows you all of the requirements that we've identified, as well as display the document that you uploaded yourself. And it's a little light on this screen. I don't know if you guys can see it, but we highlight-- like this is b. It's a little green highlighted right here. We highlight exactly where we brought that in from your spec book itself.

So not only can you use this to be comfortable with the work that we're doing in regards to how accurate we are, but it's very easy to access, verify, and identify these within the platform within just a couple of seconds. I've seen scenarios where someone trying to find a submittal. I have my Safeway spec book and just turning to page 732 and finding paragraph four-- at least it would take me like maybe two to three minutes. But even then, once again, take those two three minutes, multiply that by 200 submittals, and just that in itself is a lot of time just trying to find where a submittal is in your actual documents.

On the left-hand side, we break down every division and every section, and I can come in now and say, hey, I want to figure out what my rough carbon Q requirements are. I have a couple of filters here. I'm going to clear my filters that we can see everything.

I click on it. It brings me to that section of my spec book. It highlights exactly where we brought in these materials certificate requirements from. And then beyond that, I can now go and edit any aspect of this as well.

But now, let's say there was a requirement that we miss, which doesn't happen very often, is that coming from clients directly, we've been marked at about 99.7% accuracy. But what we do here is highlight if there ever is even the slightest doubt that there was an error. And what this is kind of notifying teams is, hey, we did search through this, but we did not find any submittals.

We're highlighting this so that you can double-check, review this to ensure we didn't miss anything. But let's say in the rare scenario where we do miss anything, we have what you called smart builds. You can come to smart builds.

So they're showing you how to use it. I can say, hey, you missed this requirement. All I do is highlight that, and it automatically fills everything in for me and creates that requirement for me.

So now, once again, let's take away the manual entry. Let's take away some of this just unnecessary time crunch that we have, do it, and then you can come in here and make any changes, of course, that you want. You add it.

And now you have a whole new requirement there. Beyond that, we capture all of your product data with something else you spoke about. This is being used to build procurement logs, to bill of material expediting logs. I can come in here and very simply search for any basis of design requirements. It's going to show me anything that has that.

So I can very quickly narrow that down. I can search for sole resource requirements, search for manufacturer information, and export this directly into whatever format that I want. And [INAUDIBLE], this can be used to help superintendents out. This can be help to use building schedules.

This can be pushed into scheduling platforms or really wherever you want. You're going to have it in an Excel sheet. And now, let's touch on versioning-- so going to hop into another project that we have. Some of this data already set up in, so we can understand once again how are these documents evolving.

How is my scope of work evolving? We bid, and we put a time, scope, and a cost out there. And then we got issued a whole new set of specs, and that drastically impacts the scope of this project.

Well, you can simply the new version of specs, and we will compare that for you once again within a minute or two. So now you can see, hey, this is our 65% IC. This is 100%.

We added 1,000 requirements. By the way, that's going to have an impact on cost. It's definitely going to have impact on schedule. And, of course, all the architects are going to say that's your problem. You already bid on this.

We already have this is what we expect you guys going to figure. No, now, you have proof. You went from seven mockups to 28 mockups. Currently, not many people are even getting to this stage because it does take a lot of time. But now, you actually have actionable data where you can understand everything that's been added, modified, or deleted with the click of a button, narrow down on what's going to have the largest impact on cost, the largest impact on schedule, and bring this back to the table and say, hey, this is what we're dealing with.

Let's figure out how to make this work for everyone. This is the time impact. This is the cost impact.

This is a team game. This does not all just fall on the shoulders of a general contractor or a subcontractor, whoever that may be. And this data allows us to really take action on those.

So as I said, it's not super complicated. There's not 50 clicks you've got to do to get into anything. You upload your document. We provide you the data, and you guys take action on that data to create much more efficient workflows, effective workflows that give people their time and their back. Do you have a question? Oh, I'm sorry. Go ahead-- yeah.

AUDIENCE: [INAUDIBLE]

SATYAM VERMA: A flattened PDF?

AUDIENCE: [INAUDIBLE]

SATYAM VERMA: To my knowledge, there should be no effect of it whatsoever. We will function just as I'm showing you here today. So if we take a quick step back, we uploaded a document.

We got a nice base understanding of what those requirements were. We went in, and we did a review process with our project team. I can now share this with my design team.

I can share this with my architect. I can share this with other project team members. They can come in. They can help me fill out things like what subs are these being assigned out to, what are the target dates. I can very simply generate reports like submittal schedules.

I can come in here and say, hey, I want to know everything that's been assigned to contractor ABC, narrow that down. I can hit Generate. And what that's going to do for me is generate a fully-branded hyperlink searchable PDF document that can be sent directly to these subs. And they now have a very clear understanding with full detailed descriptions of what is required of them-- so very straightforward, very simple.

Now in the end, the burning question is this is great. If this can't manage my symmetries, where do I put this stuff and how do I get it there? Well, it's as simple as clicking on our Export button, and we have a long list of integrations.

We integrate with pretty much every last project management platform that's out there. Of course, BIM 360 is at the top of that list. Direct integration, where we integrate directly with the similes module as well the document module, will send all of your symbols directly into BIM 360 as well as break down your entire document into doing the proper naming structure for every section and proper folder, send all that information directly into BIM 360 Docs, as well as the requirements overview, as well as an entire submittal log so that you guys don't have to do that manually-- going back to the same concept of saving time and giving that back to implement stronger workflows around QA, QC, and bringing sanity back to a product engineer's life.

So went over quite a bit. Once again, I appreciate you bearing with me with the technical difficulties that we were having. I wanted to see if anyone has any more questions as we're getting near our time limit here.

AUDIENCE: [INAUDIBLE]

SATYAM VERMA: Yeah, so any division, it will. It works. And as long, as I said, it follows a general CSI, it doesn't matter which CSI format. We will be good. Right there.

AUDIENCE: [INAUDIBLE]

SATYAM VERMA: So there's different workflows. That's really dependent on the users themselves. You can choose to give subs access directly to the system.

And the great part is, as I said, we have audit functionality. So you will know if your sub goes in there, you come in here. You come to actions. You do history. If you give them direct access, this is how you'll be able to kind of keep tabs on what they're doing or--