Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

Tips

Form Design

Sample Form Settings

Sample forms used for asphalt lot reporting need to have a few settings applied to them. Application of the Asphalt Lots form setting will automatically add the core fields to the sample form design that are necessary for the asphalt lot reporting to work.

Form SettingNotes
Sample Material
  • Designates the form as being used for asphalt material
Asphalt Lots
  • Designates the form as bing used to ultimately generate an asphalt lot report - the parent sample to all tests performed on the lot
  • Automatically adds the required Lot Number (AsphaltLotNumber) field
  • Automatically adds the required Supplier (AsphaltSupplier) field
  • Automatically adds the required Plant (AsphaltPlant) field
  • Automatically adds the required Mix Design (AsphaltMixDesign) field
  • All fields added as a result of this setting are added (and required) at the root of the sample form 

Field Mappings - Sample Report Section

Fields reported in the Sample section of the Asphalt Lot report need to be mapped to the form fields.  This is accomplished by applying the Asphalt Lot Report setting to a field on the sample form and selecting (mapping) the form field to the report field applicable to the Sample section of this report.

Test Form Settings - Sieve Report Section

Test forms used for asphalt lot reporting need to be identified and need to have a few settings applied to them. These settings and field mappings are outlined below.

Form SettingNotes

Test Material

  • Designates the material the test form is for
  • Standard on all tests - not unique to lot analysis
Material Specification
  • Designates the the type of material specification used on this report - sieve material specification should be used
Asphalt Lot Test - Sieves
  • Designates that this form can be used as a source of data for the Sieve section of the lot analysis report

Field Mappings - Sieve Report Section

Field mappings are not required for the Sieve section of the Asphalt Lot report. Because the target fields are predicable and sourced from the material specification selected on the form form record, the system is able to source the appropriate data dynamically from the form design and material specifications assigned to that form.

Sourced DataNotes
Sieve Size Columns
  • Dynamic based on the sieve sizes associated with the material specification selected on the form record
  • Sieve sizes reported in metric screen size value (mm)
Percent Passing
  • Dynamic based on the material specification value for the selected material specification on the form record

Test Form Settings - Mix Analysis Report Section

Test forms used for asphalt lot reporting need to be identified and need to have a few settings applied to them. These settings and field mappings are outlined below.

Form SettingNotes
Test Material
  • Designates the material the test form is for
  • Standard on all tests - not unique to lot analysis
Material Specification
  • Designates the the type of material specification used on this report - sieve material specification should be used
Asphalt Lot Test - Mix Analysis
  • Designates that this form can be used as a source of data for the Mix Analysis section of the lot analysis report

Field Mappings - Mix Analysis Report Section

Fields reported in the Mix Analysis section of the Asphalt Lot report need to be mapped to the form fields.  This is accomplished by applying the Asphalt Lot Report setting to a field on the sample form and selecting (mapping) the form field to the report field applicable to the Mix Analysis section of this report.

Test Form Settings - Gyrations Report Section

Test forms used for asphalt lot reporting need to be identified and need to have a few settings applied to them. These settings and field mappings are outlined below.

Form SettingNotes
Test Material
  • Designates the material the test form is for
  • Standard on all tests - not unique to lot analysis
Material Specification
  • Designates the the type of material specification used on this report - sieve material specification should be used
Asphalt Lot Test - Gyrations
  • Designates that this form can be used as a source of data for the Gyrations section of the lot analysis report

Field Mappings - Gyrations Report Section

Field mappings are not required for the Gyrations section of the Asphalt Lot report. Because the target fields are predicable and sourced from the material specification selected on the form form record, the system is able to source the appropriate data dynamically from the form design and material specifications assigned to that form.

Sourced DataNotes
Gyration Count Columns
  • Dynamic based on the material specification values associated with the material specification selected on the form record
Voids At "X" Gyrations
  • Material specification value for each tested gyration count (voids at "x" gyrations)

Lot Aggregations - Sources of Data

Data appearing under the grids containing data for the multiple tests belonging to a lot is sourced from a variety of areas.

DataNotes
Average
  • Simple average of the data above

Formulation
  • Mix design formulation metadata

Measured Deviation
  • Delta between Average and Formulation

Allowable Deviation
  • Allowable deviation threshold defined at the project level (Project Specifications)

Critical Deviation
  • Critical deviation threshold defined at the project level (Project Specifications)

Minimum Requirement
  • Minimum specification value defined in Material Specifications

Maximum Requirement
  • Maximum specification value defined in Material Specifications


Report Design

The Asphalt Lot Sample Report is the report that aggregates the defined sample and test fields together on a single report for a given asphalt lot number within a given project. This report is a hard coded report that is not based on a custom report design within Report Designer.  Administrators can control the report settings of the report, but they can't control the look of the overall report design.

  • No labels