The Inspections Work Breakdown Structure (WBS) is a deliverable hierarchical decomposition to accomplish project inspection objectives.  The WBS is the cornerstone of SYNCHRO Control’s effective inspection, controlling, monitoring and reporting process.

SYNCHRO provides the option to import your own inspection form requirements using the Administration > Inspections Configuration option.

SYNCHRO also provides a default template file to use to create your customized inspections forms along with a sample inspections spreadsheet to view.  

Download the sample and template files to a local directory. The sections below will look at each sheet included in the sample file and provide information on the data fields.

View and Populate the Inspections Spreadsheet

Open the sample File and review the data, spending a little time analyzing the worksheets within the Excel Spreadsheet, particularly the sequence from left to right. 

Important: Each Worksheet has an important part to play in the import process, take time to study and interpret every column header and data. 

Config

The Config worksheet determines how the import process is performed. Today, the only field that can be modified is the "Config Value" column for the "All Types" row.

What is Clean Import

Clean import is the value of the "Config Value" column for "All Types" row, where it can have the following values:

• True:  It will delete all Inspections configuration data of the project in the Inspections Database and create again. 
• False: It will match each data type by the codes to make Inserts, Updates and Deletes. 

Note: A Clean Import is not recommended if you have active inspections in the project.

Specs

Each row in the Specs tab represents a node in the Inspections hierarchy tree.

• Level 1 to 10: Unique code value for the spec. Must be unique, and only one level column can be filled for each row.
• Description: Spec name
• Inspection Group: Inspection group related to the spec. Each spec can be associated with multiple form groups, separated by semicolon (;).

Hierarchy tree based on sample

From the sample below:

The following Hierarchy tree is generated:

Inspection Groups

This tab is used for creating Inspections groups.

• Inspection Group: Unique group code
• Group Name: Name of the group
• Form Definitions: Form definition code that belongs to the group. Each group can be associated with multiple form groups, separated by semicolon (;).

What is an Inspection Group

The groups are used to define which forms the tree items can inspect. So the Inspection groups work as a filter to the tree items, allowing the tree items only inspect the Forms associated with the group.

Group Structure generated based on the sample

Using the sample below:

The following groups are generated:

Form Definitions

Each row in the Form Definitions tab represents a Form that will be generated.

• Code: Unique code value of the form definition. Must be unique.
• Name: Name of the form. Prefix: Form prefix, up to 25 characters.
• Workflow Type: It's used to associate a type to a form, when adding APPLY indicators, like this "APPLY-Project Forms", it will create a workflow associated to the form.
• Form Sections: Relation of forms sections codes separated by semicolon(;), that will be added in the form generation.
• Update: It defines if the Form will be generated in the Forms Service and have different behaviors depending of the Clean import value in the Config Tab and if the Form already exists. Possible values: yes or no. When empty, default value is no.

Form Definitions generated based on the sample

The following sample of the Forms Definition tab:

Will generated the following form definitions:

Notice that the only Forms that has workflows are the one related to Project Forms, because of the Apply flag.

Form Creation Behavior

How does the process check when the Form exists?

The process check the Inspections Forms by the name, if the it found an existing form with the same name, it means the Form exists.

Form Sections

Each row in the Form Sections tab represents a section control that will be added in the Form generation.

• Code: Unique code value of the form section. Must be unique.
• Name: Name of the form section.

Line Items

Each row in the Line Items tab represents a control that will be added in the Form generation. Each Line Item needs to be linked to a Form Section.

• Code: Unique code value for the line item. Must be unique.
• Form Sections: Form section code that the Line item will be placed.
• Priority: Order of the line in the section
• Type: Type of the control. Check supported controls to see the possibilities.
• Type Extensions: Possible properties in the control, only applies for some controls.
• Line Item Text: Related label for the control, when empty, the label is not included.
• Binding: Custom binding name, when empty it will be composed by Type + Form Section + Code, example "textbox PD PD-1"
• Hidden: Set the control as hidden. Possible values: yes or no. When empty, default value is no.
• Read Only: Set the control as read only. Possible values: yes or no. When empty, default value is no.
• Required: Set the control as required. Possible values: yes or no. When empty, default value is no.

 

Import the Inspections Spreadsheet

Once the spreadsheet is populated it can be imported into SYNCHRO Control. 

Drag and drop your sample file into the grey area or select Browse to navigate to the Excel sample data file.

Confirm the Sample Data.xlsx file is ready to be published and Publish button.  

Observe the sample data importing process is followed by the form generation process.

Observe the green ticks and Published day, date and time stamp.

You can check the success of each Worksheet by selecting View Details on the xlsx import.

You can also check the success of the Form Generation by selecting View Details.

You can view the Inspections Hierarchy and WBS created and imported by clicking on the the Work by Items tab.