What are planned tasks - Intergraph Smart Completions - 5.3.6 - Help - Hexagon PPM

Smart Completions Help

Intergraph Smart Completions

Smart Completions is Task-based software. The work is planned, created and executed according to Tasks. A "Task" includes the checksheet, the asset(s) to which it is assigned, and the scheduling and systemization. If you are using a paper-based solution, the Task is the checksheet that a specific worker will use to complete work on a specific asset/pack/loop.

The Planned Task manager houses all tasks that have been created in the project. You can create paper-based or digitally executed tasks. The latter will be executed from a tablet device, using either iOS or Windows applications (which are delivered separately). Every task is created from a Task Model.

In the Planned Tasks Manager you can search, check in/out, execute and upload tasks. These actions are completed using the lower control ribbon.

Each TASK will have a status that would be one of the following:

  1. "Past Due" status means that the task has not been started but and the current date is past the scheduled start date,

  2. "Completed" means the task is completed with no pending punchlists,

  3. "Checked Out" means the task has been checked out by a Smart Completions user.

  4. "Partial" means the task has been completed, but has a non-critical pending punchlist that needs completion,

  5. "Rejected" means that the task has been completed, but has a pending "Critical" punchlist that needs completion, and

  6. "Closed" means the task has been completed and reviewed by a supervisor.

You can not edit the Comments and Observations section with in the smart form if the status of the planned task is Closed. In another scenario, where a task is rejected yet accepted at all the sign off levels, the Comments and Observations section is non-editable.


tab placed on the secondary action panel, allows you to check out a planned task and make changes as requested. You can re-open a task limitlessly for any changes that have to be made to the inspection steps. You can identify the latest changed document with the help of their naming convention. For example: Originally, a planned task is named: T- 02158-0037. For the first rework it will be shown as R1- 02158-0037, for the second iteration, R2- 02158-0037 and so on.