Video - InEight Completions (Legacy) - ELEMENTS: 4 Adding Linked Elements

TRANSCRIPT

In this Completion's HQ video, we'll cover adding linked elements within the Elements module. We'll start by finding an element that we need to link another element to. Linking elements is also sometimes known as creating a sibling element. That's because it describes an operation occurring to multiple elements with this new element type that isn't hierarchical.

In this concrete pour example, we have two different foundations. We have a concrete pad for a tank, and then one for a pump. Going into the Details for the first foundation, I select the Element button and then add an element. Not every project roll will have permission to use this button.

If the roll is not permitted, the Add Element button will be grayed out. Specifically, I select a Concrete Pour, which represents the actual poor event that's going to happen on this project. I'll apply this foundation. You could give it a Position in the hierarchy, though sometimes with these sibling elements, they might exist in different subsystems.

So in our case, we won't apply a hierarchy value to it. We'll add a Pour Description and schedule it for a specific date and time, as well as add a Quantity and Mix Design. Clicking. OK, creates the element.

What we've done is to create a concrete pour type element that's linked to this particular concrete pad foundation. Now, I can go through and link another foundation to it. By filtering down to my other foundation, which is the tank foundation I can select my tank foundation and link the selected element. For an element-to-element link, like this one, I'm going to say NO to setting the creator.

What I've done is create an element from another element. I have this element link to the foundation and that helps provide context for both quality process and for reporting purposes. For the individual concrete pads, we might have checklists associated to them for things like the rebar, mesh, formwork, or erect and strip checklists. But on the concrete pour, which is an entirely different element, we'd have a different checklist profile, with different attachments associated to it.

You'll put the order form as an attachment for the concrete that was ordered for the pour. You'll put the pre-pour checklist associated to the actual poor event to the concrete pour itself... and not to the individual foundation that it's covering. We use these sibling elements to describe what individual quality processes are associated to what assets. In another example, if we are doing piping and you had multiple isometrics in the system, you might create from one of these isometrics, a test package for doing a hydro test, and then select multiple isometrics that are contributing in that test.

As a result, that test package, the test package checklist and everything associated to it through linking, indicates it applies to these isometrics. Then. through reporting we can pull that information out to make it useful to understand for each isometric. What tests was it involved in?

What was the success of those tests? And have we tested all of the scope? Doing it this way gives you different ways to intersect the information as opposed to just adding to the test package in with a descriptive reference to the individual isometrics. Thanks for watching.