In this video, we'll walk through how to create an ad-hoc checklist in Completions HQ> There aren't a lot of reasons why you'll need to create an ad-hoc checklist, since your project admin is going to create a checklist mapping for every different element type in the system. That's going to create a checklist inventory. For example, they'll determine at the beginning of the project if every single cable that's installed on the project requires a checklist, or for every pump that's installed, if it requires five checklists. But there may be a situation -- such as compaction reports or activities where multiple checklists need to be executed for a single scope -- that might require you to ad-hoc create a checklist as the work is progressing.
There are two ways to do this. The first way is to create a new checklist that isn't tethered to anything in the Elements hierarchy. You'd just be creating a brand-new checklist. When I press the Create New Checklist button, I'll choose a template and then add in some basic information.
You'll likely need to work with your project admin to figure out what fields need to be filled in, or they might even add some of it after the fact. With the information added, I'll click OK, which creates the checklist. Now, I'm ready to execute it, so I can start answering some questions. The other way to build a checklist is to go into your Elements and find the element that relates to the checklist.
The block represents the actual work area itself. It's a civil item in this case, and by double clicking on it, I'm going into my checklist from here, and I'll add a checklist. When I build a new checklist through the element, it's going to link back to that particular element, which makes it easier to find for reporting purposes. With the basic information added, I can click the OK button... aand there's my checklist.
If I look at my Elements, it's linked back to that specific block item, so I can keep stacking as many checklists as I need to against that item. Then from a reporting perspective, because you have the context of the element, it is really easy to understand where that checklist actually applies to. When we're talking about infrastructure projects, the element hierarchy should be in regard to work lots or segments... some method in order to actually locate these ad-hoc'd checklists more easily. You'll notice that my checklist number are currently TBD.
That's because the checklist numbers are reserved for once I actually publish my changes. So, if I go through and publish, it's going to communicate with the server, and it'll apply the next number in line. If I go to my checklist and clear my inventory, we'll see Checklist-a, which are checklists created through auto- mapping. Checklist 01 is one that's been created through ad-hoc means.
So because this is missing the "A", it means this is our first ad-hoc checklist. Remember to publish changes so that any work that was added can be observed by the rest of the project teams. And that concludes our recap on how to create an ad-hoc checklist in Completions HQ. Thanks for watching.
Additional Information
9977 N 90th Street, Suite 250 Scottsdale, AZ 85258 | 1-800-637-7496
© 2024 InEight, Inc. All Rights Reserved | Privacy Statement | Terms of Service | Cookie Policy | Do not sell/share my information
