Smart Forms - Intergraph Smart Completions - 5.3.6 - Help - Hexagon PPM

Smart Completions Help

Intergraph Smart Completions

Smart ® Forms (SF) is a web-based technology used in for developing digital forms used both in the cloud as well on mobile applications. The smart forms are only created as “Inspection Points” within a task model. A SF honors specific configuration filled out against the task module, such as recurrence, tools, material and resource allocations to name a few.

Since most completions systems are “forms” centric and SC is “task” centric, where all tasks are an instance of a task model. We first create a list of task models from a list of forms identified on a project. When importing the list of TMs, its important to define that it has “digital” for “execution type”. This will expose the “inspections steps” tab in the task model edit form.

Developing the forms is comprised of three (3) components:

  1. Header: section used to define the object (e.g. asset, loop, pack etc.), systemization, phase/stage, and task information. There is a standard header configured as shown above, but users with access to task models will also be able to configure their own task model headers. Clients typically develop their own “Header Types” by discipline so they can extend additional information into the header (e.g. HP, RPM, Voltage). See “Task Model Headers” on how to create headers.

  2. Body: section used to recreate the core content of a project form and acts as the “data capture” mechanism for the test form.

    Weightage: Each inspection step has the ability to apply a Weightage (wt%) so a project can report on “progress” vs. the standard “completion”. Task completion looks at the “completion” state of the tasks workflow and does not take into account inspection steps. Task Progress reviews the completion of each task step, then weighs it against the weighted value.

    To report on progress, the inspection steps DO NOT need to be weighted however if they are it will provide more accurate progress report. A few examples:

    • If not weighted: If there are 10 steps, with no weightage, and I complete 5 of the 10 steps then progress reporting will reach 50% progress for that task.

    • If weighted: if there are 10 steps, where the first 9 steps are weighted at 1%, and the 10th step is weighted at 91% then the majority of the task progress would be based on the 10th step.

  3. Footer: section used to capture the Submission, Completion and Closure of a task. There are several options available. The following options are available:

The TASK WORKFLOW IS NOT CONFIGURABLE due to complex inter-relationships with other workflows, statuses, reports and data exchange requirements, and therefore users would need to select from one of the sign-off options.

Import Form Creation: Creating inspection steps through and import can be complex for more complex forms, but for simple checklists they can dramatically speed up the build out of your forms. To import steps, go to the IMPORT module and select VIEW “vInspectionPoints”. It will take time to scrub out the text from the source document into the template import file however will save lots of time doing manually via the interface.