Good afternoon. Welcome to PCI's webinar series. Today's presentation is Optimize and Automate Your Precast Production Using Edge. This webinar is sponsored by PTAC. My name is Nicole Clow, Marketing Coordinator at PCI, and I will be your moderator for this session. Before I turn the controls over to your presenters today, I have a few introductory items to note. Note that all attendee lines are muted. The GoToWebinar toolbox has an area for you to raise your hand. If you raise your hand, you will receive a private chat message from me. If you have a question, please type it into the questions pane where I will be keeping track of them, and will read the questions to the presenters during the Q&A period. Also, a pop-up survey will appear after the webinar ends. Today's presentation will be recorded and uploaded to the PCI eLearning Center. Questions related to specific products or publications will be addressed at the end of the presentation. PCI is a registered provider of AIA CES, but today's presentation does not contain content that has been endorsed by AIA. Today's presentation is non-CEU. Our presenters for today are Jordan Watkins, CEO of PTAC Engineering. Joining Jordan is Alyssa Roberson, Director of GoToMarket Strategy at PTAC Engineering. I will now hand the controls over so we can begin our presentation. Today we're going to be going over what exactly is EDGE, and how do we employ it to make the precast workflow more seamless. We're going to be diving into the EDGE platform, which is really composed of four different solutions to facilitate the different processes throughout the lifecycle of a precast concrete project. Taking a bit of a step back here, what exactly is EDGE? Back when PTAC Engineering was in its infancy, it was really just a consulting engineering firm that catered to the precast concrete industry. As they were going through and creating these models, detailing them, designing them, they figured out that all of these software solutions that they were using were cumbersome, and it was very difficult to accomplish just the basic things that you would need to get out of these programs. So that's really when EDGE was born. EDGE is a software package that facilitates not only the modeling and design process, but it also finishes it out through the end phases towards production and the erection phases of the model as well. All of these solutions are based on a Revit model. So once the model exists, each of these different solutions or platforms are going to basically be extracting model data to facilitate those different processes or the different end needs. So the first platform we're going to be talking about is going to be the EDGE for Revit. This is actually an add-on tool for Revit. It is composed of a suite of roughly 80 tools, and this is going to really facilitate not only the modeling process, but everything that we can extract from the model through the Revit interface as well. So using our custom EDGE content, this is going to allow us to efficiently and very easily generate highly detailed models. We're going to be able to use these suites of tools to generate very custom and unique precast shapes. We'll be able to extract section properties very easily and rapidly from those pieces that we model. And then based on that model that we generate, we're able to easily extract all of that model data and all of those parameters to use for processes later on in the project, such as scheduling to create your production bombs or your loose material accounts, all the way to your shop tickets and your erection drawings. So we're going to dive a little deeper into some of our key tools in Revit. Like I mentioned before, it's very easy using our EDGE content to create very unique and custom precast members. So in this graphic here, I'm showing basically a wall panel with some cutouts and some supporting members on them. This is a very generic example, but it demonstrates what I'm talking about here when I say that we use an add to cut from workflow. So we start out with very simple shapes like the square or the rectangular wall panel that you're seeing here. And then we add on concrete to it to create additional features, whether it be architectural features or supporting members like ledges or haunches. And then we can also go through and use voids to create openings, recesses, or reveals in that member as well. And through a combination of those add-ons or voids, we're able to create as complex of a shape as we need very rapidly within the project. And that's nice because that means that you're able to create these unique shapes on a per project basis, rather than having to spend a lot of time creating custom unique families for a job that you're only going to use once. So it's eliminating that overhead of having to create custom families when you're able to create them on the fly within the job. We also built these families with a nominal workflow in mind, meaning that these families have a joint parameter built into them. So we can go ahead and lay out the entire job without having to go through the mental gymnastics of thinking about what our values or our spacing needs to be with that joint in mind. Instead, we could essentially model it without the joint and then at the end, come back through, apply a joint value to those, and it's going to update the model accordingly to reflect the joint between each of those precast members. That's also nice if your joint ends up changing later on throughout the project. Again, you're easily able to go through and update all of those after the fact as well. Like I mentioned, all of our Edge tools are really model driven. So we're able to also automate the estimating process. And again, it's all going to be based on that Revit model that you create. So we're able to pull out information from the precast members, such as the overall length and width of that member, whether it has any openings, what are the size of those openings, and if it has any haunches on it and whether those haunches are up in form or not. So we're able to take all of this information, extract it out, save it to some external file format, which can then be imported directly into an external estimating or proposal software. So not only can you take it from the conceptual phase, but as you're working through the model, Revit kind of automates the scheduling process for you. It's all based on what you physically modeled. But through the Edge parameters that we've employed, we're going to allow you to be able to refine those schedules much more easily. With the Edge parameters and with certain Edge tools, we'll be able to customize schedules to show maybe just our loose material, or maybe we just want to get a schedule for our materials for a certain product line. Or maybe even we have a few different phases of a project, and we're wanting to only schedule out phase one, and then come back later and get a schedule for phase two. Using these parameters, we're able to quickly filter down our schedules according to those criteria. A common theme with our Edge tools is we try to automate those tedious tasks. And one of those is going to be piece marking. So we have a suite of tools that allow you to automate this process once you have a model that's generated in Revit. So essentially what this tool is going to do is it's going to look at every single precast member that you have modeled, and it's going to compare them to one another. As it's going through and making that comparison, it's going to be comparing things such as the overall geometry of the precast piece, which will be inclusive of any openings that it may have, any recesses, any reveals. It's also going to look to see if it has any of those add-on concrete members that we were talking about with that add-to cut from workflow. So does it have any ledges? Does it have a bullnose? And where those are actually located on the piece. It's also going to be comparing plate locations between those precast members when it's looking at them, and also making sure that they have the same types of plates in order for them to potentially get the same piece mark assigned to them. And it's also doing a full section property analysis on those precast members. When it's going through and doing those comparisons, it allows for a user-defined tolerance. So when it's looking at, for example, the plate location comparison, when it's looking at the two precast members to see if their plates are in the same location, if the user had defined a tolerance of, let's say, half an inch, that means that the plate locations can vary by up to half an inch, and those two precast members still potentially get the same mark assigned to them. So once it's created all of those buckets, so to speak, of like precast members, it's then going to go through and automatically assign piece marks to each of them. The naming convention that it uses for the piece marks is, again, something that's defined by the user. So that's completely customizable, so you can define what that should look like for each of your producers. This piece marking system allows us to group like pieces together to more easily allow us to cut down or make us more efficient during the shop ticketing phase. That way, we're able to create one shop ticket to represent all of those piece marks, rather than maybe having to duplicate or triplicate those shop tickets for pieces that aren't, are identical that we didn't maybe manually identify previously. Another task that we automate through EDGE is working. So let's take, for example, this parking garage that we have on our screen here. If we were wanting to work the deck to allow for drainage in here, this tool is dependent on the user defining what the changes in elevation should be. So based on those changes in elevation, we can see here that once they run the tool, this is going to automate the warping of the actual precast members. So here in a second, we'll be able to see that the double Ts and also the T girders in this project were automatically warped. And in addition to that, it also fully displays what the version of the model looks like in both the flat state and the warp state. So as it was going through and toggling on visibilities, we were able to see all of the connections in the erected or in the warp state, in addition to all of the connections in the flat state, which is going to allow us to be able to more rapidly create sections and details during the erection drawing portion. We also have tools to facilitate the project management portion. So one in particular is our ticket manager. This is basically a snapshot of every piece ticket or sorry, piece mark in the job. And it quickly tells you at what stage of the project lifecycle it's in. So it's going to let you know if it's been reinforced or if it's had a shop ticket created for it yet, all the way to whether or not it's been released. We also have the ability to automate shop tickets that are fully detailed. So for starters, one thing that the tool needs to know is what the shop ticket should actually look like. Since there's no standard really across the board of how everyone wants their shop tickets to look. And it varies from one producer to the next. We have a tool called the ticket template creator. This basically lets the user define what their actual shop tickets should look like for a certain product line. So this is going to let the user define what you should actually exist on the sheet. What should be visible in those views, where the views should be located? What bill of materials should exist on the sheet? If any, where it should be placed? Also, what information should be filled out in the title block? And any standard details that you might want to see on that sheet as well can all be defined within that ticket template. So once those ticket templates are defined, that is what our actual shop tickets are going to be based on. So using this auto ticket generation tool, this is the one that's going to let you know So using this auto ticket generation tool, this is the one that's actually going to create your shop tickets for the specific pieces in your job. When you run the tool, you choose what project or what ticket template should be based on. It's going to regurgitate all of that information. In addition to adding dimensions for the precast member and its associated materials. And it's going to add call outs for the materials as well. So here's a video kind of going through both the modeling and then the shop ticket creation phase. So we can see here that using some edge tools, we're able to generate a simple model here with cutouts, openings, also our connections, reinforcing. We have this one particular assembly here, which we're about to create a shop ticket out of. So using the auto ticket generation tool, you define what ticket template it should reference. That lets it know all the information about what view should exist, what should exist in them, where they should be placed. It regurgitates that specific to this assembly. It goes ahead, places that all on a sheet and it dimensions to the precast member itself, including any cutouts and also to the materials in the view, along with call outs for them. And it also generates your bill of materials and fills out your title block with the typical information that you would want to see. Here are just a couple more examples of shop tickets completed using the edge tools. This has a different example on it that I wanted to show. This one has some standard details that were built in, such as the shop note at the bottom, the finish note and the production finishes. And again, just one more example of a shop ticket created using those edge tools. And lastly, the last tool I want to point out here with the edge for Revit tools is we also have an auto dimensioning tool that allows you to more rapidly generate dimensions that you may need for your erection drawings. So I'll go ahead and play this video really quick. But what it's going to go through and do is show you that with just a few clicks, you can run this erection drawing auto dimension tool and it's going to automatically place dimensions for the selected elements. So previously, I placed dimensions for my grids. Now I'm going through and I'll be placing dimensions for all of those double T's that were selected. It's going to dimension to the extreme extents in that direction of those double T's. And now I'm placing a dimension in here from those selected grids to all of those spandrel plates. The unique thing about when you're dimensioning to materials is not only is it adding the dimension string, but it's also going to include a text note out beside the dimension string that includes the quantity of those elements that were dimensioned to, in addition to what their mark or name is. So moving on to the next Edge solution, which is Edge ERP. So Edge ERP basically takes your Edge for Revit model again and extracts relevant information from it. That relevant information that's extracted is saved to an Excel file, which can then be imported into enterprise resource planning solutions. So this is going to allow you to track your precast members throughout the design for erection phases of the project. It's also going to allow you to more easily predict your long range and short range scheduling needs. In addition to allowing you to order your mixes appropriately based on the precast members that exist in the project. The Edge for ERP tools are actually split out into three separate components. There is a pieces export and assemblies export and a materials export, regardless of which of those three you're actually running. You have the option to export everything within the model, or you can tailor it down to just specific elements or a specific grouping within the model. So onto the pieces export, this tool is geared towards the precast members within the model. What it's going to do is it's going to extract general information about those pieces, such as their length and width, what their surface area is, their volume, their weights. Then we have our assemblies export, which is geared more towards the embeds of plates, cast in place materials and loose materials. This export is going to include information about the quantities of each of those that exist in the model. It's also going to tell you which particular precast member that element is associated with back in the model. And then it's going to give some identifying information about those as well. And then lastly, we have the materials export, which is going to include information about the quantities of each of those that exist in the model. And finally, we have the materials export, which is going to handle things like mesh, rebar, or strand. This is going to be very similar to the assemblies export in that it's going to export information such as quantities, what particular precast member that element is associated with back in the model. And then again, some identifying information about it as well. So now that we have an example, it's going to go through and show the pieces export. But you can see here that we have pieces, assemblies, and the materials export. Regardless of which you run, again, you can either choose to run it on the whole job or just specific portions of the job. Once it finishes, it saves the file to an Excel file, which is what we're looking at here on the screen. Since we ran the pieces export, it contains information like the piece marks, quantities, your length, width, weight. And then also at the end, we're able to see information about what revisions exist for the sheet, if a sheet exists, who drew the sheet, who marked the sheet as detailed, and the dates and people that perform those actions. So here are just a few more examples of the ERP exports. We actually have one of each on the screen. So up top, we're showing the assemblies export on the left and the materials export on the right. It shows each of the materials, the quantities of each, and then again, some identifying information about them. And then down at the bottom of the screen, we have another example of the pieces export, which again, for each piece mark, it gives us our quantities and then some basic information that we may need to know about it. Which brings us to our next EDGE solution, which is EDGE for Cloud. EDGE for Cloud is more geared towards the production side of things. So traditionally, when the production personnel are going through and producing a piece, they have a printed 2D shot drawing that they're referencing. EDGE for Cloud is intended to either supplement or replace that traditional 2D shot drawing that they're using. So EDGE for Cloud is a web-based solution. It provides both a 3D and a 2D view of the piece. And it's linked directly back to that Revit model again. So everything that is available for that piece in Revit is sent to EDGE Cloud and is accessible in that web viewer. So this is going to provide more information than is typically available on that paper shot drawing. And it also opens up the line of communication between the production team and the engineering team. So it does have the two different viewers, but regardless of which viewer you're using, some of the information that's available to the user is going to be the same for both of those views. It's always going to provide member information about the piece, such as its weight, its volume, any architectural mixes that it may have, if it has any finishes, things of that nature. It's also going to contain or list the same information about the piece that would be available in Revit. So if there were parameters defining what the final strength is or what the release strength is of the piece, those would be reported here as well. In addition to all of this other information, which I'll show you a little bit later on in the video. Another thing that it automates for you is revision tracking. So when you send a piece from Revit to Edge Cloud, it's going to log each time that that piece gets sent to the Edge Cloud platform. Meaning if you exported a piece once, and then the engineering team goes in and decides that they need to make some sort of revision to it, they go ahead and make that change in Revit, they re-export it out to Edge Cloud. That's going to show both the initial export and then the most recent export. And then users who are actually looking at the web-based Edge Cloud platform are going to be able to easily see if they're looking at that older upload or if they're looking at the newest version of the piece, which we have a video here showing. So here's just my 3D model of a piece within Revit. There's also a 2D view associated with it or a shop ticket. We're going to run the Send to Edge Cloud tool on it, which is going to export all of this Revit information out to Edge for Cloud. So you go through, it splits it out into the different projects that these exist for. We load the piece that was just exported, and it opens us up to that 2D view that we were seeing back in Revit. Now, again, let's say some change needed to happen. Maybe this bottom view wasn't supposed to exist. We delete it in Revit. We rerun the Send to Edge Cloud tool. This is going to re-export the most current information about the piece to Edge Cloud. And you'll notice that it provides a banner at the top telling you you're not looking at the latest version. You're looking at one of those older ones. Once you reload it, it pulls in the newest version, and you can see there that it's no longer showing that bottom view that I deleted back in Revit. So the 3D viewer on Edge for Cloud, it's going to provide a view that looks very similar to what you might be familiar with in Revit. You'll be able to pan and rotate around the piece just as you would in Revit. You have visibility controls so that you can change the transparency of concrete, create section boxes, and you can also add things like annotations and pull dimension strings within this 3D view as well. So here in this video, it's going to kind of walk you through some of those tools. Like I was saying, you can control the transparency of concrete so that you can actually see the materials within it. We have toggles for embed, lifting, and rebar to easily be able to control their visibility. There's also the option to create section boxes around specific elements. You can control the size of the section box using that slider bar, but this allows you to get a more detailed look at a specific portion of the piece. You're also able to see the parameters or the properties associated with those specific model elements. And again, everything that was available in Revit will be listed in that properties menu there as well. And then in the 3D view, we're able to pull dimension strings on the fly as well. It's also going to list out your bill of materials. As you can see on the left, it splits it out into whether it's embeds, lifting, rebar, or strand. As you actually click through the bill of materials, which is on the right hand side, you'll notice that the elements that are selected in the list are actually being highlighted or selected in the model, making it more easy for the user to find where those particular pieces are. And then we also have the production sequence, which allows users to be able to toggle between those different states so that they can view the appropriate portion of the piece that they need for that production phase, such as just the form geometry, just the bottom and form plates, or just the top and form plates. We also have the 2D viewer side on Edge for Cloud. The 2D viewer, at first glance, looks very similar to just what a printed shop ticket would look like. But in addition to that, you're also going to have the added ability to incorporate your quality control process. So we have a suite of tools to allow you to mark up a sheet and actually save those markups associated with that sheet. So again, another little video here to demonstrate the 2D viewer on Edge for Cloud. Like I said, we have what looks like just a traditional shop drawing, but there's other information baked in here, like it's showing a chart right now that allows you to view basically the overall state of the job, how many pieces had been marked as reinforced, how many had been released. You can also pull dimensions on the fly, just like we were able to in the 3D view. It gives you customization over the precision and what units it's reporting that dimension in. Some of the tools that you saw in the 3D viewer are also available in the 2D viewer. Like here, it's showing the toggles for embed, lifting, and rebar. We have those same options here in the 2D viewer to easily turn on or off the visibility of those things. We also have our properties, which is going to show all of the information associated with that particular element. Again, we have our bill of materials, exactly the same as we saw in the 3D viewer. As you're selecting it in the list, it's actually highlighting it in the, or on the sheet as well, making it easier to find those elements. It also has that added ability to create markups directly on your sheets. It's going through now and creating a new markup for this sheet. You can create different shapes, such as revision clouds, circles, rectangles, arrows. You can also add text for any comments or notes that you need to add in here. There's also a highlight tool that will allow you to go through and highlight things as necessary. After you've added these markups, you still have the ability to modify them or delete them as you see fit. Once you've added all the necessary markups, you can save it to the sheet. And then from that point forward, you can always reload those markups that have been saved just by loading it from this drop down menu here. And then at this point, you could either add to it or modify the markup as you see fit and you could resave it if necessary. So our fourth and final solution with the Edge platform is our Edge CAM solution. This is again geared more towards the production side of things. This extracts your Revit model information into a file format that's going to be able to be consumed by production automation machines. So again, this is all driven, but once your model exists, you'll be able to take what's visible in the view and convert that into either a PXML or a UXML file format that can then be fed into these machines for different production processes. The exported file that's sent out by this tool is going to be split out into basically three main groupings. The first grouping, Lots, is going to contain the information about your actual precast member. So if you have maybe a face mix and a back mix, those are going to be represented as different layers within that exported file. It's also going to represent what the perimeter or the contour of that precast member is, in addition to any cutouts that may exist for the piece. It's also going to send out information about mount parts, and what it means by mount parts is that's going to include things such as plates or lifting and handling type elements. And then lastly, we have our third category of reinforcement, which is going to include your actual rebar elements or your mesh. At this point in time, there are two file formats that we support export out to. It's either Progress Groups PXML file format, or we also support Unitechnics UXML format, and we support three different versions of that one right now. So here's an example of the UXML export. We have our piece within Revit. You can actually customize these exports to contain only the relevant materials that you want to actually be exported or sent out. So what we're showing here is it's going through and hiding those plates in the piece. That means that when I send this export out, I can tell it to only export what's visible in the view, and the export will essentially ignore those plates or anything that had been hidden. So I'm actually selecting that option to export what's visible in the view. I would choose the file format that I want to send this export out to. When it does that, it's actually saving this file to somewhere on your machine. So here in a second, it's going to switch over to a viewer. And in that viewer, we'll be able to see what that exported file actually looks like. So there's the file that was exported, and it's just loading it in. Over on the right-hand side, it shows a visual representation of the information that's actually in the exported file. So you're able to see the actual outline of the precast member. You'll notice that the plates that we hid aren't actually visible in this export, but we are still seeing all of the reinforcement and lifting and handling that were still visible in that view when we exported the piece. So moving on, now we have a brief example of the PXML export, which is that other file format that we support. Here I have two different views of the same piece. One is customized to show just plates and lifting. The other one is showing the reinforcement. So here it's going to show the reinforcement one first. You'll notice that, again, it just exported what was visible in the view, which happened to be the reinforcing. And then we have this piece over here, which was just supposed to export our lifting and plates. Another unique thing about this is, and you can kind of see it in this view, you can tailor what things look like when they're exported as well. So not only just whether they're visible or represented in the export, but you can also control whether a plate is showing through as maybe just a line in the exported file, which is what you're seeing on the screen. There's a few vertical and horizontal lines, which are representing plates. Or maybe you wanted plates to be represented as just a dot. That's also achievable through this. So it doesn't have to be the geometry of the plate itself that's in the export, but you can tell it exactly what you want that to be represented as instead. Now with our exports, it is dependent on the precast member being prismatic. So what that means is we can't have any variation in the depth direction of the piece, because it's just not supported by those file formats. So the way we work around this for things such as our double Ts is we've added an option to be able to only export out a certain portion of the double T. So I'm going to go ahead and play this video of the example, and I'll talk through what it's doing. So if I were to just export out this double T, since it's dependent on it being prismatic, it's going to export out one solid block that represents the double T, and it's not going to be exporting out the flanges, since those are not prismatic with the most extreme exterior extents of the flange. So when it exports this out, we'll actually be able to see that. So notice here how when we rotate around, it just looks like a large box that represents the double T. We're not actually seeing the stems or any of that come through. So with this additional option, it's actually a parameter on the piece called can flange only, if that is checked on or enabled, what that's going to do is it's going to tell the export tool that it should only export the flange portion of the double T, and it's basically going to ignore everything that's beneath the bottom face of the flange, which means the stems and any of the materials within the stems. So when we reload this file, you'll see that for the outer extents of the precast member, we're just seeing the flange now, and we're only seeing the reinforcing and plates that were within the flange portion, and everything else essentially gets excluded from this export. So one key differentiation between the UXML and the PXML file formats is the support for reinforcement. UXML is definitely more limited in terms of what it's actually able to support, and that's all just based on the file structure. So what I mean by limited is that there's only a couple of orientations of reinforcement or rebar where when you export it to UXML, it's actually going to be able to show the bar as its actual shape. In most orientations, it's actually going to end up showing each rebar as a bounding box that basically defines the most extreme extents of that rebar, rather than showing the real rebar shape. PXML is more advanced. It's going to allow you to be able to give a more accurate representation of each of those individual bars, which is what you're seeing on the screen here are a few different examples. So regardless of how complex that shape of the reinforcement is, the PXML exports will be able to represent the actual geometry of those bars, rather than dumbing it down to the bounding box approach. For the mesh export portion of the CAM export, there are two different workflows that can be used. The first one is supported by both UXML and the PXML file formats. This is going to be a dumbed down version of mesh, basically meaning that it's just going to represent the most extreme length and width directions or the bounding box piece. And that's how it's also going to be reflected in the exported file. The second option is only available for PXML. And again, this is just a limitation of the file format. But with the second option, it's going to allow you to have a more accurate representation of the mesh. You'll be able to see each of the wires that make up the mesh construct within that exported file. So this video here is going to talk through that first example, the simplified version of mesh. So what you're seeing on the screen here, that dashed outline, that's our simplified mesh family. It just represents the length and width direction or basically a bounding box for the mesh. When we export this, the exported file is basically going to reflect the same thing. We're just going to end up with a bounding box that represents that overall length and width of this shape here, rather than showing the individual bars. So when we open up that exported file, like I was saying, that blue bounding box that you're seeing, again, it's just a bounding box. It's not representing real bars or real wires within that mesh. Here's an example of that more accurate representation. In our model here, I have the mesh modeled as mesh families with nested bars within them. And I'm able to associate those bars with the overall sheet of mesh using that mesh sheet parameter that it's pointing out. On the top sheet, it had all of those bars associated together with the mesh, whereas on that bottom sheet, it's showing that since the mesh sheet parameter is empty, they're not associated with that overall sheet. And in terms of the export, that is going to mean something. The ones that aren't associated with the overall sheet of mesh are not going to get exported as actual mesh. They will instead get exported as individual bars. Whereas that top sheet of mesh where everything was associated will get exported as one sheet of mesh that contains each of the bars within it. So here's our exported file, and again, this workflow is only supported for PXML. But over on the left-hand side, you'll see all of those instances that say single items. Those are all of those individual pieces of rebar that were not associated with a sheet of mesh, basically the ones on the bottom. Whereas we have that mesh category on the left-hand side, that's representing that top sheet of mesh that had all of the bars associated with it or grouped together. So what are some real-world applications for these Edge4Can export files? One is going to be a laser projection. Using these files, you'll be able to project elements directly onto the bed and directly onto the top is cast face of the piece. It can also be used for water-soluble bed plotting, which is going to eliminate the need for extensive detailing since you're able to directly plot those elements. They can also be used for automated rebar bending machines. So instead of going through and manually bending them, we can take that rebar information that was extracted directly from the Revit model, feed it into the rebar bending machine. It can also automate the mesh fabrication process. This is going to allow you to create those custom mesh sheets on the fly and also incorporate any cutouts that may need to be represented within them. It also eliminates the need to inventory mesh. And lastly, it can also be used for concrete distribution and also for shuttering robots to automate the placement of formwork. All right, thank you, guys. Thank you, Alyssa, for a great and informative presentation. We will now start the Q&A portion of our presentation where Alyssa will be joined by Jordan Watkins. Our first question is, is Edge compatible with out-of-the-box Revit? If Jordan is P-TECH, I can take that one. Yes, Edge absolutely is compatible with out-of-the-box Revit. In fact, P-TECH Engineering and our Edge for Revit software team is partners with Autodesk, the creators of Revit, in our development. So it's a very complementary solution between our Edge software as well as our Revit software, and we ensure that they're always complementary of each other. Wonderful, thank you. Our second question is, what is the advantage of using Edge over other 3D software? I can take that one as well, too. So obviously, we're a little bit biased, but I think a lot of advantages of staying within the very traditional AEC ecosystem and neighborhood. So as a lot of the folks on the call know, Autodesk Revit is the predominant detailing and 3D modeling solution for architects and engineer records around the country, and being in that same environment as them and not working through a disconnected IFC type of data transfer makes our process a lot more elegant. One thing that also I think is a large advantage is, as P-TECH Engineering, we are solely in the precast, pre-stressed concrete business, whether it be our detailing business or our design software business, our software business. We stay within that system. So with our market being very niche, I think we're in tune with a lot of the needs of the customers and a lot of the needs of the industry, and we're working to ever-evolve our solutions to make sure we satisfy a lot of the pain points of the industry from cradle to grave is our approach. So living and breathing the industry on a daily basis and being partners with Autodesk, I think is a huge advantage of Edge. Sounds good. We do have another question come in. Is Edge available for universities for teaching purposes? It is, absolutely. We handle that on a case-by-case basis, but I would ask anyone to reach out to me directly. We have sponsored or helped a number of PCI studios use access to Edge for senior designer capstone projects as well as other university coursework. So we're very interested in getting it out into the community in that way. So please reach out. Another question just came in. What units does the tool support, SI, IP, or both? So a lot of our tools are being developed to also incorporate metric units. With it being in the Autodesk ecosystem, the vast majority of our utilities are unit agnostic and they'll allow us to utilize metric or imperial units as the user sees fit. So I would say about 90% of our tools can be used in any units possible, and we're working to make that 100%. Sounds good. Thank you. I haven't... Oh, how do we contact... Jordan, this is for you. How do we contact you about Edge for universities? Yeah. So you can email me directly, happy to distribute that. I can put my email in the chat for everybody. But also if you want to reach out through our ptac.com website or our edge.ptac.com website, all of our contact information is available there as well. Sounds good. As of right now, that's all the questions we've received. I'll give it about like 10, 15 seconds just in case a couple more questions come in. And I actually apologize. It looks like I can't send a chat to everyone. So yeah, please just access our website and you can get our contact information there. So someone did ask, will this presentation be archived on PCI? That is correct. It will be. It'll be on PCI's eLearning Center. And in your attendee post email, you will also receive the handout. And you can download the handout of this webinar now under the handouts toolbar portion. I don't see any other questions coming in. For right now, that concludes our Q&A portion of today's presentation. On behalf of PCI, I'd like to thank Alyssa and Jordan for a great presentation. If you have any further questions about today's webinar, please email marketing at pci.org. Thank you again and have a great day and stay safe.

Optimize and Automate

Precast Production

Edge

Webinar

Alyssa Roberson

PTAC Engineering

Nicole Clow

PCI

Revit Model