Creating a TOP and Assign TOP Content Requirements - Intergraph Smart Completions - 5.3.6 - Help - Hexagon PPM

Smart Completions Help

Intergraph Smart Completions

The Turnover Package (TOP) or Handover Packages (HOP) module is designed to compile data, documents and images. These are done in a manner that simplifies the recipient to go through all the information and store either into a file server, share point or document management system (DMS).

A TOP contains several TOCs and configured for all projects within the same instance. They typically include:

  1. Systemization

    • Systemization Hierarchy Report

  2. Engineering Lists

    • Equipment lists

    • Instrument Lists

    • Pipe and Valve Lists

    • Documents and Drawing List

  3. Completions Deliverables

    • Preservation Task Report without Completed Forms

    • Preservation Non-Compliance Report

    • Completions and Commissioning Task Report w/ Completed Forms

    • Punchlist Report

    • Notice of Energization Report without Completed NOEs

    • Assurance Certificate Report without Completed Certificates

Before a TOP can be created an administrator must first define the content, Table of Content (TOC) item.

To create or edit TOCs,

  1. Select Gear Icon at the bottom of any open module and enter in “Table of Content” text within the “Open Manager” dropdown,

  2. It filters for the module, select and load.

If within the TOP module, select Gear icon and it will be an available configuration module.

With every release of Smart ® Completions there is a default PPM project, which includes a template of Turnover Package Types (e.g. Mechanical Completion, Turnover Package), which will also be pre-configured with TOCs as listed above.

Within the TOC module you can filter all TOCs by the package they are assigned to. A TOC can be assigned to multiple TOPs. The instructions below will cover the following TOCs:

  1. Tag list

  2. Punchlist

  3. Completions Task

Create a Tag List TOC

TOC for tag lists is created, if you combine all tags (for all disciplines) into one TOC or break out into specific disciplines. In the example below we will create a mechanical equipment list as a TOC, and you can follow the same concept for any other tag list by different disciplines.

General: The primary configuration item is to select the view (e.g. vAssets_Mechanical) you want to extract information from as part of a TOP.


  • Description

  • Manager (view / module)

  • Report name (will be filtered down to that modules reports)

  • Show TOC (a TOC can be configured but hidden from selection)


  • Package Type (ability to define which package types it is assoc. with)

  • Responsible Company (used if you know a specific company is responsible)

  • Show Excel? (ability to define data to dump into XLS file)

  • Include Files? (ability to dump out asset images)

  • Include Document Files (includes docs uploaded manually against this TOC)

Not Applicable: Associated with completions data and documentation

  • Executed Forms

  • Planned Forms

Export Columns:

  1. Select and order, the fields to be exported.

  2. When developing the configured export, you can sequence the fields, top to bottom, which would be left to right in the XLS file once exported.

  3. In addition, you can change the export column name using the “Alias” column. For example, if the destination system does not have “Asset – Name/Tag” then add an Alias name called “Equipment No” so when the destination database consumes the XLS file it will map to their schema/table configuration.

Criteria: If you wish to restrict the list of data to specific records, use the Criteria tab to apply a “saved” filter. The search panel displayed is the exact same search panel as shown for the selected module/view. In this case, it will show the mechanical search panel as in the example above, we have selected the “vAssets_Mechanical” view. A user could develop TOCs for specific type of mechanical equipment, such as Rotating Motors, where they would apply a filter for any “asset type” that is rotating such as compressors, pumps etc.You can use the TOP module to configure load sheets for Maintenance Systems, where they do not consume data by system, but by specific equipment types.

Creating a Punchlist TOC

To create a TOC for punch list, we recommend using the template TOC from the PPM Template project. It includes a standard configuration for dumping out the Punchlist reports, Datasheets, and Images. You can do this by going to the Project Wizard and selecting the option to pull content from one project to another project, and TOP/TOC configuration is selected at the instance level.

Creating a TOC for punch, you would select vPunchlist view, select the report you wish to include as part of the TOP package compilation. Then make sure you select the Include Files as it will include all punch images, and all image files will reference the punch list ID with a suffix

The punch list datasheets will be compiled into one (1) PDF, along with reference images. Each image will reference the punch ID.

Creating Completions Task TOC

When creating a TOC for completions and commissioning tasks, it is important that you utilize the “Test Forms” section as it will enable the project to define the taxonomy of the exported completed files. The view that must be selected is “vTasks_TestsPlanned” where it will allow for exporting/dumping of all completed test forms across asset, loop, pack, system-based modules.

We recommend that the "task completion by systemization" is used as it will show tasks for a system/subsystem for all modules (e.g. asset, loop, pack etc.). To export all the completed forms an administrator must select YES to the "Include Executed Forms". Including Planned Forms is only needed if the project wants to include the PDFs of the non-started tasks. When exporting the files, there are several options to the naming convention, it is suggested that the circled option is used, so that all A, B, C check sheets are sequentially in order. Select Yes to "Include Files" if the project has uploaded reference documents for the planned tasks completed. It will include the reference files with the same taxonomy as the planned tasks.

The Completed test forms will be exported into its respective folder, and each file will have a name as configured in the TOC.

Assign TOCs to Package Type

Once all the TOCs are created, the Package Type module can be used to pre-define which TOCs are assigned to the different TOPs. This configuration will expedite the creation of TOPs (of a particular type). Once a user selects from the list of TOCs configured, they then can be sequenced and nested by selecting child. Where the Child selection would be made is when you want to create a set of TOCs in a parent grouping such as creating a content label called “Engineering Lists” then make the equipment, line, instrument lists as “Child” sections. In this case, to just have a parent grouping for Engineering Lists you do not need to select a TOC from the dropdown, just put in a Description, then add in TOCs below and make those as child’s as shown below