FAB Parts in Revit: Where’s my Fabrication Data? How to Overcome the Lack of It.

WILLIAM TUCKER: All right. Good afternoon everybody. I think I'm about ready for this day to be over. I don't know about y'all. This is about the last one. I'm William Tucker, I work for Confer Systems. Kevin Allen and I work for Confer Systems.

We just wanted to point out that those who are having issues with the data, getting their data from fabrication, who are trying to use FAB parts in Revit. So we thought we'd point out some of the struggles we've had to maybe help y'all along. Did anybody download the data, I mean the content. Because you're probably going to go back and download this stuff because we have some files, some Dynamo files and share a primitive file that you may want to start with.

I have no idea what that is. Let's go back the other way. There we go. FAB parts of Revit, can we make it work?

In about 2016 we probably started looking at it, and then we started implementing it in 2017. Our thought here was that we could use FAB parts in production when we could draw everything in Revit.

And without needing to draw and take it back to AutoCAD.

We decided that if we were to export our parts to fabrication, that was fine, but we didn't want to come back into Revit with them. Also, we could produce all the sheets and the documentation inside of Revit. We figured out in the first three were pretty obvious and we could do that. But the last part, trying to produce our sheets in Revit and get our documentation, was not so easy.

One of the first things we looked at was creating the bill of materials for spool drawings and assemblies. Well, thought number one was that we would just use filter by service type. That was the first thought. So here we go, we're over looking for a service type, and where is it? We knew right then that we were in trouble.

So all this was in early 2017. And so, even at that time I don't think that we had, did we have access to the service type and API at that time? So we didn't. For Dynamo, it didn't work either. What we had, well, we could get the custom data through the API. We went to our library and we made another custom data field, and wrote a script to go through every item in the library, and write that service type to a custom data field. Then we used an API to pump the data into our parameter. So it was a tough way to get around it, but we got around it.

For the data we need to refract from fabrication parts, and we need to read service type, and we need connectors on our spool bill material. We had part material in there, but we also had the group name and the material. But we found that with Dynamo, we could actually access that with just the group name off of it just to give us a cleaner bill of materials. And we needed to CID, and sometimes the bought out flag, unless we can do a Dynamo.

Now, connectors, we actually have a node in Dynamo to run the connectors. But if you have any kind of a tab off of a piece of duct, or off a pipe, that one broke. So, sorry. We're trying to get it fixed, but hopefully we'll get it fixed sometime. A lot of people are aware of it. Then there are some things that we need to read from Revit. And write the fabrication parts for when we go back to sheet metal labels, things like that, for like equipment number VAV, item number.

Then we also carry some dynamic hole information for our sheet metal shop. Because I don't know how many people are using dynamic holes, but we find them very useful. So writing information for dynamic holes in the parameter. Now the bad thing is that all of this cannot be done with a Dynamo, it has to be done via the API.

How many of y'all have started working on the shared parameter file? To us, when we see the shared parameter file, to us it's just like what we have in fabrication. It's just custom data. That's the way we look at it. And we're kind of still concerned of why we can't get all of our custom data over to Revit. Our parameters are no different.

Things to think about whenever you're creating your shared parameter file is-- the shared parameter file, you'll make sure you put that in a location that everybody in the organization can access. And think about how you want to creature your groups for organization. We know that ours that we're probably already had to rebuild ours at least-- at least twice. All right?

The type of parameter. Now, another old trick right here is do you want the user to be able to edit that field or not. You know, if we're going to carry over stuff like CID, we don't want the user to think that he can type in there and change that value. So we have a little tip here for trying to make that to where they can't even edit that field.

AUDIENCE: It's readable, schedulable but not modifiable.

WILLIAM TUCKER: And it's writable via programming, yes. All right? So can everybody see that right there? So now, the very first line or the second line right there from the shared parameter file, you have a nice little warning right there, do not edit manually. But we don't see any other way to do this. Well, you probably do it programmatically, but in that user modifiable field there, you just change your value to zero and then that'll change that-- change the one to a zero and it'll make it to where the users can't modify that.

AUDIENCE: So that's opening the text file.

WILLIAM TUCKER: Yes. That's the shared parameter. That just opened in Excel is all it did to make it a little bit easier. I mean, I usually edit it in Notepad myself. But just to make that a little clearer, I opened it in Excel. All right.

Now, when you-- let's see-- add the parameter, you're for most cases here, I'm gonna say that you're going to want that an instance parameter, not a type parameter. And also, the values, the group type, your values are aligned by group type means that if you create a group, then I believe, everything in all groups are going to have the same parameter. But if you do it varies by group instance, then you can have different parameters for different groups. And it's a little bit complicated to explain right there, but-- and to comprehend.

PRESENTER: So everybody understands, or hopefully, you build the shared parameter and then load what you want into your project from there.

WILLIAM TUCKER: Oh, yeah. Yeah. Missed that part there. Building your shared parameter and loadin your parameters into your project.

PRESENTER: And then when you load them, you have to tell them what they're for. So the bottom dialog box there, were ticking the boxes for fabrication, ductwork, hangers, pipework-- and what's the other one-- containment, I believe. So we just tick all four of those boxes whenever we're creating these to make them available to the fabrication parts.

WILLIAM TUCKER: And there's I guess there's other parameters we have that we assign to assemblies sheets. Did you--

PRESENTER: Yeah.

WILLIAM TUCKER: You got all kinds of categories that you will need to help you apply that to. All right. And right now, with service type we can apply that to that parameter with Dynamo. And we should uploaded all the or the Dynamo scripts we're using for this we should have those uploading and they're actually really pretty simple.

PRESENTER: So if you see here on the left, part of those are grayed out, the names. That's the user modifiable option and those are set to know, so that the user can see it, but they can't change it. And then the ones on the bottom is where we can type in our equipment name, all of that good stuff, bought out, dynamic hole. So those are modifiable by the user.

WILLIAM TUCKER: Yeah. For, like you say, the bottom ones we can fill but and you probably use them on schedules or something, but without the API you can't write them back to fabrication parts. All right? There it's just showing a schedule that once we got the data across, then we can actually use that in our schedules.

PRESENTER: Yeah. That's a pretty big one right there. Limitations, we only have and. We don't have or. So you really have to be creative when you build that schedule about how you build it, because you can't have a couple of different options there with or. It's always and. So that does make it a little more difficult when you're building that schedule. But this is where this additional data came in, because now we can filter specifically for, like in this case, 2041. So yeah, it worked out, works out better.

WILLIAM TUCKER: Yeah. And I guess at one time whenever we were trying to use all the filters, so that was actually before we actually had reports, whenever we had all those filters trying to use our or, we didn't have reports available. So reports help.

PRESENTER: Yeah. Reports help.

WILLIAM TUCKER: All right. You even use them for the stuff your view filters. Should have something here you can actually see. We've colored our hangers here different colors, [INAUDIBLE] a different color, if you want to. All right. Same with the REVIT API, just pointing out that inside of it that we can get to some of that other data that we can't get to. And we know that everybody out there probably can't afford a programmer and we're wanting just to try to help them start getting people with Dynamo to-- if it's accessible in the API, they should be able to hit it with the Dynamo. So you just to get somebody to start building the Dynamo nodes. Probably needs everybody input on that to help that, so that everybody doesn't have to go and hire a programmer. All right. So--

PRESENTER: Back up one there.

WILLIAM TUCKER: Back up?

PRESENTER: Yeah. So on the--

WILLIAM TUCKER: Yeah. Probably easier said than done.

PRESENTER: On the custom data status and spool name there, we've actually got our developer to write-- if we process duct work for instance, and we send it for fabrication, in REVIT that duct work by default, the status of that duct work is always design. So we've got our guy, if we process duct work, we've got a button on our ribbon, he actually changes that to sent to fab for us behind the scenes, OK, through the API. And he's filtering for that, just like what happens in Academy P.

If we don't have our status set to approved, we can't even send ductwork out for fabrication. So we have to physically change the status first, then we can send the duct. You know, exact same processes that we were using in Academy P we've now got to work in REVIT from accessing the API.

So and then we're taking assembly name and writing it into our spool name field for the fab parts, which then goes out with the MAJ, so we know what the spool name was based on the assembly that was created. So all of that's happening with just one click of a button for us right now.

We want to-- we think at some point, we're just going to make that tied right in where when the user hits Save or something, it just does all of these things for us. But we're just-- we haven't gone there yet. We're still using it as a user button right now to say I need to update some data.

WILLIAM TUCKER: So our thoughts right here is yes we can make the fabrication parts work. All right. Get back to REVIT here.

PRESENTER: It's not showing.

WILLIAM TUCKER: It's not showing?

PRESENTER: No.

WILLIAM TUCKER: OK. Hang on.

AUDIENCE: Would it help if we start talking and pretend you're done?

PRESENTER: Yep.

WILLIAM TUCKER: What's that?

PRESENTER: They're going to start clapping to say, we're done.

WILLIAM TUCKER: OK. I don't know about the rest you all but--

PRESENTER: Somebody-- somebody get up and do a dance right now.

AUDIENCE: [INAUDIBLE]

PRESENTER: No.

AUDIENCE: You're already up.

PRESENTER: I had to do that on Monday.

WILLIAM TUCKER: Trying to get screens duplicated here.

AUDIENCE: [INAUDIBLE].

PRESENTER: Yeah. There we go. That's--

WILLIAM TUCKER: There we go. All right. Thought I'd just open up a shared parameter file here. And then like I say, just make sure you put this thing-- that can be seen, can't it? Can't be seen very well, but it can be seen. There we go. A little better?

PRESENTER: Yeah.

WILLIAM TUCKER: All right. So yeah, just make sure you put that shared parameter file where it can be accessed by everybody.

PRESENTER: So do the pull down there. Yeah.

WILLIAM TUCKER: And just notice here, I just put two groups in and all this is in the documentation. Then I've got some that's read only, some writable, just so when I get back in the shared parameter file to modify it I can figure out which ones to change, because things get a little bit jumbled around in that. All right. Let's look at some-- what time's it getting to be anyway? Still got--

PRESENTER: You're only 15 minutes in, 20 minutes in.

WILLIAM TUCKER: Is that it?

PRESENTER: Yeah. You got a long ways to go.

WILLIAM TUCKER: I got a long way [INAUDIBLE].

PRESENTER: Yeah. You're just getting started.

WILLIAM TUCKER: Now notice that here everything here is gray. Let me go open up one of those Dynamos here and-- So how many went to Kevin's class on the fab parts-- on Dynamo's fab reports.

PRESENTER: A few. OK.

WILLIAM TUCKER: Yeah. It's--

PRESENTER: Not many.

WILLIAM TUCKER: Not many?

PRESENTER: No.

AUDIENCE: [INAUDIBLE]

WILLIAM TUCKER: All right. So here's the Dynamo script. We're just writing to that FP_Service Type field. And let me store this and I got this one piece selected here. Soon as I run it, it should populate a service type and that actually should have done everything in the drawing at that time. That's all the fab parts in the drawing. All right. Should have also shared another one with you. That should be all of them. Right, Kevin?

PRESENTER: Think that's the one that has everything. Yeah.

WILLIAM TUCKER: Yeah. So just point out you don't need to do these one at a time.

PRESENTER: Yeah. So this is on the web for you to download and look at--

WILLIAM TUCKER: Right.

PRESENTER: --and run. I mean, you'll have to make some modifications to it yourself for your parameter names, what you need for you, but for the most part, this should be ready to go for you.

WILLIAM TUCKER: All right. As soon as I run that and that should do everything for us. We have all of our parameters updated. I don't know if you noticed there, but as soon as it did that that valve changed color and hangers there should have changed color. If I can find my 3D.

So got some-- all right. See-- using those in the filters as well. And we should have some schedules here. Duct works schedule here that we're-- get my magnifying glass. All right. Ductwork schedule here, we got the parameters in it so at least we're not dead in the water right now anyway. What am I missing here, Kevin?

PRESENTER: Pipe--

WILLIAM TUCKER: Anything?

PRESENTER: Pipework schedule, fittings. So now we can filter out with CID. We can do-- because the schedule is set to build a schedule for pipe work, then we use CID filter, not 2041. So we get all of our fittings and everything else in a list. OK? Couldn't do that before. Didn't exist. OK? So now we can do a fitting schedule, a pipe schedule. You know, I think that Lee's got a--

WILLIAM TUCKER: Yeah. I got--

PRESENTER: Yeah. So there's the filter, not 2041. So that was pretty big, when we can access those kinds of things, that really opened up a lot of things for us.

WILLIAM TUCKER: Yeah. All right?

PRESENTER: And then there's a bought out one too. I don't know if you've got anything in there that's bought out. [INAUDIBLE]

WILLIAM TUCKER: Yeah.

PRESENTER: Yeah. So now, here's our adjustable elbows for anything sheet metal wise that's bought out. And again, without running the Dynamo script, none of this existed. So--

WILLIAM TUCKER: All right? So-- Get rid of that. Can't see. All right. Any questions? I know I went pretty quick.

AUDIENCE: Does that dynamic hole field work? If we went back to that [INAUDIBLE] piece of duct, does it tell me if I have a hole in it?

WILLIAM TUCKER: No, it will not. We're actually accessing that via the API.

PRESENTER: Show them the button for--

WILLIAM TUCKER: Let me get back to the drawing here. But-- go to the-- just move that over a little bit and that'll work out. All right. But now, that piece of duct right there is going to have a dynamic hole in it.

AUDIENCE: Can I see it in the properties?

WILLIAM TUCKER: What's that?

AUDIENCE: Can you see it in the properties?

WILLIAM TUCKER: In the properties?

AUDIENCE: Yeah.

WILLIAM TUCKER: No. We haven't populated that. We can do it with the API. And actually, to be honest with you, We can probably do it.

PRESENTER: We could probably do it with Dynamo, but we haven't thought about that.

WILLIAM TUCKER: You can probably do it with the Dynamo, but that's going to fall back into our issue where we're having a problem with our connectors right now. I bet if they get that fixed, then yes, we would probably be able to use that same node.

AUDIENCE: [INAUDIBLE].

PRESENTER: So when you create a yes or no parameter in REVIT, it puts the tick box in there. It's not actually on. If you click in the bought out field, see it's there, but it's grayed out. That means it's actually off right now.

WILLIAM TUCKER: It's neither.

PRESENTER: It's neither.

WILLIAM TUCKER: It's neither yes or no. It's a yes/no field. And by default-- you can't see that.

AUDIENCE: If you put the duct piece next to it, it's still checked? It doesn't--

PRESENTER: Yes. Yes.

WILLIAM TUCKER: Yeah. I haven't done anything-- I haven't done anything with it. It's just there.

PRESENTER: So when you create that yes no parameter in REVIT it always puts that tick box in there like that. OK? Yes.

AUDIENCE: So that one we're working on too.

PRESENTER: Yeah. So if William clicks that piece of duct, that'll go to your add in.

WILLIAM TUCKER: Go to the snoop tool?

PRESENTER: Yeah. Does everybody know about the REVIT snoop tool? If you're kind of digging in here and looking around with things, it's very handy. OK. So the REVIT snoop tool-- so he just clicked on a piece. And he's browsing through, so now we can see again, kind of behind the scenes, behind the door, all of the information that's available to that fabrication part not exposed to the user at this point in time. OK?

So and-- so for that piece of duct, if you look right here, it's got three connectors, because it's got a tap connected to it. If William would do the snoop tool on the duct right next to it, it would only have two connectors. OK? So REVIT understands as soon as you put that tap on that piece of duct, it adds another connector, which essentially is the dynamic hole that's going to cam duct. OK? But you can't see that without the snoop tool. You don't even understand what's happening there. You just see you got a tap on a piece of duct. OK?

AUDIENCE: Where do you get the snoop tool?

PRESENTER: So it's downloaded off the web. We could probably-- yeah. It's pretty easily accessible. REVIT snoop tool, it's downloadable, pretty handy though. We use it for-- we use it to try to determine things that we need to when we talk to our developer, it's like, OK, if we can see it in the snoop tool, then that means he's probably got access to the data through the API as well. So we kind of point him in a direction, because really, he's just a code writer. He doesn't understand REVIT at all, but he's able to-- now, he's getting better with understanding REVIT. You know, now we can start talking to him about things and because he's done it enough, he understands, oh, yeah. I know what you're talking about.

WILLIAM TUCKER: So I mean, actually my thoughts right there with the Dynamo script if we can just-- if we get our connectors working, then we can just search for CID 866 connectors greater than 2.

PRESENTER: And tick the bought out-- or tick the box for dynamic hole to yes with Dynamo. OK? So the reason we're doing that, to take that a step further, we created that parameter in REVIT, dynamic hole yes or no, so the end user can turn that on or turn that off. OK? That field now comes across for cam duct. The cam guy goes to the audit trail and he filters for dynamic hole. He adds the custom data field, because we write that to a custom data field. He filters for that and if the dynamic holes are set to yes on his side, he processes for dynamic holes and we burn that duct.

If it's set to no, then he processes that group and takes the dynamic hole out. Because by default, everything has a dynamic hole coming out of REVIT.

WILLIAM TUCKER: We first set this up in the beginning of '18. I think it was the beginning of '18, is that we had control over that. And that's what we actually wanted, which is manual, so that we could do it once we get to cam. Now, in 2018 point two, all your holes come across in cam whether you want them or not. So now you need to decide--

PRESENTER: So we have to remove the ones that we don't want.

WILLIAM TUCKER: Yeah.

PRESENTER: Yeah. OK? So--

AUDIENCE: I can see you guys having a problem with that where, you know, depending on how testing works on a particular job, you know, when you would want those holes cut in or not. And he right now, doesn't have control.

PRESENTER: Yeah. Yeah. But this gives you that.

WILLIAM TUCKER: You got to take all your duct that's got a dynamic hole, move it out 200 foot, update dynamic holes and bring it all back.

PRESENTER: Move it back in cam.

AUDIENCE: In cam?

PRESENTER: In cam, yeah.

WILLIAM TUCKER: That's the way we have to do it.

PRESENTER: Because in cam, if cam sees the tap connected to the piece of duct, it has a hole. But if you select that duct and we've got the parameter there that's coming across, we select that, go to the 3D view in cam, move it, run dynamic hole UDH for update dynamic hole in cam, it takes the holes out, and then just you can actually do a control Z in cam, undo, it will move the duct back to its original location, but it won't undo the dynamic hole. OK? So another little trick that we found. Move the duct, run UDH, and then Control Z, and it puts the model right back where it was in cam, but did not add the hole back. Yeah?

AUDIENCE: So if I understand you correctly, that you're saying in REVIT 2018.2, it's ignoring that database setting that we have [INAUDIBLE].

PRESENTER: So if you have it on, yes, it's on. And if it's off, it's off. But it's not doing what it's supposed to do.

WILLIAM TUCKER: We had the choice of what, off, manual, or on.

PRESENTER: Yes. We had it set to manual.

WILLIAM TUCKER: We had it set to manual.

PRESENTER: It's giving us everything no matter what.

WILLIAM TUCKER: Manual's auto.

PRESENTER: Yeah. So just I mean, for you cam guys where you're working with the shops, it's just one more thing to be aware of that, you know, that's how it's working. OK? So--

WILLIAM TUCKER: I want to point out right here on the connectors though that I opened this duct up this time and the very first connector, this is ID one, which we're going to have a zero, a one, and a two. And if I were to go back and open up that a second time, it might, the connector of the type might be zero and it might be two. So that's kind of where we're having issues with this. Scripts, those things that don't seem align up all the time.

PRESENTER: The index is not staying the same. So therefore, when we're writing the connector to the part, especially like on a piece of pipe, bevel on one end thread on the other, the next time you run it, it's putting thread on this end and bevel on this end. It's just flipping them around. It's like, no, this is not good.

WILLIAM TUCKER: It just appears-- it just appears that way here, looking through the look up tool. And our programmer had a fit over that one.

PRESENTER: So the look up tool, like I say, it's handy just if you're starting to dig in and try to access some of the things behind the scenes if you want to fiddle with that. I mean, you can see all the data that's listed here in the lookup tool, but again, not all exposed to the end user. But as, you know, if you're doing the develop side and can access the API, you can gather all of this data and start writing anything you want out to a parameter. We're limited with Dynamo only because Dynamo's open source, so we're reliant on individual people to write a node to work in Dynamo that again, goes into the API and makes things happen.

So we're really not stuck, but we're reliant on somebody else who wants to invest some of their own time to write some nodes for Dynamo that now we can push this, or pull this data out from these parts. The other key is pushing it back in. So right now, none of the Dynamo nodes that are available today push any data back into the fabrication part. It's only pulling it out. OK? So we hope at some point that somebody has some spare time on Saturday or Sunday and wants to write code all day, because that's what it's going to take to develop some nodes to make that happen. All right?

So in-- let's see. That field, so if William goes up and ticks the box-- so go tick the box, William, for dynamic hole. So it's grayed out right now. Highlight that piece of duct and tick it. Now it's on. OK? So by default, it's in its static state. It's a grayed out tick box. It's kind of confusing, because it kind of looks like it's on, but it's not really on. Now it's on, because he ticked it. And if he ticked it again, it would go off. So once you touch it, now it's either on or off. It's not sitting in that limbo state, so to speak. OK? So that's the field that comes across for us.

WILLIAM TUCKER: And then all of these, I mean, we would just fill in by hand. And of course, we've got these that we're actually pulling from here and pumping back to custom data via the API.

PRESENTER: So through the API as well, we're able to recognize where the part sits in a room and write room name and room number into that part automatically, because it's reading it from the REVIT link. So now we can build schedules based on material delivery right to a room. OK? Again, we couldn't do that in Academy P. It didn't understand that. We had room name and room number.

AUDIENCE: Well, you can do it in Academy P.

PRESENTER: We have to go type it. We have to go type it in, right? I mean--

AUDIENCE: I just list it in script.

PRESENTER: OK. Well, so similar approach. Yeah. Customizing it to make it more automated. So that was one of the other things that we found with REVIT is-- and we see more and more things that we want to do. We just haven't had time to get to them to expose more data and to make processes more automated. So we have a button. Go to our tab, William.

WILLIAM TUCKER: Nothing's going to run right now. I have--

PRESENTER: Yeah. Nothing's going to run in here, but we've created our own ribbon now in REVIT that's specific for comfort. And so one of the ones up there is change status and send to fab. So when we send to fab, that's when it's processing it, change in the status behind the scenes for us automatically, and only selecting the duct that's approved for fabrication. OK? So yeah. So those are some things that we're working on. And we see that thing completely filling out and maybe even having another tab at some point here in the near future that we're doing to just make REVIT, just like everybody does in Academy P, lists, scripting, all the things that you do to make your work, your life easier. We're doing it in the REVIT environment now. OK? So--

WILLIAM TUCKER: Yeah. We got isolate service.

PRESENTER: Isolate service, show service, just like our SL1 and SL2 commands in Academy P. We built the same thing in REVIT. So pretty handy.

WILLIAM TUCKER: Then we just built the isolated. I don't think we did the [INAUDIBLE].

PRESENTER: Right. It's just isolate right now.

WILLIAM TUCKER: Yeah. And then we're doing some-- what else do we have for hanger tools here? Place hanger in hanger installation adjustment.

AUDIENCE: So [INAUDIBLE] now available in this vision? Or are you using fab [INAUDIBLE]?

PRESENTER: Yes. Absolutely.

AUDIENCE: So you [INAUDIBLE].

PRESENTER: What's that?

AUDIENCE: So now, when you [INAUDIBLE] exposure on API then pull a report in, you're still able to grab all that data off that report?

PRESENTER: Absolutely. Yeah. And that's what's alarming and also, you know, somewhat frustrating to us, is you gave me the fabrication report. You're proving to me that all of this data is here, but you don't give me access to any of it, except through the API on a limited basis. And so-- yeah. William, pull up a-- run a hanger report here or something. I mean, run one of our-- run one of our hanger reports right there.

AUDIENCE: How does it work? Is the report separate from the scheduling? Or are they--

PRESENTER: Absolutely. So he's going to run one right now. So it-- go to set up item reports. You didn't select anything. So go select something first. When-- [INAUDIBLE] to your model. Do you have any-- is there hangers in-- there's some hangers in there. So yeah. Run our hanger report.

WILLIAM TUCKER: If I can find them.

PRESENTER: So if you go to fabrication reports and item reports-- not print preview.

WILLIAM TUCKER: You don't want print preview?

PRESENTER: Well, you can do that too. That's fine. I was going to show them the actual Report Builder.

WILLIAM TUCKER: OK.

PRESENTER: Yeah. Exit back out of that and just-- so here's the Report Builder that's in Academy P or Cam or Est right inside of REVIT. You can add fields. I mean, it's just like you're doing it in the fabrication side of things, but now you have the ability to do it in REVIT.

WILLIAM TUCKER: And that's where the problem is, is that anybody can do it.

AUDIENCE: [INAUDIBLE].

PRESENTER: It will change on the CAD side, so it's the same exact report. OK? Also, keep it mind, he clicked on set up reports. In the fabrication world, we have a user log in that limits who has admin access to certain things. Reports are one of those that we normally take out and don't let everybody be mucking around in there. Not the case in REVIT. Every user you have has access to that report right now.

So what we're telling people is use the Print Preview, don't go to set up. You know, it's just a training thing right now until we get there. OK? So switch to a hanger report there, William. Do our clevis hanger, fab clevis hanger type, or something right there. There you go and then Print Preview. So this is our report that we run out of fabrication, Academy P. We can run the exact same report right here in REVIT. Gives us all the fabrication data we need to build that hanger.

So this was big. This was a big thing when this came in. So there are some things though, that if you have a filter built in your report that you were looking for a specific custom data field, for instance, that report's not going to work here in REVIT, because you're not writing that custom data field back to that fabrication part right now.

If we get Dynamo working, we can. We can write that back and now that report will work, because it's going to read that custom data field and filter by it. So you've got to be a little bit careful about which reports here work and which ones don't. You may be thinking you're getting all the data, but you might not be because of what the filter is in your specific report. So just be a little-- just be a little careful about that.

WILLIAM TUCKER: And for controlled [INAUDIBLE] reports that we know we're going to have that problem, we're trying to suggest that we have a CAD, a cam, a S folder for reports. We're thinking now, we're going to want a REVIT folder for reports so we can do reports and we can only run in REVIT in there. So--

PRESENTER: OK. Make sense? All right.

WILLIAM TUCKER: All right. Any other questions?

AUDIENCE: Shortest class of the day.

PRESENTER: What's that? Shortest class of the day-- of the-- we got 15 minutes. Otherwise, we can let everybody else out early. And-- oh. Questions?

AUDIENCE: Why did-- did you add level to one of your parameters, so you could utilize that throughout the [INAUDIBLE]?

PRESENTER: We have not yet. We've discussed it.

WILLIAM TUCKER: Levels?

PRESENTER: Level. Yeah. It's section in fabrication reports. So if we're grouping by sections--

WILLIAM TUCKER: It's actually already there though, right? I mean, [INAUDIBLE] levels in-- levels are not in schedules?

PRESENTER: No.

WILLIAM TUCKER: OK.

PRESENTER: No. We would have to write that to another parameter. And again, modify the report, because it can't look for section anymore. It's got to look for a custom data field. Therefore, the reason why we think we need a whole other folder for REVIT reports.

AUDIENCE: Yeah.

PRESENTER: Because I don't want to-- I don't want to modify it, because then I break it for fabrication.

AUDIENCE: Those reports are only looking in the CAD?

PRESENTER: Right now, we believe that is the CAD folder. Yes. Yes. I think we tested that and proved that, that it is looking at the CAD-- the MIS Academy P folder. Yeah.

AUDIENCE: It's real easy to find [INAUDIBLE].

PRESENTER: Oh, it's really easy to find out. Go modify-- oh, yeah. And that's what I'm saying. I think we did that, but-- yeah. It's been a-- we might have slept since then or something. I don't know.

WILLIAM TUCKER: I'm pretty sure we verified that they're going to the CAD folder. Yes. Wherever your [INAUDIBLE].

PRESENTER: Anything else? I mean, it doesn't have to be just about data or whatever. I mean, I know this class is about data. But anything else?

AUDIENCE: [INAUDIBLE].

PRESENTER: Well, OK. I guess we're done. You get out early.