Video - InEight Design
Document Claiming

TRANSCRIPT

Welcome to InEight Design! In this video, you'll learn how to update claiming on your scope items to stay in sync with their corresponding documents. Having a way to keep the claiming of your scope items and documents in sync can simplify and speed up your process for tracking progress.

Setting Up Document Integration

In this video, you'll learn how to ensure Document integration is set up for claiming, map document statuses to claiming schemes, and then, if there are any deltas, update claiming on your scope items to be in line with the statuses of their associated documents.

Before using document claiming, Document integration must be set up on your platform, typically by an administrator at your company. First, under Suite administration, Application integrations, for Document, the InEight document URL and project must be set up to sync with your project. For additional info on how to set up Document integration, see the Document-Platform Application Integrations guide in the Knowledge Library.

Configuring Project Settings

Under project settings for Design.

Under Engineering > Documents, both Document integration and Document claiming must be enabled.

Mapping document statuses to claiming scheme steps

With Document integration set up, let's look at how document claiming is managed in Design.

In the Design > Engineering module on the Scope Items tab, we can see the scope items we've created, currently filtered down to our foundation drawings. Notice each of these items is using the foundation's claiming scheme for tracking their progress.

Let's go to the Claiming schemes page to take a closer look at this claiming scheme.

Let's select the claiming scheme and click Edit to view its steps.

Here we can see the steps we've defined for tracking the progress of our foundation items. And here, because we've enabled integration with InEight Document, we have a column to map document statuses to the corresponding steps.

This way, as documents associated with scope items that have this claiming scheme achieve a certain status, the system will check the corresponding scope item to see if it has been claimed up through the corresponding step. And if it hasn't, the system will give it a status of Pending review, recommending it to be claimed.

Associating Documents with Scope Items

But first, documents must be mapped to scope items so the system can know which scope item each document pertains to. From the Scope items page, go to Actions > Associate documents, and click on the Mapping tab.

Here we can see the list of my scope items and the list of documents coming from InEight Document for this project.

Because document claiming was enabled in project settings, a button is available to auto map our scope items to documents based on a direct match between scope item description and document number. Notice we've already auto mapped our documents to our scope items.

Understanding claiming status of scope items based on related documents

Click on the Claiming tab. Notice once again, we filtered to our foundation scope items and we have three columns available for tracking scope items based on the progress of their corresponding documents.

The Scope item claim status refers to the furthest claimed document status on each scope item.

For example, the Foundations 2 scope item has the first two steps of the Foundations claiming scheme completed, but the furthest corresponding document status completed is just Not Started.

The Document status column refers to the latest document status of the document associated to each scope item.

The Claiming state indicates the claiming status based on the comparison of the Scope item claim status and the Document status. For example, looking at our Foundations 1 scope item, it has a Scope item claim status of Not Started, but the corresponding document coming from InEight Document has the status of Issued for Review.

When the claiming status is further along in the document than on the scope item, the Claiming state is set to Pending review.

Let's take a look at the scope item for Foundations 3.

It's been claimed up through Issued for Review, but the corresponding document is Not Started.

When the scope item is progressed to a claiming status further than the document, the Claiming state will say Pending - Undo Review.

Notice the claiming states of several of our items are set to Idle, indicating the statuses of the scope items and their documents are the same.

Updating Document Status

Let's see what happens when we update the status of one of these documents in InEight Document.

We'll review the Foundations 4 document, where we find it is ready to be issued for review.

Back in Design, we need to click the Document sync icon to bring in updates from InEight Document.

Notice the Document status for Foundations 4 is now updated to Issued for Review and is Pending review.

Synchronizing Claiming with Document Status

Now that we've reviewed current statuses, we can update claiming to match our scope items' progress to the status of the related documents. First, let's select the items pending review.

We can select one or more items individually, or we can filter by claiming state to all our items pending review.

Then check the box to select all the filtered items. Select Claim item.

This lists all the scope items ready to be claimed. Click Next to view all the steps included to be claimed for the selected scope items. Click Save to finish claiming.

We'll remove our filter, and we now see the scope items that were formerly pending review. Now I've updated Scope item claim status and their Claiming state is Idle.

Reverting Claiming Status

Let's select Foundations 3, which has progressed farther than its corresponding document. We can select Undo claim to revert the scope item progress to match the status of its corresponding document.

Great! Our claiming is now up to date, and our percent complete updates accordingly. If integrated with InEight Control, the respective earned quantities based on the percent complete will update in Control as well.