cdot procedure manual

CDOT Procedure Manual

Materials Management and LIMS

March 9, 2012

Revised June 20, 2013

i

Table of Contents

Table of Contents ................................................................................................................. i

SECTION 1 Introduction ..................................................................................................... 1

1.1 Introduction ..................................................................................................................... 2

1.2 CDOT Materials Management Documentation Requirements ......................................... 2

1.2.1 Definition .................................................................................................................................... 2

1.2.2 Purpose...................................................................................................................................... 2

1.2.3 Contract Activation by Region Finals Engineer ......................................................................... 2

1.2.4 Generation of the Report 250 .................................................................................................... 3

1.2.5 Preparation and Processing Requirements ............................................................................... 3

1.2.6 Project Personnel Responsibilities ............................................................................................ 4

1.2.7 Materials Documentation ........................................................................................................... 5

1.2.8 Distribution by Region Finals Engineer ..................................................................................... 5

1.3 SiteManager® Materials Management ............................................................................. 6

1.3.1 SiteManager® Introduction ......................................................................................................... 6

1.3.2 SiteManager® Materials Laboratory Information Management System (LIMS) ........................ 6

1.3.3 Satisfying SiteManager® Sampling and Testing Requirements ................................................ 6

1.3.4 Historical/Discussion Notes ....................................................................................................... 8

1.4 Working Within SiteManager Materials and LIMS ............................................................ 8

1.4.1 Colorado Procedures ................................................................................................................. 8

1.4.2 Material Codes and Tests .......................................................................................................... 9

1.4.3 Material Users .......................................................................................................................... 11

1.4.4 Accessing SiteManager Materials and LIMS ........................................................................... 11

SECTION 2 Materials Information .................................................................................... 13

2.1 Population of Material Codes and Tests ........................................................................ 14

2.1.1 Overview .................................................................................................................................. 14

2.2 Material Detail Window.................................................................................................. 14

2.2.1 Description Panel ..................................................................................................................... 14

2.2.2 Tests Panel .............................................................................................................................. 22

2.2.3 Gradations Panel ..................................................................................................................... 23

2.2.4 Historical/Discussion Notes ..................................................................................................... 27

2.3 Maintain Sample and Testing Requirements Window ................................................... 29

2.3.1 Materials Panel ........................................................................................................................ 29

2.3.2 Sample and Testing Panel....................................................................................................... 32


SECTION 3 Contract Materials ......................................................................................... 41

3.1 Contract Materials Window ........................................................................................... 42

3.1.1 Contract Materials Panel ......................................................................................................... 43


3.2 Contract Sample and Testing Requirements Window ................................................... 45

ii

3.2.1 Materials Panel ........................................................................................................................ 46

3.2.2 Sample and Testing Panel....................................................................................................... 50

3.2.3 Reports .................................................................................................................................... 57

3.3 Estimate Discrepancies Window ................................................................................... 57

3.3.1 Estimate Discrepancies Panel ................................................................................................. 58

3.4 Material Inspection Detail Window ................................................................................ 61

3.4.1 Material Inspection Detail Panel .............................................................................................. 62

3.5 Process List Window ..................................................................................................... 64

3.5.1 Process List Panel ................................................................................................................... 64

3.6 Key Dates Window ........................................................................................................ 65

3.6.1 Key Dates Panel ...................................................................................................................... 66

3.7 Checklist Scheduled Events Window ............................................................................ 67

3.7.1 Checklist Scheduled Events Panel .......................................................................................... 68

3.8 Checklist Event Dates Window ...................................................................................... 70

3.8.1 Checklist Event Dates Panel ................................................................................................... 71

SECTION 4 Mix Designs ................................................................................................... 73

4.1 SUPERPAVE Mix Design Window ................................................................................ 74


4.1.2 Properties Panel ...................................................................................................................... 78

4.1.3 Materials Panel ........................................................................................................................ 81


4.1.5 SUPERPAVE Custom Template ............................................................................................. 86

4.2 Portland Cement Concrete Mix Design Window ............................................................ 88


4.2.2 Properties Panel ...................................................................................................................... 92

4.2.3 Materials Panel ........................................................................................................................ 95


4.3 Aggregate Mix Design Window ................................................................................... 100

4.3.1 Description Panel ................................................................................................................... 100

4.3.2 Compressive Strength Panel ................................................................................................. 103

4.3.3 Materials Panel ...................................................................................................................... 105

4.3.4 Gradations Panel ................................................................................................................... 107

4.3.5 Reports .................................................................................................................................. 109

4.4 Aggregate Blend Data Window ................................................................................... 109

4.4.1 Aggregate Blend Data Panel ................................................................................................. 109

4.5 Contract Mix Design Adjustments Window .................................................................. 111

4.5.1 Contract Mix Design Adjustments Panel ............................................................................... 111

4.6 Contract Mixes Window............................................................................................... 112

4.6.1 Contract Mixes Panel ............................................................................................................. 112

4.7 Accessing SiteManager Generic Mix Design Reports ................................................. 114

4.7.1 Sample Using Mix Design Window ........................................................................................ 114

4.7.2 Mix Design for Contract Window ........................................................................................... 114

4.7.3 Aggregate Mix Design List Window ....................................................................................... 116

iii

4.7.4 View Saved Reports (PSR) Window ..................................................................................... 117

4.8 Pavement Structural Design Data Window .................................................................. 118


SECTION 5 Sampling, Testing, and LIMS ...................................................................... 147

5.1 Maintain Sample Information Window ......................................................................... 148

5.1.1 Basic Sample Data Panel ...................................................................................................... 148

5.1.2 Addtl Sample Data Panel....................................................................................................... 159

5.1.3 Contract Panel ....................................................................................................................... 164

5.1.4 Other Panel ............................................................................................................................ 167

5.1.5 Tests Panel ............................................................................................................................ 169

5.1.6 Assigning Tests to a Sample ................................................................................................. 171

5.1.7 Service Menu for Maintain Sample Information Window ....................................................... 173

5.1.8 Reports .................................................................................................................................. 175

5.1.9 Historical/Discussion Notes ................................................................................................... 178

5.2 Find Sample Window .................................................................................................. 179

5.2.1 Find Sample Panels ............................................................................................................... 180

5.3 Sample and Testing Requirements Window ................................................................ 181

5.3.1 Sample and Testing Requirements Panels ........................................................................... 181

5.4 Standard Sample Remarks Window ............................................................................ 181

5.4.1 Standard Sample Remarks Panel ......................................................................................... 182

5.5 LIMS View-Only Sample Information Window ............................................................. 183

5.5.1 View-Only Sample Information Panel (Upper Pane) ............................................................. 184

5.5.2 Sample Details Panel ............................................................................................................ 185

5.5.3 Contract Details Panel ........................................................................................................... 188

5.5.4 Other Details Panel ................................................................................................................ 189

5.5.5 Sample Receive Panel .......................................................................................................... 190

5.5.6 Tests Assigned Panel ............................................................................................................ 191

5.5.7 Test Status Panel .................................................................................................................. 192

5.6 LIMS Receive Sample at Destination Lab Window ...................................................... 193

5.6.1 Receive Sample at Destination Lab Panel ............................................................................ 194

5.7 LIMS Receive Sample in Lab Unit Window ................................................................. 195

5.7.1 Receive Sample in Lab Unit Panel ........................................................................................ 196

5.8 LIMS Enter Test Results Window ................................................................................ 199

5.8.1 Enter Test Results Panel ....................................................................................................... 200

5.8.2 Service Menu for Maintain Sample Information Window ....................................................... 203

5.8.3 Enter Add Testers Window (Sub-Panel) ................................................................................ 203

5.9 LIMS Review Tests Window ........................................................................................ 205

5.9.1 Review Tests Panel ............................................................................................................... 207

5.10 LIMS Review Samples Window ................................................................................. 210

5.10.1 Review Samples Panel ........................................................................................................ 211

5.11 LIMS Maintain Test Queue Window .......................................................................... 214

5.11.1 Maintain Test Queue Panel ................................................................................................. 215

5.11.2 Enter Add Test Window (Sub-Panel) ................................................................................... 218

iv

5.12 LIMS Alternative Test Workflow Window ................................................................... 220

5.12.1 Alternative Test Workflow Panel .......................................................................................... 221

5.13 LIMS Test Triggered Events Window ........................................................................ 223

5.13.1 Test Triggered Events Panel ............................................................................................... 224

5.14 LIMS Test Assignment Information Window .............................................................. 226

5.14.1 Test Assignment Information Panel ..................................................................................... 226

5.15 LIMS Assign Products Window ................................................................................. 229

5.15.1 Assign Products Panel ......................................................................................................... 229

5.16 LIMS Maintain Product Users Window ...................................................................... 232

5.16.1 Maintain Product Users Panel ............................................................................................. 233

SECTION 6 Approved Lists ............................................................................................ 235

6.1 Approved Materials Window ........................................................................................ 236

6.1.1 Approved Materials Panel...................................................................................................... 236

6.2 Maintain Producer/Supplier Window............................................................................ 244


6.2.2 Plants Panel ........................................................................................................................... 249

6.3 Producer/Supplier Materials Window........................................................................... 252

6.3.1 Producer/Supplier Materials Panel ........................................................................................ 253

6.4 Qualified Labs Window................................................................................................ 255

6.4.1 Qualified Labs Panel .............................................................................................................. 256

6.4.2 Tests Associated to Each Laboratory Unit ............................................................................ 259

6.5 LIMS Maintain Destination for Lab Units Window ........................................................ 280

6.5.1 Maintain Destination for Lab Units Panel .............................................................................. 281

6.6 Qualified Labs Report Window .................................................................................... 283

6.6.1 Qualified Labs Report Panels ................................................................................................ 284

6.7 Material User Window ................................................................................................. 285

6.7.1 Material User Panel ............................................................................................................... 286

6.8 Sampler Qualifications Window ................................................................................... 289

6.8.1 Sampler Qualifications Panel ................................................................................................ 290

6.9 Tester Qualifications Window ...................................................................................... 293

6.9.1 Tester Qualifications Panel .................................................................................................... 294

6.9.2 Tests Associated to Qualification Type ................................................................................. 299

6.10 LIMS Maintain Lab Users Window ............................................................................ 316

6.10.1 Maintain Lab Users Panel.................................................................................................... 317

6.11 Test and Fee Schedule Window ................................................................................ 319

6.11.1 Test and Fee Schedule Panel ............................................................................................. 319

6.12 Test and Fee Schedule Report Window .................................................................... 320

6.12.1 Test and Fee Schedule Report Panels ................................................................................ 320

6.13 Calibrated Equipment Window .................................................................................. 322

6.13.1 Calibrated Equipment Panel ................................................................................................ 322

6.14 Welder Window ......................................................................................................... 324

6.14.1 Welder Panel ....................................................................................................................... 324

v

SECTION 7 CDOT’s Application for Reporting (CAR) .................................................. 327

7.1 Introduction ................................................................................................................. 328

7.2 Accessing Reports ...................................................................................................... 328

7.3 Printing a Report From CAR ....................................................................................... 331

7.4 Types of Reports ......................................................................................................... 331

7.5 Additional Resources .................................................................................................. 332

SECTION 8 System Operational Parameters ................................................................. 335

8.1 System Operational Parameters ................................................................................. 336

SECTION 9 Security Groups .......................................................................................... 339

9.1 Security Groups .......................................................................................................... 340

9.1.1 Group Definitions ................................................................................................................... 340

9.1.2 Security Group Matrix ............................................................................................................ 342

9.2 Group Security Window............................................................................................... 345

9.2.1 Group Security Panel ............................................................................................................. 345

9.3 Maintain Group Security Window ................................................................................ 347

9.3.1 Maintain Group Security Panel .............................................................................................. 348

9.4 User Security Window ................................................................................................. 349

9.4.1 User Security Panel ............................................................................................................... 349

9.5 System Tables Maintenance Window .......................................................................... 351

9.5.1 Code Table Panel .................................................................................................................. 352

9.5.2 Error Message Panel ............................................................................................................. 353

9.6 Contract Archival Window ........................................................................................... 357

9.6.1 Contract Archival Panel ......................................................................................................... 357

9.7 Contract Restore Window ........................................................................................... 358

9.7.1 Contract Restore Panel ......................................................................................................... 358

9.8 Process Security Window ............................................................................................ 360

9.8.1 Process Security Panel .......................................................................................................... 360

9.9 Define Custom Process Window ................................................................................. 361

9.9.1 General Panel ........................................................................................................................ 361

9.9.2 Parameters Panel .................................................................................................................. 363

9.9.3 Templates Panel .................................................................................................................... 365

9.9.4 Programs Panel ..................................................................................................................... 365

9.9.5 Files Panel ............................................................................................................................. 366

SECTION 10 Test Templates .......................................................................................... 369

10.1 Material Test Template Procedure and Guidelines .................................................... 370

10.1.1 Material Test Template Procedure ...................................................................................... 370

10.1.2 Guidelines ............................................................................................................................ 372

10.1.3 Material Test Template Design Forms ................................................................................ 374

10.1.4 Material Test Template Revision Process ........................................................................... 376

10.2 Material Test Template Design – Quick Reference Guide ......................................... 377

SECTION 11 Creation of Reports ................................................................................... 381

vi

11.1 Report Procedures and Guidelines ........................................................................... 382

11.1.1 Reporting Requirements ...................................................................................................... 382

11.1.2 Report Formatting ................................................................................................................ 385

11.1.3 Historical/Discussion Notes ................................................................................................. 385

SECTION 12 Answers to Possible Questions ............................................................... 389

12.1 Introduction ............................................................................................................... 390

12.2 Crystal Ball used for Construction ............................................................................. 390

12.3 Test Numbers in SiteManager vs. in the FMM (03/08/13) .......................................... 391

12.4 SM Rate per Freq vs. FMM QA IA Schedule (03/11/13) ............................................ 392

Trns•port CDOT Materials Procedure Manual 1

SECTION 1 Introduction

2 Introduction

1.1 Introduction SiteManager

® is a comprehensive construction management software product that covers the complete

construction and materials management process from contract award through contract finalization in one enterprise-wide software package. This procedure document complements two other help manuals. One manual is the generic User Reference Manual and the other is the Colorado Department of Transportation (CDOT) Training Manual. This procedure manual addresses SiteManager 3.9a.

1.2 CDOT Materials Management Documentation Requirements This Section defines the documentation required by CDOT to ensure that adequate records are maintained during contract administration.

1.2.1 Definition

Documentation is a record, written or electronic, which includes measurements, calculations, and results of tests that occur during the administration of a highway construction contract.

1.2.2 Purpose Documentation is required by law and is an essential part of contract administration. It is also necessary to ensure contract compliance and that the Contractor is properly paid.

1.2.3 Contract Activation by Region Finals Engineer In order for the SiteManager

® Quality Assurance Sampling Checklist (SiteManager

® Report 250),

SiteManager® Certification Checklist, and SiteManager® IAT Sampling Checklist (SiteManager

® Report

379) to be created the project must first be activated in Site Manager® Construction (SMC) by the region

finals engineer. The region finals engineer will also grant contract authority to project staff to give them access to contract information.

Figure 1.1 Project Activation Flow Chart


These are instructions for the Finals Engineers to activate a project.

Once the Finals Engineer receives the Notice-To-Proceed (NTP), the Contract & Bond, and Project Specials, the project will be activated in SMC via the established activation procedures.

Since there are times that a Project Engineer has not been selected at the time of NTP the Region Finals Engineer will need to contact the RE to obtain the name of the designated PE or use their username as the Project Engineer.

Once the project is activated, the Region Finals Engineer will notify the Central Laboratory Materials Documentation Unit and the final Project Engineers through an email. When the Report 250 is available and complete, the Central Laboratory Materials Documentation Unit will notify the Region Finals Engineer and the final Project Engineers through an email.

1.2.4 Generation of the Report 250 After receiving the project activation notification from the Region Finals Engineer, the Central Laboratory Materials Documentation Unit has 10 business days to generate and complete the Report 250. Immediately after generation, an incomplete version of the Report 250 will be available in CAR. There is no warning that the report is incomplete; please wait until the Central Laboratory Materials Documentation Unit sends notification that the report is complete. Once the Report 250 is complete, the project staff listed on the activation email will receive an email notification that the Report 250 is available and complete. It is the responsibility of the Finals Engineer to notify all other project personnel that the completed Report 250 is available through CAR on the SAP Portal. Project personnel must also be made aware that the Report 250 will be updated throughout the life of the project. The Report 250 must be regenerated frequently to view the updates. PowerPoint presentations on how to generate and update a Report 250 were created by John Kacinski and are available through Headquarters Pavement Design.

1.2.5 Preparation and Processing Requirements

Document Preparation Project records must be accurate, complete, and easily understood. Documents should be prepared in a manner that will allow individuals not familiar with the project to easily and accurately determine what was performed, even if reviewed several years later. The Project Engineer may choose to complete the project documentation by utilizing SiteManager®, hard copies or a combination of both hard copies. Regardless of which method is utilized, all the required test results must support the pay documentation. All test result documentation that is not actually in SiteManager

® must be referenced in SiteManager

® so

the documentation can be easily located. Project Number and Project Code All documents will contain the project number and project code (i.e., subaccount). Original Source Document

4 Introduction

The original source document is the document or electronic file on which the original information was recorded and supports the final test results. Original information will include, as necessary, measurements, input values, supporting calculations, and results. Hard-Copy Documentation All hard-copy documentation must be signed and dated by the person who recorded the information. Electronic Documentation Electronic documentation in SiteManager

® will be processed as follows:

1. SiteManager

® Access Agreement. Each user must sign a SiteManager

® access agreement to

create an individual account. The access agreement provides a password for the individual to utilize when accessing SiteManager

®. The access agreement establishes that data entered into

SiteManager® under each individual user’s password is equivalent to signing the following

statement:

The item(s) and material(s) were inspected and found to conform reasonably with the Contract Plans and Specifications except as noted.

A copy of the access agreement can be obtained from the SiteManager

® website at

http://internal/sitemanager.

2. Username Entries. SiteManager® automatically records the name of the person entering data. If a

different person performed the measurements or calculations, enter this person’s name in the proper record.

3. Hard Copies. At the Project Engineer’s option, a paper copy may be maintained in addition to the electronic version in SiteManager

®. However, hard copies of supporting information that cannot

be easily entered into the electronic version of the test method (e.g., measurements, charts, sketches) must be properly referenced and maintained as a separate document.

1.2.6 Project Personnel Responsibilities

Resident Engineer The Resident Engineer is responsible for assuring that complete and accurate documentation is compiled. The documentation is subject to Federal and State audits and reviews. Project Engineer The Project Engineer will compile, or cause to be compiled, the required documentation. The Project Engineer is also responsible for the materials documentation on his project. Project Inspector The Project Inspector has the primary duty of ensuring that construction is performed in accordance with the Contract. The Project Inspector is the representative of the Project Engineer and will maintain complete and accurate records of the work performed, the materials used, the disposition of rejected materials, and the measurements of the items inspected. Project Materials Tester


The Project Materials Tester reports to the Project Engineer. The Project Materials Tester has the responsibility for sampling, testing, reporting, and documenting the quality of material for acceptance.

1.2.7 Materials Documentation

The requirements for materials documentation are presented in the CDOT Field Materials Manual. The Project Engineer must comply with the documentation requirements. Safety - Nuclear Gauges Chapter 800 of the CDOT Field Materials Manual, Documentation Chapter, addresses the proper use and storage of nuclear gauges that are used to perform various materials testing. A radiological monitoring device must be worn by all personnel that operate testing equipment with a nuclear source (i.e., moisture/density gauge, asphalt content gauge), in accordance with CDOT Procedural Directive 89.2 – Medical Monitoring for Hazardous Materials Workers. See Chapter 800 of the CDOT Field Materials Manual for additional guidance. Field and Laboratory Test Results If material test results are found to be outside specified limits, the Contractor should be immediately notified using Form 626 – Field Laboratory Test Results. This will enable the Contractor to take corrective action in a timely manner to address non-complying materials. Form 626 is normally prepared by the Project Materials Tester, signed and dated by the Project Engineer, and presented to the Contractor for acknowledging signature. The completed and signed Form 626 is distributed to the Contractor, Project Engineer and the Project Materials Tester. Calculation for Price Reduction When the materials furnished, the work performed, or the finished product does not conform to the Contract, the material or work will be evaluated for price reduction according to subsection 105.03 of the Standard Specifications. Use the latest version of the price reduction software to perform the calculations. Check the data input carefully. Include the printout in the final pay quantity documentation, and the Project Engineer will enter the price reduction on the pay estimate as a negative dollar amount. Record the out-of specification material on the appropriate materials summary report, and attach a copy of the printout from the price reduction software.

1.2.8 Distribution by Region Finals Engineer After the Region Finals Engineer has received, reviewed, and checked all the required and applicable documentation, one copy each of the forms will be distributed by the Region Finals Engineer as referenced in the Construction Manual, Section 121.3.3. Note: The Region Finals Engineer will distribute the materials documents: Form 250, Buy America Certification, and Form 473.

1.2.8.1 Form 1212 Final Acceptance Report for Federal-Aid Projects Refer to the Construction Manual, Appendix B and check Construction Bulletins for Form 1212 updates involving SAP workflow and distribution of the form.

6 Introduction

1.3 SiteManager® Materials Management

1.3.1 SiteManager® Introduction The Materials component of SiteManager

® stores materials information, including, specifications, testing

requirements, mix designs, and lists of approved suppliers, personnel, labs, and fees. It can be used to build and maintain a Contract Materials List, enter sample data and track test results, and run reports.

1.3.2 SiteManager® Materials Laboratory Information Management System (LIMS)

The Laboratory Information Management System (LIMS) component of SiteManager

® streamlines the

sampling and testing workflow from recording a sample to reviewing and authorizing samples. LIMS captures sample details, assigns tests, assigns and receives the sample at the destination lab, and sampler/tester enters test results, may review the test results, and supervisors authorize the sample results. SiteManager

® Materials and LIMS emulates CDOT Field Materials Manual (FMM). The FMM is the

required guidance and when the FMM is updated and revised SiteManager® Materials and LIMS follow.

The FMM has very few restrictions on how to do business. SiteManager® Materials and LIMS is restricted

to a computer environment.

1.3.2.1 Additional LIMS Component Explanation The Laboratory Information Management System integrates seamlessly with SiteManager

®. LIMS

streamlines the sampling and testing workflow from recording a sample to reviewing and authorizing samples. When a sample arrives, enter the information into the SiteManager

® Maintain Sample Information window

to capture the sample details and assign tests. After you assign tests, the sample record appears in the Receive Sample at Destination Lab queue. Once you receive the sample in the destination lab, the sample record is ready to receive in the appropriate lab unit. Once you receive the sample in the lab unit, the Enter Tests Results queue displays the tests based upon qualifications and assigned lab units. Completed tests from the Enter Test Results queue appear in the Review Tests queue. Review results, mark tests as complete, requeue tests, or order retests. After you complete the review of all assigned tests on a sample, review and authorize the sample in the Review Samples queue. If needed, send test results back to the lab. At any time in the process, monitor the test assignments and easily add or cancel tests in the Maintain Test Queue window. Access all available information about all samples with View-Only Sample Information window.

1.3.3 Satisfying SiteManager® Sampling and Testing Requirements

Satisfying a sampling and testing requirement is determined by comparing information entered in the Sample Information window to the contract requirements (as defined in the Contract Sampling and Testing Requirements window) and to the system requirements (as defined by the system operational parameters).


In all, SiteManager® evaluates the following seven values entered for a sample and test record to satisfy a

requirement:

1. Producer/Supplier 2. Test Method 3. Acceptance Method 4. Sample Type 5. Authorization Status (only if set as required in the System Operational Parameters) 6. Sample Status (only if set as required in the System Operational Parameters) 7. Represented Quantity

Once SiteManager

® determines that the values for these six fields in the Sample Information window

match the contract and system requirements, a requirement is “satisfied”. Only a satisfied requirement counts toward satisfying the overall sampling and testing requirements for a contract item. The total number of samples and tests required is based on the total installed material quantity for a contract item and the sample rate and sample frequency defined for each test method. Note: If any of the values for Producer/Supplier (PS), Test Method (TM), Acceptance Method (AM), or Sample Type (ST) are left blank in the Contract Sampling and Testing Requirements window for a material, then any value specified in the Sample Information window for that material will be accepted.

8 Introduction

1.3.4 Historical/Discussion Notes Two philosophies govern CDOT’s setup of SiteManager

® Materials:

The first, is that no customization will be done to SiteManager

®

Materials, except for one. At the beginning, only one customization would be allowed and that was to include the QC/QA (incentive/disincentive) calculation. Later it was called Quality Pavement Management (QPM) calculation. As it turned out no customization was done in SiteManager

® Materials. The QPM

calculation was developed as a report using SiteManager®

Materials data and CDOT Application for Reporting (CAR).

The second, is any material permanently incorporated into a CDOT construction project has to have some documentation in SiteManager

® Materials. The documentation may be a test, a visual

acceptance, a pre-inspected item, a Certificate of Compliance (COC), a Certified Test Report (CTR), or a pre-approved item (per APL). These have a mechanism to document each in SiteManager

®

Materials.

1.4 Working Within SiteManager Materials and LIMS

1.4.1 Colorado Procedures

When submitting a new Colorado Procedure or modifying one, a checklist was developed because SiteManager

® Materials and LIMS create another level of complexity. This checklist incorporated the old

way of doing business with the new.

Determine if it is an update to a CP or CPL or a new CP or CPL.

Format new procedures per CDOT Central Documentation Unit’s requirements, saving all documents as a Word document.

Update existing Job Safety Analysis (JSA) or develop new JSA for new procedures.

Update existing or develop new SiteManager®

LIMS test templates.


LIMS reports.


LIMS Material codes, assigned lab units, tester and lab required certifications, etc.

Update existing Quality Assurance and Independent Assurance schedules in the CDOT Field Materials Manual.

Determine any changes to CDOT Standard Provisions or CDOT Project Standard Special Provisions.

For HMA procedures, submit all information to the FPOG group for review and approval.

If a non-HMA item or if approved by FPOG, submit all information to the MAC for review and approval.

Contact OIT to discuss implementation and updating of SiteManager®

LIMS databases.

Send all documentation to CDOT Central Documentation Unit for inclusion in the upcoming CDOT Field Materials.


1.4.2 Material Codes and Tests

The following chapters show windows and panels. For each window and panel is a detailed explanation of each. The flow chart documents how the windows are related. If a window is not populated the next window is negated in the system. If a window is not populated the Material Codes and Tests will not be linked properly. The main heading in the box is the title of the window. The numbered steps shows, which panels apply. Below the line shows who has update rights.

Figure 1.2 Population of Material Codes with Tests into Database

10 Introduction

Figure 1.3 Population of Assigned Products and Users into LIMS Databases

Figure 1.4 Population of Tests into Databases


1.4.3 Material Users

The following chapters show windows and panels. For each window and panel is a detailed explanation of each. The flow chart documents how the windows are related. If a window is not populated, the next window is negated in the system. If a window is not populated, the Material Users may not be able to sample a material or test it. The main heading in the box is the title of the window. The numbered steps show, which panels apply. Below the line shows who has update rights.

Figure 1.5 Population of Material Users into Databases

1.4.4 Accessing SiteManager Materials and LIMS Before you obtain your username and password for SiteManager

Materials and LIMS, you must attend a

training course through the HQ Pavement Design Program. At the training class, you will receive a training manual, which will be a helpful reference as you begin to enter data in SiteManager Materials and LIMS. After the training course, you will fill out three forms, have them signed by your supervisor, and send them to the Service Desk. After your forms are processed, you will receive your username and password.

12 Introduction

The three forms are:

1. Form #984 Information Interchange Account Request Form – Employee -OR- Form #1275 Information Interchange Account Request Form – Consultant/Contractor

2. SiteManager Access Agreement 3. Form #1387 ERP (SAP) Authorization Request Form

On Form #1387 ERP (SAP) Authorization Request Form; in section SEM/BPS & BW Roles; select the Add checkbox for BF945-Trns*Port Users. Below, for the line beginning with “This role has multiple versions…”, write BF 945_0000.


SECTION 2 Materials Information

14 Materials Information

2.1 Population of Material Codes and Tests

2.1.1 Overview An interlayer of coding must be performed to link bid items to tests performed. The coding is called Material Codes. Materials Codes need to be populated in various windows. SiteManager

® Materials and

LIMS (Laboratory Information Material System) are two linked software components. The Materials Codes must be populated in these two software components. In SiteManager

® Materials there is a global

population and a project specific population. The flow chart below shows the windows that need to be populated with Material Codes and associated tests in both SiteManager® Materials and LIMS.

2.2 Material Detail Window

SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > MATERIAL INFORMATION > MATERIAL DETAIL

Window Procedure: Use the Material Detail window to enter and view base material information and testing options for the material inventory.

Security Procedure: CDOT update authority for this window should be available Technical Support, IT System Administration, and Central Lab Pavement Design Program. Inquire rights would apply to All Other Users which includes Consultants.

Functional Procedure: CDOT will utilize this window and panels to record base material information used on CDOT projects. All materials that need to be tested or documented for acceptance are required to be linked to a base material that is coded. Several fields may be required to be completed to save a material record. These fields include Material Code, Short Name, Full Name, Category, English Units, Metric Units, and Status. Several fields will be required by CDOT procedure to be completed and these are Recycled, Type Code, Specification Reference, and Status Date.

2.2.1 Description Panel

Use the Description panel to add and modify standard material inventory information for material validations throughout other portions of SiteManager, including approved lists, mix designs, and sampling and testing.


Figure 2.1 Material Detail Window - Description Panel


Table 2.1 Material Detail Window - Description Panel – Fields

Field Name Required Description Characters

Material Code Yes Free-form field. The unique identifier of the material. See naming convention below.

15

Short Name Yes Free-form field. An abbreviated description of the material. Mixed case.

20

Full Name Yes Free-form field. The full name or description of the material. Mixed case.

40

Category Yes Drop-down menu. The classification type of the material. Category is mixed case. See Code Table = MATLCAT.

40

Recycled Yes Check Box. Yes/No --

English Unit Yes Drop-down menu. The English unit of measure for the material. See Code Table = UNITS

14

Metric Unit Yes Drop-down menu. The Metric unit of measure for the material. See CDOT Table = UNITS

14

Type Code Yes Free-form field. The main heading of the Section series of the specification book. See Code Table = MATLTYPE

40

Size Code No (CDOT will not use) 10

Brand Name Required

No Check Box. Yes/No --

Control Number Required

No (CDOT will not use) --

Specification Reference

No Free-form field. Indicates the material specification reference number.

10

Status Indicator Yes Drop-down menu. Indicates if the material is active (A) or inactive (I). Defaults to active.

8

Status Date Yes Manual entry. Date when status of the material record was last changed. Defaults to current date for new records. Enter the date the material was added or the status was last updated in SiteManager.

DD/MM/YY

Remarks No Free-form field. General remarks. Location: Services Menu and" Remarks" button. CDOT has no specific use for this field, although this is available for use as needed. Mixed case.

255

2.2.1.1 Required Fields

MATERIAL CODE: The material code is a twelve-digit code with decimal points separating the numbers, defined as follows: SSS.BB.CC.DD SSS - The 1st three digits indicate the section of the specification book in which the material is listed. A decimal point is the 4

th digit.

BB - The 5th and 6

th digits represent the specification book subsection.


A decimal point is the 7th digit.

CC - The 8th

and 9th digits represent the specification book sub-subsection.

A decimal point is the 10th digit.

DD - The 11th and 12th digits represent the sequence number for that specification - ordered by

further detail. Last three digits are not used. Reserved for future use. Coding of the 1st three digits (SSS) were generally held. Liberties were taken to fit coding to subsections. Numeric Example: 403.02.01.00 - Hot Mix Asphalt 626.01.00.00 - Mobilization-No Material 703.04.01.01 - Aggregate, Hot Mix Asphalt, Grading SX 702.01.01.03 - Asphalt Cement, Binder PG 64-22 Alpha coding is used for non-contractor items. Alpha Example: PRELIM.SOIL - Soil and Rock, Soil Survey PRELIM.SUBGRADE - Subgrade, Pavement, Soil Survey PRELIM.BASE - Base, Pavement, Soil Survey PRELIM.SURFACE - Surface Course, Pavement, Soil Survey NO.MATERIAL - No Material NO.TEST.ASSIGN – No Testing Assigned NO.TEST.REQD – No Testing Required SHORT NAME: Abbreviated full name. Mixed case. FULL NAME: Describe the material and indicate the size/grade after the material name using mixed case lettering and abbreviations as necessary to fit the 40-character field width. Mixed case. CATEGORY: Maximum 4 characters code - 40 characters description. Categories refer to the title of sections of the specification book or may be a non-specification book description, e.g. Preliminary Roadway and Foundation Soil Survey. Enter in upper case for 4-character code. Enter mixed case for 40-character description code. Example: 711.01.02.01 material code is described as "Concrete, Curing, Type I (Resin Based)" that has a category code of "CONC" and a description of "Concrete" as titled in Section 711.


Code Table = MATLCAT – Category of Material

Category Category

CODE

Requires Certified Sampler

Sampler Certifications

Producer Supplier

Aggregate AGGR Yes LABCAT Yes

Asphalt ASPH Yes LABCAT Yes

Bituminous Material BTMN Yes LABCAT Yes

Building Material BLDM No No

Cement CEMT Yes ACI Yes

Chemical CHEM No No

Concrete CONC Yes ACI Yes

Precast Concrete PCON Yes ACI Yes

Environmental ENVR No No

Fence FNCE No No

General GEN No No

Geosynthetic GEOS No Yes

Irrigation IRRG No No

Joint, Waterproofing,

& Bearing Material JWBM No No

Lighting LGHT No No

Mineral Filler MINF Yes LABCAT Yes

Paint PNT No Yes

Pipe PIPE No Yes

Rebar & Strand REBR No Yes

Soil SOIL Yes WAQTC No

Structure STR No No

Traffic TRAF No Yes

RECYCLED: Indicates if the materials has been produced for recycling or is being used as a recycled material . Example: 202.07.01.00 is a removal of concrete pavement. This operation is producing a recycled material. The check box would be checked. 403.02.01.00 is hot mix asphalt. When a percentage of RAP is used in the asphalt mixture. The check box would not be checked. 405.02.02.00 is heating and remixing treatment. (A small percentage of non-recycled asphalt is used in this process.) The check box would be checked. 406.02.01.00 is cold bituminous pavement (recycle). This operation is milling an asphalt roadway then treating the millings with emulsion and lime then pave and compact it. The check box would be checked.


703.03.09.00 is recycled concrete pavement that has been crushed to produce and to be used as an aggregate. The check box would be checked. ENGLISH UNIT: The English unit of measure for the material (e.g., LOT, SF, LF or TON). This field is required to save the record. Enter the English unit of measure for the material. METRIC UNIT: The Metric unit of measure for the material (e.g., LOT, M2, M or T). This field is required to save the record. Enter the Metric unit of measure for the material.

Code Table = UNITS – Units of Measure

Code Description

ACRE Acre

CF Cubic Foot

CY Cubic Yard

DAY Day

DOL Dollar

EACH Each

F A Force Acct

GAL Gallon

HA Hectare (= 2.471 Acres)

HOUR Hour

KG Kilogram (= 2.2046 Pounds)

L Liter (= 0.264 Gallons)

L S Lump Sum (Spec Year 90,91)

L B Pound

LF Lin Foot

LM Lane Mile

LOT Lot

LS Lump Sum (Spec Year 1989)

Lkm Lane Kilometer

M Meter (= 3.281 Feet)

M2 Sq Meter (= 1.196 Sq Yd, 10.764 Sq Ft)

M3 Cu Meter (= 1.308 Cu Yd)

M3km Cubic Meter Kilometer

MFBM M Ft Bd Measure

MGAL M Gallon

MILE Mile

MKFT M Kip Foot

MNM Mega Newton Meters

MON Month

NCU No Common Units Possible

OZ Ounce

PCT Percent


Code Description

SF Sq Foot

SHML Shoulder Mile

SY Sq Yard

SYI Square Yd - Inch

T Metric Ton (= 1.102 Short Tons)

TM Ton Mile

TON Ton

Tkm Metric Ton Kilometer

WD Work Day

WK Week

YM Yard Mile

g Gram

km Kilometers (= 0.621 Miles)

mL Milliliter

psi Pounds Per Square Inch

TYPE CODE: The main heading of the Section series of the specification book. Example: Section 500 Structures with a maximum mixed case 40 character description of "Structures". Mixed case for 40-character description.

Code Table = MATLTYPE – Material Type

Code Description

BASE Bases

ETWK Earthwork

FSUR Final Soil Survey

MATD Material Details

MISC Miscellaneous Construction

NMAT No Material

PSUR Preliminary Soil Survey

PVMT Pavements

STRU Structures

BRAND NAME REQUIRED: If the indicator displays a checkmark, the brand name of an approved product must be entered in the Product Name field on the Sample Information window when creating a sample record for the material. Yes/No (Check Box).

SPECIFICATION REFERENCE: A referencing of where the material is to be found in the specification book, standard or project special provisions. This field is a duplication, SSS.BB - The 1st three digits of the material code indicates the section of the specification book in which the material is listed and the 2

nd two digits indicates the subsection.


STATUS INDICATOR: Indicates if the material is active (A) or inactive (I). Defaults to active. All initially loaded materials will have a status of active. Inactive indicates the material is no longer in use and will not be available for use in SiteManager. STATUS DATE: Date when status of the material record was last changed. Defaults to current date for new records. Enter the date the material was added or the status was last updated in SiteManager.

2.2.1.2 CDOT will not use Fields

CDOT will not use the following fields: Size Code and Control Number Required.

SIZE CODE: If the material has requirements and is reference in a table, the table number is shown. The tables may be located in the specification book, standard or project special provisions. Mixed case.

CONTROL NUMBER REQUIRED: Indicates if a control number must be supplied when sampling the material. Yes/No (Check Box).

2.2.1.3 Drop-down Services Menu

REMARKS CDOT has no specific use for this field, although this is available for use as needed. Mixed case. GENERIC FIELDS CDOT will not use. ATTACHMENTS Optional PROCESS STATUS This window is available almost system wide by selecting Process Status from the Services menu. The window consists of two tab pages: Regular and Scheduled. REGULAR TAB The Regular tab page lists Distributed Processing Services (DPS) submitted processes; that is, Report Template Facility (RTF) custom report processes, SiteManager PowerBuilder reports, and background or batch processes. Here, authorized users can see the current status of submitted processes, delete submitted or complete jobs, or drill down to view or print the output produced by completed or failed processes. SCHEDULED TAB The Scheduled tab page lists DPS submitted processes; that is, RTF custom report processes, SiteManager PowerBuilder reports, and background or batch processes. Here, authorized users can see the current status of submitted processes, delete submitted or complete jobs, or drill down to view or print the output produced by completed or failed processes. The processes listed on the Scheduled tab are those processes which have be set to run on a specific schedule by an authorized user. Standard SiteManager window and tab-level security applies to the scheduled tab page window. Only those processes to which the user has been assigned security access will be presented on the displayed list.


2.2.2 Tests Panel

Use the Test panel to add, modify, and delete specific tests that can be performed on a material. Associations made here provide a list of valid tests for a material during the sampling and testing processes. To delete a test with material specifications, SiteManager prompts the user to confirm the decision. Upon confirmation, the system deletes both specifications and the test method. To delete a test with sampling and testing requirements and/or contract sampling and testing requirements, delete the associated z template prior to deleting the test. To add materials specifications to a test method, select the test, then from the Services menu, select the Material Specifications choice.

Figure 2.2 Material Detail Window - Tests Panel


Table 2.2 Material Detail Window - Tests Panel


Material Code N/A Auto populated. Uniquely identifies a material.

--

Test Method N/A Search. Uniquely identifies a test method.

--

Test Nbr N/A Auto populated. Test Number. Identifies the test window on which the test result information is recorded.

--

Test Description N/A Auto populated. Descriptive name of the test.

--


ATTACHMENTS Optional PROCESS STATUS A Process Status window is displayed. See above explanation. MATERIAL SPECIFICATIONS A specification window is displayed. Users assign Minimum and Maximum values to a test for each Material Code by selecting the New button in the menu. All min/max values have a unique Effective Date assigned to them. Status may be changed to Active or Inactive. Any number may be used between (negative)99999999 (minus sign plus 8-9s) and (positive)99999999 (8-9s). The 8-9s signify a null value or no value. When using the 8-9s, the min/max numerical field box in the test procedure windows should disappear. This means the results are compared to a true numerical min/max and not a place holder of spaces signifying a null value. SiteManager-Materials does not recognize null values. Null values are numerical zeros. The label of the min/max does not disappear. CASE ONE: The hiding and un-hiding of min/max numerical field boxes of 8-9s is quirky when changing the Effective Date on the fly. Changing the Effective Date is sometimes necessary to have the results be compared to the proper specification when there is more than one possible selection. Work around 1 - One needs to save the template and reopen the template for the min/max numerical field boxes to properly appear or not. Work around 2 – Do not use 8-9s as a specification. One may use any number (suggest to use (9)9s) and the min/max numerical field boxes will always be visible on the test template. CASE TWO: When there are two zTemplates associated with one test template, both zTemplates must have the same Effective Date for both min/max numerical field boxes to be populated at the same time.

2.2.3 Gradations Panel

Use the Gradations panel to add, copy, or modify material gradations with details of gradations limits of passing percentages for a material through a sieve. Since material gradations can change over time, use effective dates. The gradations may be either numeric or alphanumeric. SiteManager uses this information to validate information by the mix design and sampling and testing functions.


Figure 2.3 Material Detail Window - Gradations Panel


Table 2.3 Material Detail Window - Gradations Panel – Fields


Material Code N/A Auto populated. Uniquely identifies a material. --

Effective Date Yes Date the gradation becomes effective. Defaults to current date.

mm/dd/yy

Status Yes Drop Down. Identifies the current status of this contract item record (for example, active or inactive). Status defaults to active.

Sieve Size YES Drop Down. AASHTO and ASTM standard sieve sizes (that is, 2” (50 mm), 1-1/2” (37.5 mm), and so on). Required when minimum or maximum values are entered. May use “English (Metric)” format to allow for ease of use in both systems. SEE Code Table = SIEVESZ

Minimum Range Yes Beginning value for the gradation limit. 10

Maximum Range Yes Ending value for the gradation limit. Must be greater than or equal to minimum range value.

10

Code Table = SIEVESZ – Sieve Sizes

Sieve Code

Sieve Description

E010 12" (300 mm)

E020 8" (200 mm)

E030 6" (150.0 mm)

E040 4" (100.0 mm)

E050 3" (75.0 mm)

E060 2-1/2" (63.0 mm)

E070 2" (50.0 mm)

E080 1-1/2" (37.5mm)

E090 1-1/4" (31.5 mm)

E100 1" (25.0 mm)

E110 3/4" (19.0 mm)

E120 5/8" (16 mm)

E130 1/2" (12.5 mm)

E140 3/8" (9.5 mm)

E150 5/16" (8.0 mm)

E160 1/4" (6.3 mm)

E170 # 4 (4.75 mm)

E180 # 5 (4.00 mm)

E190 # 6 (3.35 mm)

E200 # 8 (2.38mm)

E210 # 10 (2.00 mm)

E220 # 12 (1.70 mm)

E230 # 16 (1.18 mm)

E235 # 18 (1.00 mm)


Sieve Code

Sieve Description

E240 # 20 (0.850 mm)

E250 # 30 (0.600 mm)

E260 # 40 (0.425 mm)

E270 # 50 (0.300 mm)

E280 # 80 (0.180 mm)

E290 # 100 (0.150 mm)

E300 # 200 (0.075 mm)

E310 20μ (0.020 mm)

E320 5μ (0.005 mm)

E330 1μ (0.001 mm)

M010 300 mm (12")

M020 200 mm (8")

M030 150.0 mm (6" )

M040 100.0 mm (4")

M050 75.0 mm (3")

M060 63.0 mm (2-1/2")

M070 50.0 mm (2")

M080 37.5mm (1-1/2")

M090 31.5 mm (1-1/4")

M100 25.0 mm (1")

M110 19.0 mm (3/4")

M120 16 mm (5/8")

M130 12.5 mm (1/2")

M140 9.5 mm (3/8")

M150 8.0 mm (5/16")

M160 6.3 mm (1/4")

M170 4.75 mm (# 4)

M180 4.00 mm (# 5)

M190 3.35 mm (# 6)

M200 2.38mm (# 8)

M210 2.00 mm (# 10)

M220 1.70 mm (# 12)

M230 1.18 mm (# 16)

M235 1.00 mm (# 18)

M240 0.850 mm (# 20)

M250 0.600 mm (# 30)

M260 0.425 mm (# 40)

M270 0.300 mm (# 50)

M280 0.180 mm (# 80)

M290 0.150 mm (# 100)

M300 0.075 mm (# 200)

M310 0.020 mm (20μ)

M320 0.005 mm (5μ)

M330 0.001 mm (1μ)


2.2.3.1 Drop-down Services Menu PROCESS STATUS A Process Status window appears. See above explanation. COPY GRADATIONS Copies the gradation table and assigns an Effective Date (current date) with Status being Active. User revises Sieve Size, Minimum Range, and Maximum Range as appropriate.

2.2.4 Historical/Discussion Notes Material Code - CDOT material code is based on Montana's material code convention. The material code references the section of CDOT 2005 Standard Specifications for Road and Bridge Construction book. Coding of the 700 Section series was performed first. Coding of the 200 through 600 Section series followed. Generally mix design coding used 200 through 600 Section numbers. Components of mix designs fell into the 700 Section series. Not all components are found in the 700 Section series. Exceptions are when components are defined in the 200 through 600 Sections; the SSS digits reference those sections and not the 700 Section series. A material sampler/tester should not see the material code NO.TEST.ASSIGN. This coding is reserved for unknown tests, unknown quantities, or testing frequencies assigned to it. Size Code - CDOT will not use this field. No apparent relation to CDOT existing procedures. Brand Name Required – If three or more products are listed on the Approved Products List, the checkbox will be checked and the Sample will have to select a product from a list of approved products. If two or less products are on the Approved Products List than the Sampler will have, a choice to select any approved products or submit a new product. Control Number Required - CDOT will not use this field. Used by other state agencies and has no equivalent in CDOT existing practice.

Below are excerpts from emails that John Kacinski thought were valuable to the many discussions that were held regarding materials codes.

-----

The SiteManager Construction module Bid Item Codes are already in place, and we must live with them, whether we agree with them or not. (i.e. We would have to retrain the Cost Estimate squad and Design Engineers, as what not to use, and we do not control how they create new Bid Item codes.)

If there is a material documentation requirements for a Test; COC; or CTR then the Bid Item Code requires a Material Code to be associated to it. This will include any Bid Item Description including the wording (Furnish)

NO.TEST.ASIGN No Testing Assigned……..This is to be used as a Material Code only if: a) the Bid Item requires a Project Special Provision; b) the wording of the Bid Item Code includes the word (Special); c) the wording of the Bid Item description is not understandable OR not even vaguely related to the Blue (or Green) Book(s) material items (i.e. looks like the Designer, Landscape Architect (erosion control), or Cost Data squad added an item for one-time, special use case)


NO.TEST.REQD No Testing Required…… This is to be used as a Material Code ONLY IF: a) the wording of the bid Item code includes the word (Install and place, sometimes); b) there is no material involved to test (i.e. Clear & Grub; Most, but not all 630 Bid Item codes)

----- Cast-in-place vs. Precast: You can’t code for both without a lot of deletions by the 250 creator. We decided to have all Inlets set up as poured in-place; so if in the field you have precast you would have to supply a one line explanation of exceptions on the Form 473 Page2, this should be easily understandable to all involved in resolving the FINAL Item Discrepancy Report. (This was assumed to be easier than Pavement Design Program adding all of the individual cast in place items.) We decided to have all Manholes set up as Precast, since the barrel sections on round manholes are 99% of the time delivered that way. This should set up the tester for the heads up on COCs needed to be covered. If the base / floor (Boxbase, Slabbase) or walls are poured in place, then similarly Page 2 of the Form 473 would need to resolve the missing COC for a precast base or wall (riser section) by stating poured in place and account for Class B and Epoxy bars as needed (you probably do not even track this small quantities now). The M&S Standards and the blue book need to be used in this process, as I found out while doing Inlets and Manholes. ----- FYI The question is whether 412 will eventually be all compressive or flexural strength by specification. As we have discussed in the Material Info Subcommittee, we either would set up 412 as NO TEST ASSIGNED or choose between compressive or flexural tests when assigning tests and frequencies on the old Form 250. All 412 tests are currently set up for the flexural spec.

Insight used to determine what the most 2011 common future PCCP strength tests will be:

Industry was involved with the Task Force and Specification Committee meetings that developed the new criteria. Here are the notes to the designer for the specification issued on June 16, 2011:

Instructions for use on CDOT construction projects: Use on all projects with Portland cement concrete pavement The designer will place a note in the General Notes indicating whether the project will be accepted by flexural strength or compressive strength.

The Region Materials Engineer shall be consulted for assigning the acceptance criteria. For rural projects the following criteria will be used for assigning acceptance criteria:

Projects with greater than 5,000 sq. yds of PCCP will be accepted by flexural strength criteria.

Projects with 5,000 or less sq. yds of PCCP will be accepted by compressive strength criteria

If a rural project with greater than 5,000 sq. yds of PCCP consists of scattered repairs, or only intersection replacements, compressive strength criteria will be used for acceptance.

For metro area projects:

Projects with more than 50,000 sq.yds. will be flexural strength.

Project with less than 5,000 sq.yds. will be compressive strength


Projects with 5,000 to 50,000 sq.yds could be either compressive or flexural. Consult the RME to determine acceptance method

2.3 Maintain Sample and Testing Requirements Window SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > MATERIAL INFORMATION > SAMPLING & TESTING REQUIREMENTS

Windows Procedure: Use the Maintain Sample and Testing Requirements window to identify materials for a bid item and specify minimum sampling and testing requirements. Use to identify the minimum frequency, responsibilities, sample size, and/or unit for the sampling and testing of a material for a bid item globally. SiteManager uses this information as a guideline for the entry of new contracts.

Security Procedure: CDOT update authority for this window should be available to Technical Support, IT System Administration, and Central Lab Pavement Design Program. Inquire rights would apply to All Other Users which includes Consultants.

Functional Procedure: CDOT will utilize this window and panels to associate material codes and sample and testing requirements with the exception of items that may not have tests required and/or assigned to bid items.

2.3.1 Materials Panel Use the Materials panel to specify the conversion factor and a special instruction describing the conversion factor or any other instruction that one should be aware of for a selected material on a bid item.


Figure 2.4 Maintain Sample and Testing Requirements Window - Materials Panel


Table 2.4 Maintain Sample and Testing Requirements - Materials Panel – Fields


Item Yes Code for the bid item. Agency-defined. Supplied by the Item Master from Trns•port PES and Trns•port LAS.

13

Spec Year Yes Drop-down. Item List specification year for the bid item from the Item Master.

--

Item System Unit N/A Auto populated. Indicates whether the units of measure are English or Metric.

--

Item Unit N/A Auto populated. Indicates the unit of measure for the pay item.

--

Desc 1 N/A Auto populated. Description 1. Description of the selected pay item from the Item Master.

--

Desc. 2 N/A Auto populated. Description 2. Description of the selected pay item from the Item Master.

--

Material Code Yes Search. Uniquely identifies a material. --

Material Description (no label)

N/A Auto-populated. Describes the material.

Conversion Factor Yes Used by the required samples calculation to convert current bid item units to required test units. Used to calculate the quantity of material represented in the associated pay item.

--

Special Instruction Optional Pertains to the material on the contract. Passes to the Contract Sampling and Testing Requirements window. Intended for the user to type special instruction specific to the pay item to material relationship.

2.3.1.1 Drop-down Services Menu PROCESS STATUS This window is available almost system wide by selecting Process Status from the Services menu. The window consists of two tab pages: Regular and Scheduled.

Regular Tab

The Regular tab page lists Distributed Processing Services (DPS) submitted processes; that is, Report Template Facility (RTF) custom report processes, SiteManager PowerBuilder reports, and background or batch processes. Here, authorized users can see the current status of submitted processes, delete submitted or complete jobs, or drill down to view or print the output produced by completed or failed processes.

Scheduled Tab

The Scheduled tab page lists DPS submitted processes; that is, RTF custom report processes, SiteManager PowerBuilder reports, and background or batch processes. Here, authorized users can see the current status of submitted processes, delete submitted or complete jobs, or drill down to view or print the output produced by completed or failed


processes. The processes listed on the Scheduled tab are those processes which have be set to run on a specific schedule by an authorized user.

Standard SiteManager window and tab-level security applies to the scheduled tab page window. Only those processes to which the user has been assigned security access will be presented on the displayed list.

VIEW MATERIAL The Material Detail window appears. COPY RECORDS Copies a new record to assign a New Material Code to the existing bid item. COPY ITEM RECORDS Copies a new item bid record.

2.3.2 Sample and Testing Panel Use the Sample and Testing panel to modify materials sample and testing information for a given bid item. Note: If a test method does not appear in this window for a material on a given pay/bid item, it will not appear as a test option in the Contract and Sampling Requirements window.

Figure 2.5 Maintain Sample and Testing Requirements Window - Sample and Testing Panel


Table 2.5 Maintain Sample and Testing Requirements - Sample and Testing Panel – Fields


Sample Type Yes Drop Down. Identifies the type of the test being performed (for example, QA, IAT, COC, etc.). See Code Table = SMPLTYPE

--

Acceptance Method Yes Drop Down. Identifies how the material will be accepted on the contract (for example, Sample & Test, COC, CTR, etc. See Code Table = ACPTMETH

--

Test Method Yes Search. Method used for testing the material (for example, T11, T27, T84, and so on). May be optional based on the System Operational Parameters.

Sample Location Drop-down. (CDOT will not use)

Rate Yes Rate at which a sample must be collected.

5

Sample per: Frequency

Yes Used in conjunction with the Rate field. 10

Sample Units Yes Drop Down. Unit of measure for a sample (for example, mm, feet, yards, inches). See Code Table = UNITTYPE

Sample Size (CDOT will not use)

Sample Responsibility

Drop-down. (CDOT will not use)

Test Responsibility Drop-down. (CDOT will not use)

2.3.2.1 Required Fields SAMPLE TYPE: Identifies the type of the test being performed.

Code Table = SMPLTYPE – Sample Type

Code Description

COC Certificate of Compliance

CTR Certified Test Report

IAT Independence Assurance Testing

INFO Information Only Testing

PRE Preconstruction Testing

QA Quality Acceptance Testing


ACCEPTANCE METHOD: Identifies how the material will be accepted on the contract.

Code Table = ACPTMETH – Acceptance Method

Code Description

ST Sample and Test



APL z DO NOT USE - Product Eval Coord Only

Sample Type and Acceptance Method. The Sample Type and Acceptance Method must match as per the following table, in order for a sample to be applied to a contract. Explanations of the above tables are shown below. These tables are the same as in the Section “Maintain Sample Information Window”.

Table 2.6 Sample Method and Acceptance Method Relationships

Sample Type Acceptance

Method Comments

Project Pay

Quality Acceptance Testing

Sample and Test

Standard project samples for project verification testing and acceptance. (If an item is visually accepted, the Visual Test Template should be used.)

YES

Independence Assurance Testing

Sample and Test

Sample for IA testing on projects. The QA, 10K and/or IA samples will be linked by the Lab Control Number. IA's for Item 403 can be done at the same time as 10K samples; they will be linked by Lab Control Number, but will have a separate sample ID number.

NO

COC COC

Material acceptance based on COC submittal by the contractor or a manufacturer listed on the CDOT APL. A Product Name will be required for final material acceptance. If a manufacturer is on the CDOT APL, the contractor supplies the COC. If the manufacturer is not on the CDOT APL, the manufacturer supplies a COC to the project.

YES

CTR CTR

Material acceptance based on CTR submittal from supplier. A Product Name will be required to be recorded before material acceptance. Examples: Mill Certification, Lab Certification, etc.

YES

Information Only Testing

Sample and Test

Material testing at HQ, Region, or field labs that are for information only. Samples submitted for project and non-project Information Only Testing including, but not limited to: project HMA 10K samples not for contract pay or IA check testing, concrete information cylinders, Bridge Unit items (concrete, strand, rebar, etc.), HMA Mix Design items, project/contractor check testing, Round Robin testing conducted by HQ, Region and Field Laboratories and forensics and research by HQ or regions for specific or nonspecific projects. Samples can be linked to a QA test and IA test

NO



Method Comments

Project Pay

by Lab Control Number if needed. Sample and testing of materials to qualify a supplier’s product to be used on CDOT projects. APL and QML may use this Sample Type and Acceptance Method to submit samples for approval to be included on the APL.

Preconstruction Testing

Sample and Test

Samples submitted by the region or staff specialty units (Geotech, Concrete, etc.) for design of a specific or nonspecific project in the future. Samples could be tested in the field, region or HQ labs. Pavement investigation, soil surveys, etc. If a preconstruction project number changes over time, it will be recorded in a field in the OTHER tab "Preconstruction Project Number". Samples with tests being conducted in different labs would be linked by Lab Control Number.

NO

NA APL

“z DO NOT USE - Product Evaluation Coordinator Only”. To be used only by the Product Evaluation Coordinator to be able to export materials to the web based APL list.

NO


Table 2.7 Sample Method and Acceptance Method Result Combinations

Sample Type

Acceptance Method Results

QA Sample and Test OK

PRE Sample and Test OK

INFO Sample and Test OK

IAT Sample and Test OK

COC COC OK

CTR CTR OK

APL OK

QA COC Error, do not save sample

PRE COC Error, do not save sample

INFO COC Error, do not save sample

IAT COC Error, do not save sample

QA CTR Error, do not save sample

PRE CTR Error, do not save sample

INFO CTR Error, do not save sample

IAT CTR Error, do not save sample

QA APL Error, do not save sample, APL for use only for Product Evaluation

PRE APL Error, do not save sample, APL for use only for Product Evaluation

INFO APL Error, do not save sample, APL for use only for Product Evaluation

IAT APL Error, do not save sample, APL for use only for Product Evaluation

COC APL Error, do not save sample, APL for use only for Product Evaluation

CTR APL Error, do not save sample, APL for use only for Product Evaluation

TEST METHOD: Method used for testing the material (for example, T11, T27, T84, etc.) RATE: Rate at which a sample must be collected.

Note: A business decision was agreed to use rate/frequency (99,999 to 1) for all COC’s and CTR’s.

SAMPLE PER FREQUENCY: Used in conjunction with the rate field.

Note: A business decision was agreed to use rate/frequency (99,999 to 1) for all COC’s and CTR’s.

SAMPLE UNITS: Unit of measure for a sample (for example, mm, fee, yards, inches).

Code Table = UNITS – Units of Measure

Code Description

ACRE Acre

CF Cubic Foot

CY Cubic Yard

DAY Day


Code Description

DOL Dollar

EACH Each

F A Force Acct

GAL Gallon


HOUR Hour




L B Pound

LF Lin Foot

LM Lane Mile

LOT Lot


Lkm Lane Kilometer






MGAL M Gallon

MILE Mile

MKFT M Kip Foot


MON Month


OZ Ounce

PCT Percent

SF Sq Foot

SHML Shoulder Mile

SY Sq Yard



TM Ton Mile

TON Ton


WD Work Day

WK Week

YM Yard Mile

g Gram


Code Description


mL Milliliter

psi Pounds Per Square Inch


SAMPLE LOCATION: Location of Sample. SAMPLE SIZE: Minimum sample quantity to be collected. SAMPLE RESPONSIBILITY: Who or which group of individuals collect the sample. TEST RESPONSIBILITY: Who or which group of individuals tests the sample.

2.3.2.3 Drop-down Services Menu REMARKS CDOT has no specific use for this field, although this is available for use as needed. Mixed case. PROCESS STATUS This window is available almost system wide by selecting Process Status from the Services menu. The window consists of two tab pages: Regular and Scheduled. VIEW MATERIAL The Material Detail window appears. COPY RECORDS Copies a new record to assign a New Material Code to the existing bid item.

2.3.3 Historical/Discussion Notes Conversion Factor Comments for Incidental Items and Staff Bridge approved precast bid items. At a meeting there were a few decisions that should be noted for those that could not attend:

1) If a Bid Item Code has Incidental Items (i.e. not paid for within another Bid Item), and Documentation does not involve a Material Test (only a COC, CTR, MTR) then the conversion factor SHALL be 1.

2) Precast operations for pre-stressed and post tensioned structure items with Concrete (Class PS) are currently handled by Staff Bridge, and we receive a Form 193. This is similar to a CTR, therefore use a Conversion Factor of 1. (Precast Sound walls, according to Eric Prieve of Central Lab’s Concrete Program have had field personnel from some Regions perform testing; assume standard testing frequency and record the tests.)

----- Norma, (InfoTech consultant) Can a Conversion Factor be set up as a BLANK for future entry? There are a lot of Bid Items w/(Special) in their description awaiting Project Special Provisions to find out one piece of information from the Plans or Specials in order to determine a Conversion Factor. Currently I enter a ONE, rather than a ZERO, to indicate that a test or COC, CTR, MTR, or CTR will be required for documentation; a ZERO could be misused as no test or documentation required.. Here is an example of


how I can currently note a process in generic terms…You will have to scroll off of the screen to view Column M for Special Instructions…..Note the use of ONE: John, Unfortunately, the conversion factor field in the database won’t allow a blank. It allows only numbers. Thanks, Paul ----- Rate/Frequency: Options and Decisions. The largest data entry for Rate (smpl_frq_rte @ 5 characters Max) (OR Sample Frequency Rate) would be five/9’s (99999). The largest date entry for Frequency (smpl_frq @ 12 characters w/ 3 decimals .i.e. As Many as NINE/9’s) (The subcommittee CHOSE TO USE SEVEN /9’s) ((OR Sample Frequency) COULD be seven/9’s (9999999). IV: (Two or More COCs expected) / Contract: Use five/9’s to 1 (OR 99999 to 1) (One COC expected) / Contract: Use 1 / (seven/9’s) (OR 1 to 9999999) V: (One Test) / Contract: Use 1 / (seven/9’s) (OR 1 to 9999999) VI: (One Test / Source / Contract) Use: five/9’s to 1 (OR 99999 to 1) (IF MORE THAN ONE SOURCE is known before Form 250, then setup all sources individually in this same format.) VII: (Minimum One Test) / Each: Use five/9’s to 1 (OR 99999 to 1) VIII: (One Test) / Day Time Frequency: Use five/9’s to 1 (OR 99999 to 1) IX: (Minimum One Test) / Day Time frequency: Use five/9’s to 1 (OR 99999 to 1) ----- From: Norma Stephens [mailto:[email protected]] Sent: Tuesday, August 23, 2011 1:43 PM To: Bergles, Robert; Locander, Robert; DeLuccie, Veronica Subject: S&T Freq, COC & CTR smpl_frq –up to 12 numeric - Equals “Frequency” on the window above smpl_frg_rte – up to 5 numeric – Equals “Rate” on the window above. smpl_frg_rte smpl_frq 1 99999999 - Any material that could require only one test for the entire bid quantity 99999 1 - New Enhancement - This will apply to the COC and CTR process – the number or COC or CTR tests will not matter in this process. The system will ignore the number of COCs or CTRs and only look at the Bid Item –Placed Quantity and the Satisfied Represented Material Quantity (Contract Tab on Sample). If the Satisfied Represented Material Quantity is equal to or greater than the Placed Bid Item Quantity when the estimate runs, S&T requirements will be satisfied. Thanks, NJS

Above coding is from InfoTech (consultant). ----- Spreadsheets provided for estimating the number of required tests for pipes bid as complete in place. SiteManager/LIMS has to have incidental or “included free in the work” material codes attached to the Bid Item Codes. If any Regions bid 603, or 510 Items as Complete In Place (CIP), then the following APPROXIMATIONS can be used to calculate out Embankment and Structural Backfill (Class I) for Form 250 (QA assurance Sampling Checklist) testing purposes ( You may have to scroll down to find a specific shape, or a pipe with different Bedding Requirements.) My assumptions should be just on the high side for Class I testing purposes. It will be quite some time before these are used, so do not delete. Thanks.


PS: Pipe dimensional information was not available for some of SiteManager’s existing 624 Bid Items, so if “Inch Equivalent Drainage Pipe Elliptical”, or “Inch Equivalent Drainage Pipe Arch” comes up at bid time, then these will have to be added. I also threw in the Drilled Caisson calculator for Concrete BZ and Rebar estimation.

----- Decision To code for IA testing and discussion on QA binder samples that will not get tested because of 1/10,000 PASSED and nine samples remain without tests. Here are the highlights as they effect the Material Info group:

1. IA tests can be coded to material codes, for future report extraction. To do so Mat Info will change the t_requirements Data spreadsheet by copying rows of Bid Item codes associated to material codes requiring IA tests, BUT using the IAT acceptance method and Sample/Test associations, and potentially use IA frequencies as ZERO / Rate…….On 9/28/11 InfoTech will see if this ZERO /Rate will work, by testing in Atlanta. This is a change from the MIT suggestion to keep IA tests managed outside of SiteManager, at least initially; all in attendance seemed to agree with making the change to an electronic data entry/report format. (a brief review of MIT approved System Operational Parameters, did not reveal a conflict)

2. zTemplates were not created for the Bituminous Lab initial/main templates; the ranges

determining Pass / Fail are within the main templates. OIT has identified this an issue when future

range changes will require reworking the initial template w/ potential loss of historical template

data. Giselle and Steve Gonser will review the initial templates, and get w/Ed Trujillo for any

changes determined as needed, as well as creating any zTemplates.

3. The Binder tests have varying sampling versus testing frequencies within each test. Again OIT

and InfoTech identified this as a problem. The ZERO / Rate was again suggested so that

samples not actually having tests performed on them (.i.e. No failing tests at 10,000, therefore no

tests on prior 1,000 samples)….AGAIN: On 9/28/11 InfoTech will see if this ZERO /Rate will work,

by testing in Atlanta.

4. UPLOAD: The t_matl_test Data Spreadsheet will be completed ASAP, hopefully by 9/28/11+/-.

The t_requirement Data Spreadsheet will be revised for IA based on the Atlanta testing of the use

of the ZERO / Rate frequency for IA tests, and for the Binder sampling/testing conflicts. (SEE

ABOVE) These two data spreadsheets will allow limited the Testing Subcommittee to test at least

the Group A material test templates identified as not requiring zTemplates.

From: Norma Stephens [mailto:[email protected]]

Sent: Thursday, September 29, 2011 7:50 AM Tests for item #1 were performed successfully in Atlanta. No impact on the estimate process if IA samples are setup as discussed. The Sampling Checklist will list IA samples and track the number taken & completed. -----

mailto:[email protected]


SECTION 3 Contract Materials

42 Contract Materials

3.1 Contract Materials Window

SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > CONTRACT MATERIALS > CONTRACT MATERIALS

*CDOT IS NOT PRESENTLY USING THE OUTSTANDING ITEM LIST The Report 250 in CAR will replace the SiteManager Outstanding Item List report.

Windows Procedure: Use to associate sampling and testing requirements to a contract through the contract materials generation process. Through this background process, SiteManager generates contract sampling and testing requirements and associates the pay item to material relationships initially outlined on the Sampling and Testing Requirements window with the pay items associated to the specified contract.

Security Procedure: CDOT user authority for this window should be available to Technical Support, IT System Administration, and Central Lab Pavement Design Program.

Functional Procedure (Using the Outstanding Item List in SiteManager. Not used at this time.): The Outstanding Item List is generated from the Contract Materials window and lists all the items on the Contract that do not have Sampling and Testing (S&T) Requirements. The Documentation Unit will generate the Outstanding Item List after the Contract is active. The Documentation Unit will review the list and determine if generic S&T Requirements should be established. The Documentation Unit will generate Contact Materials (this is equivalent to the creation of the Form 250). After activating a contract, review the Outstanding Item List report for any item that should have material sampling and testing requirements defined. For any item identified during the review, determine the corrective action. Decide if the item should be added to the global list. Once resolved, generate contract materials. This is currently done via Services – Outstanding Item List. The Documentation Unit may decide to generate materials without resolving outstanding item issues. For example, if the item is not standard and specific to the contract or if generating materials is time sensitive. In those cases, the user should define the necessary sampling and testing requirements manually in the Contract Sample and Testing window.

Functional Procedure (Using the CAR Report 250): From the Contract Materials window, the Documentation Unit will generate the contract sampling and testing requirements and associate the pay item to material relationships. The Documentation Unit will review the paper copy of the plans and project special provisions, as well as the CAR reports Quality Assurance Sampling Checklist (Form 250) and the Project Materials Item Report. The Documentation Unit will identify bid Line Item Numbers with the following material codes:

NO.MATERIAL – Black font – No testable materials within the bid item NO.TEST.REQD – Green font – No material testing needed or inspector test NO.TEST.ASSIGN – Red font – Project special provision or vague description resulting in

unknown material codes The Documentation Unit will review the plans and project special provisions and for all items marked as NO.TEST.ASSIGN (red font), either assign sampling and testing requirements or mark the item as


NO.TEST.REQD (green font). This eliminates the NO.TEST.ASSIGN (red font) from the Project Materials Item Report in CAR. In CAR, the Quality Assurance Sampling Checklist (Form 250) will be generated and all bid Line Item Numbers will have material associations and sampling and testing requirements.

3.1.1 Contract Materials Panel

Figure 3.1 Contract Materials Window

Table 3.1 Contract Materials Window – Fields


Contract ID NA Auto-populated. Uniquely identifies the contract for which the pay item to material association will be generated.

--

Fed St/Prov Prj Nbr

NA Auto-populated. Federal State/Province Project Number. Identifies the contract. --

Status NA Auto-populated. Current status of the contract (for example, Active). --

Primary County

NA Auto-populated. Contract’s primary county. One county must be indicated as the primary county. --

Location NA Auto-populated. Description of the contract’s work location. --


3.1.1.1 Required Fields CONTRACT ID: Auto Populated – uniquely identifies the contract for which the pay item to material associated will be generated. FED ST/PROV PRJ NBR: Auto Populated – Federal State/Province Project Number. Identifies the contract. STATUS: -Auto Populated. Current status of the contract (for example, active, pending). PRIMARY COUNTY: Auto Populated – Contract’s primary county. One county must be indicated as the primary county. LOCATION: Auto Populated. Description of the contract’s work location.

3.1.1.2 Drop-down Services Menu PROCESS STATUS This window is available almost system wide by selecting Process Status from the Services menu. The window consists of two tab pages: Regular and Scheduled. GENERATE Updates the Contract for outstanding items. OUTSTANDING ITEM LIST Sends the generated outstanding items to a printer for the Contract that was highlighted.

3.1.2 Historical/Discussion Notes

This does not have item quantities.

Some agencies have established a “dummy” material to put on every item that does not have materials so that the person who generates the report will only see items that SHOULD have materials.

Pro and Con of No Materials o If the dummy material is used, then the Outstanding Item List should only show items that

need materials. However, then these items will also show on the Sampling Checklist with no requirements and will have to be deleted from the Contract Sampling and Testing window.

o DECISION: This is not needed. Generation:

Generate once per contract.

When you generate materials, SiteManager takes the generic list of material requirements and puts them in the Contract S&T window so that they can be modified specifically for the Contract.

When a Contract is activated, CO #1 is automatically generated. Training Comments: Contract Materials cannot be generated until a project in activated by the finals engineer. (This process needs to be included here). Generation is via Services.


In addition to generating Contract Materials, the Sampling Checklist must be run. This process is located in the Process status icon under Materials Management. The process must be generated anytime changes are made to Contract and Sampling and Testing requirements. The CDOT Form 250 will need to be generated with CDOT specific sampling and testing requirements. See customized Form 250. (At this writing it was being developed). In addition, rather than using the “Outstanding Item List” from above, CDOT has developed a report that will show items that do not have “tests assigned” or “no tests required” that may take the place of the outstanding item list. The report is under Sample Tests LIMS, STL Reports, Documentation. Material Testing for Default Bid Items and Project Material Item Report.

3.2 Contract Sample and Testing Requirements Window SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > CONTRACT MATERIALS > CONTRACT SAMPLING AND TESTING

Windows Procedure: Throughout the life of the contract, use the Contract Sample and Testing window to add, delete and modify sampling and testing requirements for an active contract with generated materials. After materials are generated or after a change order is approved, make all contract specific modifications to the sampling and testing requirements. Modify based on proposal specifications, project plans or the addition or modification to a contract item via a change order.

Follow this procedure to notify Central Lab Pavement Design Program , Documentation Manager on Change Orders that have been approved. Project Engineer is to notify Documentation Manager by email. Documentation Manager will add Material Codes and Tests to appropriate Line Items.

Figure 3.2 Contract Order Flow Chart


Security Procedure: System Wide – There is not Contract Authority. Contract authority is not applied in SiteManager on the Sample & Testing window or in the Sample Information window. All projects will be displayed in the Sample and Testing window. For the LIMS portion (where test results would be entered), this is filtered by Contract. The testers can be given specific contract authority so that they can only see their contracts in LIMS. If you accidently generate Contract Materials for the wrong contract, you can manually create the requirements. Currently the “Documentation Unit” creates the Form 250. Only the Technical Support, IT System Administration, and Central Lab Pavement Design Program and will have update access to this window.

Functional Procedure: Materials Folder Tab On the materials folder tab, the main field that may need to be modified is the Conversion Factor. The other fields will be auto-populated after materials are generated. The Conversion Factor will convert the pay units to material units and calculate the percentage of the material in the pay item. If the Conversion factor is changed to 0 (zero) then no tests will be required. The Approved Source Required checkbox is informational only. The Material Unit field will not be used. The Special Instructions field is used to document how the conversion factor was determined and any special instructions regarding what should be considered if this field was to be changed.

3.2.1 Materials Panel

Use the Materials panel to specify the conversion factor and approved source required indicator for a selected material on a bid item. If a material will not be used during the life of the construction project, delete the material. If the material is not currently scheduled to be used on an item, but may potentially be used later in the project, set the Conversion Factor to zero; doing so prevents the system from requiring sampling and testing for the material. Note: Setting the Conversion Factor to zero has advantages and disadvantages. While the system will no longer require sampling and testing, the material may appear in Sampling Checklist Reports.


Figure 3.3 Contract Sample and Testing Requirements Window - Materials Panel


Table 3.2 Contract Sample and Testing Requirements - Materials Panel - Fields


Contract Yes Choose from Contracts in the pick list. Uniquely identifies the associated contract.

--

Project Yes Choose from Projects in the pick list. Uniquely identifies the associated project.

--

Bid Item Code

Yes Choose from pick list. Uniquely identifies the associated contract pay item (from the Item Master).

--

Item Unit NA Auto-populated. Unit of measure associated to the pay item (for example, inches, feet, tons). --

Desc. 1 NA Auto-populated. Description 1. Describes the contract pay item associated to the displayed material.

--

Desc. 2 NA Auto-populated. Description 2. Describes the contract pay item associated to the displayed material.

--

Supp Desc1 NA Auto-populated (If used). Supplemental Description 1. Describes the contract pay item associated to the displayed material.

--

Supp Desc2 NA Auto-populated (If used). Supplemental Description 2. Describes the contract pay item associated to the displayed material.

--

Material Code

NA Auto-populated. Uniquely identifies the material. --

Material Description

NA Auto-populated. Describes the material. --

Conversion Factor

No User-entered. Conversion factor to calculate the quantity of material represented in the associated contract pay item. Must be changed if the Material Unit is changed.

12

Approved Source Required

No Information Only. Indicates whether or not an approved source must be the producer and/or supplier of the material for the specified contract.

--

Material Quantity

Yes Auto-populated (calculated). Total material quantity expected to be used over the life of the contract. Equals (Bid Qty of Pay Item) + (Change Order Qty) x Conversion Factor.

--

Material Unit Yes Auto-populated, MIT voted to not allow this to be changed. Unit of measure associated with the contract material (for example, square yards). Typically, the Material Unit should not change. In cases where this field is changed, the Conversion Factor must also be changed to reflect the new units of measure relationship between the item and the component unit.

--

Special Instruction

No User-entered. Text to describe the relationship of the pay item to the material. If text appears in this window, it was provided from the global sampling and testing requirements.

254



CONTRACT ID: Choose from Contracts pick list – uniquely identifies the associated contract. PROJECT: Choose from Project/Line Item pick list – uniquely identifies the project. MATERIAL: Choose from Material pick list. Uniquely identifies the associated contract pay item (from the Item Master). PRIMARY COUNTY: Auto Populated – Contract’s primary county. One county must be indicated as the primary county. ITEM UNIT: Auto-populated. Unit of measure associated to the pay item (for example, inches, feet, tons). DESC. 1: Auto populated. Description 1. Describes the contract pay item associated to the displayed material. DESC. 2: -Auto populated. Description 2. Describes the contract pay item associated to the displayed material. SUPP DESC1: Auto populated. Supplemental Description 1. Describes the contract pay item associated to the displayed material. SUPP DESC2: Auto populated (if used). Supplemental Description 2. Describes the contract pay item associated to the displayed material. MATERIAL CODE: Auto populated. Uniquely identifies the material chosen. MATERIAL DESCRIPTION: Auto populated. Describes the material. CONVERSION FACTOR: Conversion factor to calculate the quantity of material represented in the associated contract pay item. MATERIAL QUANTITY: Auto populated. Total material quantity expected to be used over the life of the contract. Equals (Bid Qty of Pay Item) + (Change Order qty) x conversion factor. MATERIAL UNIT: Auto populated. MIT voted to not allow this to be changed. Unit of measure associated with the contract material (for example, square yards). Cannot be changed. SPECIAL INSTRUCTION: Text to describe the relationship of the pay item to the material. If text appears tin this window, it was provided from the global sampling and testing requirements.


VIEW MATERIAL The Material Detail window appears.

COPY RECORDS Copies a new record to assign a New Material Code to the existing bid item. COPY ITEM RECORDS


Copies a new item bid record.

3.2.2 Sample and Testing Panel Use the Sample and Testing panel to specify details of the sampling and testing requirements for a given contract pay item and material association. This window is usually updated immediately following the generation of contract materials. This window can be modified throughout the life of the Contract, for example, when a change order is approved. The Producer/Supplier Code field will not be used. The Acceptance Method field is required, but its status is pending LIMS committee discussions. The Test Method field will be required. Sample Location, Sample Size, Sample Responsibility, and test Responsibility fields will not be used. For the code tables that will not be used by CDOT, other committees have been referring these to the System Admin team so that a common value can be put in for each of these code tables that means “CDOT is not using.” This could be NA, NONE, etc. See Contract Materials Summary in historical notes to review how Sampling and Testing requirements will be used at CDOT.

Figure 3.4 Contract Sample and Testing Requirements Window - Sample and Testing Panel


Table 3.3 Contract Sample and Testing Requirements Window - Sample and Testing Panel - Fields


List of Producer Supplier Code, Sample Type, Acceptance Method and Test Method Combinations

-- NA Auto-populated. Fields repeated with inquiry-only format to aid when selecting row.

--

Producer Supplier Code

NA (CDOT will not use) Uniquely identifies the producer/supplier of the associated material. --

Sample Type NA Auto-populated. Identifies the type of the test to be performed on the material for the associated contract pay item.

--

Acceptance Method

NA Auto-populated. Identifies how to accept the material on the contract.

--

Test Method NA Auto-populated. Unique identifier of test template that will be used to capture the test data.

--

Sample Location

NA (CDOT will not use) Area from which to collect the sample.

--

Sample Frequency and Rate

NA Auto-populated. Rate at which a sample must be collected. --

Sample Units NA (CDOT will not use) Size of the sample. --

Sample Responsibility

NA (CDOT will not use) Office or department responsible for taking the sample.

--

Test Responsibility

NA (CDOT will not use) Person or office responsible for processing the test.

--

3.2.2.1 Required Fields ACCEPTANCE METHOD: Auto populated. Identifies how to accept the material on the contract. TEST METHOD: Auto populated. Unique identifier of test template that will be used to capture the test data. SAMPLE FREQUENCY AND RATE: Auto populated. Rate at which a sample must be collected.


PRODUCER SUPPLIER CODE: Uniquely identifies the producer supplier of the associated material. SAMPLE LOCATION: Area from which to collect the sample. SAMPLE UNITS: Unit of Measure. SAMPLE SIZE: Size of the sample. SAMPLE RESPONSIBILITY: Office or department responsible for taking the sample.


TEST RESPONSIBILITY: Person or office responsible for processing the test.

3.2.2.3 Drop-down Services Menu REMARKS CDOT has no specific use for this field, although this is available for use as needed. Mixed case. PROCESS STATUS This window is available almost system wide by selecting Process Status from the Services menu. The window consists of two tab pages: Regular and Scheduled. VIEW MATERIAL The Material Detail window appears. COPY RECORDS Copies a new record to assign a New Material Code to the existing bid item.

3.2.2.4 Historical/Discussion Notes For Materials Tab Materials Folder Tab Field Discussion

Conversion Factor o SiteManager does not allow you to lock this field. It is controlled by window security. The

Documentation unit and the Independent assurance group will have update access to this window.

o A zero (0) conversion factor will require nothing. o This field will come from Maintain S&T Requirements window. o Example – Cast in Place/Precast. You may want one option as 0 so that requirements

are not required by SiteManager but are available in case the contractor changes how the item is placed.

Approved Source Required o System Operational Parameters issue in that you can hide the field so that it does not

show up on the window. o This is informational only. o Recommendation from Committee: Not needed.

Material Unit o This is another area that is determined by System Operation parameters. o You can allow a user to change the Material Unit. o If you change the material unit, then you would most likely need to change the

Conversion factor as well. o Recommendation from Committee: Make this field read only.

Special Instructions o Other agencies usually use this area to document how the conversion factor was

determined and any special instructions regarding what should be considered if this field was to be changed.

o If this is not done, then the conversion factor will have to be reviewed each time the contract is activated. For example, when the conversion factor was determined, did it consider a 4” or a 6” base? This would make a difference regarding how much material was in the item pay unit.

o Contract Materials Recommendation to Material Information – use this field to document the conversion factor and instructions.

3.2.2.5 Historical/Discussion Notes for Sample & Testing Tab


Contract Sampling and Testing Folder Tab

Each Region has a set of materials folks and they set up the Independent Assurances (IA’s)

This window will have Independent Assurance and Project Acceptance.

Each Region is required to do form 279, which is the Independent Assurance Schedule. o The Sampling Checklist will take care of the IA form. o Currently- The 250 is considered a legal binding document and only Tony has access to

change it. If there is a problem, then the Region tells The Documentation Unit (Tony). Page 2 of the 473 contains explanations of exceptions to the sampling and

testing requirements for the project when completed. This is not currently done by the Documentation Unit, but it is sent to him.

Under the present system, the Form 250 is not updated when a CO is approved, unless specifically requested from the field. Field inspectors should be manually entering changes on the Form 250 over the course of the project. At the time of Final, the Form 250 is checked against the Final Estimate to ensure that all items on the Final are included in the Form 250 and that proper sampling and testing has taken place.

With the new system, the Form 250 will be automatically updated by SiteManager when a CO is completed. The SiteManager version of the Form 250 is called the Sampling Checklist, but this may be modified. This issue is still to be decided. The Sampling Checklist is initially updated when Contract Materials are generated at the beginning of the project. Then, it is automatically updated with the generic Sampling and Testing requirements by part of the CO approval process. If there are new items added via change order, the Documentation Unit should review these to be sure that the automatic update to the 250 is appropriate to the Contract.

With new system, as long as the CO is added as line items that already have sampling and testing associated, LIMS will automatically update the Form 250 requirements. However, many CO's are lump sums that include many items. In this situation, the PE will now have to notify the Documentation Unit of an approved CO and associated items so that the Form 250 can be updated. If there are new items added via change order, Tony should probably review these to be sure that the automatic update to the Form 250 is appropriate to the Contract.

How LS items are to be addressed will be decided by the Materials Information Subcommittee at a later date.

Schedule of Testing that should be tracked: o Independent Assurance – Regional Level

This is standard frequency. There are 2 programs for IA. Acceptance at Project and System Based. If System Based, this is based on time and not quantity. May be critical to set up own frequency – Region Materials Engineer. Statement for deleting In remote areas, the IA tech can’t really follow a schedule as they have a large

quantity in short about of time. They would say 4 times. This should be done by the Regions.

o Quality Control Notebook – Quality Control submits test results at the end of the project. This would not be in LIMS

o Quality Assurance


The Documentation Unit will let Regional Materials Engineer know when materials have been generated.

Decision for IA – put the schedule for quantity based in the generic sampling and testing requirements.

Contractor Options: o Scenarios that may have contractor options at CDOT:

Manholes Inlets Barrier

o Ways to deal with Contractor options in SiteManager: Enter both options in the generic S&T and then when materials are generated

delete the one that is not used. Enter NOTHING. It will show up on the Outstanding Item list and it can be

manually entered. Enter just the most common. If the other option is used, then add the other option

manually and delete the original option. o Contractor could change his mind in the middle of the contract. If you change the

conversion factor to zero, then requirements won’t be requested by SiteManager. o DECISION: Set SM up to have both in there and modify as needed.

Sampling Checklist Report

This is an RTF report that can be moderately modified if desired.

It will show all the requirements that were listed on the Contract S&T Requirements window.

This is also a dynamic report in that it will show how many samples have been taken and how many are required by the end of the contract.

CDOT is currently not using any RTF reports. You may want to create this report in crystal to show just the information you would need.

Security

System Wide – There is not Contract Authority.

What if you accidently generate Materials for the wrong contract? Then, you can manually create the requirements.

ISSUE: o Currently the “Documentation Unit” is the person who does the 250, the Region does the

IA schedule, and the field may update testing requirements when a CO is done. o If you have update access to the windows, you can change EVERYTHING in the window. o How do you want to distribute this security? (This will be discussed in the next meeting).

Sample and Testing Folder Tab Field Discussion

P/S Code o Optional to make required by System Parameters o Make this field optional o You are only allowed to assign one P/S at a time for a material. If the P/S changes over

time, you cannot show the change with the history in this window. o The actual P/S can be identified on the Sample record.

Sample Type o Optional to make required by System Parameters o Make Required o The LIMS committee has come up with suggestions for this field.

Acceptance Method o Optional to make required by System Parameters o Recommendation: Required o The LIMS committee has come up with suggestions for this field.

Test Method o Optional to make required by System Parameters


o Recommendation: Required

Rate/Frequency o This is where you indicate the frequency of this test for this sample type.

The following fields are optional on the window, but they will be automatically populated if they are entered in the generic S&T Requirements window:

o Sample Location (Code Table) Information Only Procedural Requirement This is a code table that requires the committee to determine all possible sample

locations. o Sample Units (Code Table)

Information Only o Sample Responsibility (Code Table)

Information Only o Test Responsibility (Code Table)

Information Only o Sample Size

Information Only

These fields are assigned to this committee even though they initially are populated by the Material Information committee because this committee will use them from a Contract perspective. We should recommend to the MI committee how these fields would be useful to the Contract personnel.

Tony – from the 250 Standpoint o We should have these fields populated to say this is where we will take the samples. o Example – Sample Location – Plant, Project, Other o This would provide guidance in the terms of where the sample should be taken.

Other perspective – the actual location should be listed in the sample. However, everything will change throughout the project. Not sure if this has much to do with the contract.

For the code tables that will not be used by CDOT, other committees have been referring these to the System Admin team so that a common value can be put in for each of these code tables that means “CDOT is not using.” This could be NA, NONE, etc.

============================================================================

1/12/2012 by Paul Neumann and Janie Valdez Contract Materials Summary After testing Sampling and Testing Requirements extensively below is a brief explanation of how samples are counted in SiteManager Sampling Checklist.

Samples are counted at the line item level. Thus, if a bid item is on several different categories

each of those line items need to have a Sample with associated tests to count for that line item.

The Samples can be copied for each line item; however, test results would need to be entered for

each of those samples as well.

This would probably require more testing on these types of scenarios than is done today.

This currently does not match the CDOT business process, the CDOT business process is that the total quantity of a bid item is used to calculate how many tests must be performed for that bid item which may include multiple line items. Therefore, CDOT must decide how Contract Materials will be used in SiteManager Materials. Below are the options:

Use SiteManager the way it is designed.

o Samples would need to be created for each line item including test results.


o Tester would need to be trained to insure that each line item is accounted for when

testing materials.

o As indicated above, this may result in more testing requirements.

o Estimate discrepancies could be turned on and show up for deficient tests per line

item.

o Contract line item adjustments would work and could be utilized to adjust payment to

the contractor for deficient testing per line item.

o Estimate discrepancies could be “overridden” which would not result in a contract

line item adjustment.

o Create a CDOT specific 250 and 379 with all line items, test methods, etc. (See

Bob’s example).

Fit SiteManager to CDOT business process.

o Contract Sampling and Testing requirements would need to be modified for each

project that has a bid item with multiple line items. This could be done in two ways:

The testing requirements for line items that have a small quantity (defined by

Materials Manual), could be updated to show 0 in the rate field. This would

eliminate the testing requirements for that line item. However, in addition, a

test method for visual could/should be added to the line item to match

business process requirements.

If the rate is changed to 0, then the business process to use 0 for rate on IA

testing would need to be changed to 1 to allow accurate reporting on 250,

379.

o OR

The test methods for the line items with a small quantity (defined by Materials

Manual) could be deleted from Contract Sampling requirements. In addition,

a test method for visual could/should be added to the line item to match

business process requirements.

Deleting test methods could be both audit questionable and allows for

potential deletion of wrong tests be deleted which would require IT

assistance to re-generate Contract and Sampling requirements.

For both scenarios above, estimate discrepancies would be turned off because they would

require too much maintenance trying to determine what the discrepancy was for (i.e.

materials that don’t need testing or IA tests or true insufficient samples). If discrepancies are

turned off, then contract line item adjustments would need to be turned off as well. However,

once they are turned off as part of the implementation process going back and changing the

decision will be challenging.

There still may be multiple line items with quantities greater than the “defined” small quantity;

thus, the tester would still need to create a sample for each of those line items.

Design both 250 and 379 to sort by line item after Project so that they would match the

contractor pay estimate.


3.2.3 Reports

The Report 250 and Report CERT may be printed from CARs and samples are counted automatically for QA. In addition, the Report 379 may also be printed from CARs and fits IA business processes.

3.3 Estimate Discrepancies Window SiteManager Navigation MAIN PANEL > CONTRACTOR PAYMENTS > ESTIMATE > ESTIMATE DISCREPANCY

*CDOT IS NOT PRESENTLY USING THIS WINDOW FOR MATERIALS FUNCTIONALITY

Window Procedure: To view all discrepancies associated with an estimate, use the Estimate Discrepancies window. Resolve discrepancies in one of two ways:

1. Override each discrepancy.

2. Correct each discrepancy by navigating to the appropriate area in SiteManager (that is, click the Navigation button), updating the data, and recalculating discrepancies.

Note: Discrepancies for progress and supplemental estimates can be overridden, but final estimates cannot. The types of discrepancies include the following:

Overrun or under-run quantities of an item

Material sampling and testing requirements not met

Milestone or contract completion date missed

Checklist event date missed

Payroll certification missed

DBE compliance not met

Security Procedure: CDOT user authority for this window should be available to Technical Support, IT System Administration, and CDOT and Consultant Project Engineers.

Functional Procedure: The Estimate Discrepancies window will NOT be used. SiteManager will show if the project is deficient in samples and/or tests. The discrepancy will not go away until the sample is completed. The PE can review the window for discrepancies and can elect to allow a discrepancy to remain unresolved until the last progress estimate. On the last progress estimate, the PE should resolve all discrepancies or provide a letter explaining why the discrepancies exist to the Finals Engineer. The Finals Engineer will have access to turn the discrepancy off for the final estimate. If there is an estimate discrepancy on a progress estimate, it can be left unresolved, overridden or fixed. If overridden, remarks that explain why it was overridden are required. If it is not resolved by the next


estimate generation time, it will again show up on the estimate as unresolved and it will have to be overridden, again. If the discrepancy is corrected, the discrepancy list can be recalculated and the corrected discrepancy will fall off the list. The window will only show samples that do not meet sample & testing requirements. It will not distinguish between samples that have failed and samples that have not been taken.

3.3.1 Estimate Discrepancies Panel

Figure 3.5 Estimate Discrepancies Window


Table 3.4 Estimate Discrepancies Window - Fields


Key Information

Contract ID NA Auto-populated. If blank, is selected from the “Select Contract and Estimate Window.” ID code for the contract. Agency-defined.

--

Estimate Nbr NA Auto-populated. Sequential number for the estimate on a contract.

--

Status NA Auto-populated. Status of the estimate.

--

Discrepancy Information

Description NA Auto-populated. Description of the discrepancy.

--

Status Yes Drop down menu - Unresolved or Override. Status of the discrepancy.

--

By NA Auto-populated when user selects Override from the Status dropdown list. User ID of the user overriding the discrepancy.

--

Resolve Date

NA Auto-populated. Date user overrode the discrepancy.

--

Resolve Time

NA Auto-populated. Time user overrode the discrepancy.

--


REMARKS CDOT has no specific use for this field, although this is available for use as needed. Mixed case. PROCESS STATUS This window is available almost system wide by selecting Process Status from the Services menu. The window consists of two tab pages: Regular and Scheduled. NAVIGATION The Contract window appears. RECALCULATE DISCREPANCIES This function will recalculate the discrepancies on the estimate.

Procedure: The user must first select the Contact ID and Estimate number. Estimate Discrepancies Window


The Estimate Discrepancies window will NOT be used. SiteManager will show if the project is deficient in samples and/or tests. The discrepancy will not go away until the sample is completed. The PE can review the window for discrepancies and can elect to allow a discrepancy to remain unresolved until the last progress estimate. On the last progress estimate the PE should resolve all discrepancies or provide a letter explaining why the discrepancies exist to the Finals Engineer. The Finals Engineer will have access to turn the discrepancy off for the final estimate. If there is an estimate discrepancy on a progress estimate, it can be left unresolved, overridden or fixed. If overridden, remarks that explain why it was overridden are required. If it is not resolved by the next estimate generation time, it will again show up on the estimate as unresolved and it will have to be overridden, again. If the discrepancy is corrected, the discrepancy list can be recalculated and the corrected discrepancy will fall off the list. The window will only show samples that do not meet sample & testing requirements. It will not distinguish between samples that have failed and samples that have not been taken. Estimate Pay Deductions CDOT will not use this functionality. The Estimate Pay Deductions functionality allows Line Item Adjustments. Currently, the Stockpiled Materials Report is used instead of Line Item Adjustments. The Material Discrepancy Adjustment indicator will be viewable and modifiable in the Items window. However, since the functionality is turned off, even if it is changed it won’t do anything in the system. The PE can see the item window. When a sample is completed, there will be three possible statuses. These statuses are: Complete, Fail and Price Reduce (no discrepancy will be shown), Fail (a discrepancy will be shown).

3.3.1.2 Historical/Decision Notes: Estimate Pay Deductions

Line Item Adjustments – currently this is not used at CDOT o Stockpiled Materials Report – used at CDOT instead of Line Item Adjustments o CDOT uses stockpiled materials but view a report instead of the Line Item Adjustments

window. o This window is not visible to the PE.

Would you want to not pay for an item if the sampling and testing requirements are not met?

Would not want this done automatically.

If the number of samples or tests taken were not sufficient, then it is the Project Staff responsibility to address.

Currently don’t let SM do anything automatically as it is at the subject to the PE to withhold payment

What about COC gathering? o Usually, don’t put item in SM until the COC’s are gathered.

DECISION – Do not use this functionality.

The Material Discrepancy Adjustment indicator will be viewable and modifiable on the Items window. However, since the functionality is turned off, even if it is changed it won’t do anything in the system.

The PE can see the item window.

Estimate Pay Deductions due to Failing Material

If a material fails but remains in place, CDOT will create a price reduction. This is done with a Change Order and then posted on a DWR as an Item.


When a sample is completed, you can choose up to 3 sample status’s which can be used to “Count” towards sample and testing requirements. This really falls to the LIMS committee, but input can be provided by the Contract Materials Committee.

Currently, CDOT processes Letters of Exceptions – calculation of Price Reductions Form 626. This lets the contractor know if they are out of spec.

We would want something like that. o Scenarios of samples submitted for projects: o Complete o Remove and Replace – would need new material and new tests. Not count towards

sampling and testing o Does not meet, but will count and do a pay reduction

This will not show up on the Estimate Discrepancy window. o Not Testable – Sample was taken, so a retest. Not meet S&T requirements.

DECISION: Initially, there is no change to the current process.

The calculations for how SM does this function are at the end of the minutes in case anyone wanted more information.

Certification Acceptance

How is CDOT currently tracking COC’s?

This is on the Form 250. Changes are manually added to the Form 250. A check against the Final Estimate should be done at completion of project.

o COC is submitted and it is documented on the Form 157 and an approval date is recorded.

o This is stamped by the contractor and certified for a certain quantity. o Some items have a certain quantity that has been approved – good for this lot only. o You can have one per item. o Issues-problems – This can be more of a contractor issue than a CDOT issue.

Sometimes contractors stall on providing this information.

DWR vs. Sample Record o Some states do not record COC’s as samples because it could be a lot of work to be sure

that the requirements are met. Other states set up COCs as requirements so that SM will tell them when they are deficient.

o This is a method of acceptance for a lot of items. o The sample would replace From 157. o Want some sort of tracking mechanism. o DECISION – Use as a sample so it will show up as an estimate discrepancy.

Testing and Training Suggestions: After testing sampling and checklist requirements, it was recommended that CDOT not use the estimate discrepancy window because it lacks information on what tests are deficient and in addition, the requirements are by line items and CDOT does not currently require testing by line item but rather the entire bid quantity as a whole. Therefore, discrepancies would always exist and the PE would not know which discrepancies were legitimate. In addition, there is no generic “estimate discrepancy report”. If at some future time discrepancies are turned on, then a report would be useful rather than just using the window.

3.4 Material Inspection Detail Window

SiteManager Navigation MAIN PANEL > DAILY WORK REPORTS > DAILY WORK REPORTS > WORK ITEMS (TAB) > WORK ITEM (RECORD WORK ITEM VIEW) > OPEN MATERIAL INSPECTION DETAIL WINDOW (BUTTON)


*CDOT IS NOT PRESENTLY USING THIS WINDOW FOR MATERIALS FUNCTIONALITY Use the Material Inspection Detail window to view test methods, producer/supplier information and more information about contract sampling and testing, including samples linked to a DWR item.

3.4.1 Material Inspection Detail Panel

Figure 3.6 Material Inspection Detail Window - Material Inspection Detail Panel


Table 3.5 Material Inspection Detail Window - Material Inspection Detail Panel - Fields

Field Name Description

Key Information

Contract ID ID for the contract. Agency-defined. Unique.

Inspector Creator of the DWR.

DWR Date Date the DWR was created.

Recorded Work Information

Project Nbr Project Number. Agency-defined. Unique. Number of project.

Line Itm Nbr Line Item Number. Contract line item number of the item.

Item Code ID for the item.

Category Nbr Category Number. Category of the item.

Item Desc Item Description. Short description of the work item.

Unit Price Cost per unit of measure.

Supp Desc 1 Supplemental Description 1.

Supp Desc 2 Supplemental Description 2.

Qty Reported to Date Quantity Reported to Date. Total of all reported quantities on DWRs, whether authorized or unauthorized and regardless of inclusion on an estimate.

Qty Authorized to Date Quantity Authorized to Date. Total of all reported quantities on authorized DWRs.

Units Type Price per unit of item.

Qty Installed to Date Quantity Installed to Date. Total of all authorized reported quantities on DWRS included in an estimate of any status.

Will always equal the Qty Paid to Date value, unless adjusted on the Estimate Item Detail window.

Bid Qty Bid Quantity. Original amount bid for an item.

Pay to Plan Qty Pay to Plan Quantity. Indicates if line item is paid to plan quantity. No overruns allowed.

Status Item status. Example: active, closed.

Qty Paid to Date Quantity Paid to Date. Total quantity reported on DWRs that were authorized in diaries and included in an estimate of any status.

Current Contract Qty Current Contract Quantity. Current contract quantity of the contract line item including any change orders. Calculated by the sum of bid quantity and the net change order quantity.

Material Inspection Detail Information

Material Component Short material description.

Cont Est Matrl Qty Contract Estimated Material Quantity. Current quantity of contract items multiplied by the conversion factor.

Satisf Repr Matrl Qty Satisfied Represented Material Quantity. Total material quantity reported on the Contract panel of the Maintain Sample Information window.

Reprt Matrl Qty Reported Material Quantity. Total material installed is calculated based on installed quantity of contract item multiplied by the conversion factor.

Matrl Unit Material Unit. Item material unit.



Conversion Factor Used by the required samples calculation to convert current quantity to required quantity.

Contract S&T Contract Sampling and Testing. Indicates item has contract sampling and testing requirements defined.

DWR Sample Indicates sample was created from DWR.

Contract Sampling and Testing Requirements Information

Test Method Unique ID to identify the method used for testing the material.

Sampling Rate Rate at which a sample must be collected.

Sampling Frequency Frequency at which a sample must be collected.

Acceptance Method Identifies how the material will be accepted on the contract.

Sample Type Identifies the type of the test being performed.

P/S Code Producer/Supplier Code. Unique ID for the producer/supplier.

P/S Name Producer/Supplier Name. Name of the producer/supplier.

Procedure:


3.5 Process List Window

SiteManager Navigation MAIN PANEL > PIPELINE > PROCESS LIST

*CDOT IS NOT PRESENTLY USING THIS WINDOW FOR MATERIALS FUNCTIONALITY SiteManager displays for a user only those processes assigned to that user’s security group. Processes may include standard RTF report templates or customized processes for on-line and background execution. Some processes may only be run as background processes.

3.5.1 Process List Panel


Figure 3.7 Process List Window

Table 3.6 Process List - Fields


Process ID Uniquely identifies the custom process. This field is required to save the record.

------------------------------------------------------------------------------------------------

Process Type Processes created by the user default to Custom. SiteManager-provided processes are designated as Standard.

Process Description Short description of the process.

Procedure: -Right clicking on the Process ID opens the Confirm Process Submission window.


3.6 Key Dates Window

SiteManager Navigation MAIN PANEL > CONTRACT ADMINISTRATION > CONTRACT RECORDS > KEY DATES


*CDOT IS NOT PRESENTLY USING THIS WINDOW FOR MATERIALS FUNCTIONALITY Use the Key Dates window to add, modify, and delete the key dates for the selected contract. Create the schedule and record the actual occurrence on this panel.

3.6.1 Key Dates Panel

Figure 3.8 Key Dates Window


Table 3.7 Key Dates - Fields


Contract ID Uniquely identifies the contract. Agency-defined.

Key Date Type Type of key date (for example, Closed to Traffic Date, State Final Inspection Date, Open to Traffic Date). After the record is saved, this field is protected. Required. Agency-defined.

Projected Date Date the event is targeted to occur.

Actual Date Date the event actually occurs. When entered, the date must be current or in the past. The Recipient or Distribution List is notified when this date is entered.

Required to Activate Indicates that a key date must occur before the contract status can be changed from Pending to Active (for example, Letting Date, Award Date, Execution Date). A key date cannot be both Required to Activate and Required to Finalize.

Required to Finalize Indicates that a key date is part of the contract finalization process. A key date cannot be both Required to Activate and Required to Finalize.

Key Date Type Type of key date (for example, Closed to Traffic Date, State Final Inspection Date, Open to Traffic Date). After the record is saved, this field is protected. Required. Agency-defined.

Projected Date Date the event is targeted to occur.

Required to Activate Indicates that a key date must occur before the Contract status can be changed from Pending to Active (for example, Letting Date, Award Date, Execution Date). A Key Date cannot be both Required to Activate and Required to Finalize.

Actual Date Date the event actually occurs. When entered, the date must be current or in the past. Recipient or Distribution List is notified when this date is entered.

Required to Finalize Indicates that a key date is part of the contract finalization process. A key date cannot be both Required to Activate and Required to Finalize.

Distribution List Group to be notified that the event has occurred. Either a Distribution List or Recipient field value must be entered. After a valid entry in either field, the other field is protected.

Recipient User ID of a person to be notified that the event has occurred. Either a Distribution List or Recipient must be entered. After a valid entry in either field, the other field is protected.

Message Text Standard message to be sent to the recipient(s).

Procedure:


3.7 Checklist Scheduled Events Window

SiteManager Navigation MAIN PANEL > CONTRACT ADMINISTRATION > CONTRACT RECORDS > CHECKLIST SCHEDULED EVENTS


*CDOT IS NOT PRESENTLY USING THIS WINDOW FOR MATERIALS FUNCTIONALITY Use the Checklist Scheduled Events window to schedule events for the selected contract.

3.7.1 Checklist Scheduled Events Panel

Figure 3.9 Checklist Scheduled Events Window


Table 3.8 Checklist Scheduled Events Window - Fields


Upper pane


Event Type Type of event (for example, bonding verified DBE commitment verified, Final Inspection Completed). After the record is saved, this field is protected. Required. Agency-defined.

Frequency Type For repetitive events, the frequency with which those events occur (that is, Daily, Weekly, Biweekly, Monthly, Quarterly, Semi-Annually, or Annually). One Time Only is for non-repetitive events. Required.

Event Group Type Grouping of associated event types (for example, EEO, Training, or Certification). Required.

Next Proj Date Next Projected Date. Next target date for the repetitive event to occur. For a new checklist event, it is the first occurrence date. Required.

Nbr of Occrnc Number of Occurrences. Number of times the event is scheduled to occur in the specified frequency type. If the frequency type is ‘One Time Only’ this field will default to 1. Required.

Required to Activate Indicates that the event must occur before the Contract status can be changed from Pending to Active. Only events with a frequency of One Time Only can be Required to Activate. An event type cannot be both Required to Activate and associated with a Discrepancy. If one of these check boxes is selected, the other field is protected. Protected if the Contract is already active.

Discr Ind Discrepancy Indicator. Indicates that if the event has not occurred by the time of estimate generation, this event is noted as a Discrepancy. An event type cannot be both Required to Activate and associated with a Discrepancy. If one of these check boxes is selected, the other field is protected.

Required Doc Type Required Document Type. Defined codes identifying the type of document when an external document is expected (for example, Training Report, EEO Report, Material Certification). Required when the Ext Ind check box is selected. Agency-defined.

Ext Ind External Indicator. Indicates that a document is expected to be received from an external source. A valid Document Type must be entered when the check box is selected.

Lower pane

Event Type Type of event (for example, bonding verified DBE commitment verified, Final Inspection Completed). After the record is saved, this field is protected. Required. Agency-defined.

Event Group Type Grouping of associated event types (for example, EEO, Training, or Certification). Required.

Frequency Type For repetitive events, the frequency with which those events occur (that is, Daily, Weekly, Biweekly, Monthly, Quarterly, Semi-Annually, or Annually). One Time Only is for non-repetitive events. Required.

Event Day Day of the week or month that these events are to occur. For weekly and bi-weekly events, the day of the week (01-07) the events are to occur. For monthly events, the day of the month (01-30) they are to occur. This field is protected for all other frequency types.



Milestone No Milestone Number. Identifies a milestone number within the contract.

Next Proj Date Next Projected Date. Next target date for a repetitive event to occur. For a new checklist event, it is the first occurrence date. Required.

Required to Activate Indicates that the event must occur before the contract status can be changed from Pending to Active. Only events with a frequency of One Time Only can be Required to Activate. An event type cannot be both Required to Activate and associated with a Discrepancy. If one of these check boxes is selected, the other field is protected. Protected if the contract is already active.

Nbr of Occurrences Number of times the event is scheduled to occur in the specified frequency type. If the frequency type is ‘One Time Only’ this field will default to 1. Required.

Discrepancy Indicates that if the event has not occurred by the time of estimate generation, this event is noted as a Discrepancy. An event type cannot be both Required to Activate and associated with a Discrepancy. If one of these check boxes is selected, the other field is protected.

Required Doc Type Required Document Type. Codes identifying the type of document when an external document is expected (for example, Training Report, EEO Report, Material Certification). Required field when the External Indicator is checked. Agency-defined.

External Indicator Indicates that a document is expected to be received from an external source. A valid Document Type must be entered when the check box is selected.

Distribution List Group to be notified when the Checklist Event’s projected date expires and the actual date is not entered. Either a Distribution List or Recipient field must be entered. After a valid entry in either field, the other field is protected.

Recipient User ID of a person to be notified when the Checklist Event’s projected date expires and the actual date is not entered. Either a Distribution List or Recipient field must be entered. After a valid entry in either field, the other field is protected.

Message Text Standard message to be sent to recipient(s).

Procedure:


3.8 Checklist Event Dates Window

SiteManager Navigation MAIN PANEL > CONTRACT ADMINISTRATION > CONTRACT RECORDS > CHECKLIST EVENT DATES

*CDOT IS NOT PRESENTLY USING THIS WINDOW FOR MATERIALS FUNCTIONALITY Use the Checklist Event Dates window to view the scheduled events for the selected contract.


3.8.1 Checklist Event Dates Panel

Figure 3.10 Checklist Event Dates Window


Table 3.9 Checklist Event Dates - Fields


Upper pane


Event Type Code representing a type of event (for example, bonding verified, DBE commitment verified, Final Inspection Completed). Agency-defined.

Frequency Type For repetitive events, the frequency with which those events occur (that is, Daily, Weekly, Biweekly, Monthly, Quarterly, Semi-Annually, or Annually). One Time Only is for non-repetitive events.

Event Group Type A grouping of associated event types (for example, EEO, Training, Certification).

Next Proj Date Next Projected Date. The next targeted date for the event to occur.

Nbr of Occrnc Number of Occurrences. Number of times the event is expected to occur.

Required to Activate Indicates that an event must occur before the Contract status can be changed from Pending to Active.

Discr Ind Indicates whether a discrepancy should be noted if an event has not occurred by the time of the estimate generation.

Required Doc Type Required Document Type. Codes identifying each type of document (for example, Trainee report, EEO report, Material Certification document). Agency-defined.

Ext Ind External Indicator. Indicates that a document is expected to be received from an external source.

Lower pane

Projected Date Date the event is targeted to occur. Protected after the record is saved. When entered, the date must be in the future and cannot be greater than the next projected date. For a new row, default to Next Proj Date.

Actual Date Date the event actually occurs, which is protected when the Ext Ind check box is selected. When entered, the date must be current or in the past.

Comments Comments about this record.

Procedure:



SECTION 4 Mix Designs

74 Mix Designs

4.1 SUPERPAVE Mix Design Window

SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > MIX DESIGN > SUPERPAVE MIX DESIGN

Window Procedure: SUPERPAVE Mix Design window allows for the addition, modification, and approval of SUPERPAVE Mix Designs. A SUPERPAVE Mix Design may not be changed if it is approved. The test results on this window are used by SiteManager for comparison. A SUPERPAVE Mix Design may also be downloaded for a specific contract.

Security Procedure: User authority for update of this window is available to the Technical Support, IT System Administration, and Region Materials Office. Everyone with access to LIMS will have inquiry access, except the Central Lab Unit groups (Concrete and Physical Properties, and Soils).

Functional Procedure: CDOT will utilize this window, panels and template to approve SUPERPAVE mix designs and to have form 43’s generated. Several fields will be required to be completed in order to proceed to the next panel. These fields include Mix ID, Material Code and Producer Supplier Code. Be sure to save the data.


Use the Description panel to identify the mix design with a unique mix ID, material code, producer/supplier and effective dates.


Figure 4.1 SUPERPAVE Mix Design Window - Description Panel

Table 4.1 SUPERPAVE Mix Design Window - Description Panel – Fields


Mix ID YES Free-form field. Uniquely identifies a SUPERPAVE mix design. See Naming convention below. 15

Material Code YES Search, Uniquely identifies a specific asphalt mix. --

Material Full Name (no

label) NA

Auto populated. Describes the material from the Material Code.

--


YES Search, Identifies a supplier and/or source/location of the material. Must have an active status on the Producer Supplier table, when entered. --

Producer Supplier

Description(no label)

NA Auto populated. Describes the producer/supplier.

--

Designer Name

YES Free-form field, Name of the company responsible for the original SUPERPAVE mix design submitted. 15

AC Type YES Drop-down menu. Identifies the type of asphalt binder to be used in the mix. See Code Table ASPHCEM --

Mix Type YES Drop-down menu. Describes the type of mix design. See Code Table MIXDSN --

Effective Date YES Free-form field. Effective date for the SUPERPAVE mix. Defaults to current date when a new SUPERPAVE mix is entered. MM/DD/YY

Termination YES Free-form field. Date 2 years after Effective Date. MM/DD/YY

76 Mix Designs


Date

Approved Date

NO Free-form field. To be used at the discretion of the RME. MM/DD/YY

4.1.1.1 Required Fields MIX ID: Uniquely identifies a SUPERPAVE mix design. Add naming convention. Digit 1 = Region # (e.g. 1,2,3) Digit 2-5 = Year mix design is issued (e.g. 2011) Digit 6 = code for mix design placement within section;

T for Top layer I for Intermediate layers B for Bottom layer A for all layers V for varies G for aggregate mix designs

Digit 7 thru 13 – Region choice as long as unique alpha/numeric is chosen. Possible uses: date (mmdd) and time (hr-military), first initial of person’s last name that initiated design.

Digit 14 – Underscore _

Digit 15 – Blank for original mix or letter for revision.

Note: Each Region should determine what their naming convention will be for digits 7-13 prior to training. Region 6 will be: name of supplier, followed by mix design # for the year. (i.e. APC01 = Asphalt Paving Company, 1

st mix design of the year)

MATERIAL CODE: Search for material code. MATERIAL FULL NAME: Auto Populated, Describes the material from the material code. PRODUCER SUPPLIER CODE: Search – identifies a supplier and/or source or location of the material. Must have an active status on the Producer Supplier Table, when entered. PRODUCER SUPPLIER DESCRIPTION: Auto-Populated with producer supplier name. DESIGNER NAME: Name of the entity responsible for the original SUPERPAVE mix design submitted. AC TYPE: Drop down. Identifies the type of asphalt binder to be used in the mix. Note: Binder Supplier is entered in the SuperPave Custom Template.

Code Table = ASPHCEM – AC Type


Code Description

PG1 PG 58-28

PG2 PG 58-34

PG3 PG 64-22

PG4 PG 64-28

PG5 PG 70-28

PG6 PG 76-28

MIX TYPE: Drop down. Describes the type of mix design (S, SX, SMA, etc.).

Code Table = MIXDSN – Mix Type

Code Description

CIPC CIP-coarse

CIPM CIP-medium

HIPC HIP-coarse

HIPM HIP-medium

MS Micro-Surfacing

RCI RCI

S S

SF SF

SG SG

SM25 #4 SMA

SM38 3/8” SMA

SM50 1/2” SMA

SM75 3/4” SMA

ST ST

SX SX

UB Ultrathin B

EFFECTIVE DATE: Effective date for the SUPERPAVE mix, defaults to current date when a new SUPERPAVE mix is entered. TERMINATION DATE: Date 1-2 years from effective date. APPROVED DATE: To be used at the discretion of the RME.

4.1.1.2 Drop-down Services Menu REMARKS CDOT has no specific use for this field, although this is available for use as needed. Mixed case. ATTACHMENTS Optional

78 Mix Designs

PROCESS STATUS This window is available almost system wide by selecting Process Status from the Services menu. The window consists of two tab pages: Regular and Scheduled. APPROVE Used to approve the mix. . COPY RECORDS Copies a new record to assign a New Mix ID to a SuperPave mix. CUSTOM RECORD

CDOT has added additional data to database. Entering data in this custom template saves the information.

4.1.2 Properties Panel Use the Properties panel to document the properties of the mix design.

Figure 4.2 SUPERPAVE Mix Design Window - Properties Panel

Table 4.2 SUPERPAVE Mix Design Window - Properties Panel - Fields


N (Initial) Optional Initial compaction gyrations of the specific mix design

N Initial (Max) Optional

Maximum compaction gyrations of the specified mix design --



N (Design) Yes Free-form field. Design compaction gyrations of the specified mix design. 3

% Gmm @ N (Init)

No Percent of solids by volume at maximum compaction gyrations of the specified mix design. --

% Gmm @ N (Max)

No Percent of solids by volume at maximum compaction gyrations of the specified mix design. --

Equiv Single Axle

No Number of load axle equivalent weight that pavement can endure before damage occurs. --

Optimum AC % by Tot Weight

Yes

Free-form field. Asphalt content that will be used to produce the specified mix in the field. Includes virgin asphalt cement and any provided by the RAP, if applicable. --

Dust Proportion

Yes Free-form field. Ratio of Dust to Asphalt. Num

VMA % Yes Free-form field. Percentage of voids in the mineral aggregate for the specified mix design. Num

VFA % No (CDOT will not use) The Form 43 will be auto-populated based on the N Design #. Num

Lottman TSR Optional Free-form field. Tensile strength ratio for the specified mix. Num

Sand Equivalent

Optional Free-form field. Specification of the Sand Equipment Num

Maximum Specific Gravity

Yes Free-form field. Maximum specific gravity for the specific mix.

Num

Bulk Specific Gravity

Yes Free-form field. Bulk specific gravity of the SUPERPAV mix design at the optimum AC %. Num

Mixing Temperature

Optional Design mixing temperature Num

Mixing Temperature Units Type

N/A

Drop-down menu. Unit of Measure for the associated mixing temperature value. Required if the Mixing Temperature field is populated. See Code Table: TEMP --

Compaction Temp

Optional Design compaction temperature for the specified bituminous mix. Num

Compaction Temp Units Type

N/A

Drop-down menu. Unit of Measure for the associated design compaction temperature value. See Code Table TEMP. Required if the Design Compaction Temperature field is populated. --

High Air Temp Optional Average high air temperature --

High Air Temp Units

N/A Drop-down menu. Unit of Measure for the high air temperature. Required when high air temperature entered. --

4.1.2.1 Required/Optional Fields N (INITIAL): Initial compaction gyrations of the specified mix design. N (MAX): Maximum compaction gyrations of the specified mix design.

80 Mix Designs

N (DESIGN): Design compaction gyrations of the specified design. OPTIMUM AC % BY TOT WEIGHT: Asphalt content that will be used to produce the specified mix in the field. Includes virgin asphalt cement and any provided by the RAP, if applicable. DUST PROPORTION: Ratio of Dust to Asphalt. VMA %: Percentage of voids in the mineral aggregate for the specified mix design. LOTTMAN TSR: Tensile strength ratio for the specified mix. SAND EQUIVALENT: Specification of the Sand Equipment. MAXIMUM SPECIFIC GRAVITY: Bulk specific gravity of the SUPERPAVE mix design at optimum AC%. BULK SPECIFIC GRAVITY: Bulk specific gravity of the SUPERPAVE mix design at optimum AC%. MIXING TEMPERATURE: Design mixing temperature. MIXING TEMPERATURE UNITS TYPE: Drop Down. Unit of measure for the associated mixing temperature value. Required if the Mixing Temperature field is populated.

Code Table = TEMP – Temperature Unit of Measure

Code Description

C Degree Celsius

F Fahrenheit

COMPACTION TEMP: - Design compaction temperature for the specified bituminous mix. COMPACTION TEMPERATURE UNITS TYPE: - Drop down. Unit of measure for the associated design compaction temperature value. Required if the Design Compaction Temperature field is populated. HIGH AIR TEMPERATURE: - Average high temperature. HIGH AIR TEMPERATURE UNITS TYPE: - Drop Down. Units of measure for high air temperature. Required when high air temperature entered.

4.1.2.2 CDOT will not use Fields % GMM @ N (INIT): Percent of solids by volume at initial compaction gyrations of the specific mix design. % GMM @ N (MAX): Percent of solids by volume at initial compaction gyrations of the specified mix design. EQUIV SINGLE AXLE LOADS: Number of load axle equivalent weight, that pavement can endure before damage occurs. VFA %: Percentage of VMA filled by the effective asphalt for the specified mix. This number will be found on the Form 43 based on the N design #.


4.1.2.3 Drop-down Services Menu REMARKS CDOT has no specific use for this field, although this is available for use as needed. Mixed case. ATTACHMENTS Optional PROCESS STATUS This window is available almost system wide by selecting Process Status from the Services menu. The window consists of two tab pages: Regular and Scheduled. APPROVE Used to approve the mix. CUSTOM RECORD


4.1.3 Materials Panel Use the Materials panel to document the component materials of the mix design. This tab is populated with aggregates and hydrated lime. Do not populate binder, or additives such as mineral filler, fibers, or liquid additives. Binder is entered in the Description tab panel, but the Binder Supplier is entered in the custom template. Use the SuperPave Custom Template to document those other mix components.

82 Mix Designs

Figure 4.3 SUPERPAVE Mix Design Window - Materials Panel

Table 4.3 SUPERPAVE Mix Design Window - Materials Panel - Fields


Material Code Yes Search. Uniquely identified a component material associated with the bituminous mix materials with which the mix design will be associated.

Material Description

N/A Auto populated. Full description for the selected material. --


Yes Search. Uniquely identified the producer/supplier approved to provide the component material for the bituminous mix material. 3

Producer Supplier Name (no label)

N/A Auto populated. Full Name the selected producer/supplier.

--

Brand Name No (CDOT will not use) --

Blend Percent Yes Free-form field. Percentage of the component material contained within the bituminous mix material. --

Sample ID Optional Uniquely identifies a sample record created to capture sample data during the evaluation process of the component material. --

Specific Gravity (Apparent)

Optional Free-form field. Apparent specific gravity of the component material contained within the bituminous mix materials.

Specific Gravity (Bulk)

Optional Free-form field. Bulk specific gravity of the component material contained within the bituminous mix material.


4.1.3.1 Required/Optional Fields

MATERIAL CODE: Search – Uniquely identifies a component material associated with the bituminous mix material with which the mix design will be associated.

Note: No binders or additives are to be populated on this panel. Other panels are to be used for their capture.

MATERIAL DESCRIPTION: Auto Populated. Full description for the selected material. PRODUCER/SUPPLIER CODE: Search – Uniquely identifies the producer/supplier approved to provide the component material for the bituminous mix material. PRODUCER/SUPPLIER NAME: Auto Populated. Full name for the selected producer/supplier. BLEND PERCENT: Free Form. Percentage of the component material contained within the bituminous mix material. SAMPLE ID: Uniquely identified a sample record created to capture sample data during the evaluation process of the component material. SPECIFIC GRAVITY (APPARENT): Free Form. Apparent specific gravity of the component material contained within the bituminous mix material. SPECIFIC GRAVITY (BULK): Free Form. Bulk specific gravity of the component material contained within the bituminous mix material .

4.1.3.2 CDOT will not Use Field

BRAND NAME: Brand name of the component material.

4.1.3.3 Drop-down Services Menu PROCESS STATUS This window is available almost system wide by selecting Process Status from the Services menu. The window consists of two tab pages: Regular and Scheduled. VIEW SAMPLE The Maintain Sample Information window appears. . CUSTOM RECORD



Use the Gradations panel to document the gradation data of the mix design.

84 Mix Designs

Note: When only Min and Max Production Tolerances are entered it causes the gradation template (CP31 and CP31x) not to indicate pass or fail, but only NA because it is looking for the sieve values, not the production tolerances.

Figure 4.4 SUPERPAVE Mix Design Window - Gradations Panel

Table 4.4 SUPERPAVE Mix Design Window - Gradations Panel - Fields


Effective Date N/A Date the gradation specification becomes effective. Defaults to current date when a new set of material gradation specifications are created or copied.

Status N/A Identifies the current status of this sieve size record (for example, active or inactive). Status defaults to active. --

Sieve Size Yes Auto populated. AASHTO and ASTM standard sieve sizes (1/2 No. 4, and so on). Required when minimum or maximum entered. 3

Sieve Value Optional Free-form field. Job mix formula (composite). Percentage of bituminous mix material passing through the sieve screen. --

Minimum Range

N/A Beginning value for the gradation specification limit. --

Maximum Range

N/A Ending value for the gradation specification limit. --

Min Production Tolerance

Yes Free-form field. Minimum production tolerance value specification. Required when the sieve value field is populated. --

Max Yes Free-form field. Maximum production tolerance value



Production Tolerance

specification. Required when sieve value field is populated.


EFFECTIVE DATE: Date the gradation specification becomes effective. Defaults to current date when a new set of material gradation specifications are created or copied. STATUS: Identifies the current status of this sieve size record (for example, active or in active). Status defaults to active. SIEVE SIZE: Auto Populated. AASHTO and ASTM standard sieve sizes (1/2, No. 4, etc.) Required when minimum or maximum entered. SIEVE VALUE: Job Mix formula (composite). Percentage of mix material passing through the sieve screen. MINIMUM RANGE: Beginning value for the gradation specification limit. MAXIMUM RANGE: Ending value for the gradation specification limit. MIN PRODUCTION TOLERANCE: Minimum production tolerance value specification. Required when the sieve value field is populated. MAX PRODUCTION TOLERANCE: Maximum production tolerance value specification. Required when the sieve value field is populated.

4.1.4.2 Drop-down Services Menu PROCESS STATUS This window is available almost system wide by selecting Process Status from the Services menu. The window consists of two tab pages: Regular and Scheduled. . CUSTOM RECORD


86 Mix Designs

4.1.5 SUPERPAVE Custom Template

Use the SUPERPAVE Custom Template to document additional required data of the mix design. The additional data is required for the Project Specific Asphalt Job Mix Formula (SiteManager Form 43).

Figure 4.5 SUPERPAVE Mix Design Window – SUPERPAVE Custom Template Panel

Table 4.5 SUPERPAVE Mix design Window – SUPERPAVE Custom Template Panel - Fields


Design Type YES

Radio Button. Must check one button or you cannot save data. --

# of Blows only for

Marshall mixes Free-form field. Identifies the number of blows of the mix design. 3

Plant(s) YES Free-form field. Identifies Producer's plant where only this mix may be produced.

50

Source of AC

YES Free-form field. Identifies the Refinery where the AC binder is being produced.

20



1st Recycle Mat'l % AC

only when recycled

material is in the mix

Free-form field. Identifies the percent AC binder in the recycled material. Also, use just the number for the different recycled materials in mix.

2.2

2nd Recycle Mat'l % AC

only when recycled



2.2

3rd Recycle Mat'l % AC

only when recycled



2.2

4th Recycle Mat'l % AC

only when recycled



2.2

Acceptance Criteria YES

Radio Button. Must check one to identify the Acceptance criteria. --

Changes to original Mix Design or not.

YES

Radio Button. Must check just one button or you cannot save data. First two self-explanatory; 'modified' could be that mix has been revised or transferred to another project as is etc.

--

Bulk Sp. Gr. of Fine Agg.

YES Free-form field. Identifies the bulk Specific Gravity of the Fine aggregate in the mix.

1.3

Bulk Sp. Gr. of the combined Agg.

YES

Free-form field. Identifies the bulk Specific Gravity of the Combined aggregate in the mix.

1.3

% Agg. Absorption (SSD)

YES Free-form field. Identifies the % water absorption of the aggregate as stated in CP52.

2.2

Angularity (T304)

YES Free-form field. Identifies the Uncompacted Void Content of Fine Aggravate (angularity) specification.

2.1

% Voids YES Free-form field. Identifies the % voids in mix at N (des) 2.2

Stability YES except

SMA Free-form field. Identifies the Stability from the mix design. 4

Flow only for

Marshall mixes Free-form field. Identifies the Marshall Stability flow from the mix design. 2

Region materials Engineer

YES Free-form field. Identifies the Region Materials Engineer (RME) signing the Form 43 Report. 1st name, last name e. g. George Washington 25

Remarks 1 Optional Free-form field. Each of the 4 remarks lines has a maximum of 50 characters 50

Remarks 2 Optional and may use in any manner. e. g. one may use half of # 1 and all of #3; 50

Remarks 3 Optional may use part of #2 all of #3 and half of #4; may use all of #1 and part of 50

Remarks 4 Optional #4; etc. 50

Additive 1 % only as needed

Free-form field. Identifies the % of the first additive used in the mix. 1.2

88 Mix Designs


Additive 1 Material only as needed

Free-form field. Identifies the additive material or process. Examples of additives are mineral fillers, fibers, or liquid additives or enhancers. 20

Additive 1 Supplier only as needed

Free-form field. Identifies the supplier of the additive. 30

Additive 2 % only as needed

Free-form field. Identifies the % of the second additive used in the mix. 1.2

Additive 2 Material only as needed

Free-form field. Identifies the additive material or process. Examples of additives are mineral fillers, fibers, or liquid additives or enhancers. 20

Additive 2 Supplier only as needed

Free-form field. Identifies the supplier of the additive. 30

TESTING AND TRAINING SUGGESTIONS: The screenshots were populated with real data. Good information for training exercise. The template is populated as well. Learning material codes will be a challenge until they become used to the numbers and will use the same numbers over and over. A cheat sheet with common material codes for Mix Design (SMA), (Aggregate), etc. would be useful initially. Mix IDs won’t be uniform across the state. Thus, each Region should determine what their MIX ID code will be prior to implementation and training. An exercise to enter a Marshall Mix would also be useful. It will be entered in the SuperPave window NOT the Marshall Mix window.

4.2 Portland Cement Concrete Mix Design Window

SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > MIX DESIGN > PORTLAND CEMENT CONCRETE MIX DESIGN

Window Procedure: Use the Portland Cement Concrete Mix Design window to add, modify and approve Portland concrete mix designs. Users cannot change a Portland concrete mix design once approved. Site Manager uses the test results on this window for comparison. Users may download a Portland concrete mix design for a specific contract.

Security Procedure: Everyone with access to LIMS will have inquiry access, except the Central Lab Unit groups (Binder, Flexible Pavement and Chemical, and Soils). This will allow anyone to view or search for mix designs to see if they have been previously approved and to verify that the mix listed on a batch ticket match the approved mix design. The Technical Support, IT System Administration, Region Materials Office, Technician 3 and above in the Concrete Unit of the Central Lab will have input, update and approval access for the mix designs.


Functional Procedure: One custom template will be needed for PCC mix designs with the following fields:

Table 4.6 PCC Custom Template Fields

Name Format Units Description

Average 7-Day Compressive Strength XX,XXX psi

Average 7-day compressive strength of the trial mix







Average 7-Day Flexural Strength X,XXX psi

Average 7-day flexural strength of the trial mix

Average 28-Day Flexural Strength X,XXX psi

Average 28-day flexural strength of the trial mix

In addition to the inputting the information in the mix design windows and custom template, the original mix design will be scanned and attached as a PDF file so that additional information that may be useful in future research or forensic investigations will be available. Typically, concrete mix designs are sent to the Concrete Unit of the Central Lab for review, approval and assignment to a project. However, some concrete mix designs, such as Class R concrete are approved by the Region Materials Engineers. Mix designs approved by the Central Lab are placed on the approved products list, while mix designs approved by the RMEs are not. Mix designs will be approved if they meet the requirements listed in CP-62 or the requirements for Class R concrete. The termination date for standard mix designs will be 2 years from the Trial date or the aggregate test date, whichever is earlier. The termination date for project specific or Class R concrete will be the date they are approved so that they will not be included in the pre-approve concrete mix design report. A mix may also be terminated upon unsatisfactory field results. Changes to the proportions, sources or type of cement, fly ash or aggregates will require a new mix design number. Changes to admixtures will be documented by copying the original mix design and adding R#(Reason) to the end of the mix ID. # will be the revision number, sequential starting with 1. (Reason) may be Admix Change, Accelerated, Retarded or other. These revised mixes will be used for tracking changes and will not be issued to projects or listed on the approved products list. The original mix design will be assigned to the project. The stamped letter requesting the admixture change will be scanned and attached to the revised mix design. For example a pre-approved mix with the ID 2009099 has been approved to have an accelerator added and this is the 1

st revision, the revised mix ID will be 2009099R1(Accelerated).

To approve a mix design: Click services, then approve. Click save to approve the mix. Changes cannot be made to mix after approval.

4.2.1 Description Panel Use the Description panel to identify the mix design with a unique mix ID, material code, producer/supplier, and effective dates.

90 Mix Designs

Figure 4.6 Portland Cement Concrete Mix Design Window - Description Panel

Table 4.7 Portland Cement Concrete Mix Design - Description Panel – Description Tab


Mix ID

Yes Uniquely identifies a mix design. CDOT will use a four-digit year and then a 3-digit sequence number for standard mix designs (Format: YYYYXXX, example 2010054). Revised mixes will have the original mix ID followed by R#(Reason). # will be the revision number, (reason) will be Admix Change, Accelerated or Retarded. Project Specific or Class R concrete will be given a mix ID of R#YYYYXXX. # will be region number, followed by the 4-digit year and a three digit sequential number.

15

Material Code Yes Search Field. Uniquely identifies a material. This will be associated with the class of concrete.

--


Yes Search Field. Uniquely identifies a source/location of the material. Producer/Supplier Code must have an active status on the Producer Supplier table when entered.

--

Designer Name Yes Supplier’s Mix ID. 50 alpha/num

Concrete Class Type

Yes Drop-down menu. Used for the Sulfate Resistance Class of concrete (Sulfate Resistance Class 0 thru 3).

Effective Date Yes Date the concrete mix is approved. Defaults to current date when a new Portland cement concrete mix is entered.

mm/dd/yy



Termination Date Yes Date the Portland cement concrete mix is no longer available for use. Must be greater than Effective Date. This is 2 years from the Trial date or the aggregate test date, whichever is earlier

mm/dd/yy

Approved Date Yes Date when the Portland cement concrete mix was approved. System-generated. Defaults to current date when a Portland cement concrete mix is approved.

mm/dd/yy

Approved By User ID

Yes User ID of the person who approved the Portland Cement Concrete mix. System-generated.


MIX ID: Uniquely identifies a mix design. CDOT will use a four-digit year and then a 3-digit sequence number for standard mix designs (Format: YYYYXXX, example 20100540). Revised mixes will have the original mix ID followed by R#(Reason). # will be the revision number, (reason) will be Admix Change, Accelerated or Retarded. Project specific or Class R concrete will be given a mix ID of R#YYYYXXX. # will be region number, followed by the 4-digit year and three-digit sequential number. MATERIAL CODE: Search field – uniquely identified a material. This will be associated with the class of concrete. PRODUCER SUPPLIER CODE: Search field – uniquely identifies a source/location of the material Producer/Supplier Code must have an active status on the Producer Supplier table when entered. DESIGNER NAME: Suppliers Mix ID. CONCRETE CLASS TYPE: Dropdown. Used for the Sulfate Resistance Class of Concrete (Sulfate Resistance Class 0 thru 3).

Code Table = PCCCLASS – Portland Concrete Classes

Code Description

CL0 Class 0 Sulfate Resistance




EFFECTIVE DATE: Date the concrete mix is approved. Defaults to current date when a new Portland cement concrete mix is entered. TERMINATION DATE: Date the Portland cement concrete mix is no longer available for use. Must be greater than effective date. This is 2 years from the trail date or the aggregate test date, whichever is earlier. APPROVED DATE: Date when the Portland cement concrete mix was approved. System-generated. Defaults to current date when a Portland cement concrete is approved.

92 Mix Designs

APPROVED BY USER ID: User ID of the person who approve the Portland Cement Concrete mix. System-generated.

4.2.1.2 Drop-down Services Menu REMARKS CDOT has no specific use for this field, although this is available for use as needed. Mixed case. ATTACHMENTS Optional PROCESS STATUS This window is available almost system wide by selecting Process Status from the Services menu. The window consists of two tab pages: Regular and Scheduled. . COPY RECORDS Copies a new record to assign a New Mix ID to a Concrete mix. CUSTOM RECORD


4.2.2 Properties Panel

Use the Properties panel to document the properties of the mix design.

Figure 4.7 Portland Cement Concrete Mix Design Window - Properties Panel


Table 4.8 Portland Cement Concrete Mix Design Window - Properties Panel – Fields


Min Average Strength Required

Yes

Specified strength of the concrete class in psi. From Table 601-1 of CDOT Specifications.

15

Design Strength Specified

Yes

Required strength of the laboratory trial mix in psi. This is currently 115% of the specified strength.

15

Theoretical Unit Wt Yes Unit weight of the laboratory trial mix. 15

Theoretical Unit Wt Unit Type

Yes

Drop-down menu. Unit of measure for measured unit weight. Required when Unit Weight Measured entered. See Code Table = PRESSURE

--

Water Cement Ratio Yes The water to cementitious ratio of the laboratory trial mix.

15

Unit Weight Measured Yes The relative yield of the laboratory trial mix

15

Unit Weight Measured Unit Type

Yes Drop-down menu. Use “Not Applicable (For PCC Mix Designs)”

Air Content Measured Yes Air content of the laboratory trial mix. 15

Slump Measured Yes Slump of the laboratory trial mix. 15

Slump Measured Unit Type

Yes

Drop-down menu. Unit of measure for measured slump. Required when Slump Measured entered. See Code Table = LENGTH

--

4.2.2.1 Required Fields MIN AVERAGE STRENGTH REQUIRED: Specified strength of the concrete class in psi. From Table 601-1 of CDOT Specifications. DESIGNED STRENGTH SPECIFIED: Required strength of the laboratory trial mix in psi. This is currently 115% of the specified strength. THEORETICAL UNIT WT: Unit weight of the laboratory trial mix. Theoretical Unit Wt Unit Type – Drop down – Unit of measure for measured unit weight. Required when Unit Weight Measured entered. See Code Table = Pressure.

94 Mix Designs

Code Table = PRESSURE – Pressure Unit of Measure

Code Description

KCM Kilograms Per Cubic Meter

KPA kPa - Kilopascals

KSF Ksf – Thousand Pounds Per Square Foot

MPA MPa - Megapascals

NA Not Applicable (FOR PCC Mix Designs)

PA Pa - Pascals

PCF Pounds per Cubic Foot

PSF psf – Pounds Per Square Foot

PSI psi – Pounds Per Square Inch

WATER CEMENT RATIO: The water to cementitious ratio of the laboratory trial mix. UNIT WEIGHT MEASURE: The relative yield of the laboratory trial mix. UNIT WEIGHT MEASURED UNIT TYPE: Dropdown – use “Not Applicable (For PCC Mix Designs)” AIR CONTENT MEASURED: Air content of the laboratory trial mix. SLUMP MEASURED: Slump of the laboratory trial mix. SLUMP MEASURED UNIT TYPE: Dropdown – Unit of measure for measured slump. Required when Slump Measured entered. See Code Table = LENGTH

Code Table = LENGTH – Length Unit of Measure

Code Description

FT Foot

IN Inch

MILE Mile

YD Yard

cm Centimeter

km Kilometer

m Meter

mm Millimeter

4.2.2.2 Drop-down Services Menu REMARKS CDOT has no specific use for this field, although this is available for use as needed. Mixed case. ATTACHMENTS Optional PROCESS STATUS


This window is available almost system wide by selecting Process Status from the Services menu. The window consists of two tab pages: Regular and Scheduled. CUSTOM RECORD



Use the Materials panel to document the component materials of the mix design.

Figure 4.8 Portland Cement Concrete Mix Design Window - Materials Panel

96 Mix Designs

Table 4.9 Portland Cement Concrete Mix Design Window - Materials Panel – Fields


Material Code Yes Search Field. Uniquely identifies a material. Agency-defined. Must have an active status on the Material table.

For admixtures use the following codes:

711.02.01.01 – Concrete Mix, Admixture 1





--


Yes Auto-populated. Full description of the selected material.

--

Brand Name Yes Brand name of the component material. Only used for admixtures. Enter the brand name of the admixture

50


Yes Search Field. Uniquely identifies the producer/supplier.

For the water, use the concrete supplier as the source of water

--

Producer Supplier Description (no label)

Yes Auto-populated. Full name of the selected producer/supplier.

Sample ID (CDOT will not use)

Spcfc Gravity SSD Specific gravity. Used for the aggregates only 15

Bulk Spcfc Gravity (CDOT will not use)

SSD Weight (CDOT will not use)

Absorption Percent Absorption of the aggregate. Used for the aggregates only

15

Fineness Modulus (CDOT will not use)

Mass Quantity of the material within the Portland cement concrete mix design.

10

Unit Type Drop-down menu. Unit of measure for the quantity of material within the Portland cement concrete mix design. Required when Mass entered. See Code Table = WEIGHT

--

4.2.3.1 Required Fields MATERIAL CODE: Search Field – Uniquely identifies a material. Agency-defined. Must have an active status on the Material table. For admixture, use the following codes:

711.02.01.01 – Concrete Mix Admixture 1




711.02.01.04 - Concrete Mix, Admixture 4


MATERIAL DESCRIPTION: Auto Populated. Full description of the selected material. BRAND NAME: Brand name of the component material. Only used for admixtures. Enter the brand name of the admixture. PRODUCER SUPPLIER CODE: Search Field – Uniquely identifies the producer/supplier. For the water, use the concrete supplier as the source of water. PRODUCER SUPPLIER DESCRIPTION: Auto Populated. Full name of the selected producer/supplier. SPCFC GRAVITY: SSD Specific gravity. Used for the aggregates only. ABSORPTION PERCENT: Absorption of the aggregate. Used for the aggregates only. MASS: Quantity of the material within the Portland cement concrete mix design. UNIT TYPE: Dropdown – Unit of measure for the quantity of material within the Portland cement concrete mix design. Required when Mass entered. See Code Table = WEIGHT

Code Table = WEIGHT – Weight Unit of Measure

Code Description

G Gram

KG Kilogram

L Liter

LB Pound

MT Metric Ton

OZ Ounce

TON Ton(English)

4.2.3.2 CDOT will not use Fields SAMPLE ID: BULK SPCFC GRAVITY: SSD WEIGHT: FINENESS MODULUS:


98 Mix Designs

PROCESS STATUS This window is available almost system wide by selecting Process Status from the Services menu. The window consists of two tab pages: Regular and Scheduled. . CUSTOM RECORD



The Gradations folder tab will not be used at this time. Use the Gradations panel to document the gradation data of the mix design.

Figure 4.9 Portland Cement Concrete Mix Design Window - Gradations Panel


Table 4.10 Portland Cement Concrete Mix Design Window - Gradations Panel - Fields


Effective Date Date the gradation specification becomes effective. Defaults to current date when a new set of material gradation specifications are created or copied.

Status Identifies the current status of this sieve size record (for example, active or inactive). Defaults to active.

Sieve Size AASHTO and ASTM standard sieve sizes (that is, 1/2, No. 4, and so on). Required when Minimum or Maximum entered.

Sieve Value Percentage of bituminous mix material passing through the sieve screen.

Minimum Range Beginning value for the gradation specification limit.

Maximum Range Ending value for the gradation specification limit.


Minimum production tolerance value specification. Required when the Sieve Value field is populated.

Max Production Tolerance

Maximum production tolerance value specification. Required when the Sieve Value field is populated.

4.2.4.1 Drop-down Services Menu PROCESS STATUS This window is available almost system wide by selecting Process Status from the Services menu. The window consists of two tab pages: Regular and Scheduled. . CUSTOM RECORD


100 Mix Designs

4.3 Aggregate Mix Design Window

SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > MIX DESIGN > AGGREGATE MIX DESIGN

Windows Procedure: Use the Aggregate Mix Design window to add, modify, and approve aggregate mix designs. Once approved, an aggregate mix design may not be changed. SiteManager uses the test results on this window for comparison.

Security Procedure: CDOT user authority for this window should be available to Technical Support, IT System Administration, Region Materials Office, and the Central Lab Unit groups (Binder, Flexible Pavement and Chemical, Concrete and Physical Properties, and Soils).

Functional Procedure: Aggregate Mix Designs are used only 10-15 times per year.


Use the Description panel to add and modify description information for the aggregate mix design.

Figure 4.10 Aggregate Mix Design Window – Description Panel


Table 4.11 Aggregate Mix Design Window – Description Panel - Fields


Mix ID Yes Uniquely identifies an aggregate mix design. See naming convention below.

Material Code Yes Search Field. Uniquely identifies a material. Agency-defined. Pertains to the aggregate mix.

--

Material Code Full Name

Yes Auto-populated. Description of the material. --

Producer Supplier Code Yes Search Field. Uniquely identifies a source/location of the material. Agency-defined. Producer/Supplier Code must have an active status on the Producer Supplier table when entered.

--

Producer Supplier Name

Yes Auto-populated. Source name. --

Designer Name Yes Name of the designer responsible for the aggregate mix design. Must exist on the Testing Personnel table when entered.

45

Effective Date Yes Effective date for the aggregate mix. Defaults to current date when a new aggregate mix is entered.

mm/dd/yy

Termination Date Yes Date the aggregate mix is no longer available for use. Must be greater than effective date. CDOT does not have mandatory term. Set by approver.

mm/dd/yy

Approved Date Yes Date the Aggregate mix was entered. System-generated. Defaults to current date.

mm/dd/yy

Approved By User ID Yes User ID of the person approving the aggregate mix. System-generated.

Raw Soil Maximum Density

Yes Oven-dry density of the soil at optimum moisture content.

num

Units Yes Drop-down menu. Unit of measure for Raw Soil Maximum Density. Required when Raw Soil Maximum Density entered. See Code Table = DENSITY

--

Raw Soil Optimum Moisture %

Yes Moisture content corresponding to the peak of the curve produced by plotting the densities and corresponding moisture contents for the soil.

num

Raw Soil + Cement Percent

Yes Percentage of cement content in soil-cement mixture. Required when Soil Cement Maximum Density and Soil Cement Optimum Moisture % are entered.

num

Soil Cement Maximum Density

Yes Oven-dry mass of the soil cement mixture at optimum moisture content.

num

Units (Soil Cement Max Density Units)

Yes Drop-down menu. Unit of measure for Soil Cement Maximum Density. Required when Soil Cement Maximum Density entered. See Code Table = DENSITY

--

Soil Cement Optimum Yes Moisture content corresponding to the peak of the num

102 Mix Designs


Moisture % curve produced by plotting the densities and corresponding moisture contents for the soil-cement mixture.

Recommended Cement Content by Volume

Yes Recommended percentage of cement content in mixtures of cement with soil by volume of soil.

num

Recommended Cement Content by Weight

Yes Recommended percentage of cement content in mixtures of cement with soil by weight of soil.

num

Maximum Volume Change %

Yes Difference between the volume of the specimen at the time of molding and subsequent volume as a percent of original volume.

num


MIX ID: Uniquely identifies an aggregate mix design.

Digit 1 = Region # (e.g. 1, 2, 3) Digit 2-5 = Year mix design is issued (e.g. 2011) Digit 6 = code for mix design placement within section; T for Top layer I for Intermediate layers B for Bottom layer A for all layers V for varies G for aggregate mix designs Digit 7 thru 13 – Region choice as long as unique alpha/numeric is chosen. Possible uses: date (mmdd) and time (hr-military), first initial of person’s last name that initiated design. Digit 14 – Underscore _ Digit 15 – Blank for original mix or letter for revision. Note: Each Region should determine what their naming convention will be for digits 7-13 prior to training. Region 6 will be: name of supplier, followed by mix design # for the year. (i.e. APC01 = Asphalt Paving Company, 1st mix design of the year)

MATERIAL CODE: Search field – uniquely identifies a material. MATERIAL FULL NAME: Auto Populated. Description of the material. PRODUCER SUPPLIER CODE: Uniquely identifies a source/location for the material. PRODUCER SUPPLIER NAME: Auto Populated. Source name. DESIGNER NAME: Name of the designer responsible for the aggregate mix design. Must exist on the testing personnel table when entered. EFFECTIVE DATE: Effective date for the aggregate mix. Default to current when a new aggregate mix is entered. TERMINATION DATE: Date the aggregate mix is no longer available for use. Must be greater than effective date. CDOT does not have mandatory term. Set by approver.


APPROVED DATE: Date the aggregate mix was approved. System-generated. Defaults to current date. APPROVED BY USER ID: User ID of the person approving the aggregate mix. System-generated. RAW SOIL MAXIMUM DENSITY: Over-dry density of the soil at optimum moisture content. UNITS: Drop Down. Unit of measure for raw soil maximum density. Required when raw soil maximum density entered.

Code Table = DENSITY – Density Types

Code Description


PCF Pounds Per Cubic Foot

RAW SOIL OPTIMUM MOISTURE %: Moisture content corresponding to the peak of the curve produced by plotting the densities and corresponding moisture contents for the soil. RAW SOIL + CEMENT PERCENT: Percentage of cement content in soil-cement mixture. Required when soil cement maximum density and soil cement optimum moisture % are entered. SOIL CEMENT MAXIMUM DENSITY: Oven-dry mass of the soil cement mixture at optimum moisture content. RECOMMENDED CEMENT CONTENT BY VOLUME: Recommended percentage of cement content in mixture of cement with soil by volume of soil. RECOMMENDED CEMENT CONTENT BY WEIGHT: Recommended percentage of cement content in mixtures of cement with soil by weight of soil. MAXIMUM VOLUME CHANGE %: Difference between the volume of the specimen at the time of molding and subsequent volume as a percent of original volume.

4.3.1.2 Drop-down Services Menu REMARKS CDOT has no specific use for this field, although this is available for use as needed. Mixed case. PROCESS STATUS This window is available almost system wide by selecting Process Status from the Services menu. The window consists of two tab pages: Regular and Scheduled. APPROVE Used to approve the mix.

4.3.2 Compressive Strength Panel Use the Compressive Strength panel to add and modify compressive strength information for the aggregate mix design. Dependent on type of mix design.

104 Mix Designs

Cement Subgrade you would this panel. If FDR, with emulsion, would not use this panel.

Figure 4.11 Aggregate Mix Design Window - Compressive Strength Panel

Table 4.12 Aggregate Mix Design Window - Compressive Strength Panel – Fields


Age Optional Age of the specimen break.

Age Type Yes Drop-down menu. Specifies the type of age (for example, days, hours, minutes). See Code Table: See Code Table: TIME

--

Cement Percent Yes Percent of cement in mixture. Num

Compressive Strength Yes Compressive strength of the mixture. Num

Compressive Strength Units

Yes Drop-down menu. Unit of measure for compressive strength value (for example, PSI). Required when Compressive Strength entered.

4.3.2.1 Required Fields AGE: Age of the specimen break. AGE TYPE: Drop Down. Specifies the type of age (for example, days, hours, and minutes).


Code Table = TIME – Time Units of Measure

Code Description

DAY Day

HOUR Hour

MIN Minute

MON Month

SEC Second

YEAR Year

CEMENT PERCENT: Percent of cement in mixture. COMPRESSIVE STRENGTH: Compressive strength of the mixture. COMPRESSIVE STRENGTH UNITS: Unit of measure for compressive strength value (for example , PSI). Required when compressive strength entered.

Code Table = PRESSURE – Pressure Unit of Measure

Code Description


KPA kPa - Kilopascals

KSF Ksf – Thousand Pounds Per Square Foot

MPA MPa - Megapascals

NA Not Applicable (FOR PCC Mix Designs)

PA Pa - Pascals

PCF Pounds per Cubic Foot

PSF psf – Pounds Per Square Foot

PSI psi – Pounds Per Square Inch



Use the Materials panel to add and modify material information for the aggregate mix design.

106 Mix Designs

Figure 4.12 Aggregate Mix Design Window - Materials Panel

Table 4.13 Aggregate Mix Design Window - Materials Panel – Fields


Material Code Yes Search field. Uniquely identifies a material. Must have an active status on the Material table.

--

Material Name N/A Auto-populated. Identifies the brand of the material contained within the aggregate mix design.


Yes

Search field. Uniquely identifies a source/location of the material. P/S Code must have an active status on the Producer Supplier table when entered.


N/A Auto-populated. Identifies the name of the producer supplier

Blend Percent Yes Percentage of material contained within the aggregate mix design.

num

Sample ID ? Uniquely identifies a sample. Pertains to the sample used to approve the material contained within the aggregate mix design.


4.3.3.1 Required Fields MATERIAL CODE: Search field - Uniquely identifies a material. MATERIAL NAME: Auto populated – Identifies the brand of the material contained within the aggregate mix design. PRODUCER SUPPLIER CODE: Search field – Uniquely identifies a source/location of the material. PRODUCER SUPPLIER NAME: Auto populated – Identifies the name of the producer supplier. BLEND PERCENT: Percentage of material contained within the aggregate mix design. SAMPLE ID: Uniquely identifies a sample. Pertains to the sample used to approve the material contained within the aggregate mix design.



Use the Gradations panel to add and modify gradation information for the aggregate mix design.

Figure 4.13 Aggregate Mix Design Window – Gradations Panel

108 Mix Designs

Table 4.14 Aggregate Mix Design - Gradations Panel – Fields


Effective Date Yes Auto populated. Date the gradation specification becomes effective. Defaults to current date when a new set of material gradation specifications are created or copied.

--

Status Yes Auto populated. Identifies the current status of this sieve size record (for example, inactive). Defaults to active.

--

Sieve Size Yes Auto populated. AASHTO and ASTM standard sieve sizes (that is, 1/2, No. 4, and so on). Sieve size required when Minimum or Maximum entered.

--

Sieve Value Yes Percentage of bituminous mix material passing through the sieve screen.

num

Minimum Range Yes Auto populated. Beginning value for the gradation specification limit. Maintained in the Material Detail window.

--

Maximum Range Yes Auto Populated. Ending value for the gradation specification limit. Maintained in the Material Detail window.

--


Yes Minimum production tolerance value specification. Required when the Sieve Value field is populated.

num

Max Production Tolerance

Yes Maximum production tolerance value specification. Required when the Sieve Value field is populated.

num

4.3.4.1 Required Fields EFFECTIVE DATE: Auto populated. Date the gradation specification becomes effective. Defaults to current date when a new set of material gradation specifications are created or copied. STATUS: Auto populated. Identifies the current status of this sieve size record (for example, inactive). Defaults to active. SIEVE SIZE: Auto populated. AASHTO and ASTM standard sieve sizes (that is, 1/2, No. 4, and so on). Sieve size required when Minimum or Maximum entered. SIEVE VALUE: Percentage of bituminous mix material passing through the sieve screen. MINIMUM RANGE: Auto populated. Beginning value for the gradation specification limit. Maintained in the Material Detail window. MAXIMUM RANGE: Auto Populated. Ending value for the gradation specification limit. Maintained in the Material Detail window. MIN PRODUCTION TOLERANCE: Minimum production tolerance value specification. Required when the Sieve Value field is populated.


MAX PRODUCTION TOLERANCE: Maximum production tolerance value specification. Required when the Sieve Value field is populated.


4.3.5 Reports Aggregate Mix Design Report is being developed by IT.

4.4 Aggregate Blend Data Window

SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > MIX DESIGN > AGGREGATE BLEND

CDOT will not use this Window.

Windows Procedure: The Aggregate Blend window allows a user to create aggregate blends based on the current aggregate sieve data. This data can be used to develop new mix designs. The user enters the sample ID(s) and the percentage of each one. Using this information, SiteManager retrieves the sieve data. The blend percentage is calculated for each sieve. This is calculated by multiplying the percentage of the sample by the passing percentage of each sieve. The overall blend percentage is calculated by summing the newly calculated passing percent for each sieve. The maximum number of sieves per sample is 25. The blend data is not stored in SiteManager. However, the user can export the blend result data to a text file in a tab-delimited format. This information can be used by mix designer software to develop or graph new mix designs. Each record in the file would contain the sieve size and the percentage passing of the sieve.

4.4.1 Aggregate Blend Data Panel

110 Mix Designs

Figure 4.14 Aggregate Blend Data Window

Table 4.15 Aggregate Blend Data Window - Fields


Sample ID Free-form field. Uniquely identifies the sample.

Material Code The unique identifier of the material.

Material Full Name The full name or description of the material

Percent Free-form field. The percentage of the sample to be using in determining the blend result.

Blend Blend of the sample.

4.4.1.1 Drop-down Services Menu PROCESS STATUS This window is available almost system wide by selecting Process Status from the Services menu. The window consists of two tab pages: Regular and Scheduled. EXPORT Used to export to a text file.


4.5 Contract Mix Design Adjustments Window

SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > MIX DESIGN > CONTRACT MIX DESIGN ADJUSTMENTS

CDOT will not use this Window

Windows Procedure: Use the Contract Mix Design Adjustments window to record minor adjustments to bituminous concrete mix designs.

4.5.1 Contract Mix Design Adjustments Panel

Figure 4.15 Contract Mix Design Adjustments Window

112 Mix Designs

Table 4.16 Contract Mix Design Adjustments Window - Fields


Contract ID Uniquely identifies a contract.

Vendor Full Name Full name of the primary contractor.

Fed State Project Number

Federal state/province project number that identifies the contract.

Level2 Office Number Contract level 2 office assignment.



Effective Date Date the adjustment was effective. Effective Date must be unique for Mix ID or Contract ID. Defaults to current date when a new adjustment is made.

Asphalt Content Percentage of asphalt content.

Maximum Density Maximum density of the mix.

4.6 Contract Mixes Window

SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > MIX DESIGN > CONTRACT MIXES

Windows Procedure: Use the Contract Mixes window to associate an approved design mix with a contract. Selecting a mix ID will list all contracts associated with it, if any. Associate a contract to the mix ID to add it to the list. A contract cannot be deleted from the list.

Security Procedure: CDOT user authority for this window should be available to Technical Support, IT System Administration, and Region Materials Office.

4.6.1 Contract Mixes Panel


Figure 4.16 Contract Mixes Window

Table 4.17 Contract Mixes Window - Fields


Mix ID Uniquely identifies a mix design.

Contract ID Uniquely identifies the contract to which the mix design is associated.

Vendor Full Name Full name of the primary contractor for the associated contract.

Fed State Project Number

Federal state/province project number that identifies the contract.

Level2 Office Number (CDOT will not use) Contract level 2 office assignment.




114 Mix Designs

4.7 Accessing SiteManager Generic Mix Design Reports

4.7.1 Sample Using Mix Design Window

SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > MIX DESIGN REPORTS > SAMPLE USING MIX DESIGN

Use the Sample Using Mix Design report to view a list of samples that were identified on the Maintain Sample Information window as being sampled for the selected mix design.

Figure 4.17 Accessing SiteManager Generic Mix Design Reports Window

Table 4.18 Accessing SiteManager Generic Mix Design Reports Window - Fields


Sample ID Uniquely identifies a sample.

Sample Date Date the sample was taken.

Sample Type Type of sample taken.

Status Status of the sample.

Authorized Date Date the sample was authorized.

Contract ID Uniquely identifies the contract associated to the sample associated to the mix design.

4.7.2 Mix Design for Contract Window

SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > MIX DESIGN REPORTS > MIX DESIGN FOR CONTRACT

Use the Mix Design For Contract window to generate a report that displays mix designs associated to a contract and design type.


Figure 4.18 Report Criteria Window

Figure 4.19 Mix Design for Contract Window

Table 4.19 Mix Design for Contract Window - Fields


Contract ID Uniquely identifies the contract to which the mix design is associated.

Description Pertains to the associated contract.

Prime Contractor Pertains to the associated contract.

Design Type Code Code for the mix design type.

Description Full name of the mix design type (for example, Superpave).

Mix ID Uniquely identifies a mix design.

Material Code Uniquely identifies a material. Agency-defined.

Material Full Name Full name of the selected material.

Producer/Supplier Code Uniquely identifies a source/location of the material. Agency-defined. Producer/Supplier Code must have an active status on the Producer Supplier table when entered.

Producer/Supplier Name

Full name of the selected Producer Supplier.

116 Mix Designs

4.7.3 Aggregate Mix Design List Window

SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > MIX DESIGN REPORTS > AGGREGATE MIX DESIGN LIST

Use the Aggregate Mix Design List window to display aggregate mix designs for selected effective dates, approved dates, material codes, and producer/supplier codes.

Figure 4.20 Select Aggregate Mix Design Report Window

Figure 4.21 Aggregate Mix Design List Window


Table 4.20 Aggregate Mix Design List Window - Fields


Mix ID Uniquely identifies the aggregate mix design.

Material Code Uniquely identifies a material. Agency-defined. Pertains to the aggregate mix.

Material Full Name Description of the material.

Producer Supplier Code Uniquely identifies a source/location of the material. Agency-defined. Must have an active status on the Producer Supplier table when entered.


Source name.

Designer Name Name of the designer responsible for the aggregate mix design. Must exist on the Testing Personnel table, when entered.

Effective Date Effective date for the aggregate mix. Defaults to current date when a new aggregate mix is entered.

Termination Date Date the aggregate mix is no longer available for use. Must be greater than Effective Date.

Approved Date Identifies when the aggregate mix was approved. System-generated. Defaults to current date when aggregate mix is approved.

Approved By User ID User ID of the person approving the aggregate mix. System-generated.

4.7.4 View Saved Reports (PSR) Window

SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > APPROVED LISTS REPORTS > VIEW SAVED REPORTS

Use the View Saved Reports (PSR) window to retrieve and view SiteManager reports that have been previously generated and saved.

CDOT will not use this functionality.

118 Mix Designs

Figure 4.22 View Saved Reports (PSR) Window

Table 4.21 View Saved Reports (PSR) - Fields


< Varies > Depends on report. See actual report window for definitions.

4.8 Pavement Structural Design Data Window

SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > MIX DESIGN > PAVEMENT STRUCTURAL DESIGN DATA

Window Procedure: Use the Pavement Structural Design Data window to add, update or view as-built/as-constructed pavement structural design data for a contract and project, replaces the current RSAR Form.

Security Procedure: CDOT update authority for this window should be limited to these SiteManager Materials groups: Technical Support, IT System Administration, Regional Materials Office, CDOT and Consultant Project Engineers, and Pavement Management. CDOT inquiry authority for this window should be available to all SiteManager Material users except the Central Lab Unit groups (Binder, Flexible Pavement and Chemical; Concrete/Physical Properties; and Soils).

Functional Procedure:


CDOT will utilize this window to record As-Constructed pavement structural data. The window documents the roadway's engineering properties and where the roadway is located. This data is used by CDOT Pavement Management Unit and Region Pavement Managers. Note that Regional Materials Office has a Pavement Manager that that would have updates rights. Enlist their expertise to help fill out this window. The Regional Pavement Manager will rely heavily on this data. More than one window record may be attached to a Contract to document changes in pavement type, design, or segmenting by clicking on the New record on the menu. The window records have to be unique. SiteManager Materials compares two fields of the window data. The two fields are Project Type and Direction. The combination of these two fields must not be the same. Example:

Project Type Direction

Roadway 1-Asphalt Both

Roadway 1-Asphalt Increasing Milepost (Primary)

These are both valid entries, but one cannot have Roadway 1-Asphalt Both twice on the same Contract. To add an additional record which has the same Direction select the next available Project Type from the table. Example: Roadway 2-Asphalt. This window primarily documents interstates and state highways. All interstate and state highways have a 4 character Route ID. Refer to Table 4.23 Auxiliary Route Information at the end of this Section for Route IDs. If other roadways are populated in this window, their description is to be documented in the remarks.


Use the Description Panel to add the pavement structre data for the Project under the Contract. Multiple roadway may be added using the New record.

120 Mix Designs

Figure 4.23 Pavement Structural Design Data Window


Table 4.22 Pavement Structural Design Data Window - Fields


Region Yes Free-form. Uniquely identifies area of the design data for the project. CDOT Region (1,2,3,4,5,6,HQ for statewide). (2 characters)

2

Project Type Yes Drop-down. Type of project. CDOT Base Codes. (Asphalt, Asphalt Over Concrete, Concrete, and Concrete Over Asphalt). See Code Table = PRJTYP.

--

Subaccount # Yes Free-form, Numerical. CDOT Project Code. 10

Funding Category Drop-down. CDOT Treatment Category (for example, Preventative Maintenance, Minor Overlay, Major Overlay, and so on). See Code Table = FUNDCAT

--

Activity Date Yes Date. Date opened to traffic for that segment of roadway.

DD/MM/YY

Route Free-form. Route number of project construction. Use CDOT 4 digit code for highways on CDOT system. Other non-CDOT roadways use free form. (cell shows only limited number of characters)

20

Top Surface Layer Yes Drop-down. Top surface treatment. (for example, Bituminous surface treatment, Mixed bituminous, and so on). See Code Table = SURFACE.

--

Surface Thickness Yes Free-form. Total thickness of all new surface treatments, report to nearest 0.25 inches.

18 alpha/num

Second Surface Layer Drop-down. Second surface treatment. (for example, Bituminous surface treatment, Mixed bituminous, and so on). See Code Table = SURFACE.

--

Base Thickness Free-form. Total Thickness of all new base material, report to nearest 0.25 inch.

18 alpha/num

Third Surface Layer Drop-down. Third surface treatment. (for example, Bituminous surface treatment, Mixed bituminous, and so on). See Code Table = SURFACE.

--

Subbase Thickness Free-form. Total Thickness of all new subbase material, report to nearest 0.25 inch.

18 alpha/num

Pavement Base

Drop-down. Pavement base layer.

(for example, Aggregate Base Coarse, Lime Treated Base, and so on). See Code Table = PAVBASE.

--

Effective Thickness

Free-form. Effective thickness. Total pavement thickness: surface, base, and subbase thicknesses of new and existing layers, report to nearest 0.25 inch.

18 alpha/num

122 Mix Designs


Pavement Subbase

Drop-down. Pavement Subbase is the layer below the Pavement Base. (for example, Roadbed soil, Granular, Cement stabilized, and so on). See Code Table = PAVBASE.

--

Subgrade R-Value Free-form. R-value of the subgrade. 18 alpha/num

Pavement Shoulder

Drop Down. Pavement shoulder of the surface. (for example, Asphalt, Curbed, and so on). Code Table = PAVSHOLD.

--

Structural Capacity

Free-form. Structural capacity value. Total Structural Number (SN) of work performed (surfacing, base, subbase, and stabilized embankment) excluding existing pavement structure. For concrete surfacing will be total depth of work performed excluding existing pavement structure.

18 alpha/num

Drainage Condition

Drop-down. Drainage condition of the surface. (for example, Surface Drainage to Ditches, Edge drain, and so on). See Code Table = DRAINAGE.

--

Composite K-Value Free-form. Composite K-value 18 alpha/num

Beginning Reference Point

Yes

Free-form. Beginning Reference Point value.

(for example MP 78.400)

18 alpha/num

Ending Reference Point

Yes

Free-form. Ending Reference Point value.

(for example MP 80.000)

18 alpha/num

Milled Depth

Free-form. Milled Depth value, report to nearest 0.25 inch.

18

Number of Lanes

Yes

Free-form, Numerical. Number of lanes on highway for Direction indicated.

10

Direction

Yes

Drop-down. Direction of surface treatment (for example, Both, Primary Only, and so on). See Code Table = DIRECT.

--

Lanes Affected: Inside Shoulder

Check Box. Indicates surface treatment completed of new construction on the inside shoulder of lanes affected. Inside shoulder is on the left side for ramps.

Lanes Affected: Lane 1 Check Box. Indicates surface treatment completed on Lane 1 of lanes affected. On multilane highways, Lane 1 is the first lane counting out from the median.

Lanes Affected: Lane 2 Check Box. Indicates surface treatment completed on Lane 2 of lanes affected. Lane 2 is the second lane counting out from the median.

Lanes Affected: Lane 3 Check Box. Indicates surface treatment completed on Lane 3 of lanes affected. Lane



3 is the third lane counting out from the median.

Lanes Affected: Lane 4 Check Box. Indicates surface treatment completed on Lane 4 of lanes affected. Lane 4 is the fourth lane counting out from the median.

Lanes Affected: Lane 5 Check Box. Indicates surface treatment completed on Lane 5 of lanes affected.






Lanes Affected: Outside Shoulder

Check Box. Indicates surface treatment completed of new construction on the outside shoulder of lanes affected. Outside shoulder is on the right side for ramps.


Region: Formatting of this box is only two characters, may be alpha/numerical combination. Enter the region's number. HQ denotes statewide.

Example: 3 or 03 for Region 3

Project Type: Type of Project.

124 Mix Designs

Code Table = PRJTYP – Project Type

Code Description

PT01 Roadway 1-Asphalt

PT02 Roadway 1-Asphalt Over Concrete

PT03 Roadway 1-Concrete

PT04 Roadway 1-Concrete Over Asphalt













PT17 N/A

Subaccount #: Formatting is maximum of 10 digits, numerical only. This is the CDOT Project Code.

Example: 12345

Funding Category: CDOT Treatment Category that relates to Pavement Management System coding.

Code Table = FUNDCAT – Funding Categories – Pavement

Code Description

FC01 Preventative Maintenance, <2.0 inches

FC02 Minor Rehab, >= 2.0 to <4.0 inches

FC03 Major Rehab, >= 4.0 to <6.0 inches

FC04 Reconstruct, >= 6.0 inches

FC05 N/A

Activity Date: Date opened to traffic for which the particular roadway segment data is entered. Project Type and Direction must be a unique combination of these two entries for each roadway segment.

Example: 03/06/10


Route: CDOT Route Designation. See Auxiliary Route Information at the end of this section. CDOT uses a four digit alpha/numerical code for each CDOT interstate, US highway, and state highway. A county roadway may be specified by the county route number and for cities the street name. Formatting is a maximum of 20 characters and may be alpha/numerical combination.

Example: 024A is US Highway 24 from I 70-A and SH 6-E north of Minturn southeast via Tennessee Pass, Leadville, Buena Vista, Wilkerson Pass To I 25-A in Colorado Springs at Cimarron St.

Obtained from Department of Transportation Development DTD) website. See route info at the end of this document. http://apps.coloradodot.info/dataaccess/Highways/index.cfm?fuseaction=routes

Top Surface Layer: Top Surface Treatment. See Code Table, SURFACE.

Code Table = SURFACE – Surface Layers

Code Description

SL01 Asphalt Crack Seal

SL02 Sand Seal

SL03 Blade Batch

SL04 Micro Seal

SL05 Chip Seal

SL06 Mill and Fill

SL07 Hot In-Place Recycle

SL08 Cold In Place Recycle

SL09 Heater/Scarify/Overlay

SL10 Stone Mastic Asphalt

SL11 Thin Overlay, < 2 inches

SL12 Medium Overlay, ≥ 2 to < 4 inches

SL13 Major Overlay, ≥ 4 inches

SL14 Thin Whitetopping, < 8 inches

SL15 Whitetopping, ≥ 8 inches

SL16 Asphalt Reconstruction

SL17 Concrete Crack Seal

SL18 Concrete Slab Replacement

SL19 Asphalt Overlay of Concrete

SL20 Diamond Grinding

SL21 Concrete Reconstruction

SL22 Concrete Rubblization

SL23 Full Depth Reclamation

SL24 N/A

http://apps.coloradodot.info/dataaccess/Highways/index.cfm?fuseaction=routes

126 Mix Designs

Surface Thickness: Formatting is a maximum of 18 characters and may be alpha/numerical combination. Surface thickness should always be entered in units of inches, accuracy of ¼ inch. Entering of units is to be avoided.

Example: 18 signifying 18 inches or 18"

Top Surface Layer: Top Surface Treatment. See Code Table, SURFACE.

Second Surface Layer: Second Surface Treatment. See Code Table, SURFACE.

Base Thickness: Same as Surface Thickness.

Third Surface Layer: Third surface treatment. See Code Table, SURFACE.

Subbase Thickness: Same as Surface Thickness.

Pavement Base: Pavement base layer. See Code Table, PAVBASE.

Code Table = PAVBASE – Pavement Base

Code Description

PB01 Aggregate Base Course (Class 1)







PB08 Aggregate Base Course (Special)

PB09 Recycled Asphalt Pavement

PB10 Recycled Concrete Pavement

PB11 Lime Treated Subgrade

PB12 Cement Treated Base

PB13 Lean Concrete Base

PB14 Geosynthetic Material Reinforcement

PB15 Filter Material Layer

PB16 Permeable Asphalt Treated Base

PB17 Permeable Aggregate Base Course

PB18 Emulsified Asphalt Treated Base

PB19 Plant Mix Bituminous Base

PB20 Rubblized Concrete Pavement

PB21 N/A


Effective Thickness: Formatting is a maximum of 18 characters and may be alpha/numerical combination. Effective thickness should always be entered in units of inches. Effective thickness is the total pavement thickness including new pavement, existing pavement, base, subbase, and stabilized soil or stabilized embankment. Entering of units is to be avoided.

Example: 26 signifying 26 inches or 26"

Pavement Subbase: Pavement base Layer. See Code Table PAVBASE above.

Subgrade R-Value: R-value of the subgrade.

Example: 40 signifies the R-Value of 40

Pavement Shoulder: Drop Down. Pavement shoulder of the surface.

Code Table = PAVSHOLD – Pavement Shoulder

Code Description

PS01 Asphalt

PS02 Concrete

PS03 Curbed

PS04 Recycled Asphalt

PS05 No Shoulder

PS06 No Shoulder Activity

PS07 Earth

PS08 Aggregate/Stone

PS09 N/A

Structural Capacity: Structural capacity value. Total Structural Number (SN) of work performed (surfacing, base, subbase, and stabilized embankment) excluding existing pavement structure. For concrete surfacing will be total depth of work performed excluding existing pavement structure. Enter a number only.

Example: 2.36 is the SN and 11.5 is for the depth of the concrete in inches.

Drainage Condition: Drainage condition of the surface.

128 Mix Designs

Code Table = DRAINAGE – Drainage Condition

Code Description

DC01 Surface Drainage to Ditches

DC02 Surface Drainage to Storm System

DC03 Below Roadway Surface Collection System

DC04 Edgedrain Water Collection System

DC05 Correct Frost Heave Problems

DC06 Correct Collapsible Soils

DC07 N/A

Composite K-Value: Formatting is a maximum of 18 characters and may be alpha/numerical combination. Enter a number only.

Example: 125

Beg Reference Point: It is strongly recommended by Regional Pavement Managers to enter the milepost. If one does not know the milepost, contact your Region Materials Engineer for which the beginning of the surfacing starts. Note, the beginning of the surfacing may not coincide with the beginning of the project. Therefore, enter the beginning of each surfacing the particular data goes with.

Example: MP 82.345

End Reference Point: Same as Beginning Reference Point.

Milled Depth: Milled depth should always be entered in units of inches accuracy of ¼ inch. Enter a number only.

Example: 2.25 signifying 2.25 inches or 2¼"

Number of Lanes: Enter the Number of lanes on highway for Direction indicated.

Example: 4

Direction: Direction of the surface treatment (for example, Both, Primary Only, etc.).


Code Table = DIRECT – Direction of Lane

Code Description

DL01 Both

DL02 Increasing Milepost (Primary)

DL03 Decreasing Milepost (Secondary)

DL04 Frontage Road (Primary Side)

DL05 Frontage Road (Secondary Side)

DL06 Ramp 1 (Primary to Primary)

DL07 Ramp 2 (Primary to Primary)

DL08 Ramp 1 (Secondary to Secondary)

DL09 Ramp 2 (Secondary to Secondary)

DL10 Ramp 1 (Primary to Secondary)

DL11 Ramp 2 (Primary to Secondary)

DL12 Ramp 1 (Secondary to Primary)

DL13 Ramp 2 (Secondary to Primary)

DL14 Ramp 1 (Increasing off)

DL15 Ramp 2 (Increasing off)

DL16 Ramp 1 (Increasing on)

DL17 Ramp 2 (Increasing on)

DL18 Ramp 1 (Decreasing off)

DL19 Ramp 2 (Decreasing off)

DL20 Ramp 1 (Decreasing on)

DL21 Ramp 2 (Decreasing on)

DL22 N/A

How to handle intersections:

Review Functional Procedure at the beginning of this section of Pavement Structural Design Data Window. To have unique roadway sections the combination of two fields must not be the same. The two fields are Project Type and Direction. Project Type is a dropdown menu that has four pavement descriptions repeated in four roadways designated as 1, 2, 3, and 4. Between Project Type and Direction there should be a sufficient number of combinations for an intersection. The Beginning and Ending Reference Points can also be used to distinguish the segments.

Example: One highway is in a north-south direction and the other highway is an east-west direction. Both are of asphalt pavement and are asphalt in both directions. The first highway is designated as Project Type = Roadway 1–Asphalt with Direction = Both. The second highway is designated as Project Type = Roadway 2–Asphalt with Direction = Both. Both of these roadway segments are unique and the data can be entered for each segment.

Lanes Affected: Inside Shoulder: Indicates inside shoulder of Multi-lane highways, area next to median. Inside shoulder is on the left side of ramps.

130 Mix Designs

Lanes Affected: Lane Numbers: On multilane highways, Lane 1 is the first lane counting out from the median. Lane 2 is the second lane counting out from median.

Lanes Affected Outside Shoulder: Indicates outside shoulder of lanes affected. Outside shoulder is on the right side of ramps.


Choose Keys Choose Keys – Use to attach the Pavement Structural Design Data to the Project under the Contract. REMARKS Use for Project Description (255 characters for use in comment remarks box). Example of remarks may be; a geosynthetic was placed between asphalt layers 2” from top, soft spots were removed and replaced with base course material throughout the increasing milepost direction in the right lane, or side streets were paved to their curb end returns or to state right of way. PROCESS STATUS This window is available almost system wide by selecting Process Status from the Services menu. The window consists of two tab pages: Regular and Scheduled. See above explanation.

4.8.1.3 Reference Table of Route Information Auxiliary Route Information

Obtained from Department of Transportation Development (DTD) website. http://apps.coloradodot.info/dataaccess/Highways/index.cfm?fuseaction=routes Auxiliary Route Information was populated as of 3/1/2012.

http://apps.coloradodot.info/dataaccess/Highways/index.cfm?fuseaction=routes


Table 4.23 Auxiliary Route Information

Route Ref

Point End Ref

Point Route Description

001A 0.000 10.053 From U.S. 287C North of (Willox Dr) in Fort Collins at the South Side of Terry Lake To the Frontage Road East of the I-25 Interchange at MilePost 278 in Wellington

002A 0.000 9.842 From U.S. 285D (Hampden Ave) and (Colorado Blvd) in Denver North To A Direct Connection onto U.S. 06H North of 52nd St in Commerce City

002B 10.860 13.345 From a Direct Connection Fly Over at Jct U.S.6H at (Vasquez Blvd) in Commerce City To MilePost 13 - Begin SH 002C at (Quebec St) End SH 002B

002C 13.345 19.944 From SH 002B at Quebec St in Commerce City northeast To the I-76 Interchange between Commerce City and Brighton

003A 0.000 2.444 From U.S. 160A at (Dominguez Dr) in south Durango North To U.S. 160A in Durango Begin (Santa Rita Dr)

005A 0.000 14.894 From SH 103A at Echo Lake south Visitor Center To the Summit of Mount Evans in the Arapaho National Forest

006A 11.080 26.080 From the East Side Ramps at I 70A South of Mack North and Southeast via Loma and Fruita To I 70A and SH 70B Northwest of Grand Junction at Milepost 26

006B 30.123 34.535 From SH 70B East Bound Secondary Direct Connection in Grand Junction East along North Ave To SH 70B West of 30th

006C 37.161 46.058 From SH 70B North of Milepost 12 west of Clifton North and East To I 70A at Milepost 44 Northeast of Palisade

006D 91.999 110.806 From SH 13A in Rifle at Milepost 92 East To the South Side Ramps of I 70A at Milepost 109 East of New Castle

006E 141.818 174.541 From I 70A East of Milepost 139 in Gypsum east via Eagle, Wolcott, and Edwards To I 70A and SH 24A north of Minturn

006F 208.659 229.896 From I 70A and SH 9D in Silverthorne east via Dillon and Loveland Pass To I 70A East of the Eisenhower Tunnel at Milepost 217

006G 257.079 284.876 From I 70-A Floyd Hill East via Clear Creek Canyon, Golden, and along West 6th Ave To (Seminole St) North and (Osage St) South

006H 290.980 296.320 From I 70-A at Steele St in Denver northeast To the South Side Ramps at I 76-A North of Commerce City South of Milepost 276

006I 343.519 346.697 From a Direct Connection with I 76A west of Milepost 64 Near Wiggins Northeast To I 76A Northeast of Wiggins at Milepost 67

006J 371.690 467.284 From I 76A and SH 34E Northeast of Brush northeast via Merino and Atwood To Sterling and east via Haxtun and Holyoke to the Nebraska State Line

006K 0.000 0.338 From the end of Service Road at (Traver Trail) and (Devereus Rd) Southeast To SH 82A at (Laurel St) in Glenwood Springs

006L 88.895 91.240 From South Side Ramps On and Off at I 70-A Milepost 87 west of Rifle east To Railroad Ave and US 6 in Rifle

006M 62.305 88.895 From Jct I-70A Frontage Rd STR (G-04-AH) Northeast of DeBeque North To CR (215) in Parachute

006Z 0.000 0.604 From SH 6J and SH 138A in Sterling southwest along 4th St To SH 6J

132 Mix Designs

Route Ref

Point End Ref


at South 3rd St and Park St

007A 0.000 33.080 From SH 36B in Estes Park at Stanley Ave south and east To SH 36B in Lyons North of Milepost 33

007B 49.506 50.639 From SH 93A at Braoadway in Boulder east via Canyon Blvd To SH 36B (28th St) in Boulder

007C 52.290 60.683 From SH 36B (28th St) and (Arapahoe Ave) in Boulder east To SH 287C northwest of Lafayette

007D 61.877 77.052 From SH 287-C in Lafayette East via Brighten To U.S. 085C in Brighton

007E 0.000 1.592 From SH 7A west of Milpost 15 at Allenspark Bus Rt southeast To SH 7-A east of Ferncliff

008A 0.000 8.683 From SH 285-D south of Morrison north To Morrison and east to SH 121-A in Lakewood

009A 0.000 46.980 From SH 50-A Northeast of Parkdale northwest To SH 24-A at Hartsel

009B 47.582 63.732 From SH 24-A west of Hartsel northwest To SH 285-D south of Fairplay

009C 64.673 97.230 From SH 285-D in Fairplay north via Hoosier Pass and Breckenridge To I 70-A at Frisco

009D 101.562 138.920 From I 70A and SH 6F in Silverthorne Northwest To SH 40A at (6th St) in Kremmling

010A 0.000 71.968 From I 25-A and SH 160-B east of Walsenburg northeast To SH 50-B in La Junta

011A 0.000 1.350 From U.S. 138-A west of Julesburg north To Nebraska State Line

012A 0.000 70.833 From U.S. 160-A southwest of Walsenburg south via La Veta, Cuchara, and Monument Park and east via Weston To I 25-A in Trinidad

013A 0.000 88.635 From Airport Road in Rifle South of I-70 North To RailRoad Ave then West To SH40A West of Craig

013B 89.580 128.070 From U.S. 40A at (4rt St) and (Yampa St) in Craig North To the Wyoming State Line

014A 0.000 32.968 From U.S. 40-A at Jackson/Grand County Line (Muddy Pass) northeast To SH 125-A southwest of Walden

014B 34.090 121.713 From SH 125-A in Walden southeast via Cameron Pass and east via Poudre Canyon To U.S. 287-C at Teds Place

014C 134.770 236.924 From U.S. 287-C in Fort Collins East via Ault and Raymer To SH 6-5 in Sterling

015A 0.000 12.374 From U.S. 160-A and U.S. 285-B in Monte Vista south To (CR 12S) at the Rio Grande/Conejos County Line

015B 20.398 30.915 From County Roads west of Capulin east via Capulin To U.S. 285-A north of La Jara

016A 0.000 3.118 From the Frontage Road West of I 25-A in Fountain Southeast To (Old Powers Blvd) SH 021A North of Fountain

017A 0.000 39.052 From the New Mexico State Line northeast via Cumbres Pass To U.S. 285A south of Antonit

017B 69.024 118.864 From U.S. 160 A east of Alamosa North To U.S. 285 B Northwest of


Route Ref

Point End Ref


Mineral Hot Springs

021A 131.813 139.582 From SH 16 at Mesa Ridge Parkway South of Colorado Springs North along ( Powers Blvd ) to Jct US 24 at Fountain Blvd in Colorado Springs

021B 141.738 154.112 From U.S. 024G at Platte Ave in Colorado Springs North along ( Powers Blvd ) to Jct SH 083A at the north end of Colorado Springs City Limits

022A 0.000 2.476 From Sable Blvd (Old SH-002D) South of Brighton West To Brighton Road and 126th at Henderson

023A 0.000 17.507 From U.S. 385-D north of Holyoke northeast To the Nebraska State Line at (CO Rd 63.2)

024A 143.400 303.840 From I 70-A and U.S. 6-E north of Minturn southeast via Tennessee Pass, Leadville, Buena Vista, Wilkerson Pass To I 25-A in Colorado Springs at Cimarron St

024B 419.950 437.200 From I 70-A CO Rd 12 on Frontage Road west of Siebert east To SH 57-A and U.S. 24C in Stratton

024C 437.200 454.828 From SH 57-A east of Stratton east End U.S. 24B To U.S. 385-C in Burlington

024D 455.882 457.290 From U.S. 385C at 8th Street in Burlington East and Northeast to the I-70 Frontage Road

024E 0.000 4.323 From Manitou Springs Business Route - U.S. 24-A west of Manitou Spgs east To U.S. 24-A at 31st St in Colorado Springs

024F 0.000 0.548 From Limon Spur Connection - From U.S. 24-A and U.S. 40-G west of Limon north To North Side Ramps at I 70-A northwest of Limon

024G 303.412 380.464 From I 25-A in Colorado Springs northeast To I 70-A and U.S. 40 H east of Limon

025A 0.000 298.879 From the New Mexico State Line north via Trinidad, Pueblo, Colorado Springs, and Denver To the Wyoming State Line

025B 0.000 1.948 From Aguilar Bus Spur - I 25-A at CO Rd 60 east To Main St and Fir St on the Aguilar Business Spur

025C 0.000 4.039 From Walsenburg Business Route - From I 25-A south of Walsenburg north To I 25-A north of Walsenburg

026B 11.170 14.140 From SH 95A Denver/Jefferson County Line at (Sheridan Blvd) East along Alameda Ave To the East of the I-25 Interchange at Santa Fe Drive and Alameda Ave

030A 0.000 20.416 From I 25-A and U.S. 285-D in Denver east via Hampden Ave , north via Havana St, east via 6th Ave, and aouth via Piccadily Rd To Quincy Ave RD E AND W (QUINCY AVE) RD S (GUN CLUB RD) END SH 30

034A 0.000 149.633 From U.S. 40-A west of Granby north via Grand Lake and east via Trail Ridge Rd, Estes Park, Loveland , and Greeley To a Fly Over Direct Connection with U.S. 034A/I 76A Northeast of Wiggins

034B 158.485 259.529 From East of I-76 at county road 14 west of Fort Morgan east via Fort Morgan, Brush, Akron, and Wray To Nebraska State Line

034C 0.000 1.690 From U.S. 34-A west of Estes Park east at Elkhorn Ave Estes Park Business Route To U.S. 34-A and U.S. 36-B east of Estes Park

134 Mix Designs

Route Ref

Point End Ref


034D 0.000 14.711 From Direct Connection Flyover from east bound U.S. 34-A west of Greeley east and south To U.S. 34-A Southeast of Greeley

034E 0.000 0.932 Brush Spur Connection - From U.S. 34-B east of Brush northeast to I 70-A and U.S. 6-J northeast of Brush

034Z 0.000 1.301 From U.S. 34-D (10th Av) and 10th St north via 10th Ave and west at Greeley Business Route To U.S. 34-D

035A 8.435 9.704 From the South Side Ramps at I-70 North and West to East 53rd Place

036A 0.000 6.982 From U.S. 34A at Deer Ridge in Rocky Mtn Ntl Park East To U.S. 34C in Estes Park west of Bighorn Dr

036B 0.000 57.252 From U.S. 34-A and U.S. 34-C in Estes Park Southeast via Lyons and Boulder To I 25-A North of Denver

036C 76.394 89.210 From the South Side Ramps at I-70A near Milepost 292 To SH 79B in Bennett Begin U.S. 36D

036D 89.210 224.718 From SH 79B in Bennett at (Adams St) east via Dyers, Last Chance, and Idalia To the Kansas State Line

036E 0.000 0.357 From SH 093A ( Braodway ) East along Baseline Road (Boulder Spur Connection) To the east side Ramps at U.S. 036A in Boulder

036Z 0.000 0.299 From U.S. 36-B in Lyons west along Main St To U.S. 36-B

039A 0.000 7.571 From U.S. 6 I and SH 52-A east of Wiggins north To SH 144 A in Goodrich

040A 0.000 258.258 From Utah State Line east via Craig, Steamboat Springs, Granby, and Winter Park To I 70-A at Empire Jct

040B 269.441 276.920 From U.S. 6G Floyd Hill east To SH 74A at El Rancho

040C 279.208 312.142 From I 70-A Genesee Interchange east via Mt. vernon Canyon and through Denver via Colfax Av To I 70-A east Aurora

040D 338.570 340.381 From U.S. 036D in Byers Southeast along I-70 To South Calhoun Road (County Road 185)

040E 346.290 352.245 I-70 Frontage Road at (Mp-324) Southeast through Deer Trail To (County Road 42) the Wall Road Underpass near the Arapahoe-Elbert County Line

040F 360.201 362.999 From I-70 Frontage Road (Mp-338) Separates from Mainline South through Agate To State Highway 70 at CR (166) in Agate

040G 380.689 382.184 From I 70-A Frontage Road west of Limon east (I-70 Milepost 357.5) To U.S. 24-A and 24-F in west Limon

040H 386.010 486.924 From I 70-A and U.S. 24-A east of Limon southeast via Hugo and Wild Horse and east via Kit Carson and Cheyenne Wells To the Kansas State Line

040Z 0.000 0.730 From U.S. 40-A at Lincoln St in Craig west To U.S. 40-A at Pershing St

041A 0.000 9.505 From U.S. 160-A Southwest of Cortez Northwest To the Utah State Line

042A 0.000 4.876 From SH 7-C east of Boulder south and east via Louisville To U.S. 287-C north of Broomfield


Route Ref

Point End Ref


044A 0.000 4.958 From SH 2-C northeast of Commerce City west To the intersection of 104th Ave and Colorado Bd in Thornton

045A 0.000 8.734 From East Side Ramps at I 25-A south Pueblo at (Greenhorn Dr) west and north To North Side Ramps at U.S. 50-A northwest of Pueblo

046A 0.000 6.610 From JCT SH 119-A north of Black Hawk southeast via Golden Gate Canyon State Park To at the Gilpin/Jefferson County Line Begin Goden Gate Dr

047A 0.000 4.635 From I 25-A and U.S. 50-A in North Pueblo east and south via College Ave To U.S. 50-B in East Pueblo

050A 31.760 314.598 From SH 70-Z in Grand Junction at (5th St) south via Delta and Montrose and east via Gunnison, Salida, and Canon City To SH 47-A in Pueblo at I-25

050B 315.709 467.583 From A Direct Connetion Flyover from South Bound I 25-A in Pueblo east via Fowler, Rocky Ford, La Junta and Lamar To the Kansas State Line

050C 0.000 16.948 From SH 96-A (Pueblo Bus Rout) south and east To U.S. 50-B east of Avondale

050D 0.000 1.539 From U.S. 50-A (Olathe Bus Rt) North of Olathe South To U.S. 50-A South of Olathe at (12 ST)

050Z 0.000 2.603 From U.S. 50-B in Rocky Ford west along Swink Ave To U.S. 50-B

052A 0.000 72.581 From SH 119-B at IBM Plant east via Fort Lupton, Hudson, and Prospect Valley and North To SH 39-A and U.S. 6-I east of Wiggins

052B 86.481 111.569 From U.S. 34-B at (Main St) in Fort Morgan north To SH 14-C east Begin (CR 133) of Raymer

053A 0.000 1.663 From The East Side Ramps on I 25-A at logan north of Denver west on 58th Ave and north on Broadway To SH 224-A at 70th Ave

055A 0.000 5.659 From U.S. 138-A at (First St) in Crook south To at (CR 81) South of SH-76A

056B 3.000 9.529 From U.S. 287-C Berthoud By-Pass East To Frontage Road East of I 25-A at (CR 44) in Johnstown

057A 0.000 0.534 From The South Side Ramps at I 70-A South of Stratton North via Stratton To Jct U.S. 24-C East of Stratton

058A 0.000 5.627 From U.S. 6-G and 93-A West of Golden East To a Direct Connection Flyover onto I 70-A in Wheat Ridge

059A 0.000 67.142 From U.S. 40-H in Kit Carson North To U.S. 36-D East of Cope

059B 74.474 173.337 From U.S. 36-D at (CR F) west of Joes north via Yuma and Haxtun To U.S. 138-A at (CR 15) east of Sedgwick

060A 0.000 4.968 From U.S. U.S. 287C at (CR 14) at Campion east To I 25-A frontage Rd Begin (CR 14) in Johnstown

060B 5.823 20.203 From the East Side Ramps at I 25A at (CR 48) east via Johnstown and Milliken and south To U.S. 85-C north of Platteville

061A 0.000 40.993 From U.S. 34-B at (CR RR) in Otis north To SH 6-5 in Sterling

062A 0.000 23.414 From SH 145-A at Placerville northeast via Dallas Divide to U.S. 550-B at Ridgway

136 Mix Designs

Route Ref

Point End Ref


063A 0.000 56.412 From U.S. 36D at Anton north via Akron To U.S. 6J in Atwood at (Front Ave)

064A 0.000 73.705 From U.S. 40-A in Dinosaur Southeast via Rangely To SH 13-A southwest of Meeker

065A 0.000 61.377 From SH 92-A east of Delta north via Cedaredge and Grand Mesa To North Side Ramps a I-70A Northeast of Palisade

066B 28.693 51.386 From U.S. 36B east of Lyons east To U.S. 85C in Platteville

067A 0.000 11.047 From SH 96A in Wetmore north To SH 115A at (Robinson Ave) in Florence

067B 11.562 15.074 From SH 115-A in Florence north To U.S. 50-A east of Canon City

067C 45.560 69.652 From Victor Ave and 4th St in Victor north via Cripple Creek To U.S. 24-A at Divide

067D 76.920 100.036 From U.S. 24-A in Woodland Park north To CR 75 and Deckers Rd in Deckers on the South Platte River

067E 117.349 127.449 From Rampart Range Road and CR 5 Northeast To U.S. 85B at Sedalia

069A 0.000 82.664 From SH 25-C Walsenburg Bus Rt northwest via Gardner and Westcliffe To U.S. 50-A at Texas Creek

070A 0.000 449.589 From the Utah State Line east via Grand Junction, Glenwood Springs, Silverthorne, Denver, Limon and Burlington To the Kansas State Line

070B 0.000 13.265 From U.S. 6-A and I 70-A northwest of Grand Junction southeast and east (Grand Junction Bus Rt) To I 70-A north of Clifton

070E 0.000 0.222 From the South Side Frontage Road at I-70 Silt Bus Spur Milepost 97 To U.S. 06D in Silt North of 9th St

070F 0.000 0.346 From Eagle Bus Spur at U.S. 6-E in Eagle North To the North Side Ramps at I 70A

070G 0.000 0.577 From the North Side Ramps at I 70A - at MilePost 163 - Edwards Bus Spur To U.S. 6-E in Edwards

070K 0.000 2.711 From Idaho Springs Bus Rt - From I 70-A west of Idaho Springs east To I 70-A east of Idaho Springs Bus Rt Idaho Springs

070L 0.000 0.400 From Watkins Bus Spur - I 70-A north To U.S. 36-C in Watkins

070M 0.000 0.348 From Strasburg Bus Spur - I 70A North To U.S. 36-D in Strasburg

070N 0.000 0.396 From Deer Trail Bus Spur - U.S. 40-E in Deer Trail northeast To I 70-A

070O 0.000 0.353 From Agate Bus Spur - U.S. 40-F in Agate east To I 70-A

070P 0.000 0.528 From Vona Bus Spur- I 70-A north To U.S. 24-B in Vona

070Q 0.137 0.377 From US 24D at 6th Ave in Burlington East (Burlington Bus Spur) To I-70A

070Z 0.000 1.338 From Grand Junction Bus Rt - SH 70-B 15th St and Ute Av west along Ute Ave To SH 70-B at 1st St

071A 0.000 9.032 From SH 350-A northeast of Timpas north To SH 10-A west of Hawley

071B 9.601 14.539 From SH 10-A at Bawley north To U.S. 50-B and SH 266-A in Rocky Ford

071C 16.157 101.063 From U.S. 50-B west of Rocky Ford north To U.S. 24-A in Limon


Route Ref

Point End Ref


071D 101.973 174.357 From U.S. 24-A in Limon north via Last Chance To U.S. 34-B east of Brush

071E 175.486 201.636 From U.S. 34-B in Brush north To SH 14-C east of Stoneham

071F 205.525 232.899 From SH 14-C Stoneham north to the Nebraska State Line

072A 0.000 29.378 From I 70-A in Wheat Ridge north on Ward Road and northwest via Pinecliffe To SH 119-A south of Nederland

072B 32.369 54.064 From SH 119-A in Nederland north To SH 7-A north of Raymond

074A 0.000 18.110 From I 70-A at El Rancho south via Bergen Park and east via Evergreen and Idledale To SH 8-A in Morrison

075B 5.287 8.524 From Bowles Ave and Lowell Blvd Southwest via Platte Canyon Blvd to SH 470A

076A 0.000 184.135 From I 70-A and SH 121-A in Arvada northeast via Hudson, Fort Morgan, Sterling, and Julesburg To Nebraska State Line

076B 0.000 0.472 From County Road 18 in Keenesburg Bus Spur - From I 76 A South To Old Hwy 6 and Elm St in Keenesburg

078A 0.000 33.272 From SH 165 A North of San Isabel east and Northeast To SH 45 A in Pueblo

078B 0.000 1.493 From Beulah Spur Connection - From SH 78-A northwest To County Road 213 and Penns Ave in Beulah

079A 0.000 1.240 From South Side Frontage Road at I 70 A To JCT U.S. 36 C in Bennett

079B 1.580 23.892 From Adams St and JCT U.S. 36 D in Bennett To SH 52-A in Prospect Valley

082A 0.000 85.293 From I 70-A in Glenwood Spgs southeast via Aspen and Independence Pass To U.S. 24-A east of Twin Lakes

083A 20.368 77.267 From Powers Blvd in Colorado Springs East and North via Franktown and Parker To SH 002A (Colorado Blvd) at Bayaud Ave in Denver

084A 0.000 27.924 From the New Mexico State Line northwest via Chrome To Chrome to U.S. 160-A at Pagosa Springs

085A 127.651 137.040 From East Side of I 25-A (South Chater Oak Ranch Rd) Fountain Interchange North To West of I 25 A just South of Colorado Springs Ending at (Ventucci Blvd)

085B 184.667 210.864 From Jct I 25-A at Founders Parkway in Castle Rock Northwest via Sedalia To I 25-A in Denver Begin (Santa Fe Dr)

085C 226.797 265.763 From I 76-A north of Commerce City north via Brighton To U.S. 34-A Sourh of Greeley

085E 0.000 1.515 From Fort Lupton Bus Route - From SH 52-A in Fort Lupton north To U.S. 085C at 16the Street North of Fort Lupton

085F 0.000 2.690 From Platteville Bus Route - From SH 66-B in Platteville north To U.S. 85-C north of Platteville

085G 0.000 1.629 From Greeley Bus Route - South of JCT with SH-34A and End of U.S. 85C south of Greeley North To U.S. 34D in Greeley

085H 0.000 2.239 From Greeley Bus Route - From U.S. 34-D in Greeley north To U.S. 85-C north of Greeley

138 Mix Designs

Route Ref

Point End Ref


085L 265.849 309.542 From U.S. 34-A South of Greeley To the Wyoming State Line

086A 1.854 59.279 From the End of SH 86B at (Ridge Rd) via Franktown, Elizabeth, and Kiowa To I 70-A Northwest of Limon

086B 100.000 104.348 From I-25 End U.S. 85B (Santa Fe) East and South to (RIDGE RD) Start SH 86 A

088A 0.000 14.770 From U.S. 40-C and U.S. 287-C at West Colfax Ave in Denver south via Federal Blvd and east via Belleview Ave To I 25-A in South Denver

088B 16.827 21.734 From the East Side Ramps at I-25 South of Denver East Along Arapahoe Road To SH 83-A (Parker Road and Arapahoe)

089A 0.000 34.340 From SH 116-A at Lycan North To SH 50-B at Holly

090A 0.000 33.874 From the Utah State Line southeast via Bedrock To SH 141-A at Vancorum

090B 81.533 89.858 From CR 90 and Shavano Valley Rd Southwest of Montrose Northeast To SH 50-A and SH 550-B in Montrose

091A 0.000 22.605 From SH 24-A North of Leadville North via Fremont Pass and Climax To I 70-A at Copper Mountain

092A 0.000 73.259 From SH 50-A in Delta east via Hotchkiss and southeast via Crawford and Black Mesa To SH 50-A at Blue Mesa Dam

093A 0.000 18.849 From SH 58-A in Golden North To SH 119-A and (Broadway) in Boulder

094A 0.548 86.174 From U.S. 024A at MeadowBrook Pkwy East of Colorado Spgs To U.S. 040H Northwest of Wild Horse in Cheyenne County

095A 0.000 14.376 From the Frontage Road at (Sheridan Blvd) south of SH 285-D north via Sheridan Blvd To SH 36-B in westminster

096A 0.000 58.812 From SH 69-A in Westcliffe east via Silver Cliff and Wetmore To SH 50-B East of Pueblo

096B 69.499 105.830 From SH 50-B east of Pueblo east via Boone and Olney Springs To SH 71-C at Ordway

096C 106.036 166.114 From SH 71-C at Ordway east via Sugar City and Haswell To SH 287-B in Eads

096D 168.992 207.454 From SH 287-B east of Eads east via Sheridan Lake To the Kansas State Line

097A 0.000 4.584 From SH 141-A in Naturita north To Third Ave in Nucla

100A 0.000 0.419 From SH 160-C North of Vilas To Main St in Vilas

101A 0.000 21.413 From SH 50-B in Las Animas south To (CO RD K) and (CO RD 18) in Toonerville

103A 0.000 22.488 From SH 70-K in Idaho Springs south via Echo Lake and East To (CO RD 151) (Little Bear Creek Rd) and Squaw Pass

105A 4.731 9.480 From County Road 8 (Woodmoor Drive) in Monument North to the Fl Paso/Douglas County Line North of Palmer Lake

105B 28.160 32.628 From CO RD 105 and Wolfenberger Rd west of Castle Rock North To SH 67-E west of Sedalia

109A 0.000 65.327 From SH 160-C north of Kim North via La Junta to Just Before Fourth Street in Cheraw Begin Grand Ave.


Route Ref

Point End Ref


109B 0.000 0.184 From SH 50-B in La Junta south via Bradish Ave To 3rd St then east via 3rd St to SH 109-A

110A 0.000 0.140 From US 550-B West of Silverton East and North To Maintenance Yard Service Rd

112A 0.000 27.802 From SH 160-A in Del Norte northeast and east via Center To SH 17-B at Hooper

113A 0.000 18.830 From SH 138-A northeast of Sterling north via Peetz To the Nebraska State Line

114A 0.000 61.697 From SH 50-A east of Gunnison southeast via North Pass To SH 285-B in Saguache

115A 0.000 47.496 From SH 50-A at 9 th St in Canon City southeast via Florence and northeast via Penrose To the North Side On Ramps onto I-25A in Colorado Springs

116A 0.000 32.322 From SH 287-A at CO RD RR.00 north of Springfield East via Two Buttes and Lycan To the Kansas State Line

119A 0.000 41.892 From SH 6-G in Clear Creek Canvon Northwest via Black Hawk and Nederland and East To SH 7-B at Braodway and H 93-A in Boulder

119B 44.237 59.089 From SH 36-B in Boulder northeast To SH 119C at IRON HORSE in Longmont

119C 59.089 63.700 From SH 119B at Iron Horse in Longmont east to I-25A in Longmont

120A 0.000 7.186 From SH 115-A east of Florence east via Portland To SH 50-A west of the Fremont/Pueblo County Line

121A 0.000 26.419 From SH 121-B and SH 470-A north along Wadsworth Blvd To SH 287-C in Broomfield

121B 0.000 4.413 From the Martin Marietta Plant Entrance in Kassler North To SH 121-A and SH 470-A south of Denver

125A 0.000 75.406 From SH 40-A west of Granby north via Walden To the Wyoming State Line

127A 0.000 9.202 From SH 125-A north of Cowdrey northeast via Kings Canyon to the Wyoming State Line

128A 0.000 7.973 From SH 93-A south of Boulder east To SH 121-A in Broomfield

128B 12.168 14.113 From SH 287-C Cozy Corner east of Broomfield East along 120th Ave To the East Side Ramps at I-25 in Thornton

131A 0.000 0.323 From I 70A at Mile Point 156 North To SH 6E East of Wolcott

131B 0.053 68.721 From SH 6-E in Wolcott North via State Bridge, Toponas, and Oak Creek To SH 40-A South of Steamboat Springs

133A 0.000 68.821 From SH 92-A in Hotchkiss northeast via Somerset, McClure Pass and Redstone To SH 82-A north of Carbondale

133B 12.159 16.076 From Jct with SH 133-A northeast to Jct SH 133-A close To the Delta-Gunnison County Line

134A 0.000 27.163 From SH 131-B at Toponas east via Gore Pass To SH 40-A northwest of Kremmling

135A 0.000 27.484 From SH 50-A in Gunnison north via Almont To Elk Ave in Crested Butte

140 Mix Designs

Route Ref

Point End Ref


136A 0.000 4.469 From SH 285-A in La Jara east To 2nd South Street in Sanfora

138A 0.000 59.823 From SH 6J and SH6Z in Sterling northeast via Crook and Julesburg To the Nebraska State Line just North of Julesburg

138Z 0.000 0.614 From SH 138-A in Sterling southwest via Broadway and 4th St To SH 6-Z at Chestnut Street

139A 0.000 72.065 From I 70-A south of Loma north via Douglas Pass To SH 64-A east of Rangely

140A 0.000 23.435 From the New Mexico State Line North To SH 160-A north of Hesperus

141A 0.000 154.109 From SH 491-B northwest of Dove Creek Northeast via Slick Rock, Gypsum Gap, Naturita, Uravan and Gateway To SH 50-A at Whitewater

141B 156.746 162.297 From SH 50-A North of Whitewater Northeast To SH 70-B South of Clifton

142A 0.000 33.840 From SH 285-A at Romeo east via Manassa and San Acacio To SH 159-A in San Luis

144A 0.000 28.796 From I 76-A Fronta e Road east of Wiggins northeast via Orchard, Goodrich and Weldona To SH 2-B in Fort Morgan

145A 0.000 116.879 From SH 160-A in Cortez Northeast via Dolores, Rico, and Ophir and Northwest via Placerville and Norwood To SH 141-A East of Naturita

149A 0.000 117.522 From SH 160-A at South Fork Northwest via Creede and Lake City To SH 50-A west of Gunnison

150A 0.000 16.114 From SH 160-A at the Alamosa/Costilla County Line North To the Great Sand Dunes National Monument

151A 0.000 33.960 From SH 172-A in Ignacio east via Arboles and northeast To SH 160-A east of Chimney Rock

157A 0.000 4.530 From SH 36-B in Boulder north to SH 119-B north to Boulder

159A 0.000 33.661 From the New Mexico State Line north via San Luis To SH 160-A in Fort Garland

160A 0.000 305.380 From the New Mexico State Line (Four Corners Monument) northeast via Cortez and east via Durango, Pasosa Springs, Wolf Creek Pass, Alamosa, and North La Veta Pass To SH 25-C in Walsenburg

160B 305.526 306.350 From SH 25-C in Walsenburg east To SH 10-A and I 25-A east of Walsenburg

160C 344.572 497.223 From I 25-A in Trinidad east via Beshoar Junction, Kim, Pritchett, and Walsh To the Kansas State Line

160D 0.000 2.488 From Mancos Bus Rt - From SH 16O-A west of Mancos east To SH 160-A east of Mancos

160E 0.000 2.439 From Bayfield Bus Rt - From SH 160-A west of Bayfield east To SH 160-A east of Bayfield

160Z 0.000 0.929 From Denver Ave and Jct U.S. 160A in Alamosa One-Way West along Main Street ( Fifth ) to Jct U.S. 160A NorthWest at the Alamosa ByPass Between Richardson Ave and Edgemont Blvd

165A 0.000 36.894 From SH 96-A southwest of Wetmore southeast via San Isabel and Rye To I 25-A east of Colorado City


Route Ref

Point End Ref


167A 0.000 4.860 From SH 96-B west of Olney Springs South To a County Road JJ.00 South of Fowler

170A 0.000 6.969 From Eldorado Springs East To North of SH 36B at the Superior Louisville City Limit

172A 0.000 24.499 From the New Mexico State Line North via Ignacio To SH 160-A Southeast of Durango

177A 0.000 6.111 From SH 470-A south of Denver North via University Blvd To SH 285-D at Hampden Ave

183A 0.000 1.000 From SH 50-B east of Las Animas South To the Fort Lyon Veterans Hospital at CO RD (HH)

184A 0.000 8.159 From SH 49-B north of Cortez East To SH 145A west of Dolores

184B 8.900 26.599 From SH 145-A west of Dolores southeast To SH 160-D (Mancos Bus Rt)

194A 0.000 20.327 From SH 109-A North of La Junta East To SH 50-B North of Las Animas

196A 0.000 8.922 From SH 50-B East of Hasty North and East To U.S. 287 South of Wiley in Prowers County

202A 0.000 3.228 From SH 50-B in Rocky Ford south and west To CO RD 16 North and CO RD FF West of Rocky Ford

207A 0.000 5.935 From SH 50-B in Manzanola North To SH 96-B South of Crowley

209A 0.000 1.528 From SH 50-B North To SH 96-B in Boone

224A 0.000 3.634 From SH 36-B North of Denver South and East To SH 6-H in Commerce City

225A 0.000 12.431 From I 25-A in Denver Northeast and North To I 70-A East of Denver

227A 0.000 1.851 From SH 50-C East of Pueblo North To SH 96-A in Pueblo

231A 0.000 2.050 From SH 50-C at Vineland North To SH 50-B at Devine

233A 0.000 2.147 From SH 50-C PuebLo Bus Rt North To SH 50-B at Baxter

239A 0.000 3.345 From Jct SH 160C (Goddard Ave) in Trinidad North and Northeast To Las Animas County Roads 75 North and El Moro

257A 0.000 18.487 From SH 60-B in Milliken North via Windsor To SH 14-C East of Ft Collins in Severance

257B 0.037 1.146 From A Barricade at SH 257-A South of Windsor East To SH 34-D at (Promontory Circle) at Greeley Bus Rt

263A 0.635 2.733 From Business Route 85 in Greeley east to County Road 45 East of Greeley

265A 0.000 3.621 From I 70-A viaduct in Denver Northeast To SH 6-H at (69th Ave) in Commerce City

266A 0.000 11.516 From SH 50-B and SH 71-B in Rocky Ford east To SH 109-A at (Otero County Road HH) Nnorth of La Junta

270A 0.000 5.986 From I 76-A and 270-B west of Commerce City Southeast To I 70-A

270B 0.000 1.100 From The End of SH 36 at I 25-A To I 270-A just north of Denver

285A 0.000 34.102 From the New Mexico State Line north via Antonito and La Jara To SH 160-A in Alamosa

142 Mix Designs

Route Ref

Point End Ref


285B 51.159 126.480 From SH 160-A and SH 15-A in Monte Vista north via Saguache and Poncha Pass To SH 50-A in Poncha Spgs

285C 126.853 148.065 From SH 50-A in Poncha Spgs North To SH 24-A at Johnson Village

285D 161.789 263.874 From SH 24-A at Antero Junction northeast via Fairplay, Kenosha Pass and Bailey To SH 30-A in Denver

287A 0.000 77.639 From the Oklahoma State Line North via Springfield To SH 50-B in Lamar

287B 85.188 133.240 From SH 50-B west of Lamar north via Bags To SH 40-H east of Kit Carson

287C 282.700 385.223 From SH 40-C and SH 88-A West Colfax Ave and Federal Blvd in Denver north via Broomfield, Longmont, Loveland and Fort Collins To the Wyoming State Line

287Z 0.000 1.763 From SH 287-C in Loveland South along Cleveland Ave To SH 287-C South of 5th Street

291A 0.000 9.135 From SH 50-A in Salida Northwest To SH 285-C northwest of Salida

300A 0.000 3.356 From SH 24-A Southwest of Leadville West and North To County Road 5A

317A 0.000 12.237 From SH 13-A at Hamilton east To County Road 29 at Pagoda

318A 0.000 60.697 From the Utah State Line To SH 40-A West of Maybell

325A 0.000 11.395 From SH 13-A north of Rifle northeast via Rifle Gap State Recreation Area To County Road 217 in Rifle Falls State Recreation Area

330A 0.000 11.395 From SH 65-A north of Mesa east To at Grove Creek Rd in Collbran

340A 0.000 13.341 From SH 6-A in Fruita southeast To SH 70-B at 1st Street in Grand Junction

347A 0.000 5.248 From Grand Junction Bus Route - From SH 50-A East of Montrose north To the Black Canyon of the Gunnison National Monument

348A 0.000 17.059 From SH 50-A in Delta (6th Street) South via Pea Green Corner South and East To SH 50-A in East of Olathe

350A 0.000 73.001 From SH 160-C Beshoar Junction East of Trinidad Northeast via Model and Timpas To SH 50-B in La Junta

368A 0.000 12.329 From SH 370-A south of Monte Vista south and east To SH 295-A south of Alamosa

370A 0.000 14.115 From SH 15-A south of Monte Vista east To SH 285-A south of Alamosa

371A 0.000 6.067 From SH 15-B east of Capulin north To SH 368-A on the Conejos/Alamosa County Line

385A 95.000 122.879 From SH 50B in Granada North via Bristol To SH 96D West of Sheridan Lake

385B 123.682 149.701 From SH 96-D in Sheridan Lake North To SH 40-H east of Cheyenne Wells

385C 150.251 216.861 From SH 40H in Cheyenne Wells North via Burlington To SH 36D east of Idalia

385D 219.448 310.996 From SH 36-D Northeast of Idalia North via Wray and Holyoke To SH 138-A East of Julesburg


Route Ref

Point End Ref


385E 313.849 317.631 From SH 138-A west of Julesburg Northwest To the Nebraska State Line

389A 0.000 12.803 From the New Mexico State Line North via Branson To SH 160-C East of Trinidad

391A 0.000 9.641 From the South Side Frontage Rd at SH285-D in Lakewood North along Kipling St. To the North side of I 70-A in Wheat Ridge at 49th Ave

392A 95.305 104.455 From US 287C at the South End of Fort Collins East along (Carpenter Rd) (Old CO RD 32) Crossing I-25 ending at 7th Street and SH 257-A in Windsor

392B 105.439 141.583 From SH 257-A East of Windsor East via Lucerne and North To SH 14C at Briggsdale

394A 0.000 9.378 From SH 40-2 (Victory Way) in Craig south and East To (County Road 65) at the Moffat/Routt County Line

402A 0.000 4.306 From US 287C at 14th Street in Loveland East To I-25A and County Road 18 in Johnstown

470A 0.000 26.195 From I 70-A west of Denver south and east To I 25-A South of Denver

470B 0.000 46.398 From I 25-A northeast to I-25A

470N 46.398 54.450 From 470E at 025A West/Southwest to Termius at 96TH Ave.

470W 0.000 1.212 From Interchange with I 70-A southeast of Golden north to US 6-G in Golden

491A 0.000 6.422 From the New Mexico State Line North To SH 160A South of Cortez

491B 26.217 69.602 From SH 160A in Cortez northwest via Dove Creek To the Utah State Line

491C 0.000 0.242 From Cortez Spur Connection-From SH 160-A in Cortez Northwest To SH 491-B

550A 0.000 16.561 From the New Mexico State Line North To SH 160A Southeast of Durango

550B 20.916 130.219 From SH 160-A in Duranqo north via Molas Divide Silverton, Red Mountain Pass, and Ouray To SH 50-A and SH 90-B in Montrose

.

4.8.1.4 Historical notes and discussions The information is currently captured on the RSAR form on the CDOT internal website. Some of the field names will change for population in the Pavement Structural Design Data window. (See bolded comments below). This discussion was with Bob Locander, Steven Henry and Eric Chavez on 2/7/12. This is a notification that the RSAR Form was filled out and submitted with the following values: -----

Project#: NH 1601-061 (not on Pavement Structure Design Data window but can be retrieved from contracts window) Sub Account/Patrol #: 17635 Highway #: 160 (This will now be Route and needs to be populated based on auxiliary route information) Prime Contractor: SEMA (not on PSDD window but can be retrieved from contracts window). Region: 5

144 Mix Designs

Maintenance Project?: False (Only maintenance projects that are bid through the bid process will be in SM) Project Description: (Use Remarks bubble to populate information) Roadway widening. FDR/AEFDR. FDR 10" min., AEFDR upper 6" of FDR. Topped with 4" HMA. Beginning MilePost: 11.5 - (Beginning Reference Point) Ending MilePost: 18.0 – (Ending Reference Point) Work End Date: 9/20/2011 (This is activity date – which is defined as “open to traffic”) Surface Treatment: Asphalt Reconstruction – (SURFACE dropdown list) Direction: Both – (DIRECT dropdown list) Treatment Thickness(inches): 14 (Surface Thickness) Average Project Width(feet): 40 (This will need to be calculated based on the lanes and shoulder checkboxes) and additional information on lane widths may be placed in the Remarks. Pavement Type: Asphalt (This will be the PRJTYP dropdown).

4.8.1.5 Reports Pavement Structural Design Data Report Purpose: This report will allow a pavement management user to extract data that has been associated to a Contract. The pavement management user will have to select the contract ID. The data is specific to one Contract. The listings are for all of the records in the Contract. The report is an Excel spreadsheet. Anyone can view and print this report. Preliminary Draft of Report Format: (Note that as of 06/10/13 this report was still in development.) The MS Excel workbook has three tabs as shown.

Contract ID

(C) Contract ID

Route

Beginning

Reference

Point

Ending

Reference

Point Direction

Funding

Category

Project

Type

Top

Surface

Layer

Second

Surface

Layer

Third

Surface

Layer

Surface

Thickness

Record 1 1 2 3 4 5 6 7 8 9 10

Record 2

Record 3

End

As-Constructed Pavement Structure Data

COLORADO DEPARTMENT OF TRANSPORTATIONProject No. Region

A B

Location

D

Pavement Structural Design Data

Report

Milled

Depth

Pavement

Base

Base

Thickness

Pavement

Subbase

Subbase

Thickness

Effective

Thickness

Subgrade

R-value

Structural

Capacity

Composite

k-value

Drainage

Condition

Pavement

Shoulder

Number

of Lanes

Inside

Shoulder

11 12 13 14 15 16 17 18 19 20 21 22 23

Lane 1 Lane 2 Lane 3 Lane 4 Lane 5 Lane 6 Lane 7 Lane 8 Lane 9 Lane 10

Outside

Shoulder

Activity

Date

24 25 26 27 28 29 30 31 32 33 34 35

Lanes Affected


Contract ID

(C) Contract

ID

Surfacing

Bid Item

Number

Long

Description

of Bid Item

Bid Item

Units

Bid Item

Quanity

Bid Item

Price

Bid Item

Amount

Record 1 50 51 52 53 54 55

Record 2

Record 3

End

Base and Subbase

Bid Item

Number

Long

Description

of Bid Item

Bid Item

Units

Bid Item

Quanity

Bid Item

Price

Bid Item

Amount

Record 1 56 57 58 59 60 61

Record 2

Record 3

End

Stablized Soils

Bid Item

Number

Long

Description

of Bid Item

Bid Item

Units

Bid Item

Quanity

Bid Item

Price

Bid Item

Amount

Record 1 62 63 64 65 66 67

Record 2

Record 3

End

Embankment

Bid Item

Number

Long

Description

of Bid Item

Bid Item

Units

Bid Item

Quanity

Bid Item

Price

Bid Item

Amount

Record 1 68 69 70 71 72 73

Record 2

Record 3

End

Pavement Bid Item Data

COLORADO DEPARTMENT OF TRANSPORTATION

Project No. Region

A B

Pavement Structural Design Data

Report

Location

D

146 Mix Designs

Contract ID

(C) Contract

ID

SuperPave Mixes

Mix ID Material Code Material Description Producer/Supplier Code Producer/Supplier Name

Record 1 100 110 120 130 140

Record 2

Record 3

End

Marshall Mixes


Record 1 200 210 220 230 240

Record 2

Record 3

End

PCC Mixes


Record 1 300 310 320 330 340

Record 2

Record 3

End

Aggregate Mixes


Record 1 400 410 420 430 440

Record 2

Record 3

End

Asphalt and Concrete Mix Designs


Project No. Region

A B

Pavement Structural Design Data ReportLocation

D


SECTION 5 Sampling, Testing, and LIMS

148 Sampling, Testing, and LIMS

5.1 Maintain Sample Information Window

SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > SAMPLING AND TESTING > SAMPLE INFORMATION

Window Procedure: Use the Maintain Sample Information window to track the collection of samples and test data results for both contract and non-contract specific materials. Any material that is tested, reviewed, approved, or verified requires a sample record.

Security Procedure: CDOT update authority for this window should be limited to the following SiteManager Materials Security groups: Technical Support, IT System Administration, Region Materials Office, CDOT Samplers and Testers, Consultant Testers, Binder, Flexible Pavement and Chemical, Concrete/Physical Properties, and Soils Groups. CDOT Samplers and Testers or Consultant Testers do not have authorization to Update nor have Inquire rights to Unauthorized Sample. CDOT inquiry authority for this window should be available to all other SiteManager Material users.

Functional Procedure: CDOT will utilize this window and panels to record sample and product information used on CDOT projects. Sample ID’s will be automatically generated using the ID of the person logged in and the date and time the sample ID was created. Several fields will be required to be completed in order to save a sample. These fields include Sample ID, Sample Type, Material, Represented Quantity, and Units. Several fields are required by CDOT to be completed in order for a sample or product to be counted towards sampling and testing requirements for a project contract. These fields include Contract/Item, Sample Type, Acceptance Method, and Tests. Several fields will be required by CDOT for the procedure to be completed. These include Producer/Supplier (P/S) and Product Number.

5.1.1 Basic Sample Data Panel Use the Basic Sample Data panel to log information about the material and associated data such as Sample Type, Material, Units, and Material Code. Note: There is no Time field to record the time cylinders were cast. Record the time by clicking the Remarks button on the toolbar, typing the time, and clicking the Remarks button again to close the window.


Figure 5.1 Maintain Sample Information Window - Basic Sample Data Panel


Table 5.1 Maintain Sample Information Window - Basic Sample Data Panel – Fields


Smpl ID N/A* Auto-populated. Sample ID. Uniquely identifies a sample.

18

Status N/A Auto-populated. Displays the current status of the sample record.

--

Revised by N/A Auto-populated. User ID of the person who created the revised sample record. Protected.

--

Revising N/A Auto-populated. Current sample has this status after it has been authorized and a revision is being made. Protected.

--

Sample Date Yes Auto-populated or Manual Entry. Date the sample was taken.

DD/MM/YY

Link To No (CDOT will not use) --

Link From No (CDOT will not use) --

Log Date N/A Auto-populated. Date on which the sample was entered into SiteManager.

--

Smpl Type Yes* Drop Down. Sample Type. Identifies the type of sample taken. See Code Table SMPLTYPE below.

--

Acpt Meth Yes Drop Down. Acceptance Method. Method by which the sample is being accepted. See Code Table ACPTMETH below.

--

Material Yes* Search. Uniquely identifies a material. --


N/A Auto-populated. Describes the material. --

Sampler Yes Search. User ID of the sampler who took the sample. --

Sampler’s Name (no label)

N/A Auto-populated. Name of the sampler. --

P/S Yes Search. Producer/Supplier. Name of the producer or supplier of the material.

--

P/S Code N/A Auto-populated. Producer/Supplier Code. Uniquely identifies the producer/supplier.

--

Type N/A Auto-populated. System-populated when supplier is selected.

--

City N/A Auto-populated. System-populated when a supplier is selected.

--

Prod Nm Yes Search. Product Name. Brand name of material. --

Mnfctr N/A Auto-populated. Manufacturer, Manufacturer of the product selected.

--

Town No (CDOT will not use) --

Geog Area Yes Drop-down menu. (CDOT will not use) --

Intd Use Yes Free Form. Intended Use. Intended use of the material.

40

Repr Qty Yes Free Form, Numerical. Represented Quantity. Quantity of the sample being associated the quantity of

12 and

0.001



material represented by the sample. accuracy

Repr Qty Units (no label)

Yes* Drop Down. Represented Quantity Units. Units of the Repr Qty field. See Code Table UNITTYP below.

--

Lab Control Number Yes Auto-populated. An umbrella number for grouping samples. Allows samples to be linked together for testing and sample review purposes.

--

Auth By N/A Auto-populated. Authorized By. User ID of the person that authorized (completed) the sample.

--

Auth Date N/A Auto-populated. Authorized Date. Date when the sample was authorized (completed).

--

Lab Reference Number

Yes Free Form. Can be used by each Lab Unit to keep track of internal sample ID.

10

Lock Type N/A Drop Down. (CDOT will not use) Determines the access level for updating the sample record. Controlled by System Parameters.

--

Locked By N/A Auto-populated. (CDOT will not use) Indicates who locked the sample. Controlled by System Parameters.

--

Lock Date N/A Auto-populated. (CDOT will not use) Indicates the date and time the sample record was locked. Controlled by System Parameters.

--

5.1.1.1 Required /Optional Fields *Required to save sample.

*SAMPLE ID: Auto-populated, 18 characters max, SiteManager standard format: -User ID-YY-M-D-Military Time

-User ID: name of person -Year: last two digits of year when sample was submitted -Months: are January-December is 1-9, A, B, C -Days 1-31: are 1-9, A-V -Military Time: time without colons Example: smith10AF114525, Smith (smith) submitted a sample on 2010 (10), October (A), 15 (F), at 11:45:25 (114525).

STATUS: Auto-populated.


Code Table = SMPLSTAT – Sample Status

Code Description

COMP Complete

FAIL Fail

LODG Logged

PEND Pending

PREA Pending Authorization

RECV Received

TEST In Testing

SAMPLE DATE: Auto-populated. Sample date can be entered manually if sample record is created after sample is obtained. Format: MM/DD/YY *SMPL TYPE AND ACPT METH: Drop-down. Sample Type and Acceptance Method. The Sample Type and Acceptance Method must match as per the table in order for a sample to be applied to a contract. These tables are the same as in the Section “Maintain Sample Information Window”.

Code Table = SMPLTYPE – Sample Type

Code Description



IAT Independence Assurance Testing





Code Description



ST Sample and Test


*MATERIAL: Search field, select material sampled. SAMPLER: Search field, qualified sampler or witness of sample, “contractor”, “supplier”. P/S: – Search filed. Producer/Supplier. CDOT procedure is to select a P/S for every sample entered. Not required for contract or to begin sample testing or logging. P/S may be selected at a later date if the P/S is not listed at the time of sample submittal.


The Pavement Design Program and/or the Region Materials Office must be notified if a Producer or Supplier is not on the P/S list. PROD NM: Search field. Product Number. Required for COC, CTR, APL logging, must be entered before final acceptance of material. Not required by contract or to begin sample submittal. MNFCTR: Search field or Auto generated by choice of Prod Nm from APL/QM list. Manufacturer:

- If Brand Name is required on the Material Detail window, then select the Product Name to auto-populate the Mnfctr field. - If the Brand Name is not required on the Material Detail window, then search for the manufacturer in the Mnfctr field. The list contains only approved producer/suppliers for that material.

INTD USE: Free form, information only, use if needed. Intended Use. Description of the intended use of sample/material used on the project. Examples: curb and gutter, sidewalk, patching, inlet, caisson, median barrier, etc. *REPR QTY: Free form, numerical. Represented Quantity. Record the quantity the sample represents. *REPR QTY UNIT: Drop-down. Represented Quantity Unit. Units are required to be selected to save a sample. Must match unit assigned to the material sampled.

Code Table = UNITTYP – Unit Type Code

Code Description

ACRE Acre

BEAM Beam

Bft Blows Per Foot

BOX Box

BUKT Bucket

C Degree Celsius

CAN Can

CB Canvas Bag

CF Cubic Foot

cm Centimeter

cm2 Square Centimeter

cm3 Cubic Centimeter

cms Centimeter per Second

CORE Core

cP Centipoise

CTNR Container

CUBE Cube

CUP Cup

CY Cubic Yard

CYL Cylinder

DAY Day

deg Degree (angle)

Dmm Decimillimeter

DOL Dollar

EACH Each


Code Description

F Degree Fahrenheit

F A Force Acct

g Gram

GAL Gallon

GASY Gallon per Square Yard

gcm3 Gram per Cubic Centimeter

gmL Gram per Milliliter (density)


HOUR Hour

in Inch

In2 Square Inch

in3 Cubic Inch

inLB Inch-Pound

ips Inch per Second


KGM3 Kilograms Per Cubic Meter


kPa Kilopascal



LB Pound

LBpm Pound per minute

LF Lin Foot

LINR Liner

Lkm Lane Kilometer

LM Lane Mile

LOT Lot




M2KG Square Meter per Kilogram




mg Milligram

MGAL M Gallon

mgL Milligram per Liter

mil Mil (0.001 Inch)

MILE Mile

min Minute

MKFT M Kip Foot

mL Milliliter

mm Millimeter

mm2 Square Millimeter

mm3 Cubic Millimeter

mmHg Millimeters of Mercury


MON Month

MPa Megapascal

mrad Millirad

mV Millivolt

N Newton


Code Description


Ohcm Ohm centimeter

Ohm Ohm

OZ Ounce

Pa Pascal

Pas Pascal Second

PCE Piece

pcf Pounds per Cubic Foot

pct Percent

PGAL Pounds Per Gallon

pH pH

PLBG Plastic Bag

PLBL Plastic Bottle

plf Pound per Linear Foot

plfk Pound per 1,000 Linear Feet

ppb Part per Billion

ppm Part per Million

psi Pound per Square Inch

pt Pint

qt Quart

rad Radian

rpm Revolution per Minute

s Second

SF Sq Foot

SHML Shoulder Mile

SY Sq Yard




TM Ton Mile

TON Ton

TSF Ton per Sq Foot

TUBE Tube

WD Work Day

WK Week

YM Yard Mile

LAB CONTROL NUMBER (LCN): Auto Generated/Search Field. Use to link multiple samples together, concrete cylinders, QA, 10K, IA (i.e. split samples), Soil survey samples, etc. Use same LCN for all samples to be linked to each other. The Sample ID may be different because it is entered by different people, but the LCN will be the same. This is done by creating a sample log or opening an existing sample, go to the SERVICES menu, Copy Sample, chose “Copy Lab Control Number from existing sample”. LAB REFERENCE NUMBER (LRN): Optional, maybe used by in house lab to keep track of samples or enter CDOT Field Sheet number if applicable. The value entered in the LRN field will be printed on Sample Label. Other values may be entered to be used to separate samples at Central lab, enter PCCP, HMA, Physical Properties, Soils, Chemical, etc.

5.1.1.2 Reference Tables

Sample Type and Acceptance Method. The Sample Type and Acceptance Method must match as per the following table, in order for a sample to be applied to a contract. Explanations of the


above tables are shown below. These tables are the same as in the Section “Maintain Sample Information Window”. Caution! Caution! Caution! If the Sample Type and Acceptance Method are miss-matched, SiteManager will allow one to proceed to the Addtl Sample Data tab. However, when going to the following tab a fatal error message will appear. After the fatal error message, you must completely exit the system, re-log on and re-start the sample. Nothing entered prior to the error will be saved.

Figure 5.2 Sample Method and Acceptance Method Relationships


Method Comments

Project Pay

Quality Acceptance Testing

Sample and Test

Standard project samples for project verification testing and acceptance. (If an item is visually accepted, the Visual Test Template should be used.)

YES

Independence Assurance Testing

Sample and Test

Sample for IA testing on projects. The QA, 10K and/or IA samples will be linked by the Lab Control Number. IA's for Item 403 can be done at the same time as 10K samples; they will be linked by Lab Control Number, but will have a separate sample ID number.

NO

COC COC

Material acceptance based on COC submittal by the contractor or a manufacturer listed on the CDOT APL. A Product Name will be required for final material acceptance. If a manufacturer is on the CDOT APL, the contractor supplies the COC. If the manufacturer is not on the CDOT APL, the manufacturer supplies a COC to the project.

YES

CTR CTR

Material acceptance based on CTR submittal from supplier. A Product Name will be required to be recorded before material acceptance. Examples: Mill Certification, Lab Certification, etc.

YES

Information Only Testing

Sample and Test

Material testing at HQ, Region, or field labs that are for information only. Samples submitted for project and non-project Information Only Testing including, but not limited to: project HMA 10K samples not for contract pay or IA check testing, concrete information cylinders, Bridge Unit items (concrete, strand, rebar, etc.), HMA Mix Design items, project/contractor check testing, Round Robin testing conducted by HQ, Region and Field Laboratories and forensics and research by HQ or regions for specific or nonspecific projects. Samples can be linked to a QA test and IA test by Lab Control Number if needed. Sample and testing of materials to qualify a supplier’s product to be used on CDOT projects. APL and QML may use this Sample Type and Acceptance Method to submit samples for approval to be included on the APL. .

NO



Method Comments

Project Pay

Preconstruction Testing

Sample and Test

Samples submitted by the region or staff specialty units (Geotech, Concrete, etc.) for design of a specific or nonspecific project in the future. Samples could be tested in the field, region or HQ labs. Pavement investigation, soil surveys, etc. If a preconstruction project number changes over time, it will be recorded in a field in the OTHER tab "Preconstruction Project Number". Samples with tests being conducted in different labs would be linked by Lab Control Number.

NO

NA APL

“z DO NOT USE - Product Evaluation Coordinator Only”. To be used only by the Product Evaluation Coordinator to be able to export materials to the web based APL list.

NO

Table 5.2 Sample Method and Acceptance Method Result Combinations

Sample Type

Acceptance Method Results

QA Sample and Test OK

PRE Sample and Test OK

INFO Sample and Test OK

IAT Sample and Test OK

COC COC OK

CTR CTR OK

APL OK

QA COC Error, do not save sample

PRE COC Error, do not save sample

INFO COC Error, do not save sample

IAT COC Error, do not save sample

QA CTR Error, do not save sample

PRE CTR Error, do not save sample

INFO CTR Error, do not save sample

IAT CTR Error, do not save sample

QA APL Error, do not save sample, APL for use only for Product Evaluation

PRE APL Error, do not save sample, APL for use only for Product Evaluation

INFO APL Error, do not save sample, APL for use only for Product Evaluation

IAT APL Error, do not save sample, APL for use only for Product Evaluation

COC APL Error, do not save sample, APL for use only for Product Evaluation

CTR APL Error, do not save sample, APL for use only for Product Evaluation



LINK TO: CDOT will not use. LINK FROM: CDOT will not use. TOWN: CDOT will not use. GEOGRAPHIC AREA: Drop-down menu. CDOT will not use.

Code Table = GEOGAREA – Geographic Area

Code Description

* CDOT will not use

LOCK TYPE: CDOT will not use, CDOT will use LIMS sample security. Anyone with proper security will be able to make changes to sample log, not just creator of sample log. LOCKED BY: CDOT will not use, indicates who locked the sample. Controlled by System Parameters. LOCK DATE: CDOT will not use, indicates the date and time the sample records was locked. Controlled by System Parameters.


5.1.2 Addtl Sample Data Panel

Use the Addtl Sample Data panel to record additional information about the sample including associated mix designs.

Figure 5.3 Maintain Sample Information Window - Addtl Sample Data Panel


Table 5.3 Maintain Sample Information Window - Addtl Sample Data Panel - Fields


Smpl ID N/A Auto-populated. Sample ID. --

Buy American No (CDOT will not use) --

Buy American (2

nd field)


Reqst By Yes Free Form. Requested By. Person, department or agency that requested the sample. Optional.

50

Witnessed By Yes Search. ID of the person who witnessed the sample being taken, must be a qualified sampler.

--

Smpl Size Yes Free Form. Sample Size. Size or amount of the material sample being submitted for testing.

10

Unit (no label)

Yes Drop Down. Unit associated to the quantity of the sample represented in the Smpl Size field.

--

Dist from Grade Yes Free Form. Distance From Grade. Distance from finished grade for height of fill, height of test, and test depth measurements.

18

Length Yes Drop Down. Length of measure in which the distance from finished grade is measured.

--

Station Yes Free Form. Station point or Mile Post along the survey line where the sample was taken.

10

Offset Yes Free Form. Distance and direction from the reference point where the sample was taken.

10

Reference Yes Free Form. Location referenced on the plans where the sample was taken. Structure number, Mile Post, inlet number, etc.

10

Smpld From Yes Free Form. Sampled From. Description of where the sample was taken. Stockpile, plant, windrow, etc.

38

Smpl Origin Yes Free Form. Sample Origin. Description of where the sample originated.

20

Control Type Yes Drop Down. Provides an additional identifier for the sample. QC/QA uses this field for the identification of its process. Examples are heat number, lot number, batch number, etc.

--

Cntrl Number Yes Free Form. Control Number. Actual number for the type of control to identify the sample. QC/QA uses this field for a number count of samples in the process.

20

Seal Number No Free Form. Used to assign an material specification Effective Date in the form mm/dd/yyyy

10

Design Type Yes Drop Down. Indicates the type of mix design to which the selected material is associated (PCCP, SUPERPAVE, or Marshall only).

--

Mix ID Yes Search or Free Form. Uniquely identifies the mix design.

14

Plant ID No (CDOT will not use) --



Plant Name No (CDOT will not use) --

Plant Type No (CDOT will not use) --

Creator User ID Yes Auto-populated. User ID of the user who created the sample record.

--

Include Standard Remarks


Last Modified User ID Yes Auto-populated. User ID of the last user to modify the sample record.

--

Last Modified Date Yes Auto-populated. Date of the last modification made to the sample record.

--

Sample Created from DWR


DWR Date No (CDOT will not use) --

DWR Inspector No (CDOT will not use) --


SAMPLE ID: Auto-populate from Basic Sample Data tab. REQUEST BY: Enter at sampler’s request. May be required by procedure WITNESSED BY: May be applicable based on material. By sampler, “consultant”, “contractor”, or qualified sampler if person creating sample is not a qualified sampler/tester. SAMPLE SIZE:

First box, free form, procedural required, enters number of samples. Sample Units: drop down list of units, type of sample etc. Need to inform preconstruction to enter any other items we want to add. Cans, buckets, cylinders, bags, etc. See Code Table UNITTYP – Unit Type Code above.

DISTANCE FROM GRADE: Enter number in box. Drop down, Feet, inches, populated by length measurements. Positive number, 2 feet below grade.

Drop down cross over from other tables, must use drop down if number is entered in box.


Code Table = LENGTH – Length Unit of Measure

Code Description

cm Centimeter

ft Foot

in Inch

km Kilometer

m Meter

mile Mile

mm Millimeter

yd Yard

STATION: Letters and numbers, mandatory for some items, 403, 203 etc. Station or MP. MP can also be entered in Reference box. OFFSET: Mandatory for most items. Offset from Center Line (CL), left, right. REFERENCE: Structure number, or MP if station is placed in Station box, left, right. SAMPLE FROM: Procedure required physical location, behind paver, plant, belt, stockpile, joint, mat, back of truck, end of pump, etc. SAMPLE ORIGIN: Required for Soil Survey Sample enter Hole number (1A, 1B, etc.) optional, samplers choice. Country of origin. CONTROL TYPE: Drop down. Information only. Procedure required, Heat number, Bill of Lading (BOL), Batch Number, Ticket Number, Lot Number, etc.

Code Table = CNTRLTYP – Control Type

Code Description

BAT Batch Number

CAT Catalog Number

CLA Class

DES Design Number

HEA Heat Number

LOT Lot Number

MOD Model Number

NFS NFS Rating

PRO Process

PTS Process Test Section

SER Serial Number

STY Style

TYP Type

CONTROL NUMBER: Free form. Procedure required, 20 digits capacity, in conjunction with Control Type, Heat number, Ticket Number, etc.


SEAL NUMBER: Required, (Effective Date) enter material effective specification date or Project Special Provision effective date for material submitted. In LIMS, the designated tester must choose a specification for the template if there are multiple. Each test template must have been assigned a “z” template in order to have an Effective Date. Material specifications are entered in the Material Detail window for each Material Code by the CDOT Pavement Management Group. The Project must notify the Pavement Management Group of any Special Provisions that have differing material specifications from the Standard Project Specifications in order for the materials test results to be validated. DESIGN TYPE: Drop down, locked by system, related to mix design window list. Procedure required, if it is involved in the sample type submitted. Use only PCC and Superpave at this time.

Code Table = DSNTYPE – Design Type

Code Description

AGG Aggregate

PCC PCC

SUP SUPERPAVE

MIX ID: Procedure required, search box from choice of PCCP or SuperPave. CREATOR USER ID: Auto-populated. The User ID of the person who created report. INCLUDE STANDARD REMARKS: Check box. Include Status Standard Remarks to printout of sample report. Samplers Choice. LAST MODIFIED USER ID: Auto-populated. User ID. LAST MODIFIED DATE: Auto-populated. Date.

5.1.2.2 CDOT will not use Fields BUY AMERICA: CDOT will not use. BUY AMERICA: (2nd Field) – CDOT not using. PLANT ID: CDOT will not use. PLANT NAME: CDOT will not use. PLANT TYPE: CDOT will not use. INCLUDE STANDARD REMARKS: CDOT will not use. SAMPLE CREATED FROM DWR: CDOT will not use. DWR DATE: CDOT will not use. DWR INSPECTOR: CDOT will not use.


5.1.3 Contract Panel

Use the Contract panel to associate a sample to a particular contract by project (or contracts). Associate a sample to a contract at the line item level. That is, sample is kept on the line item within the project within the contract. Record a represented quantity to be associated with the contract.

Figure 5.4 Maintain Sample Information Window - Contract Panel


Table 5.4 Maintain Sample Information Window - Contract Panel – Fields


Key information

Sample N/A Auto-populated. Uniquely identifies the record generated for the material sample.

--

Contract information

Contract ID N/A Auto-populated. Uniquely identifies the contract with which the displayed material is associated.

--

Project N/A Auto-populated. Uniquely identifies the project. --

Line Item N/A Auto-populated. Uniquely identifies an item associated with a contract.

--

Item Code N/A Auto-populated. Uniquely identifies an item. --

Fed State Prj Nbr

N/A Auto-populated. Federal, State, or Province Project Number.

--

Cont Est Matrl Qty

N/A Auto-populated. Contract Estimated Material Quantity. Quantity expected to be placed over the life of the contract based on the current pay item quantity to conversion factor relationship identified in the contract sampling and testing requirements.

--

Represented Qty Yes Free Form. Represented Quantity. Amount of material the COC or CTR for the sample represents.

12

Material Unit N/A Auto-populated. Unit of measure of the material. --

Reported Matrl Qty

N/A Auto-populated. Reported Material Quantity. Total material installed.

--

Satisfy Rep Matrl Qty

N/A Auto-populated. Satisfied Represented Material Quantity. Total material quantity reported on the Maintain Sample Information window’s Contract panel. For the given item, the Total Represented Quantity of satisfied samples for the material.

--

Line Item Desc N/A Auto-populated. Line Item Description. Describes a particular item.

--

Supplemental Description 1

N/A Auto-populated. Description of the item that is supplemental to the item's description.

--

Supplemental Description 2

N/A Auto-populated. A second description of the item that is supplemental to the item's description.

--

Contract Description

N/A Auto-populated. Describes the contract. --

5.1.3.1 Additional CDOT Notes

Do not use if sample is not for specific contract sampling and test.

Must be used if sample is to be used for a specific contract.

The Documentation Unit must generate contract items before information can be entered.


Representative Quantity Field: Enter quantity represented for the specific COC or CTR. For multiple COC’s or CTR for a specific material code, only enter the quantity for a particular COC or CTR per Sample ID.

o Example, for guardrail the project total quantity is 1000 LF. The contractor only delivers 500 LF with 1 COC and 1 Heat Number; enter 500 in the Represented Quantity field. When the remaining 500 LF are delivered with a different COC and Heat Number record that quantity under a new Sample ID. See Screenshot

o For all Sample ID’s the total quantity at the end of the project should equal the total plan quantity amount for each item.

o For CMO's ,info will not be available, fill out as much info as possible and complete all sample info after CMO is approved and material added to contract.

Figure 5.5 Maintain Sample Information Window - Contract Panel


REMARKS CDOT has no specific use for this field, although this is available for use as needed. Mixed case. ATTACHMENTS Optional.


PROCESS STATUS This window is available almost system wide by selecting Process Status from the Services menu. The window consists of two tab pages: Regular and Scheduled. REGULAR TAB The Regular tab page lists Distributed Processing Services (DPS) submitted processes; that is, Report Template Facility (RTF) custom report processes, SiteManager PowerBuilder reports, and background or batch processes. Here, authorized users can see the current status of submitted processes, delete submitted or complete jobs, or drill down to view or print the output produced by completed or failed processes. SCHEDULED TAB The Scheduled tab page lists DPS submitted processes; that is, RTF custom report processes, SiteManager PowerBuilder reports, and background or batch processes. Here, authorized users can see the current status of submitted processes, delete submitted or complete jobs, or drill down to view or print the output produced by completed or failed processes. The processes listed on the Scheduled tab are those processes which have be set to run on a specific schedule by an authorized user. Standard SiteManager window and tab-level security applies to the scheduled tab page window. Only those processes to which the user has been assigned security access will be presented on the displayed list. PRINT LABEL Prints a label to document what the sample is. It is shipped with the sample. LIMS Opens the SiteManager LIMS part of SiteManager – Materials.

5.1.4 Other Panel Use the Other panel to assign the current sample to entities other than contracts. Examples of other entities include Destination Lab (for LIMS) or Preliminary Soil Survey, Research Project Number, Design Project Number, Forensics, Permit Number. The Destination Lab type must be populated for a sample for it to be available in LIMS. The user then has the option to assign tests.


Figure 5.6 Maintain Sample Information Window - Other Panel

Table 5.5 Maintain Sample Information Window - Other Panel – Fields


Type Yes Drop Down. List of attributes to track a sample. Destination lab is required to have a sample tested.

--

ID Yes Search. A value representing the entity. --

Description N/A Auto-populated. Description associated to the selected ID.

--


SAMPLE: Auto completed from using Sample ID TYPE: Drop-down. List of attributes to track a sample. Destination lab is required to have a sample tested.


Code Table = OTHTYPE – Other Type

Code Description

DSGN Design Project Number

DEST Destination Lab

FRCS Forensics

INSP Inspection Agency Code

PRMT Permit Number

FACN Plant ID

PRLM Preliminary Soil Survey

RSCH Research Project Number

USER User ID for email notification

ID: Choices dependent on Sample Type, either populated or free form.

Email User: locked, search, select users and email notice that testing is complete to their Site Manager Inbox. Sample Choice, benefits, will notify you sample is complete or have email sent to PE or other testing if the person who submits the sample is not available or no longer on the project.

DESCRIPTION: Auto-populated. Description associated to the selected ID. Some IDs would net a blank description.

5.1.5 Tests Panel

CDOT will not use this panel at this time.

Access to this panel will be limited to CDOT personnel and denied to consultant personnel.

Use the Tests panel to identify the tests to be performed on the sample and to enter the results of the tests. The user can identify tests that have been defined for the material. It also allows the user to track when the test starts and is completed. A test method may be performed on a material more than once since a unique Sample Test Number must be assigned to each test.

When a sample is being tracked using LIMS then the Tests panel will be set to inquiry only for all users. The Tests panel will display all the test details from the time the sample is assigned to LIMS to the final authorization of sample.


Figure 5.7 Maintain Sample Information Window - Tests Panel

Table 5.6 Maintain Sample Information Window - Tests – Fields


Test Method N/A Uniquely identifies a test template that will be used to capture the test data.

--

Lab ID N/A Uniquely identifies a lab. Agency-defined. --

Sample Test Nbr N/A Sample Test Number. Pertains to the run of the test. --

Received Date N/A Date the associated test began. Defaults to the current date.

--

Charge Amount N/A Amount charged for the test. --

Start Date N/A Date the test results were first entered. --

Estimated Completion Date

N/A Date the test is expected to be completed. --

Actual Completion Date

N/A Date the test results were completed. Required for sample authorization.

--

5.1.5.1 Additional CDOT Notes

Disable this tab, will be done in LIMS.

Inquire (view) only for this tab, will show completed test results, but will not be able to be edited.


5.1.6 Assigning Tests to a Sample

Assign tests to a completed sample record using the Open Assign Tests button (The T icon on the toolbar.). Expand the Assign Sample Tests window by clicking the More button to reveal tests that can be assigned. Once you save tests, you cannot reassign them and the Open Assign Tests button is no longer available. Note: The Open Assign Tests button is only available after a user has assigned a material code, sample type, and a destination lab on the sample record. Note: Before assigning tests, make sure that all sample information is correct. If tests are assigned incorrectly, contact your lab manager. Lab Managers can access the Maintain Test Queue window, where tests can be added or removed from sample records. Note: CDOT will not use default tests. The following are instructions on how to assign tests to a sample.

1. On the toolbar, click the Open Assign Tests button. (This button looks like a large ‘T’.) 2. In the Assign Sample Tests window, click the More button. 3. In the Additional Available Tests pane, sort the list by clicking the name of the Test Method

column. 4. In the Additional Available Tests pane, move the scroll bar to the right to view the test methods. 5. Highlight the rows of the tests to be assigned. 6. Click the Add button. 7. In the Tests to be Assigned pane, highlight the rows for any tests to be removed and click the

Remove button. 8. Click the Save Tests button. The status of the sample changes from Pending to Logged.

Table 5.7 Assign Sample Tests Window


ACCEPT

DEFAULT

TESTS


CANCEL No Button. Click if Open Assign Tests button (The T icon on the toolbar.) was clicked by mistake.

--

MORE Yes Button. Click to see the available tests to assign to the sample.

--

SAMPLE ID N/A* Auto-populated. Sample ID. Uniquely identifies a sample.

18

Smpl Type N/A Auto-populated. Sample Type. Identifies the type of sample taken. See Code Table SMPLTYPE.

--

MATERIAL

CODE N/A Auto-populated. The unique identifier of the material. 15

TEST

DESCRIPTION N/A Auto-populated. Name of the test. Agency-defined. --

LAB UNIT N/A Auto-populated. Name of the lab unit where the test will be performed.

--

TEST METHOD N/A Auto-populated. Test Method. Uniquely identifies a test. Agency-defined.

--


Figure 5.8 Assign Sample Tests Window – Initial

DEFAULT TEST No (CDOT will not use) --

TEST RQRD No (CDOT will not use) --

AUTO-FINALIZE No (CDOT will not use) --

TEST RUNS No (CDOT will not use) --

ADD Yes Button. Select tests In ‘Additional tests available for assignment’ pane, click Add to move them to Tests already assigned to the sample’ pane.

--

REMOVE No Button. Select tests In Tests to be Assigned pane, click Remove to move them to Additional Available Tests pane.

--

SAVE TESTS Yes Button. Click to save tests. Once saved, you cannot reassign them and the Open Assign Tests button is no longer available.

--

CANCEL No Button. Click to return to the Tests panel without assigning tests to the sample.

--


Figure 5.9 Assign Sample Tests Window – Selection

5.1.7 Service Menu for Maintain Sample Information Window

5.1.7.1 Drop-down Services Menu Use the Services menu to access many other functions related to the sample record.

Table 5.8 Service Menu for Maintain Sample Information Window - Services Menu – Choices


REMARKS Yes Free Form. Opens the remarks window for free-form data entry. Available from the Basic Sample Data, Addtl Sample Data, Contract, and Other panels.

2000+

ATTACHMENTS No PDF’s only. Optional. Provides the ability to add an attachment record to the sample record. Attachments should be limited in number.

AUTHORIZE Yes Authorizes the sample.

Available from the Basic Sample Data and Addtl Sample

--


OPEN ASSIGN TEST (“T” BUTTON):

DEFAULT TEST: tests with check marks are default. Some tests need to be added or be tested on different schedules, AC every 1000T, gradation every 2000T. Setup in the Test Assignment Information window in LIMS.

TEST REQUIRED: boxes checked mean tests are required. Setup in the Test Assignment Information window in LIMS.

AUTO FINALIZE: Will not be used by CDOT at this time.

Data panels with proper security clearances.

UNAUTHORIZE No Unauthorized the sample.

Available only from the Basic Sample Data panels with proper security clearances.

--

REVISE No Provides means to revise an existing sample.

Available from the Basic Sample Data panel after a sample has been authorized.

--

LAB REPORT No Provides a report of the sample information.

Available from the Basic Sample Data and Addtl Sample Data panels.

--

TESTERS No Provides a look-up of testers that are qualified for the selected test method.

Available from the Tests panel when a test has been added.

--

ENTER/VIEW

TEST DATA No Opens the material test template associated with the

selected test method.

Available from the Tests panel when a test has been added.

--

RELATED

SAMPLE TESTS No Tests performed on the original sample. Available on the

Tests panel of the sample record that is revising another sample.

Available from the Tests panel for a Revised Sample.

--

COPY SAMPLE No Copies an existing sample record. Can copy an existing lab control number or create a new lab control number.

Available from the Basic Sample Data panel.

--

DISPOSITION

REMARKS No Provides the ability to add disposition remarks to a

sample. Only field that can be changed after a sample is authorized. Disposition remarks print on the lab report.

Available from the Basic Sample Data and Addtl Sample Data panels for an Authorized Sample.

--

ASSIGN TESTS Yes Assigns test methods based on the material on the sample created. Only available after a material code, sample type and destination lab are chosen and the Sample Status is Pending.

--

PRINT LABEL Yes Prints sample data on a single 1” X 3.5” size label. Sample ID, Date, Lab Control Number, Material Description, and Lab Reference Number (see below).

--

LIMS Yes Launches LIMS. --


TEST RUNS: default 1, can be changed if more tests required. Setup in the Test Assignment Information window in LIMS.

TEST DESCRIPTION: describes test. Setup in the Test Assignment Information window in LIMS.

Once the tests are saved, the sample is now considered LOGGED in the Status box on the Maintain Sample Info window. Labs will also be listed in the Additional Sample Data window.

Sample is now placed in a sample logging queues. Receive Sample at Destination Lab, Receive Sample at Lab Unit or Enter Test Results queues depending on how the region or lab has the process set up.

PRINT LABEL: Use, samples would only need Sample ID, may use Lab Reference Number section to separate samples at HQ enter PCCP, HMA, Soils, etc.

5.1.8 Reports

CDOT will not use this functionality. CDOT will develop custom reports for data collected by tests on the materials and recorded on templates for each test method assigned to a sample. There are no custom reports associated with the Material Information window. Reports for completed tests can be accessed by opening a sample using FILE, OPEN and selecting or searching for the appropriate sample. Select the sample and click OK, a report with the samples project information, test results and test methods will be displayed. This report can then be saved (.pdf) or printed and kept in the project records. Central lab will use this function to satisfy AMRL requirements of test documentation.


Figure 5.10 Generic SiteManager Lab Report (First Screen)


Figure 5.11 Generic SiteManager Lab Report (Second Screen)



The major decision/discussion points for the Maintain Sample Window were related to formatting the Sample ID. The following format was adopted:

Sample ID: Auto-populated, 18 characters max, Format:

-User ID-YY-M-D-Military Time -User ID: name of person -Year: last two digits of year when sample was submitted -Months: are January-December is 1-9, A, B, C -Days 1-31: are 1-9, A-V -Military Time: time without colons Example: smith10AF114525, Smith (smith) submitted a sample on 2010 (10), October (A), 15 (F), at 11:45:25 (114525).

Sample Type: Drop Down. Identifies the type of sample taken. Figure 5.12 shows graphically the relationship of CDOT’s Quality Assurance System Elements of QA Test and IAT.

Figure 5.12 CDOT Quality Assurance System Elements

Lab Reference Number: Free Form, Date, DD/MM/YYYY


This field is to communicate from the field tester to the lab what specification effective date is to be used for the sample. This information carries from the Maintain Sample information window to the Enter Test Results window in LIMS where the Effective Date is to be selected from a dropdown menu.

Contract Panel, Represented Quantity: Free Form

For Materials that have the Accepted Method of COC and/or CTR this is to be completed with the quantity of materials that a particular COC or CTR represents.

Example: For guardrail, a COC may only represent 500 LF on a project that has a plan quantity of 1000 LF. A Sample is created for the COC that represents that 500 LF that has been delivered and installed. The tester will enter 500 in the Represented Quantity field and when the remaining material is delivered and installed with a different COC, and then the tester will enter that quantity in the new Sample. At the completion of the project, all of the Represented Quantities for each Sample ID for a particular material code must be equal to the projects plan quantity.

TESTING AND TRAINING SUGGESTIONS: Multiple Exercises for Maintain Sample: Most Samples will be QA type; however, it would be useful to do a COC/CTR exercise as well. IAT will be done by only a handful of people who will be the Region Power Users. PRE type will be very small percentage. QA Sample Type with a material code Asphalt – 403, Soils – 203, Concrete – 601. Copy Sample then use INFO as the Sample Type. COC/CTR with a material code Guardrail – 710, Delineator Posts – 612

5.2 Find Sample Window

SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > SAMPLING AND TESTING > FIND SAMPLE

Security Procedure: CDOT update authority for this window should be limited to Technical Support, IT System Administration, Region Materials Office, CDOT Sampler and Testers, Consultant Testers, CDOT and Consultant Project Engineers, and Central Lab Unit Groups (Binder, Flexible Pavement and Chemical; Concrete/Physical Properties; and Soils).

Functional Procedure: Use the Find Sample window to search for sample records based on specific criteria. A minimum of one search criteria must be selected. Multiple search criteria can be selected to narrow the results.


5.2.1 Find Sample Panels

Figure 5.13 Find Sample Parameters Window (First Screen)

Figure 5.14 Find Sample Parameters Window (Second Screen)


Table 5.9 Find Sample - Fields


Geographic Area No (CDOT will not use)

Sampled By Yes Search/Free Form. ID and full name of the person who took the sample.

9

Material Code Yes Search/Free Form. Uniquely identifies the material.

20

Producer/Supplier Code

Yes Search/Free Form. Name of the producer/supplier for the material.

20

Sample Date Yes Search/Free Form. Date the sample was taken. MM/DD/YY

Contract ID Yes Search/Free Form. Uniquely identifies the contract.

20

Project Yes Search/Free Form. Uniquely identifies the contract project.

18

Line Item Yes Search/Free Form. Uniquely identifies an item associated with a contract.

18

Item Code Yes Search/Free Form. Uniquely identifies a pay item associated with a sample record. Not contract specific.

20

5.3 Sample and Testing Requirements Window SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > SAMPLING AND TESTING > SAMPLING & TESTING REQUIREMENTS

5.3.1 Sample and Testing Requirements Panels See Section 2.3 Maintain Sample and Testing Requirements Window for further explanation.

5.4 Standard Sample Remarks Window

SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > SAMPLING AND TESTING > STANDARD SAMPLE REMARKS

CDOT will not use at this time. Use the Standard Sample Remarks window to store optional standard remarks that will be added to any sample’s Lab Report when the Include Sample Remarks indicator is selected on the Maintain Sample Information window’s Addtl Sample Data panel.

Security Procedure: CDOT update authority for this window should be available to Technical Support, IT System Administration, and Central Lab Pavement Design Program. Inquire rights would apply to Regional Materials Office.


Functional Procedure: If CDOT wanted to use we will use this window to record general remarks about a material, sample, COC, etc. This information may include but not limited to; Price Reduction amounts and calculations, condition of the sample (wet or dry), Material Exception notes, etc. Standard Sample Remarks will be included on test reports. Choose the appropriate Code Description or Remark type and enter remarks in blank field. To access the Remarks, from the Maintain Sample Information window’s Services menu, click the Remarks choice. To close Remarks, from the Maintain Sample Information window’s Services menu, click the Remarks choice. Alternatively, Use the Remarks bubble icon in the toolbar to open and close Remarks bubble. Note: To access the Lab Report, from the Maintain Sample Information window’s Services menu, click the Lab Report choice.

5.4.1 Standard Sample Remarks Panel

Figure 5.15 Standard Sample Remarks Window


Table 5.10 Standard Sample Remarks - Fields

Field Name

Required Description Characters

Code Description

Yes Selection. Includes a list of all available sample statuses. When selected, the lower pane displays the remark that will be added to the Standard Remarks field on the Lab Report. The agency-defined remark will only appear if the Include Sample Remarks indicator is selected on the Maintain Sample Information window’s Addtl Sample Data panel.

--

5.5 LIMS View-Only Sample Information Window

LIMS Navigation LIMS NAVIGATION PANEL > LIMS > VIEW-ONLY SAMPLE INFORMATION

Security Procedure: CDOT update authority for this window should be available to Technical Support, IT System Administration, Central Lab Pavement Design Program, Region Materials Office, CDOT Managers, CDOT Samplers and Testers, Consultant Testers, CDOT and Consultant Project Engineers, Central Lab Unit Groups (Binder, Flexible Pavement and Chemical; Concrete/Physical Properties, and Soils), and Finals Engineers.

Functional Procedure: Use the View-Only Sample Information window to apply a filter to locate sample records. Then, for the selected sample record, view information about the sample and any associated tests in a read-only format. The information is organized on separate panels: Sample Detail, Contract Details, Other Details, Sample Received, Tests Assigned, and Test Status. Each of the panels has tab-level security. All of the information in this window is VIEW ONLY and cannot be manipulated in any way. Select a Control Number in upper half of the window to view the sample information in the lower half of the window. Note: This window does not include detailed test results.


5.5.1 View-Only Sample Information Panel (Upper Pane)

Figure 5.16 View-Only Sample Information Window - Upper Pane

Table 5.11 View-Only Sample Information Window - Upper Pane – Fields


Inquiry-only fields (in alphabetical order)

Control Number Yes Select. Control number for the sample. Highlight the CN of the sample you would like to view. The sample will show up in the bottom half of the screen.

--

Geographic Area *

N/A (CDOT will not use) --

Lab Control Number

N/A Auto-population. An umbrella number for grouping samples. Allows samples to be linked together for testing and sample review purposes.

--

Last Modified By N/A Auto-population. User ID of the last user to modify the sample record.

--

Lab Ref Number N/A Auto-population. Laboratory Reference Number. Often simpler than the auto-generated sample ID.

--

Log Date N/A Auto-population. Date on which the sample is entered into SiteManager.

--

Logged By N/A Auto-population. User ID of the user who created the sample record.

--

Manufacturer * N/A Auto-population. Manufacturer of the product --


5.5.2 Sample Details Panel Use the Sample Details panel to view information regarding the sample data entered on the Maintain Sample information window’s Basic and Addtl Data panels.

selected. May be required.

Material Code N/A Auto-population. Uniquely identifies a material. --

Material Name N/A Auto-population. Describes the material. --

Plant ID N/A Auto-population. Uniquely identifies the approved producer/supplier plant that provided the material.

--

Producer Supplier *

N/A Auto-population. Name of the producer or supplier of the material.

--

Product Name N/A Auto-population. Brand name of material. --

Requested By N/A Auto-population. User ID of the user who requested the sample.

--

Sample Date N/A Auto-population. Date the sample was taken. --

Sample Finalized Date

N/A Auto-population. Authorized Date. Date the sample was authorized (completed).

--

Sample ID N/A Auto-population. Uniquely identifies a sample. Pertains to the material(s) being tested and/or accepted for a contract. Required.

--

Sample Status N/A Auto-population. Displays the current status description of the sample record.

--

Sample Type N/A Auto-population. Sample Type. Identifies the type of sample taken (for example, acceptance, job control). Used by LIMS in the default assignment of tests for the sample.

--

Sampler N/A Auto-population. User ID of the sampler who took the sample.

--

Seal Number N/A Auto-population. Seal number of the batch of the material sampled.

--


Figure 5.17 View-Only Sample Information Window (Lower Pane) - Sample Details Panel

Table 5.12 View-Only Sample Information Window (Lower Pane) - Sample Details Panel - Fields


Inquiry-only fields (in layout order)

Smpl ID N/A Auto-population. Sample ID. Uniquely identifies the record generated for the material sample.

--

Lab Control Number

N/A Auto-population. Lab Control Number for the sample ID

--

Lab Ref Number N/A Auto-population. Laboratory Reference Number. Often simpler than the auto-generated sample ID.

--

Material N/A Auto-population. Uniquely identifies a material. Agency-defined.

--


N/A Auto-population. Name of the material. --

Sample Status N/A Auto-population. Indicates the status of the sample as it progresses through its lifecycle.

--

Sample Type N/A Auto-population. Type of sample. --

Smpld By N/A Auto-population. User ID of the user who sampled the material.

--

Sample Date N/A Auto-population. Date when the sample was taken. --

Log Date N/A Auto-population. Date on which the sample was --


entered into SiteManager.

Geographic Area N/A Auto-population. Geographic Area. Location where the sample was taken. Agency-defined.

--

Authorized By N/A Auto-population. User ID of the person that authorized (completed) the sample.

--

Authorized Date N/A Auto-population. Date when the sample was authorized (completed).

--

Acceptance Method

N/A Auto-population. Acceptance Method. Method by which the sample is being accepted.

--

Producer Supplier

N/A Auto-population. The code, name and address associated with the Producer / Supplier of the sample.

--

Manufacturer N/A Auto-population. Manufacturer of the product selected.

--

Plant N/A Auto-population. Plant ID and name of the approved producer/supplier plant that provided the material.

--

Plant Type N/A Auto-population. Identifies the type of plant from which the material was supplied.

--

Mix Design Type N/A Auto-population. Indicates the type of mix design to which the selected material is associated (Marshall, SUPERPAVE, or PCCP).

--

Mix ID N/A Auto-population. Uniquely identifies the mix design. --

Product Name N/A Auto-population. Brand name of material. --

Reference N/A Auto-population. Location referenced on the plans where the sample was taken.

--

Station N/A Auto-population. Station point along the survey line where the sample was taken.

--

Offset N/A Auto-population. Distance and direction from the reference point where the sample was taken.

--

Dist from Fnshd Grd

N/A Auto-population. Distance from Finished Grade. Distance from finished grade for height of fill, height of test, and test depth measurements.

--

Sample Origin N/A Auto-population. Sample Origin. Description of where the sample originated.

--

Town N/A Auto-population. Name of the town where the sample, lab, or equipment is located. Agency-defined.

--

Sampled From N/A Auto-population. Sampled from information associated with the sample

--

Requested By N/A Auto-population. Person, department or agency that requested the sample.

--

Intended Use N/A Auto-population. Description of intended use of the material.

--

Buy USA N/A Auto-population. Indicates if the material sampled fulfills the requirement for the Buy USA program.

--

Witnessed By N/A Auto-population. ID of the person who witnessed the sample being taken.

--

Represented Qty N/A Auto-population. Represented Quantity. Quantity of --


5.5.3 Contract Details Panel

Use the Contract Details panel to view the contract information entered on the Maintain Sample Information window’s Contract panel for the associated the sample ID.

Figure 5.18 View-Only Sample Information Window (Lower Pane) - Contract Details Panel

the sample being associated with the contract or the quantity of material represented by the sample.

Sample Size N/A Auto-population. Size of the material sample being taken.

--

Linked Sample ID N/A Auto-population. Sample ID linked to the current sample ID.

--

Revised from Sample ID

N/A Auto-population. Sample ID from which the current sample ID is revised.

--


Table 5.13 View-Only Sample Information Window (Lower Pane) - Contract Details Panel - Fields


Inquiry-only fields (in alphabetical

order)

Contract ID N/A Auto-population. Uniquely identifies the contract with which the displayed material is associated.

--

Line Item Nbr N/A Auto-population. Line Item Number. Uniquely identifies an item associated with a contract.

--

Project Nbr N/A Auto-population. Project Number. Uniquely identifies the project.

--

Represented Qty N/A Auto-population. Represented Quantity. Amount of material the sample represents.

--

5.5.4 Other Details Panel Use the Other Details panel to view information regarding the data entered on the Maintain Sample Information window’s Other Data panel (OTHTYPE).

Figure 5.19 View-Only Sample Information Window (Lower Pane) - Other Details Panel


Table 5.14 View-Only Sample Information Window (Lower Pane) - Other Details Panel - Fields



Other Information N/A Auto-population. Value populated for the code ID for the Other Type field.

--

Other Type N/A Auto-population. Description of the code ID defined for ‘OTHTYPE’ which is used on the Maintain Sample Information window.

--

5.5.5 Sample Receive Panel

Use the Sample Receive panel to view information about when sample was received at the destination lab and the lab unit.

Figure 5.20 View-Only Sample Information Window (Lower Pane) - Sample Receive Panel


Table 5.15 View-Only Sample Information Window (Lower Pane) - Sample Receive Panel - Fields



order)

Dest Receive Date

N/A Auto-population. Destination Receive Date. Date when the sample was received at the destination lab.

--

Lab Unit Receive Date

N/A Auto-population. Date when the sample was received in the lab unit.

--

Receiving Destination

N/A Auto-population. Name of the destination lab that received the sample.

--

Receiving Lab Unit

N/A Auto-population. Name of the lab unit that received the sample.

--

5.5.6 Tests Assigned Panel Use the Tests Assigned panel to view all the tests assigned to the sample which were marked as Reportable by the Lab Supervisor. Click the Remarks button to view all internal-only remarks (LMSREMIN) entered for the selected test.

Figure 5.21 View-Only Sample Information Window (Lower Pane) - Tests Assigned Panel


Table 5.16 View-Only Sample Information Window (Lower Pane) - Tests Assigned Panel - Fields



order)

Smpl Tst Nbr N/A Auto-population. Sample Test Number. Incremental number assigned to a test on a sample.

--

Test Description N/A Auto-population. Name of the test. Agency-defined.

--

Test Method N/A Auto-population. Uniquely identifies a test. --

5.5.7 Test Status Panel Use the Test Status panel to view the statuses of all the tests assigned to the sample. Click the Remarks button to view all public remarks (LMSRMRKS) entered for the selected test.

Figure 5.22 View-Only Sample Information Window (Lower Pane) - Test Status Panel

Table 5.17 View-Only Sample Information Window (Lower Pane) - Test Status Panel - Fields



order)

Actl Complt Dt N/A Auto-population. Actual Completion Date. Date when the test was marked as complete.

--


5.6 LIMS Receive Sample at Destination Lab Window

LIMS Navigation LIMS NAVIGATION PANEL > LIMS > RECEIVE SAMPLE AT DESTINATION LAB

CDOT will not use at this time. All samples should bypass this window and be directed to the Receive Sample at Lab Unit or the Enter Test Results window. Each Region and Central lab will decide the sample receiving flow in each lab. Use the Receive Sample at Destination Lab window to receive samples in a formal receiving area. When samples are created, the users will indicate what destination lab(s) where the sample will be shipped for testing. In most cases, destination labs first receive the sample. However it is possible to indicate that a destination lab be skipped and directly sent to the lab units. The Receive Sample at Destination Lab window displays all the samples that are yet to be received by the destination lab. The Select Sample Location dropdown list contains all destination labs defined in LIMS. Samples are limited by the contract authority of the user logged in to the system. If a sample has no contracts associated, it will be available to any user who meets the other security conditions.

Chrg Amt N/A Auto-population. Charge Amount. Pertains to the test. --

Due Dt N/A Auto-population. Due Date. Due date assigned to the test.

--

Lab Unit N/A Auto-population. Name of the lab unit where the test was performed.

--

Priority N/A Auto-population. Priority assigned to the test. --

Reportable N/A Auto-population. Indicates the test was or will be available to view on the Review Samples window.

--

Smpl Tst Nbr N/A Auto-population. Sample Test Number. Incremental number assigned to a test on a sample.

--

Start Dt N/A Auto-population. Start Date. Date when a user first recorded information in the test template.

--

Test Description N/A Auto-population. Name of the test. Agency-defined. --

Test Meth N/A Auto-population. Test Method. Uniquely identifies a test.

--

Test Result Val N/A Auto-population. Test Result Value. Final test result value for the template. Values: 1, 2 or 3. May represent In Spec, Out of Spec or No Spec.

--

Test Status N/A Auto-population. Status of the test. --

Tester ID N/A Auto-population. User ID of the tester assigned to perform the test.

--


5.6.1 Receive Sample at Destination Lab Panel

Figure 5.23 Receive Sample at Destination Lab Window

Table 5.18 Receive Sample at Destination Lab Window - Fields


Select Sample Location area (in layout order)

Select Sample Location Name of the destination lab where samples are being received. List contains all the destination labs.

Filter Criteria area (in layout order)

Filter Criteria Column names available from the Receive Sample at Destination Lab window.

Operator (no label) Operators for applying the filter criteria.

Value (no label) Value of the results that must be satisfied by the filter criteria.

Apply Click to filter list by selected criteria.

Reset Click to clear any selected filter criteria.

User Action fields (in alphabetical order)

Sample Received Use to indicate that the sample was received in the destination lab.


Contract ID All contracts assigned to the sample. Comma-separated.

Control Number Control number for the sample.

Geographic Area * Where the sample was taken.

Lab Control Number An umbrella number for grouping samples.

Lab Reference Number Simplified numbering scheme for samples.

Log Date Date when the sample was recorded.

Material Name Name of the material for which the sample is taken.

P/S Code Producer/Supplier Code. Uniquely identifies the producer or supplier of the material.

Plant ID Uniquely identifies the plant from where the material was sampled.

Product Name Brand name of the material from the producer/supplier.

Sample ID Uniquely identifies the sample.


5.7 LIMS Receive Sample in Lab Unit Window

LIMS Navigation LIMS NAVIGATION PANEL > LIMS > RECEIVE SAMPLE IN LAB UNIT

Use the Receive Sample in Lab Unit window to receive samples in the lab unit. Samples must be received at the destination lab unless the destination lab that the lab unit belongs to has been bypassed. The Receive Sample in Lab Unit window displays all samples that are to be received at the lab unit. The Select Lab dropdown list displays all labs to which the user belongs. Samples are limited by the contract authority of the user logged into the system. If a sample has no contracts associated, it will be available to any user who meets the other security conditions.

Security Procedure: CDOT update authority will be determined by each lab and contract. The minimum levels will include the CDOT update authority for this window should be available to Technical Support, IT System Administration, Central Lab Pavement Design Program, Region Materials Office, CDOT Sampler and Testers, Consultant Testers, and Central Lab Unit Groups (Binder, Flexible Pavement and Chemical; Concrete/Physical Properties, and Soils).

Functional Procedure: This window will be used to log samples into a specific lab unit. This window can be used to determine turnaround times for samples submitted to labs with a custom report. Each lab will decide to use or bypass this window. If a lab unit bypasses this window, then samples will be visible in the Enter Test Results window. Field labs will bypass this window because the field test will only be available to a specific contract. A tester/PE must be assigned to the contract to enter test results and authorize tests.

Sample Date Date when the sample was taken.

Sample Type * Type of sample.

Sample Requester User ID of the person requesting the sample.

Sampler User ID of the sampler.

Seal Number Seal number for the sample.


5.7.1 Receive Sample in Lab Unit Panel

Figure 5.24 Receive Sample in Lab Unit Window


Table 5.19 Receive Sample in Lab Unit Window - Fields


Select Lab Yes Drop Down. Name of the lab unit where samples are being received. List contains all lab units to which the user belongs.

--

Filter Criteria No Drop Down. Used to filter samples. Column names available from the Receive Sample in Lab Unit window.

--

Operator (no label)

No Drop Down. Operators for applying the filter criteria. --

Value (no label)

No Free Form. Value of the results that must be satisfied by the filter criteria.

--

Apply No Button. Click to filter list by selected criteria. --

Reset No Button. Click to clear any selected filter criteria. --

Sample Received

Yes Check Box. Use to indicate that the sample was received in the lab unit.

--

Contract ID N/A Auto-populated. All contracts assigned to the sample. Comma-separated.

--

Destination Receive Date

N/A Auto-populated. Date when the sample was received at the destination lab. No date displays if the destination lab was bypassed.

--

Geographic Area*

N/A Auto-populated. Where the sample was taken. --

Log Date N/A Auto-populated. Date when the sample was recorded. --

Material Name

N/A Auto-populated. Name of the material for which the sample is taken.

--

P/S Code N/A Auto-populated. Producer/Supplier Code. Uniquely identifies the producer of supplier of the material.

--

Plant ID N/A Auto-populated. Uniquely identifies the plant from where the material was sampled.

--

Product Name

N/A Auto-populated. Brand name of the material from the producer/supplier.

--

Sample Date N/A Auto-populated. Date when the sample was taken. --

Sample ID N/A Auto-populated. Uniquely identifies the sample. --

Seal Number N/A Auto-populated. Seal number for the sample. --

Procedure Below is a list of each Region and the labs in each. Field samples tested in the field will be separated by contract. Some region labs may not be used at this time, but maybe used more extensively in the future.


Table 5.20 Destination labs and Lab Unit Relationships

Destination Lab

DL Lab ID Lab Unit Lab ID Bypass Bypass

(50 characters)

(10 characters)

(50 characters)

(10 characters)

Destination Lab

Lab Unit

Region 1 Denver

R1DenverDL Region 1

Denver Lab R1DenvrLab Yes No

Region 1 Limon

R1LimonDL Region 1

Limon Lab R1LimonLab Yes Yes

Region 1 Tunnel

R1TunnelDL Region 1

Tunnel Lab R1TunelLab Yes Yes

Region 1 Mobile

R1MobileDL Region 1

Mobile Lab R1MobileLab Yes Yes

Region 2 Pueblo

R2PuebloDL Region 2

Pueblo Lab R2PueblLab Yes Yes

Region 2 Colorado Springs

R2CoSpgsDL Region 2 Colorado

Springs Lab R2CSpgsLab Yes Yes

Region 2 Lamar

R2LamarDL Region

2 Lamar Lab

R2LamarLab Yes Yes

Region 2 Mobile

R2MobileDL Region 2

Mobile Lab R2MobilLab Yes Yes

Region 3 Grand

Junction R3GrdJctDL

Region 3 Grand

Junction Lab

R3GrJctLab Yes Yes

Region 3 Glenwood

R3GlnwdDL Region

3 Glenwood Lab

R3GlnwdLab Yes Yes

Region 3 Craig

R3CraigDL Region 3 Craig Lab

R3CraigLab Yes Yes

Region 3 Mobile

R3MobileDL Region 3

Mobile Lab R3MobilLab Yes Yes

Region 4 Boulder

R4BouldrDL Region 4

Boulder Lab R4BouldLab Yes No

Region 4 Sterling

R4SterlgDL Region 4

Sterling Lab R4SterlLab Yes No

Region 4 Loveland

R4LovlndDL Region 4 Loveland

Lab R4LvlndLab Yes No

Region 4 Mobile

R4MobileDL Region 4

Mobile Lab R4MobilLab Yes No


Region 4 Evans

R4EvansDL Region 4

Evans Lab R4EvansLab Yes No

Region 5 Durango

R5DuragoDL Region 5 Durango

Lab R5DurgoLab Yes Yes

Region 5 Alamosa

R5AlamsaDL Region

5 Alamosa Lab

R5AlmsaLab Yes Yes

Region 5 Mobile

R5MobileDL Region

5 Mobile Lab

R5MobilLab Yes Yes

Region 6 Denver

R6DenverDL Region 6

Denver Lab R6DenvrLab Yes No

Statewide Field

StatFildDL Statewide Field Lab

FieldLab Yes Yes

Central Laboratory

Denver CLDenverDL Euro Lab EuroLab Yes No

Flexible

Pavement Lab

FlexLab Yes No

Physical

Properties Lab

PhPrLab Yes No

Concrete

Lab ConcLab Yes No

Chemical

Lab ChemLab Yes No

Soils Lab SoilLab Yes No

TESTING AND TRAINING Reminder: Regions 1(Denver), 4 and 6 will not bypass Lab Unit; thus, their samples will need to be received in the Lab Unit before test results can be entered. This needs to be tested by Region to determine if they want to receive all samples. Do not necessarily need to include in general training.

5.8 LIMS Enter Test Results Window

LIMS Navigation LIMS NAVIGATION PANEL > LIMS > ENTER TEST RESULTS

Use the Enter Test Results window to enter test results for tests which the user has qualifications. A test will display based on the following criteria:


Has a test status been identified in the LMSTSTQ code table.

Lab unit has the appropriate qualifications to perform the test.

Tester has the appropriate qualifications to perform the test.

Tester has the appropriate contract-level security to the sample records based on the contract authority and sample-to-contract associations. If a sample has no contracts associated, it will be available to any user who meets the other security conditions.

Security Procedure: CDOT update authority for this window should be limited to Technical Support, IT System Administration, Central Lab Pavement Design Program, Region Materials Office, CDOT Sampler and Testers, Consultant Testers, and Central Lab Unit Groups (Binder, Flexible Pavement and Chemical; Concrete/Physical Properties; and Soils) that have qualified testers from the qualified tester list.

Functional Procedure: CDOT will use this window to enter test results from both the field and lab. A sample will be selected in the top half of the window and the test results will be entered on the bottom half of the window. When all of the test results are entered the test will be marked COMPLETE and saved. The sample will then be sent to the Review Tests window for review.

5.8.1 Enter Test Results Panel

Figure 5.25 Enter Test Results Window


Table 5.21 Enter Test Results Window - Fields


Test Queue Criteria area (in layout order)

All My Lab Units Yes/No Check Box. Displays in the queue all tests for all lab units to which the user has access.

--

Select a Lab Unit Yes/No Drop Down. Drop-down list that contains names of the labs to which the user has access. Select the name of the lab unit where samples are to be received.

--


Filter Criteria Yes/No Drop Down. Column names available from the Enter Test Results window.

--

Operator (no label) Yes/No Drop Down. Operators for applying the filter criteria.

--

Value (no label) Yes/No Free Form. Value of the results that must be satisfied by the filter criteria.

150+

Select a Lab Unit (2

nd field)

Yes/No Drop Down. Name of the lab unit where samples are tested.

--

Apply Yes/No Button. Click to filter list by selected criteria. --

Reset Yes/No Button. Click to clear any selected filter criteria. --


Test Completed Yes Check Box. Select to indicate that a test is complete and all results have been entered. Click the Save button to progress the test to the Review Tests queue or another queue based on an alternative workflow.

--


Contract ID N/A Auto-populated. Uniquely identifies the contract. --

Due Date N/A Auto-populated. Due date assigned to the test. --

Effective Date Varies Drop Down or Auto-populated. Effective Date selected for the test template for specification checks. Populated with the effective date selected for the test template in relation to standard or project specification changes.

--

Lab Control Number N/A Auto-populated. Umbrella number used to group samples.

--

Lab Ref Number N/A Auto-populated. Lab Reference Number. Manually populated ID for a sample.

--

Lab Unit N/A Auto-populated. Name of the lab where the test will be performed.

--

Manufacturer N/A Auto-populated. Code and name of the manufacturer of the sample.

--


Material Code N/A Auto-populated. Material code for the sample ID.

--

Priority N/A Auto-populated. Priority assigned to the test. High, Medium or Low. Default is Medium. Selected on the Maintain Test Queue window.

--

Producer Supplier N/A Auto-populated. Code and name of the producer or supplier of the sampled material.

--

Receive Date N/A Auto-populated. Date when the sample was received in the lab unit.

--

Sample Date N/A Auto-populated. Date when the sample was taken.

--


Sample Type N/A Auto-populated. Type of sample. Code for and description of type of sample.

--

Sampler N/A Auto-populated. User ID of the person who took the sample.

--

Seal Number No (CDOT will not use.) --

Test Description N/A Auto-populated. Name of the test. --

Test Number N/A Auto-populated. Incremental number assigned to a test on a sample.

--

Test Started N/A Check Box/Auto-populated. Indicates whether test has been started by a tester. Auto-selected when test is modified and saved. May manually select check box to indicate that the test has been started.

--

Test Status N/A Auto-populated. Code and description of the current status of the test.

--

Tester N/A Auto-populated. User ID and name of the person selected to perform the test. Information only. Selected on the Maintain Test Queue window.

--

Lower pane fields/Test Template

< all fields > Varies CDOT-defined for each material test. Varies


ALL MY LAB UNITS OR SELECT A LAB UNIT: Pick one option to display test in the queue for all labs or select lab units. The tester must be qualified for the specific test method and assigned to that lab unit to view the lab units queue. FILTER CRITERIA: Use this filed if you wish to search for specific tests to enter data. EFFECTIVE DATE: Drop-down or Auto-populated. Effective Date of Standard or Project Specifications selected for the test. The drop down list for the Effective Date column has all the effective dates of the material test specification for the test template. The default date is set to the most recent one before the contract letting date for the first contract ID for the sample found in the database.


5.8.2 Service Menu for Maintain Sample Information Window


REMARKS BUBBLE: Select choices for remarks and add standard text or specific remarks, i.e. typo, calc error etc. Internal remarks can be viewed by lab; Public remarks appear on canned report. Specific Remarks about a test should be recorded on the Remarks field of the template and not in the Remarks Bubble.

Internal Remarks

Public Remarks

Requeue

Retest

ADD TESTERS: Click the Add Testers button to view testers who have contributed to the test template or add testers to the selected test.

5.8.3 Enter Add Testers Window (Sub-Panel)

Security Procedure: CDOT update authorization for this window should be limited to RME, Asst RME, Lab Manager, IA Tester.

Functional Procedure: This window is used to assign specific testers to a specific test. This is optional for the RME/Lab Manager to choose a specific person to perform a test.

Figure 5.26 Add Testers Window (Sub-Panel)


Table 5.22 Add Testers Window (Sub-Panel) - Fields


Key information (in layout order)

Sample ID N/A Auto-populated. Uniquely identifies the sample.

--

Test Method N/A Auto-populated. Uniquely identifies a test. Agency-defined.

--

Sample Test Number

N/A Auto-populated. Incremental number assigned to the run of a test on a sample.

--

Additional testers available for assignment’ pane (in alphabetical order)

Tester N/A Auto-populated. Tester assigned to perform or oversee the test.

--

Name N/A Auto-populated. Name of the tester. --

Add Button Yes Button. Select tester In ‘Additional testers available for assignment’ pane, click Add to move them to Testers already assigned to the sample’ pane.

--

Testers already assigned to the sample’ pane (in alphabetical order)

Tester N/A Auto-populated. Tester assigned to perform or oversee the test.

--

Name N/A Auto-populated. Name of the tester. --

TRAINING COMMENTS:

The tester can start the sample without completing it. They should not mark complete until they are finished entering their test results.

The tester should determine whether the material passes, fails, or has no spec, then click on the appropriate radio button that applies (in spec, out spec, no spec). The templates will show the min/max (where appropriate), and will also still automatically “flag” the offending field by highlighting it in red. This should help the tester determine if the test is in spec or out of spec.

The template window shrinks to the bottom of the page, to view the entire template maximum the template window. When a user is done entering test results, they can restore window rather than closing the enter test results window.


5.9 LIMS Review Tests Window

LIMS Navigation LIMS NAVIGATION PANEL > LIMS > REVIEW TESTS

Use the Review Tests window to review tests that have been completed. In this window, also compare test results for the same test across samples, approve, re-queue, or order a retest. Note: If all tests for a sample are set to auto-finalize, then the sample is authorized when the last test on the sample is marked Review Complete. This would only be used for Field Tests at CDOT. This function should be handled by the Alternative Test Workflow.

Security Procedure: CDOT update authority for this window should be available to Technical Support, IT System Administration, Central Lab Pavement Design Program, Region Materials Office, CDOT Samplers and Testers, Consultant Testers, and Central Lab Unit Groups (Binder, Flexible Pavement and Chemical, Concrete/Physical Properties, and Soils) for the specific contract. The Review Tests window displays tests based on the following criteria:

If reviewer acts in the role of Lab Supervisor, reviewer’s security group has been added to the LMSLBSUP code table and test status has been added to the LMSLBSQ code table. The system will filter all other test statuses.

If reviewer acts in the role of Line Supervisor (because the security group has not been added to the LMSLBSUP code table), test status has been added to the LMSLNSQ code table. The system will filter all other test statuses.

Lab unit has appropriate qualifications to perform the test.

Reviewer has appropriate test qualifications.

Reviewer has contract-level authority (Project PE) to the contract associated to the sample. If a sample has no contracts associated, it will be available to any user who meets the other security conditions.

Functional Procedure: Controlling the Display If reviewer belongs to multiple lab units, click the All My Labs button to display all tests assigned to the labs for which the user has the appropriate test qualifications. Use the Filter Criteria to further limit the number of tests displayed in the list. When the user clicks on a test, the test template results are displayed. The effective date column is populated with the effective date associated with the results. Completing Review of Tests Perform one of three possible actions on a test and determine if the test is reportable. Review Completed Select the Review Completed choice and click the Save button. System checks to see if the test template passes or fails by checking the monitor field value of the template against the values defined for the LMSAFINL code table. If the test passes, then the system checks for alternate workflows defined for the specific combination of sample type, material code, test method, and lab unit. If an alternate workflow exists for the combination, the system changes the test


status to the one defined in the alternate workflow. If there is no alternate test workflow defined, the system changes the test status based on the role to which the reviewer belongs. If reviewer belongs to a group that is designated to act in the Lab Supervisor role, then the system will assign the test status defined by the ‘Test Status for Lab Supervsr Approval’ system parameter. Otherwise, the system will assign the test status defined in the ‘Test Status for Line Supervsr Approval’ system parameter. All the previous runs for the same test method, if any, will also get the same test status as the one approved. After a reviewer approves each test, the system checks to see if all other tests for the sample have been reviewed by the Lab Supervisor role. If all other tests have been reviewed by the Lab Supervisor role, the system will check to see if the sample has been set to auto-finalize. Re-Queuing Tests Select the Re-Queue choice, click the Save button, and record a Re-queue remark to send an existing test back to the Enter Test Results window. The lab tester can now change the test results if entered incorrectly, or if the sample is retested enter the new results and discard the old results. Each lab and project should determine if a sample should be retested or a new sample submitted and tested to replace the previous sample results. If a new sample is submitted and replaces the previous samples results, then the Supervisor/Authorizer should mark the first sample as Void so it will not be counted towards project acceptance. Only one test results can be associated with one Sample ID. The system changes the test status to the one defined in the ‘Test Status for Re-Queue’ system parameter. All the previous tests for the same test method, if any, will also be changed to the same test status. Ordering Retests CDOT will not use this function at this time. If a retest of a sample is needed, it is CDOT policy for the Line Supervisor to either Re-queue the test so the tester can make any changes to the test results or have the tester submit a brand new sample and have it tested using the new test results for acceptance. If a Retest of a sample is attempted, the results will not be able to be reported because the custom CDOT reports cannot distinguish the correct results to report since there are now two tested results for one test method associated to one Sample ID. The system assigns the test status defined in the ‘Test Status for Retest in Queue’ system parameter to each new test. The system changes the test statuses of all previous tests to the one defined in the ‘Test Status for Waiting Retest’ system parameter. Reportable: Including or Excluding Tests from Sample Review A selected Reportable check box indicates that the results are acceptable for users to evaluate the test results in the Review Samples window. If the Reportable check box has been cleared (un-checked) for the test, then the test will not appear in any window except View-Only Sample Information window and the Maintain Test Queue window. The Reportable check box is selected by default.


5.9.1 Review Tests Panel

Figure 5.27 Review Tests Window


Table 5.23 Review Tests Window - Fields




--

Select a Lab Unit Yes/No Drop Down. Drop-down list that contains names of the labs to which the user has access. Select the name of the lab unit where samples are to be received. Displays all tests in the queue for the selected lab unit.

--



--


--


150+


nd field)


--

Apply Yes/No Button. Click to filter list by selected criteria.

Reset Yes/No Button. Click to clear any selected filter criteria.


Reportable Yes Check Box. Default Yes. Indicates the test will be available to view on the Review Samples window. Default: selected.

--

Supervisor Action Yes Drop Down. Select Review Completed, ReQueue or Retest Ordered. Dropdown list is enabled only if the test is the highest test number for the test method.

--


Completed Date N/A Auto-populated. Date when the sample was marked as complete in the lab unit.

--

Contract ID N/A Auto-populated. All contracts assigned to the sample.

--

Control Number N/A Auto-populated. Control number for the sample. Unique identifier to the sample.

--

Due Date N/A Auto-populated. Due date assigned to the test. Information-only.

MM/DD/YY

Lab Control Number N/A Auto-populated. An umbrella number for grouping samples. Allows samples to be linked together for testing and sample review purposes

--

Lab Ref Number N/A Auto-populated. Laboratory Reference Number. Often simpler than the auto-generated sample ID.

--


Labs may increment by one at the start of the new year.

Manufacturer * N/A Auto-populated. Code and name of the manufacturer of the sample.

--

Material Code N/A Auto-populated. Uniquely identifies a material. Agency-defined.

--

Priority N/A Auto-populated. Priority assigned to the test. Information-only. High, Medium or Low. Default: Medium.

--

Producer Supplier* N/A Auto-populated. Name of the producer or supplier of the material.

--

Sample Date N/A Auto-populated. Date when the sample was taken.

MM/DD/YY


Sample Type* N/A Auto-populated. Type of sample. --

Sampler N/A Auto-populated. User ID of the sampler. --

Seal Number N/A Auto-populated. Seal number for the sample. --

Test Description N/A Auto-populated. Name of the test. --

Test Method N/A Auto-populated. Uniquely identifies a test. --

Test Number N/A Auto-populated. Incremental number assigned to the run of a test on a sample.

--

Test Status * N/A Auto-populated. Status of the test. --

Tester * N/A Auto-populated. Tester assigned to perform or oversee the test. Information-only.

--

Effective Date N/A Auto-populated. Populated with the effective date associated with the results.

--

Test Result Views

Single Test Yes Check Box. View results of selected test in context of test template.

--

Multi-Test Yes Check Box. View results of all tests in the Review Tests queue that match the selected test’s test method. Grid format.

--

Test Results pane (Single Test result view)

< all other fields > N/A Auto-populated. Agency-defined. --

Test Results pane (Multi-test result view)

N/A

Test Template N/A Auto-populated. Equates to the test method. --

Template Column N/A Auto-populated. Field name on the template. --

Min N/A Auto-populated. Minimum acceptable value per specification.

--

Max N/A Auto-populated. Maximum acceptable value per specification.

--

< Sample ID > / N/A Auto-populated. Combination of sample ID and --


< Test Number > the sample test number.

Meeting Conditions to Auto-finalize

CDOT will not use this method. The conditions to auto finalize follow:

Test has been selected to auto finalize in the Test Assignment Information window.

All tests assigned to the sample must be set to auto finalize.

All non-cancelled tests must have a result that matches one of the values defined in the LMSAFINL code table.

If the sample passes the auto-finalize check, the system changes the sample status to the one defined in the ‘Test Status for Finalized’ system parameter. The system changes the acceptance method for the sample to the one defined in the ‘Acceptance Method for Auto-finalize’ system parameter. The system authorizes the sample and populates the Authorized By field with SYSTEM. If the sample does not pass the auto-finalize check, the system changes the sample status to the one defined by the ‘Sample Status for Pre Auth’ system parameter. Comparing Multiple Runs of the Same Test In the Single Test result view, select a test method to compare. Select the Multi-Test result view. The system displays only tests that match the selected test method. Use CTRL+click or Shift+click to select multiple tests to compare. Click the Compare Results button. The system displays the results in a grid format.

5.10 LIMS Review Samples Window

LIMS Navigation LIMS NAVIGATION PANEL > LIMS > REVIEW SAMPLES

Use the Review Samples window to approve samples. In this window, view and compare all tests approved by the Lab Supervisor that were not set to auto-finalize, tests that did not qualify for auto-finalization, and tests with an alternative workflow that passes through the Review Samples window, add remarks, or send the test back to the lab for more tests.

Security Procedure: CDOT update authority for this window should be available to Technical Support, IT System Administration, Central Lab Pavement Design Program, Region Materials Office, CDOT Sampler and Testers, Consultant Testers, and Central Lab Unit Groups (Binder, Flexible Pavement and Chemical, Concrete/Physical Properties, and Soils) for specific contracts.

Functional Procedure: The Review Samples window displays samples and tests based on the following criteria:

Reviewer has the authority to approve samples from the product group—based on the sample’s material code, sample type and the lab unit that performed the test(s). This authority is via the Maintain Product Users window.


Tests were marked as reportable and marked as test complete

Reviewer has contract-level authority to the contract associated to the sample. If a sample has no contracts associated, it will be available to any user who meets the other security conditions.

Controlling the Display Click the Lab Control Number button to display all samples grouped by lab control number. Reviewers may authorize all samples associated to a lab control number. Click the Sample ID button to display all samples sorted by the sample ID. Use the Filter Criteria to further limit the number of samples displayed in the list. Sending Tests Back to Lab To send a test back to the lab, select the Send Test Back to Lab checkbox for the desired test and click the Save button. Authorize Samples To authorize a sample, select the appropriate choice from both the Acceptance Method* (if not populated) and Sample Status* dropdown lists, then select the Authorize column, then click the Save button. The sample record will reflect the user ID of the person that authorized the sample and the date on which the authorization occurred.

5.10.1 Review Samples Panel

Figure 5.28 Review Samples Window


Table 5.24 Review Samples Window - Fields


Data View area (in layout order)

Lab Control Number N/A Sort. Select to sort list and approve by lab control number.

--

Sample ID N/A Sort. Select to sort list and approve by sample ID. --



--


--


150+




Acceptance Method* Yes Drop Down. Means of accepting the sample. --

Authorize Yes Check Box. Indicate a sample to be authorized. --

Sample Status * Yes Drop Down. Status to display on the sample record for the authorized sample.

--

Send Test Back To Lab

Yes/No Check Box. Indicate a test to be sent back to the lab for testing.

--

View/Compare Results

Yes/No Button. View or compare results of the selected test(s).

--


Completion Date N/A Auto-population. Date when the sample was marked as complete in the lab unit.

--

Contract ID N/A Auto-population. All contracts assigned to the sample.

--

Control Number N/A Auto-population. Control number for the sample. Unique identifier to the sample.

--

Lab Control Number N/A Auto-population. An umbrella number for grouping samples. Allows samples to be linked together for testing and sample review purposes.

--

Lab Ref Number N/A Auto-population. Laboratory Reference Number.. --

Lab Unit N/A Auto-population. Name of the lab where the test was performed.

--

Manufacturer * N/A Auto-population. Code and name of the manufacturer of the sample.

--

Material Code N/A Auto-population. Uniquely identifies a material. Agency-defined.

--


Producer Supplier * N/A Auto-population. Name of the producer or supplier of the material.

--

Sample Date N/A Auto-population. Date when the sample was taken.

--

Sample ID N/A Auto-population. Uniquely identifies the sample. --

Sample Type * N/A Auto-population. Type of sample. Agency-defined. --

Sampler N/A Auto-population. User ID of the sampler. --

Seal Number N/A Auto-population. Seal number for the sample. --

Test Description N/A Auto-population. Name of the test. --

Test Method N/A Auto-population. Uniquely identifies a test. --

Test Number N/A Auto-population. Incremental number assigned to a test on a sample.

--

Test Status * N/A Auto-population. Status of the test. --

Test Results pane

Test Template N/A Auto-population. Equates to the test method. --

Template Column N/A Auto-population. Field name on the template. --

Min N/A Auto-population. Minimum acceptable value per specification.

--

Max N/A Auto-population. Maximum acceptable value per specification.

--

< Sample ID > / < Test Number >

N/A Auto-population. Combination of sample ID and the sample test number.

--

Asterisk (*) indicates that the code must be used in the Value field if Sample Status is selected as Filter Criteria.

SEND TEST BACK TO LAB: If a reviewer wants to send a test back to the lab, the reviewer must first move the “Send Test Back To Lab” column to the left so that all editable fields are showing on the window. Only after the reviewer has done that will the check stay in the box and the reviewer can save the data.


Code Table = SMPLAUTH – Sample Status Allowing Sample Authorization

Code Description

COMP Complete

VOID Void

Code Description



ST Sample and Test



SAMPLE STATUS*: Choices COMPLETE: A Material Sample is complete when the sampling and testing was performed correctly to applicable specifications, test methods, procedures, recommended practices, or classifications. A Material is complete when the product or assembly was fabricated in accordance with and meets the applicable specification and documented as being acceptable. For Samples that are not counted toward project acceptance the sample status of Complete should be the only selection. (Example, preconstruction, soil surveys, survey samples authorized by HQ and/or Region Lab).

VOID: A Material Sample is void when the material has been removed and replaced at the discretion of the Project Engineer. A Material Sample is void when the sampling and testing was performed incorrectly. Note: A new material should be sampled and tested under a new Sample ID. A Sample status of Void will NOT be counted towards project acceptance requirements. Asterisk (*) indicates that the code must be used in the Value field if Sample Status is selected as Filter Criteria.

TESTING AND TRAINING COMMENTS: Once the Form 250 report has been completed with CDOT information, the project engineer needs to be trained on what Sample Status choices will count toward Sampling Checklist requirements. (i.e. COMP, VOID, FAIL, or ARDP).

5.11 LIMS Maintain Test Queue Window

LIMS Navigation LIMS NAVIGATION PANEL > LIMS > MAINTAIN TEST QUEUE

Use the Maintain Test Queue window for an overall view of samples and their current test statuses in LIMS. In this window, maintain and plan test queues and add or cancel tests for samples. Also, add priority, due date and testers to the existing tests and modify the lab unit and charge amounts for tests.

Security Procedure: CDOT approval authority for this window should be limited to Technical Support, IT System Administration, Region Materials Office, CDOT Sampler and Testers, Consultant Testers, Central Lab Pavement Design Program, Central Lab Managers (Binder, Flexible Pavement and Chemical, Concrete/Physical Properties, and Soils Group).

Functional Procedure: The Maintain Test Queue window displays tests based on the following criteria:

Sample status of the sample on which the test is performed has been added to the LMSMNTQ code table. The system will filter all other sample statuses.


User has contract-level authority for the contracts associated to the sample. If a sample has no contracts associated, it will be available to any user who meets the other security conditions.

Controlling the Display If reviewer belongs to multiple lab units, click the All My Labs button to display all tests assigned to the labs for which the user has the appropriate test qualifications. Use the Filter Criteria to further limit the number of tests displayed in the list.

5.11.1 Maintain Test Queue Panel

Figure 5.29 Maintain Test Queue Window


Table 5.25 Maintain Test Queue Window - Fields




--

Select a Lab Unit Yes/No Drop Down. Drop-down list that contains names of the labs to which the user has access. Select the name of the lab unit where samples are to be received. Displays all tests in the queue for the selected lab unit.

--


nd field)


--



--


--


150+



User Action fields – upper pane (in alphabetical order)

Due Date Yes/No Free Form. Due date assigned to the test. Information-only.

DD/MM/YY

Priority Yes/No Drop Down. Priority assigned to the test. Information-only. High, Medium or Low. Default: Medium.

--

Reportable Yes Check Box. Indicates the test will be available to view on the Review Samples window. Default: selected.

--

Tester * Yes/No Drop Down. Tester assigned to perform or oversee the test. Information-only.

Asterisk (*) indicates that the code must be used in the Value field if Tester is selected as Filter Criteria.

--

Inquiry-only fields – upper pane (in alphabetical order)

Contract ID N/A Auto-populated. Comma separated list of all contracts assigned to the sample.

--

Lab Control Number N/A Auto-populated. Lab Control Number for the sample ID.

--


Lab Ref Number N/A Auto-populated. Lab Reference Number for the sample ID.

--

Material Name N/A Auto-populated. Name of the material code for the sample ID.

--

Product Name N/A Auto-populated. Name of the product associated with the sample.

--

Receive Date N/A Auto-populated. Date when the sample was received in the lab unit.

--

Sample ID N/A Auto-populated. The sample ID that is waiting to be received

--

Sample Type * N/A Auto-populated. The type of Sample. --

Seal Number N/A Auto-populated. Seal number for the sample ID. (Not to be used by CDOT)

--

Test Description N/A Auto-populated. Description of the test method. --

Test Number N/A Auto-populated. Sample test number assigned to the test

--

Test Status * N/A Auto-populated. Current status of the test. --

Lower pane fields (in layout order)

Lab ID Yes/No Search. Uniquely identifies a lab unit. --

Lab Name (no label)

N/A Auto-population. Describes a lab unit. --

Charge Amount N/A Auto-population. Cost of the test as it appears in the test and fee schedule.

--

Start Date N/A Auto-population. Date when a user first recorded information in the test template.

--

Actual Completion Date

N/A Auto-population. Date when the test was marked as complete.

--

5.11.1.1 Drop-down Services Menu CANCEL TEST: Click Cancel Test to cancel the test. ADD TEST: Click the Add Test button to add a test to the sample. REMARKS BUBBLE: Select choices for remarks and add standard text or specific remarks, i.e. typo, calc error etc. Internal remarks can be viewed by lab; Public remarks appear on canned report. Specific Remarks about a test should be recorded on the Remarks field of the template and not in the Remarks Bubble.

Internal Remarks

Public Remarks

Requeue

Retest


5.11.2 Enter Add Test Window (Sub-Panel)

Functional Procedure: To add a test, select any test on the desired sample to associate the new test. Click the Add Tests button. Use the Add Tests window to add desired tests from the tests available or add runs for tests already associated with the sample.

Figure 5.30 Maintain Test Queue Window - Add Tests Window (Sub-Panel)


Table 5.26 Maintain Test Queue Window - Add Tests Window (Sub-Panel) - Fields


‘Additional tests available for assignment’ area (in alphabetical order)

Lab Unit N/A Auto-population. Name of the lab unit where the test will be performed.

--


--

Test Method N/A Auto-population. Test Method. Uniquely identifies a test. Agency-defined.

--

Add Button Yes Button. Select tests In ‘Additional tests available for assignment’ pane, click Add to move them to Tests already assigned to the sample’ pane.

--

‘Tests already assigned to the sample’ area (in alphabetical order)

Lab Unit N/A Auto-population. Name of the lab unit where the test will be performed.

--


--

Test Method N/A Auto-population. Test Method. Uniquely identifies a test. Agency-defined.

--

Test Nbr N/A Auto-population. Test Number. Incremental number assigned to the run of a test on a sample. Auto-populated.

--

Figure 5.31 Maintain Test Queue Window - Add Tests Window (Sub-Panel) - Select Additional Runs Window


Table 5.27 Maintain Test Queue Window - Add Tests Window (Sub-Panel) - Select Additional Runs Window - Fields


Select Additional Runs

Yes/No Drop Down. Number of additional runs to be added to a sample test. Values: 1-5

--

OK Yes Button. Click button to save additional tests assigned or runs added.

--

5.12 LIMS Alternative Test Workflow Window

LIMS Navigation LIMS NAVIGATION PANEL > SYSTEM ADMIN > ALTERNATIVE TEST WORKFLOW

CDOT will not use at this time. Use the Alternative Test Workflow window to define a custom workflow for a test based upon the test status. The test status can range from Test Completed to the final approval status. Add a new row and define a To Test Status.

Security Procedure: Full access for this window shall be limited to CDOT Technical Support and IT System Administration.

Functional Procedure: CDOT may use this method to bypass the Review Test window for COC’s and for CTR authorization. Define the alternative workflow for a combination of key information:

Test Method

Lab Unit

Material

Sample Type

From Test Status After selections have been complete, click Save in the toolbar to save.

Example: The user has a newly defined To Test Status for the aforementioned combination of keys. Whenever a test record with that specific combination of data is found at the time of a test completion or approval, the system changes the status of the test record for the sample to the newly defined To Test Status. The alternative test workflow bypasses the standard test status update at the time of a test completion or approval. The system always refers to the alternative workflow records to see if a matching record exists. If the data for the combination of keys in a sample’s test match a record in the alternative workflow function, the To Test Status is used to update the test status information for the sample’s test, thus bypassing the standard built-in status for the step in the system. If there is no matching alternative workflow record or tests fail, the standard logic in the system is executed.


5.12.1 Alternative Test Workflow Panel

Figure 5.32 Alternative Test Workflow Window


Table 5.28 Alternative Test Workflow Window - Fields


Filter Criteria area


--

Operator (no label) Yes/No Drop Down. Operators for applying the filter criteria. --


--



Inquiry-only fields - upper pane (in alphabetical order)

From Test Status N/A Auto-population. Status of the test that will initiate the alternative workflow.

--

Lab Unit N/A Auto-population. Name of the lab that will perform the test.

--

Material Code N/A Auto-population. Uniquely identifies a material. Agency-defined.

--

Material Name N/A Auto-population. Name of the material. --

Sample Type N/A Auto-population. Purpose of the sample. --

Test Description N/A Auto-population. Name of the test. Agency-defined. --

To Test Status N/A Auto-population. Status of the test after the alternative workflow is applied.

--

User Action fields - lower pane (in layout order)

Test Method Yes Search. Code for the test that corresponds to the Test Description. Required. Search results list displays test method, test description and test number.

--

Test Description N/A Auto-population. Description of the test. Inquiry-only. --

Lab Unit Yes Search. Name of the lab that will perform the test. Required.

--

Lab Unit Description

N/A Auto-population. Name of the lab. Inquiry-only. --

Material Code Yes Search. Uniquely identifies the material. Search results list displays material code and material short name.

--

Material Name N/A Auto-population. Describes the material. Inquiry-only.

--

Sample Type Yes Drop Down. Purpose of the sample. --

From Test Status Yes Drop Down. Status of the test that will initiate the alternative workflow.

--

To Test Status Yes Drop Down. Status of the test after the alternative workflow is applied.

--


5.13 LIMS Test Triggered Events Window

LIMS Navigation LIMS NAVIGATION PANEL > SYSTEM ADMIN > TEST TRIGGERED EVENTS

CDOT will not use at this time. To trigger a change in status of one test based on the change in status of another test for a sample, use the Test Triggered Events function. Both the parent test and the triggered test must always pre-exist in the sample.

Security Procedure: CDOT approval authority for this window should be limited to Technical Support and IT System Administration.

Functional Procedure: When a test method for a given sample type and material changes, then the test status will change from one predefined status to another predefined status. If another test method is changed, it will trigger another change to be taken to a predefined status (Trigger to Test Status) from whichever status it had. To trigger multiple events and in a certain order, use the Trigger SN (Sequence Number) field to determine the order of the events (for example, change in status of another test method). Note: To trigger an external program, first code and include calling procedures for the external program in the LIMS custom library. Then, in the Exec Object Name field, input the name of the external program to trigger.


5.13.1 Test Triggered Events Panel

Figure 5.33 Test Triggered Events Window


Table 5.29 Test Triggered Events Window - Fields


Inquiry-only fields - upper pane (in alphabetical order)

From Test Status N/A Auto-population. Identifies the 'from' test status of the test triggered event.

--

Material Code N/A Auto-population. Identifies the material code of the test triggered event.

--

Material Name N/A Auto-population. Name of the material. --

Sample Type N/A Auto-population. Identifies the sample type and description of the test triggered event

--

Test Description N/A Auto-population. Textual description of the test.

--

To Test Status N/A Auto-population. Identifies the 'to' test status of the test triggered event.

--

Trigger SN N/A Auto-population. Identifies the sequence number of the test triggered event.

--

Trigger Test N/A Auto-population. Identifies the description of the trigger test, or the test to be changed.

--

User Action fields - lower pane (in layout order)

Test Method Yes Search. Identifies the test method of the test triggered event.

--

Test Description N/A Textual description of the test. --

Material Code Yes Search. Identifies the material code of the test triggered event.

--

Material Name N/A Name of the material. --

Sample Type Yes Search. Identifies the sample type of the test triggered event.

--

From Test Status Yes Drop Down. Identifies the 'from' test status of the test triggered event.

--

To Test Status Yes Drop Down. Identifies the 'to' test status of the test triggered event.

--

Trigger SN Yes Drop Down. Identifies the sequence number of the test triggered event.

--

Trigger Test Yes Search. Identifies the test method of the trigger test, or the test to be changed.

--

Trigger To Test Status

Yes Drop Down. Identifies the test status that the trigger test will be changed to. This column is required.

--

Exec Object Type Yes Free Form. Identifies the type of the external program to be called, if any.

12

Exec Object Name Yes Free Form. Identifies the name of the external program to be called, if any.

70


5.14 LIMS Test Assignment Information Window

LIMS Navigation LIMS NAVIGATION PANEL > SYSTEM ADMIN > TEST ASSIGNMENT INFORMATION

*CDOT IS NOT PRESENTLY USING DEFAULT TESTS FOR MATERIALS FUNCTIONALITY CDOT will not use the default test section of this window. It was decided that testers will assign tests manually. Window Procedure:

To define the default test settings for a sample, use the Test Assignment function. The test assignment criteria consist of the following key information:

Material

Sample Type

Lab Unit

After making selections in the Test Assignment Criteria area, LIMS displays tests that meet specified criteria. Tests already assigned as defaults appear in the Default Tests pane. Tests available for assignment appear in the Available Tests pane. LIMS selects the Default Test Ind check box by default when a test is moved to the Default Tests pane. To indicate a test is required, select the Req’d Assign check box. To add or remove default test settings, select the test and click the ADD Default Tests or the Remove Default Tests buttons. LIMS moves the selected test to or from the Available Tests panel and the Default Tests pane.

Security Procedure: CDOT approval authority for this window should be limited to CDOT update authority for this window should be available to Technical Support, IT System Administration, and Central Lab Pavement Design Program.

Functional Procedure: CDOT will utilize this window to select specific test to be run on samples obtained for contract and noncontract items. The default tests should only be assigned, but additions and subtractions of tests may be selected depending on the material that is being tested and the security group. Once tests are assigned to a sample, the sample cannot be deleted. It can be Voided by proper security groups.

5.14.1 Test Assignment Information Panel


Figure 5.34 Test Assignment Information Window


Table 5.30 Test Assignment Information Window - Fields


Test Assignment Criteria

Select Material

Material Code N/A Auto-populated. Identifies the unique, department defined identifier for a material.

--

Material Name N/A Auto-populated. Identifies the abbreviated description of material.

--

Select Sample Type

Sample Type N/A Auto-populated. Identifies the sample type. --

Description N/A Identifies the sample type description. --

Select Lab Unit

Lab ID N/A Auto-populated. Identifies the unique department defined identifier for a qualified laboratory.

--

Lab Name N/A Auto-populated. Identifies the name of the lab. --

Available Tests

Test Method N/A Auto-populated. Identifies the test method for all material tests for the selected material and lab not yet assigned to the test assignment criteria.

--

Test Description

N/A Auto-populated. Identifies the description of the test.

--

Default Tests

Test Runs Yes Free Form, Numerical. Enter number of test runs required. Default 1 test run.

0-9 only

Test Method N/A Auto-populated. Identifies the test method for all material tests assigned to the test assignment criteria.

--

Test Description

N/A Auto-populated. Identifies the description of the test.

--

Start Status N/A Identifies the initial test status for the test. Default value is Pending.

--

Req’d Assign N/A Check Box. Required Assign. Indicates whether the test is required for the selected test assignment criteria.

Note: Once added to the sample, only an authorized user can cancel the test using the Maintain Test Queue window.

--

Autofinal Ind N/A Check Box. Auto-finalize Indicator. Indicates whether the test is a candidate for the LIMS auto finalization process for the selected test assignment criteria.

--

Default Test Ind N/A Auto-populated. Default Test Indicator. Indicates whether the test is a default test for the selected test assignment criteria.

--



TEST RUNS: Free form, numerical. Enter the number of test runs required for the sample. The default is 1 and the max is 9 test runs.

5.15 LIMS Assign Products Window

LIMS Navigation LIMS NAVIGATION PANEL > SYSTEM ADMIN > ASSIGN PRODUCTS

Use the Assign Products window to assign product groups to a combination of Material, Sample Type and Destination Lab. Multiple Product Groups (or Products) can have the same combination of Material, Sample Type and Destination Lab. This assignment, along with the user’s privileges to access records for a Product Group, determines the access privilege for the Review Sample window’s work queue.


Functional Procedure: CDOT will utilize this window to define a product group. To define a product group, use the following process.

In the code table LMSPRDGR, define the Product Group IDs.

Using the Assign Products window, specify a combination of Material, Sample Type and Destination Lab ID to which to assign a Product Group. Multiple Product Groups (or Products) can have the same combination of Material, Sample Type and Destination Lab criteria.

The Assign Products window displays the following:

The Materials list displays all materials from the Material Detail table.

The Sample Type list displays all sample types from the code table SMPLTYPE

The Destination Lab list displays all qualified labs that are also destination labs

The Available Products list displays all existing product groups not currently assigned to the selected test assignment criteria.

The Assigned Products list displays all product groups currently assigned to the selected test assignment criteria.

5.15.1 Assign Products Panel


Figure 5.35 Assign Products Window


Table 5.31 Assign Products Window – Fields


Material Code Uniquely identifies a material. Agency-defined.

Material Name Abbreviated description of material.

Sample Type Identifies the sample type ID value stored in the sample test type code table.

(U: SMPLTYPE)

Description Identifies the sample type description stored in the sample test type code table.

(U: SMPLTYPE)

Lab ID Identifies the unique department defined identifier for a destination laboratory.

Lab Name Identifies the name of the destination lab.

Product Group ID (Available Products pane)

Identifies the product group ID value stored in the product group code table for all products not yet assigned to the test assignment criteria.

(C: LMSPRDGR)

Product Group Description (Available Products pane)

Identifies the product group description value stored in the product group code table.

(C: LMSPRDGR)

Product Group ID (Assigned Products pane)

Identifies the product group ID value stored in the product group code table for all products not yet assigned to the test assignment criteria.

(C: LMSPRDGR)

Product Group Description (Assigned Products pane)

Identifies the product group description value stored in the product group code table.

(C: LMSPRDGR)

To add product groups to the selected test assignment criteria, select the product group(s) from the Available Products list and click on the ADD PRODUCTS button. To remove any product group(s) associated to the selected test assignment criteria, select the product group(s) from the Assigned Product list and click the REMOVE PRODUCTS button. TESTING AND TRAINING COMMENTS: This window is difficult to navigate because of the sort in the Material Code window. An external report might be useful to update this window or adding to the existing data spreadsheet (LMSPRDGR) in Sample Test/LIMS subcommittee SharePoint folder as opposed to updating this window. In addition, the list server sent out a question regarding code that might have been generated by another state to sort this window. This should be followed up on to see if another state responds.


Code Table = SMPLTYPE – Sample Test Type

Code Description



IAT Independent Assurance Testing




Code Table = LMSPRDGR – LIMS Product Groups

Code Description

BTMN Bituminous Material

CHEM Chemical

CONC Concrete

FLEX Flexible Pavement

MISC Miscellaneous

PHPR Physical Properties

SOIL Soils

5.16 LIMS Maintain Product Users Window

LIMS Navigation LIMS NAVIGATION PANEL > SYSTEM ADMIN > MAINTAIN PRODUCT USERS

The access privilege for the Review Sample work queue is based on whether a user has the privilege to access records for a Product Group. The Maintain Product Users window is used to determine access to the Review Sample records for a Product Group to existing SiteManager users. Before a user can access a lab Review Sample work queue, the system administrator must assign the user to the corresponding Product Group using this window. The Maintain Product Users window displays all the product groups under the Product Group list. The list of users in the Available Users pane comes from the SiteManager security users.


Functional Procedure: CDOT will utilize this window to add users to a product group for Sample Authorization.


To add users to a product group, select the users from the available users list and click on the ADD USERS button. To remove any users associated to a product group, select them from the Product Users list and click the REMOVE USERS button.

5.16.1 Maintain Product Users Panel

Figure 5.36 Maintain Product Users Window


Table 5.32 Maintain Product Users – Fields


Product Group ID Uniquely identifies the product group.

(U: LMSPRDGR)

Product Group Description

Describes the product group.

(U: LMSPRDGR)

Available Users area

User ID User ID of all users available that can be assigned to the product group. The user ID list contains all SiteManager security users not already assigned to the product group.

User Name Identifies the full name of the user.

Central Office Indicates whether the user belongs to the central office.

Level 2 Office Number Indicates to which level 2 office the user belongs,



Product Users area

User ID User ID of all users that are assigned to the product group.

User Name Identifies the full name of the user.

Code Table = LMSPRDGR – LIMS Product Groups

Code Description

BTMN Bituminous Material

CHEM Chemical

CONC Concrete

FLEX Flexible Pavement

MISC Miscellaneous

PHPR Physical Properties

SOIL Soils

TESTING AND TRAINING COMMENTS: RMEs, Asst RME, and Lab Managers need to be added to all product groups as well. However, they do not need contract authority because they should have office wide access by Region.


SECTION 6 Approved Lists

236 Approved Lists

6.1 Approved Materials Window

SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > APPROVED LISTS > APPROVED MATERIALS

Use the Approved Materials window to add to and modify CDOT’s list of approved materials. SiteManager uses the approved materials information for validation when sample data is entered. When a user selects a material that requires acceptance by CDOT’s Approved Products List the system will display only products (approved name brands of that material) contained on this list.

Security Procedure: CDOT update authority for this window should be limited to the following SiteManager Materials Security groups: CDOT update authority for this window should be available to Technical Support, IT System Administration, and Central Lab Pavement Design Program. CDOT inquiry authority for this window should be available to all SiteManager Material users.

Functional Procedure: CDOT will utilize this window to record approved products and generate a web-based, live data, search inquiry Approved Products List (APL). The window associates a unique Producer and/or Supplier’s (P/S) product to a material code. QML Steel and QML Epoxy manufacturers aren’t tracked through the Approved Materials window. The material code is general enough so that a contractor has alternative products to select from. It is also general enough to create a listing of like products on the APL on the web. The product category field is unique to this window. It further categorizes the general material code by an additional two tiers (sub-category and base category) on the APL web search inquiry. The remarks bubble for this window is unique to this window and will be utilized to store additional data about the individual product.

Reports: CDOT reports are generated from this window as a web-based, searchable interface available on the CDOT external webpage. No specific reports of this window’s data are generated from within SiteManager/LIMS. The data from this window may also be part of reports generated elsewhere in SiteManager/LIMS.

6.1.1 Approved Materials Panel


Figure 6.1 Approved Materials Window

Table 6.1 Approved Materials Window - Fields


Material Code N/A Auto-populated from open or choose keys command. -


N/A Auto-populated from Material Code selection.

-

Product Name Yes

Free-form field. Full name of the product, brand, model, or system as submitted by the manufacturer.

40

Effective Date Yes

Auto-populated to current date but may be changed. Date the product name was added to the approved products list. Must be less than Expiration Date.

mm/dd/yy

Expiration Date Yes

Free-form date field. Date the product’s status as an approved material will expire.

mm/dd/yy

Product Category Yes

Drop-down menu. Sub-category and base category (of the material code) to which the selected product belongs.

-

P/S Yes

Search field populated by Maintain Producer Supplier window.

-

P/S Code (no label) N/A Auto-populated from P/S entry. -

Acceptance Method Yes

Drop-down menu. Method of acceptance that qualified this product to appear on the approved products list.

-

238 Approved Lists

6.1.1.1 Required Fields PRODUCT NAME: Free form field (alpha-numeric, 40 characters) for input of the unique P/S product trade name. EFFECTIVE DATE: Auto-populated to the date of record creation. This should be the date product is added to APL. May be modified if needed by window originator. Must be less than Expiration Date. EXPIRATION DATE: Free-form date field. Enter the date the product’s status as an approved material will expire. PRODUCT CATEGORY: Drop-down menu of category (exclusive to this window). Selections will be numerous as this drop-down menu sub-categorizes the Material Code/Description for APL listing capability. See attached table. P/S NAME: Search field (populated by Maintain Producer Supplier window) used to identify specific P/S that produces or provides the specific product. P/S CODE: Auto-populated from P/S Name entry.

ACCEPTANCE METHOD: Drop-down menu to record type of acceptance of product. Selections include Sample & Test, COC, & CTR.


Code Description

ST Sample and Test




Approved Materials Remarks are where comments and remarks are to be documented for each approved materials. Central Lab and field personnel may attach comments and remarks to individual products as warranted.

Code Table = APMTRMKT – Approved Materials Remark Type

Code Remarks Heading Description

GEN General

Code Table = PRODCATG – Product Category(1st name prior to ( | ) is sub-category and 2

nd name

following ( | ) is base category for APL web search function – N/A indicates no base category.

Code Description

AAA Anchoring, Lateral | Acrylic

AAB Anchoring, Lateral | Cementitious

AAC Anchoring, Lateral | Epoxy

AAD Anchoring, Lateral | Polyester

ABA Anchoring, Overhead | N/A

ACA Bonding | Epoxy

BAA Asphalt Release Agent | Truck Beds Only


Code Description

QLF Pavt Marking | Epoxy Paint, Yellow

QLG Pavt Marking | Epoxy Paint, White

QLH Pavt Marking | Raised Flexible Marker

QLI Pavt Marking | Recessed Marker

QMA Sign Sheeting | D 4956, Type IV

QMB Sign Sheeting | D 4956, Type V

QMC Sign Sheeting | D 4956, Type VI

QMD Sign Sheeting | D 4956, Type VI [collar]

QME Sign Sheeting | D 4956, Type VII

QMF Sign Sheeting | D 4956, Type VII, Fluor

QMG Sign Sheeting | D 4956, Type VIII

QMH Sign Sheeting | D 4956, Type VIII, Fluor

QMI Sign Sheeting | D 4956, Type IX

QMJ Sign Sheeting | D 4956, Type IX, Fluor

QMK Sign Sheeting | D 4956, Type X

QML Sign Sheeting | D 4956, Type X, Fluor

QMM Sign Sheeting | D 4956, Type XI

QMN Sign Sheeting | D 4956, Type XI, Fluor

QMO Sign Sheeting | Films / Miscellaneous

QNA Sign Substrate | N/A

QPCP Qualified Precast Concrete Plants

QSTM Qualified Steel Mill

RAA Concrete Sealer | Alkyl-alkoxy Silane

RAB Concrete Sealer | Nonalkyl-alkoxy Silane

RAC Concrete Sealer | Penetrating Epoxy

RAD Concrete Sealer | Micro Repair

RBA Elastomeric Membrane | Single Component

RBB Elastomeric Membrane | Non-Asphaltic

Vegetation Control | Geotextile

Railing | Pedestrian & Bicycle

Railing | Vehicle

Qualified Manufacturers Standardized Product Names Precast Concrete Structures Coated Non-reinforced Conc Circular Pipe Coated Reinforced Concrete Circular Pipe Concrete Circular Flared End Section Concrete Meter Pit Concrete Saddle Wall, Type S Light Pole Foundation Inlet Manhole Base Manhole Grade Ring Manhole Riser

244 Approved Lists

Non-reinforced Concrete Circular Pipe Perforated Concrete Circular Pipe Precast Box Culvert Precast Cattle Guard Precast Guardrail Precast Vault Porous Concrete Circular Pipe Reinforced Concrete Arch Pipe Reinforced Concrete Circular Pipe Reinforced Concrete Elliptical Pipe Temporary Precast Guardrail


REMARKS CDOT has no specific use for this field, although this is available for use as needed. Mixed case. PROCESS STATUS This window is available almost system wide by selecting Process Status from the Services menu. The window consists of two tab pages: Regular and Scheduled.

6.2 Maintain Producer/Supplier Window

SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > APPROVED LISTS > MAINTAIN PRODUCER/SUPPLIER

Use the Maintain Producer/Supplier window to add and modify information on any organization that produces or supplies materials used by CDOT. Use to enable record of producer and/or supplier when entering sample data and material sources. Use this data to verify, document, analyze and report for Quality Control/Quality Assurance (QC/QA) programs.

Security Procedure: CDOT update authority for this window should be limited to the following SiteManager Materials Security groups: Technical Support, IT System Administration, Central Lab Pavement Design Program, Region Materials Office, and Central Lab Unit Groups (Binder, Flexible Pavement and Chemical, Concrete/Physical Properties, and Soils). CDOT inquiry authority for this window should be available to all SiteManager Material users.

Functional Procedure: CDOT will utilize this window to record producers and/or suppliers (P/S) that provide materials. If it is important to uniquely identify a plant that is supplying material, then such plants should be entered as a unique P/S. Plant folder tab should be filled out as completely as possible. The address and phone number of the P/S should also be entered by using the Address button on the toolbar. On-site (project) generated materials will require the use of the P/S code designed for this purpose (OSM100001, On Site Materials); this P/S code shall be limited to specific material codes, and for project duration only.

Reports:


No automated SiteManager reports exist for this window. No CDOT reports are available for this window. The data from this window is used to generate reports from the Approved Materials window as well as being part of reports generated elsewhere in SiteManager/LIMS. A screen shot of each panel is included as figures 0-1 and 0-2. A general description of each panel and their fields is shown in tables 0-1 and 0-2. More specific information follows each table.

6.2.1 Description Panel Use the Description panel, to add and modify specific information that describes the producer and/or supplier, including the location of its main office. Multiple records should be created for each producer and/or supplier’s plants when needed to distinguish materials produced by these plants as unique. Enter the plant location as part of the producer/suppler name.

Figure 6.2 Maintain Producer/Supplier Window - Description Panel

246 Approved Lists

Table 6.2 Maintain Producer/Supplier Window - Description Panel – Fields



Yes Free-form field. Uniquely identifies a producer and/or supplier that provides materials. Begins window record.

15

Producer Supplier Type

Yes Drop-down menu. Identifies the type of the producer and/or supplier. Used to distinguish an APL/QML producer and/or supplier from all others.

--


Yes Free-form field. Full name of the producer and/or supplier as submitted.

60

Vendor ID Yes Search field populated by pre-construction process. Select producer and/or supplier if on vendor list.

--

Geographic Area No Drop-down menu. (CDOT will not use). --

Location No Drop-down menu. (CDOT will not use). --

Approval Level Yes Drop-down menu. Origination of record. --

Location Description

No Free-form field available for additional info. 60

DBE No Drop-down menu. Shall be left blank in this record. --

Contact No Free-form field to be utilized for the name of a contact for the selected producer and/or supplier.

20

Status Yes Drop-down menu. Indicates producer and/or supplier is active or inactive.

--

Status Date N/A Auto-populated. Date of when the status was changed. --

Last Modified User ID

N/A Auto-populated. User ID of last user to update record. --

Last Modified Date

N/A Auto-populated. Date of when the last change was made

--


P/S CODE: Begins process of recording producer and/or supplier. Window-originator generated sequential 9 character alpha-numeric in the following format: XXX (3-letter code) ## (year of input) #### (sequential) e.g. - AGG090014 or HMA100314. Examples of 3-letter codes: AGG (Aggregates), CON (Concrete), GEN (General), HMA (Hot Mix Asphalt), & OSM (On Site Materials). The next sequential number shall be used for P/S code creation. Currently GEN (General) should be used for all P/S code origination and the last sequential number for entry year must be verified. P/S TYPE: Drop-down menu of type of P/S. General (GEN) shall be used for all Non-APL and Non-QML Producer/Suppliers. All APL and QML Descriptions are reserved for use by the Approved Products Coordinator. Selections are shown in the “Code Table = PRODSUPP”, below.


Code Table = PRODSUPP – Producer Supplier Type

Code Description

A APL Adhesive

B APL Asphalt

C APL Bridge Structures

CAST QML Concrete Struct Precast Manufacturer

D APL Concrete

E APL Drainage

EPOX QML Epoxy-Coatng Applicator Manufacturer

F APL Environmental

G APL Environmental, Erosion Control

GEN General

H APL Soil / Geotechnical

I APL ITS

J APL Lighting

K APL Paint / Coating

L APL Pedestrian Safety

M APL Right-of-Way Structure

N APL Roadway Safety

O APL Sealant [Joint and Crack]

P APL Environmental, Sediment Control

Q APL Traffic Control

R APL Waterproofing

S APL Steel

STEL QML Steel Mill

(Last updated 06/22/2011) SiteManager Tables will be modified and updates posted as needed.

P/S NAME: Name as submitted. Free-form field (alpha-numeric, 60 characters). If the P/S is also a Plant, include the plant location in the P/S Name field (i.e. Suncor Commerce City West Terminal). VENDOR ID: Search field to be populated when the P/S shows up on the pre-construction populated search list. APPROVAL LEVEL: Drop-down menu that will be utilized to record the entity that originates record. Selections are Central Lab, Region 1, Region 2, Region 3, Region 4, Region 5, & Region 6.

248 Approved Lists

Code Table = APPRLEV – Approval Level

Code Description

CL Central Lab

R1 Region 1

R2 Region 2

R3 Region 3

R4 Region 4

R5 Region 5

R6 Region 6

STATUS: Drop-down menu. Only selections are Active or Inactive. This is a system code table used throughout SiteManager. Note, the status “Active” is a requirement for Qualified Manufacturers to appear on the web based QML.

Code Table = STATUS – Status

Code Description

A Active

I Inactive

6.2.1.2 CDOT will not use Fields Not required fields fall into two categories – those fields CDOT will not utilize and those fields that are optional for input. CDOT will not use the following fields: Geographic Area & Location.

GEOGRAPHIC AREA: Drop-down menu. Only selection is Not currently used by CDOT.


Code Description

* Not currently used by CDOT

LOCATION: Drop-down menu. Only selection is Not currently used by CDOT.

Code Table = LOCTYPE – Location

Code Description


Optional fields:

LOCATION DESCRIPTION: Free-form field (alpha-numeric, 60 characters) to enable additional information of any type to be entered by originator.


DBE: Drop-down menu. This is a system code table used throughout SiteManager. This drop-down is controlled by the construction side of SiteManager. For materials records this field shall be left blank.

Code Table = DBETYPE – DBE/WBE Code

(Code table is extensive and not included due to non-usage noted above.)

CONTACT: Free-form field (alpha-numeric, 20 characters) for input of a contact name. Phone number should be entered in the Address button on the toolbar.


REMARKS CDOT has no specific use for this field, although this is available for use as needed. Mixed case. ADDRESS An address window appears. When the address is selected in the Description tab it is used in the QML as shown on the internet. When the address is selected in the Plants tab it is used for each individual plant. It does not show on the QML by plant address. ATTACHMENTS Optional. PROCESS STATUS This window is available almost system wide by selecting Process Status from the Services menu. The window consists of two tab pages: Regular and Scheduled. See above explanation.

6.2.2 Plants Panel

250 Approved Lists

Use the Plants panel to add and modify locations associated with the producer and/or supplier listed on the Description panel.

Figure 6.3 Maintain Producer/Supplier Window - Plants Panel

Table 6.3 Maintain Producer/Supplier Window - Plants Panel - Fields


Producer/Supplier N/A Auto-populated from description panel. --

Plant ID Yes

Free-form field formatted at originator’s discretion. Uniquely identifies a plant to begin panel data.

15

Plant Type Yes Drop-down menu. Type of plant. --

Plant Status Yes

Drop-down menu. Indicates if the plant is active or inactive.

--

Plant Name Yes Free-form field. Name of the plant, pit or quarry. 50

Portable Plant No

Check box. This box shall be checked when plant is mobile or portable.

--

Last Inspected Date

Yes Free-form date field. Date plant was last inspected or window data was recorded.

--

Location No Drop-down menu. (CDOT will not use). --

Geographic Area No Drop-down menu. (CDOT will not use). --

Location Description

No Free-form field available for physical location of this plant..

60



PLANT ID: Originator generated free-form field (alpha-numeric, 15 characters) created to begin plant line item record for this P/S. The Plant ID for Portable plants will have the company name with mobile behind it. PLANT TYPE: Drop-down menu of type of plant.

Code Table = PLANTTYP – Plant Type

Code Description

ASPH Asphalt

CONC Concrete

AGG Aggregate Crushing

OTH Other

PLANT STATUS: Drop-down menu. Only selections are Active or Inactive. This is a system code table used throughout SiteManager.

Code Table = STATUS – Status

Code Description

A Active

I Inactive

PLANT NAME: Free-form field (alpha-numeric, 50 characters). LAST INSPECTED DATE: Free-form date field. Enter date of window record creation or date of last inspection.

6.2.2.2 CDOT will not use Fields Not required fields fall into two categories – those fields CDOT will not utilize and those fields that are optional for input. CDOT will not use the following fields: Location, Geographic Area.

LOCATION: Drop-down menu. Only selection is Not currently used by CDOT.

Code Table = LOCTYPE – Location

Code Description




252 Approved Lists

Code Description


Optional fields:

PORTABLE PLANT: Check box indicating if the plant is portable. This box shall be checked if plant is mobile or portable. LOCATION DESCRIPTION: Free-form field (alpha-numeric, 60 characters) to enable physical location to be entered by originator. Originator should record as much information needed to distinguish this plant beyond the name field record.


REMARKS CDOT has no specific use for this field, although this is available for use as needed. Mixed case. ADDRESS An address window appears. When the address is selected in the Description tab it is used in the QML as shown on the internet. When the address is selected in the Plants tab it is used for each individual plant. It does not show on the QML by plant address. ATTACHMENTS Optional. PROCESS STATUS This window is available almost system wide by selecting Process Status from the Services menu. The window consists of two tab pages: Regular and Scheduled. See above explanation.

6.3 Producer/Supplier Materials Window

SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > APPROVED LISTS > PRODUCER/SUPPLIER MATERIALS

Use the Producer/Supplier Materials window to add and modify approved materials for a specified producer/supplier. SiteManager uses the producer/supplier materials data for validation when sample data is entered. An approved material can also have Remarks attached to it. Use the Producer/Supplier Materials window to track expiration dates/times for materials and make the material active or inactive for a given producer/supplier. If the combination of producer/supplier and material has not been used in the system, use this window to delete a material.

Security Procedure: CDOT update authority for this window should be limited to the following SiteManager Materials Security groups: Technical Support, IT System Administration, Central Lab Pavement Design Program, Region Materials Office, and Central Lab Unit Groups (Binder, Flexible Pavement and Chemical, and Concrete/Physical Properties). CDOT inquiry authority for this window should be available to all SiteManager Material users.


Functional Procedure: CDOT will utilize this window to associate materials produced or supplied (by material code) to an approved producer and/or supplier (P/S). Care should be taken to identify correct P/S by code if multiple plants produce the material for the P/S and separate plant names are included in P/S code name. On-site materials produced for a specific contract will be related to the P/S code that is available for this purpose (code OSM100001, On-site Produced Materials).

Reports: No automated SiteManager reports exist for this window. No CDOT reports are available for this window. The data from this window is used to generate reports from the Approved Materials window as well as being part of reports generated elsewhere in SiteManager/LIMS.

6.3.1 Producer/Supplier Materials Panel

Figure 6.4 Producer/Supplier Materials Window

254 Approved Lists

Table 6.4 Producer/Supplier Materials Window - Fields


Producer/Supplier N/A

Auto-populated (code and name) from open file or choose keys command.

--

Material Code Yes

Search field. Begins record of a material code associated to a producer and/or supplier.

--

Material Full Name N/A Auto-populated from Material Code. --

Material Category N/A Auto-populated from Material Code. --

Approval Status Yes Drop-down menu. Type of approval. --

Source Type No Drop-down menu. (CDOT will not use). --

Effective Date Yes

Auto-populated to current date but may be changed when a material is added and must be less than Expiration Date (if entered).

--

Expiration Date Yes

Free-form date field. Defaults to all zeros. If entered, must be greater than the Effective Date.

--

Sample ID No

Search field. Uniquely identifies a sample used to approve the material.

--

Last Modified Date N/A Auto-populated. Date last change was made. --

Last Modified User ID

N/A Auto-populated. User ID of last user to update record.

--

6.3.1.1 Required Fields MATERIAL CODE: Search field (populated by Material Information window) used to identify specific unique material to be associated to the selected P/S. APPROVAL STATUS: Drop-down menu to record type of approval for associating material to P/S. Selections include Approved, Rejected, & Pending.

Code Table = APPRSTAT – Approved Status Type

Code Description

APPR Approved

PEND Pending

REJ Rejected

EFFECTIVE DATE: Free-form date field auto-populates to current date but may be changed at the discretion of originator. Must be less than Expiration Date (if entered). EXPIRATION DATE: Free-form date field may be populated at the discretion of the window originator if there is a required (or desired) end to the association of this material code to this P/S. Defaults to all zeros and will save in this format. Caution: when an Expiration Date is populated the field will be grayed out after the date has passed. The status then will than change and become inactive. This is especially important when using an Approval Status of Pending. All new data must then be entered if the Approval Status is changed to Approved. Be aware when a date is entered and not a time, the expiration date is at midnight of that date. Example: if the data is to expire at the end of the year use 01/01/12 and not 12/31/11.


6.3.1.2 CDOT will not use Fields Not required fields fall into two categories – those fields CDOT will not utilize and those fields that are optional for input. CDOT will not use the following fields: Source Type.

SOURCE TYPE: Drop-down menu. Only selection is Not currently used by CDOT.

Code Table = SRCTYPE – Source Tape

Code Description


Optional fields:

SAMPLE ID: Search field (populated by Review Samples window) used at the discretion of the window originator if there is a sample ID available that was utilized to approve the association of this material code to this P/S.


REMARKS CDOT has no specific use for this field, although this is available for use as needed. Mixed case. ATTACHMENTS Optional. PROCESS STATUS This window is available almost system wide by selecting Process Status from the Services menu. The window consists of two tab pages: Regular and Scheduled. See above explanation.

6.4 Qualified Labs Window

SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > APPROVED LISTS > QUALIFIED LABS

Use the Qualified Labs window to add and maintain the laboratories qualified to test samples and the tests they are qualified to perform.

Security Procedure: CDOT update authority for this window will be limited to the Technical Support, IT System Administration and the Central Lab Pavement Design Program. CDOT inquiry authority for this window should be available to all SiteManager Material users.

Functional Procedure: CDOT will utilize this window to record qualified laboratories. Laboratories performing tests recorded in SiteManager/LIMS must be included with this window to have tests assigned to them. The window associates a CDOT qualified lab with the test procedures they are approved to perform. Also, laboratories that receive samples shall be recorded here as Destination Labs.

256 Approved Lists

Top header (subpart) shows the Lab ID, Lab Name, and Contact. Lab ID is unique and remains in the system but Lab Name and Contact are editable after creation. Destination Labs will be recorded in this subpart only as they are not assigned or qualified to perform tests. The second subpart shows Type, Method, Authority and Expiration Date of the qualification. In order to meet system restrictions and to provide for all qualified lab maintenance to occur in updates to the final subpart there will be only one type, method, and authority used (CDOT CP-10) and the lab qualification expiration date will be set to 01/01/49. All lab qualification will be maintained in the final subpart which will be populated with the tests the lab is approved to perform. This is accomplished by selecting/highlighting the final subpart and then selecting the “new” icon in the toolbar which brings up the “select tests” window of test templates for all procedures performed by CDOT.

Reports: An automated SiteManager report exists for this data in the Approved Lists Reports tab, Qualified Labs Report.

6.4.1 Qualified Labs Panel

Figure 6.5 Qualified Labs Window


Table 6.5 Qualified Labs Window – Fields


Lab ID Yes Free-form field. Uniquely identifies a lab. Agency-defined. 10

Geographic Area

No Drop-down menu. (CDOT will not use). -

Lab Name Yes Free-form field. Full name of the lab as assigned. 50

Contact Person Yes Free-form field. Lab contact person’s full name. 50

Type Yes Drop-down menu. Type of qualification. -

Method Yes Drop-down menu. Method of qualification. -

Authority Yes Drop-down menu. Authority for the qualification. -

Expiration Date Yes

Free-form date field. Date the qualification expires. Globally set to 1/1/2049.

-

Test Method Yes

Choose keys selection from “new” icon. Uniquely identifies a test method that the lab is authorized to perform.

-

Test Description

N/A Auto-populated from Test Method. Full name and/or description of the selected test template.

-


LAB ID: Uniquely identifies a lab. This ID will follow the format shown in the attached table 0-2 below. This table represents the initial load into SM Materials to demonstrate uniqueness within a 10 character limit. LAB NAME: Uniquely identifies a lab. This name will follow the format shown in the attached table 0-2 below. This table represents the initial load into SM Materials to demonstrate uniqueness within a 50 character limit. CONTACT PERSON: Uniquely identifies the contact person for this lab. TYPE: Drop-down menu to record type of approval for lab qualification. Only selection is CDOT CP-10.

Code Table = LABQUAL – Lab Qualification Type

Code Description

CP10 CP 10

METHOD: Drop-down menu to record method of approval for lab qualification. Only selection is CDOT CP-10.

Code Table = QUALMETH – Qualification Method

Code Description

CP10 CP 10

258 Approved Lists

AUTHORITY: Drop-down menu to record authority of approval for lab qualification. Only selection is CDOT CP-10.

Code Table = QUALAUTH – Qualification Authority

Code Description

CP10 CP 10

EXPIRATION DATE: Free-form date field. Due to system parameters this will be set at this time to 01/01/49. TEST METHOD: Field is populated from the new record selection in toolbar. Selections available are numerous and represent tests performed by CDOT. These tests are maintained in the Material Test Template window. TEST DESCRIPTION: Auto-populated from the selection of Test Method. Full name and/or description of the selected test template.

6.4.1.2 CDOT will not use Fields CDOT will not use the following fields: Geographic Area.



Code Description


6.4.1.3 Reference Table The table below explains the interrelationship between destination labs and labs where test are assigned to qualified labs.

Table 6.6 Qualified Labs Table

Labs shaded in yellow are destination labs entered only in top header (subpart). Labs shaded in turquoise are units that perform and have tests assigned to them

Destination Lab Name (50 characters)

DL Lab ID (10 char)

Lab Unit Name (50 characters)

Lab Unit ID (10 char)

Bypass Destination

Lab

Bypass Lab Unit

Region 1 Denver R1DenverDL Region 1 Denver Lab R1DenvrLab Yes No

Region 1 Limon R1LimonDL Region 1 Limon Lab R1LimonLab Yes Yes

Region 1 Tunnel R1TunnelDL Region 1 Tunnel Lab R1TunelLab Yes Yes

Region 1 Mobile R1MobileDL Region 1 Mobile Lab R1MobilLab Yes Yes

Region 2 Pueblo R2PuebloDL Region 2 Pueblo Lab R2PueblLab Yes Yes





(Last update 2/16/2012)


ADDRESS CDOT will not use at this time. PROCESS STATUS This window is available almost system wide by selecting Process Status from the Services menu. The window consists of two tab pages: Regular and Scheduled. See above explanation.

6.4.2 Tests Associated to Each Laboratory Unit

The tables show what tests are assigned to each Laboratory Unit.

Region 2 Lamar R2LamarDL Region 2 Lamar Lab R2LamarLab Yes Yes


Region 3 Grand Junction R3GrdJctDL Region 3 Grand Junction

Lab R3GrJctLab Yes Yes

Region 3 Glenwood R3GlnwdDL Region 3 Glenwood Lab R3GlnwdLab Yes Yes

Region 3 Craig R3CraigDL Region 3 Craig Lab R3CraigLab Yes Yes


Region 4 Evans R4EvansDL Region 4 Evans Lab R4EvansLab Yes No

Region 4 Boulder R4BouldrDL Region 4 Boulder Lab R4BouldLab Yes No

Region 4 Sterling R4SterlgDL Region 4 Sterling Lab R4SterlLab Yes No

Region 4 Loveland R4LovlndDL Region 4 Loveland Lab R4LvlndLab Yes No

Region 4 Mobile R4MobileDL Region 4 Mobile Lab R4MobilLab Yes No

Region 5 Durango R5DuragoDL Region 5 Durango Lab R5DurgoLab Yes Yes

Region 5 Alamosa R5AlamsaDL Region 5 Alamosa Lab R5AlmsaLab Yes Yes



Statewide Field StatFildDL Statewide Field Lab FieldLab Yes Yes

Central Laboratory Denver

CLDenverDL Euro/Bituminous Lab EuroLab Yes No

Flexible Pavement Lab FlexLab Yes No

Physical Properties Lab PhPrLab Yes No

Concrete Lab ConcLab Yes No

Chemical Lab ChemLab Yes No


260 Approved Lists

Table 6.7 Tests Assigned to Chemical Lab, Lab ID: ChemLab

Test Method Description

C1038 Expansion of Hydraulic Cement Mortar Bars Stored in Water

C114 Chemical Analysis of Hydraulic Cement

C1152 Standard Test Method for Acid-Soluble Chloride in Mortar and Concrete

C1218 Standard Test Method for Water-Soluble Chloride in Mortar and Concrete

C1260 Potential Alkali Reactivity of Aggregates (Mortar-Bar Method)

C151 Autoclave Expansion of Portland Cement

C1567 Standard Test Method for Determining the Potential Alkali-Silica Reactivity of Combinations of Cementitious Materials and Aggregate (Accelerated Mortar-Bar Method)

C1602 Standard Specification for Mixing Water Used in the Production of Hydraulic Cement Concrete

C1603 Standard Test Method for Measurement of Solids in Water

C185 Air Content of Hydraulic Cement Mortar

C187 Normal Consistency of Hydraulic Cement

C188 Density of Hydraulic Cement

C191 Time of Setting of Hydraulic Cement by Vicat Needle

C204 Fineness of Hydraulic Cement by Air Permeability Apparatus

C311 Sampling and Testing Fly Ash or Natural Pozzolans for Use in Portland-Cement Concrete

C451 Early Stiffening of Hydraulic Cement (Paste Method)

C452 Expansion of Portland-Cement Mortars Exposed to Sulfate

CPL2103 Determining the Sulfate Ion Content in Water or Water-Soluble Sulfate Ion Content in Soil

CPL2104 Determining Water-Soluble Chloride Ion Content in Soil

D2976 pH of Peat Materials

G51 Measuring pH of Soil for Use in Corrosion Testing

G57 Field Measurement of Soil Resistivity Using the Wenner Four-Electrode Method

T299 Rapid Identification of Alkali-Silica Reaction Products in Concrete

(Last updated 11/13/2012)


Table 6.8 Tests Assigned to Concrete Lab, Lab ID: ConcLab


C1064 Temperature of Freshly Mixed Portland Cement Concrete

C109-28 Compressive Strength of Hydraulic Cement Mortars (Using 2-in. or [50-mm] Cube Specimens) - 28 Day


C109-I Compressive Strength of Hydraulic Cement Mortars (Using 2-in. or [50-mm] Cube Specimens) - Info

C174 Standard Test Method for Measuring Thickness of Concrete Elements Using Drilled Concrete Cores

C39-28 Compressive Strength of Cylindrical Concrete Specimens - 28 Day



C39-I Compressive Strength of Cylindrical Concrete Specimens - Info

C496 Splitting Tensile Strength of Cylindrical Concrete Specimens

T106-28 Compressive Strength of Hydraulic Cement Mortar (Using 50-mm or 2-in. Cube Specimens) - 28 Day


T106-I Compressive Strength of Hydraulic Cement Mortar (Using 50-mm or 2-in. Cube Specimens) - Info

T119 Slump of Hydraulic Cement Concrete

T121 Density (Unit Weight), Yield, and Air Content (Gravimetric) of Concrete

T148 Measuring Length of Drilled Concrete Cores

T152 Air Content of Freshly Mixed Concrete by the Pressure Method

T196 Air Content of Freshly Mixed Concrete by the Volumetric Method

T24-28 Obtaining and Testing Drilled Cores and Sawed Beams of Concrete - 28 Day


T24-I Obtaining and Testing Drilled Cores and Sawed Beams of Concrete - Info

T97-28 Flexural Strength of Concrete (Using Simple Beam with Third-Point Loading) - 28 Day


T97-I Flexural Strength of Concrete (Using Simple Beam with Third-Point Loading) - Info


262 Approved Lists

Table 6.9 Tests Assigned to Euro/Bituminous Lab, Lab ID: EuroLab


CPL2202 Protective Covering Qualities for Bridge Deck Waterproofing Membrane (CTR)

CPL2203 Pliability and Thickness of Prefabricated Reinforced Membrane(CTR)

CPL2210 Determining Toughness and Tenacity of Rubberized Asphaltic Materials

CPL2211 Elastic Recovery Test Procedure

CPL2212 Residue by Evaporation of Asphalt Emulsion

CPL2213 Coating of Bitumen-Aggregate Mixtures

CPL2214 Verification of Binder Acidity or Alkalinity

CPL5112 Hamburg Wheel-Track Testing of Compacted Bituminous Mixtures

CPL5114 French Rut Testing of Compacted Bituminous Mixtures

D5329 Standard Test Methods for Sealants and Fillers‚ Hot-Applied‚ for Joints and Cracks in Asphaltic and Portland Cement Concrete Pavements

D7402 Identifying Cationic Emulsified Asphalts

D86 Standard Test Method for Distillation of Petroleum Products at Atmospheric Pressure

T228 Specific Gravity of Semi-Solid Bituminous Materials

T300 Force Ductility Test of Asphalt Materials

T301 Elastic Recovery Test of Asphalt Materials by Means of a Ductilometer

T313 Determining the Flexural Creep Stiffness of Asphalt Binder Using the Bending Beam Rheometer (BBR)

T315 Determining the Rheological Properties of Asphalt Binder Using a Dynamic Shear Rheometer (DSR)

T316 Viscosity Determination of Asphalt Binder Using Rotational Viscometer

T49 Penetration of Bituminous Materials

T50 Float Test for Bituminous Materials

T51 Ductility of Bituminous Materials

T53 Softening Point of Bitumen (Ring-and-Ball Apparatus)

T59-21 Testing Emulsified Asphalts

T72 Saybolt Viscosity



Table 6.10 Tests Assigned to Flexible Pavement Lab, Lab ID: FlexLab


CP31HMA Sieve Analysis of Aggregates for HMA

CP42 Estimation of Asphalt Content in Hot Mix Asphalt Through Back Calculations Using Gse

CP43 Determining Moisture (Water) or Volatile Distillates Content of HMA

CP44 Bulk Specific Gravity and Percent Relative Compaction of Compacted Bituminous Mixtures Using Saturated Surface-Dry Specimens

CP44L Bulk Specific Gravity and Percent Relative Compaction of Compacted Bituminous Mixtures Using Saturated Surface-Dry Specimens - LONGITUDINAL

CP46 Determination of Gradation of Aggregate in a Core from Asphalt Pavement (Use CPL-5120 to determine gradation)

CP48aa Determination of the Voids in the Mineral Aggregate (VMA) (Should be calculated in the HMA test report. Does not need to be calculated separately)

CP50 Calculation of Dust to Asphalt Ratio of Bituminous Mixes

CP51 Determining the Maximum Specific Gravity of HMA

CP85 Asphalt Cement Content of Asphalt Mixtures by the Nuclear Method

CP85C Asphalt Cement Content of Asphalt Mixtures by the Nuclear Method - Correlation Factor

CPL5106 Resistance to Deformation of Bituminous Mixtures by Means of Hveem Apparatus

CPL5109 Resistance of Compacted Bituminous Mixture to Moisture Induced Damage

CPL5111 Determining the Percent of Recycling Agent to Use for Cold Recycling of Asphalt Concrete

CPL5115 Preparing and Determining the Density of Bituminous Mixture Test Specimens Compacted by the Superpave Gyratory Compactor

CPL5120 Determination of the Asphalt Binder Content of Bituminous Mixtures by the Ignition Method

CPL5120C Determination of the Asphalt Binder Content of Bituminous Mixtures by the Ignition Method - Correlation Factor

CPL5140 Mix Design for In-Place Recycling of Asphalt Pavements

T269 Percent Air Voids in Compacted Dense and Open Asphalt Mixtures

T30 Mechanical Analysis of Extracted Aggregate


264 Approved Lists

Table 6.11 Tests Assigned to Physical Properties Lab, Lab ID: PhPrLab


A370 Standard Test Methods and Definitions for Mechanical Testing of Steel Products

C430 Fineness of Hydraulic Cement by the 45 μm (no. 325) sieve

C535 Resistance to Degradation of Large-Size Coarse Aggregate by Abrasion and Impact in the Los Angeles Machine

CP23 Determining Maximum Dry Density and Optimum Moisture of the Total Sample of Soil-Rock Mixture

CP25 Calculation of Percent Relative Compaction of Soils and Soil-Rock Mixtures

CP31 Sieve Analysis of Aggregates

CP31S Sieve Analysis of Aggregates - When Splitting on the #4 Sieve

CP31X Sieve Analysis of Aggregates - Extracted Aggregates

CP33 Total Evaporable Moisture Content and Surface Moisture Content of Aggregate by Drying

CP37 Plastic Fines in Graded Aggregates and Soils by Use of the Sand Equivalent Test

CP45 Determining Percent of Particles with Two or More Fractured Faces

CPL4102 Specific Gravity and Absorption of Fine Aggregate

CPL4209 Physical Testing of Quicklime, Hydrated Lime, and Limestone

CPL4211 Resistance of Coarse Aggregate to Degradation by Abrasion in the Micro-Deval Apparatus

CPL4215 Determination of Percent Moisture in Rock Salt

CPL4216 Determination of Salt Content of Sanding Materials

D4791 Flat Particles, Elongated Particles, or Flat and Elongated Particles in Coarse Aggregate

D5821 Determining the Percentage of Fractured Particles in Coarse Aggregate

T112 Clay Lumps and Friable Particles in Aggregate

T113 Lightweight Pieces in Aggregate

T180 Moisture–Density Relations of Soils Using a 4.54-kg (10-lb) Rammer and a 457-mm (18-in.) Drop

T19 Bulk Density (“Unit Weight”) and Voids in Aggregate

T21 Organic Impurities in Fine Aggregates for Concrete

T244 Mechanical Testing of Steel Products

T255 Total Evaporable Moisture Content of Aggregate by Drying

T304 Uncompacted Void Content of Fine Aggregate

T37 Sieve Analysis of Mineral Filler for Hot Mix Asphalt (HMA)

T84 Specific Gravity and Absorption of Fine Aggregate

T85 Specific Gravity and Absorption of Coarse Aggregate

T89 Determining the Liquid Limit of Soils

T90 Determining the Plastic Limit and Plasticity Index of Soils

T96 Resistance to Degradation of Small-Size Coarse Aggregate by Abrasion and Impact in the Los Angeles Machine

T99 Moisture-Density Relations of Soils Using a 2.5-kg (5.5-lb) Rammer and a 305-mm



(12-in.) Drop


266 Approved Lists

Table 6.12 Tests Assigned to Soils Lab, Lab ID: SoilLab


CP21 Mechanical Analysis of Soils



CPL3101 Resistance R-Value and Expansion Pressure of Compacted Soils or Aggregates by Means of Hveem Stabilometer

CPL3104 Determining the Durability of Shales for Use as Embankments

CPL3105 Grain Size Analysis of Soil for AASHTO Classification

CPL3106 Grain Size Analysis of Soil for Unified Soil Classification System

CPL3201 Continuous Penetration Test

D2487 Classification of Soils for Engineering Purposes (Unified Soil Classification System)

D4546 One-Dimensional Swell or Settlement Potential of Cohesive Soils

D5102 Unconfined Compressive Strength of Compacted Soil-Lime Mixtures

M145 Classification of Soils and Soil-Aggregate Mixtures for Highway Construction Purposes

T100 Specific Gravity of Soils


T191 Density of Soil In-Place by the Sand-Cone Method

T208 Unconfined Compressive Strength of Cohesive Soil

T215 Permeability of Granular Soils (Constant Head)

T216 One-Dimensional Consolidation Properties of Soils

T224 Correction for Coarse Particles in the Soil Compaction Test

T233 Density of Soil In-Place by Block, Chunk, or Core Sampling

T236 Direct Shear Test of Soils Under Consolidated Drained Conditions

T265 Laboratory Determination of Moisture Content of Soils

T267 Determination of Organic Content in Soils by Loss on Ignition

T296 Unconsolidated, Undrained Compressive Strength of Cohesive Soils in Triaxial Compression

T297 Standard Method of Test for Consolidated, Undrained Triaxial Compression Test on Cohesive Soils

T307 Determining the Resilient Modulus of Soils and Aggregate Materials




T99 Moisture-Density Relations of Soils Using a 2.5-kg (5.5-lb) Rammer and a 305-mm (12-in.) Drop



Table 6.13 Tests Assigned to Region Labs, Lab ID'S: R1DenvrLab, R1LimonLab, R1TunelLab, R2CSpgsLab, R2LamarLab, R2PueblLab, R3CraigLab, R3GlnwdLab, R3GrJctLab, R4BouldLab, R4EvansLab, R4LvlndLab, R4SterlLab, R5AlmsaLab, R5DurgoLab, and R6DenvrLab


ACCOST Document AC Cost per Ton










CERT Document COC or CTR
















CP48aa Determination of the Voids in the Mineral Aggregate (VMA)



268 Approved Lists


CP53 Determining Maximum Density of Cold In-Place Recycled Pavement

CP57 Determining the "Free Moisture" in Cold In-Place Recycled Pavement

CP58 Detecting and Measuring Temperature Segregation of HMA

CP66 Measuring Texture Depth of Portland Cement Concrete Using a Tire Tread Depth Gauge

CP67 Determining Adhesion of Joint Sealant to Concrete Pavement

CP77 Determination of Macro-texture of Planed Hot Mix Asphalt Pavement

CP80 In-Place Density and Moisture Content of Soil and Soil-Aggregate by the Nuclear Method

CP81 Density and Percent Relative Compaction of In-Place Bituminous Pavement by the Nuclear Method

CP82 Field Correction of the In-Place Measurement of Density of Bituminous Pavement by the Nuclear Method









































T26 Quality of Water to Be Used in Concrete














VISUAL Visual Inspect and Accept Small Quantity


270 Approved Lists

Table 6.14 Tests Assigned to Region Labs: Lab ID'S: R2PueblLab, R3GrJctLab, and R4EvansLab




Table 6.15 Tests Assigned to Region Labs: Lab ID'S: R4EvansLab, R5AlmsaLab, and R5DurgoLab





Table 6.16 Tests Assigned to Region Mobile Labs, Lab ID'S: R1MobilLab, R2MobilLab, R3MobilLab, R4MobilLab, and R5MobilLab































272 Approved Lists















Table 6.17 Tests Assigned to Statewide Field Labs, Lab ID: FieldLab
































CP77 Determination of Macro-texture of Planed Hot Mix Asphalt Pavement

274 Approved Lists
















D4972 pH of Soils

















276 Approved Lists

Table 6.18 Tests Assigned to AMRL


A370 Definitions for Mechanical Testing of Steel Products







C1152 Acid-Soluble Chloride in Mortar and Concrete

C1218 Water-Soluble Chloride in Mortar and Concrete





C1603 Measurement of Solids in Water

C174 Measuring Thickness of Concrete Elements Using Drilled Concrete Cores













C452 Potential Expansion of Portland-Cement Mortars Exposed to Sulfate




CP23 Determining Maximum Dry Density and Optimum Moisture of the Total Sample of



Soil-Rock Mixture





CP33 Total Evaporable Moisture Content and Surface Moisture Content of Aggregate





























278 Approved Lists










CPL5115 Preparing and Determining the Density of Bituminous Mixture Test Specimens Compacted by the SuperPave Gyratory Compactor









D5329 Sealants and Fillers‚ Hot-Applied‚ for Joints and Cracks in Asphaltic and Portland Cement Concrete Pavements



D86 Distillation of Petroleum Products at Atmospheric Pressure






































T297 Consolidated, Undrained Triaxial Compression Test on Cohesive Soils










280 Approved Lists





T51 Ductility of Asphalt Materials


T59-21 Weight Per Gallon of Emulsion Asphalt












6.5 LIMS Maintain Destination for Lab Units Window

LIMS Navigation NAVIGATION PANEL > SYSTEM ADMIN > MAINTAIN DESTINATION LAB

Destination Labs are the physical location where the samples are received for testing. The Lab Unit is a subunit of the Destination Lab where the actual testing takes place. The Maintain Destination Lab window is used to assign each Lab Unit to a Destination Lab. Each Lab Unit can belong to only one Destination Lab. Prior to using this window, all labs must be defined using SiteManager’s Qualified Labs window. To specify if a Lab Unit can receive a sample directly, bypass the Destination Lab. To specify if a sample can have test data placed in the LIMS Enter Test Data window directly, bypass both the Destination Lab and the Lab Unit.

Security Procedure: CDOT update authority for this window will be limited to the Technical Support, IT System Administration, and Central Lab Pavement Design Program.

Functional Procedure: CDOT will utilize this window to associate all Lab Units to a Destination Lab and to determine the flow of a sample record created.


Labs will be given a unique ID in the Qualified Labs window to define them as Destination Labs or Lab Units in order to appear in the drop-downs for these designations. To bypass the requirement of a sample being received by the Destination Lab, populate the check box for Bypass Destination Receive for the Destination Lab / Unit Lab combination line desired. This will enable the sample to appear directly in the LIMS Receive Sample in Lab Unit window. To bypass the requirement of a sample being received by the Lab Unit, populate the check box for Bypass Lab Unit Receive for the Destination Lab / Unit Lab combination line desired. This will enable the sample to appear directly in the LIMS Enter Test Results window.

Reports: No automated SiteManager reports exist for this window. No CDOT reports are available for this window. Note: An attached table at the end demonstrates the labs currently assigned to SiteManager Materials and the selections for bypassing Destination Lab and/or Lab Unit for each as of the date shown at the bottom of the table.

6.5.1 Maintain Destination for Lab Units Panel

Figure 6.6 Maintain Destination for Lab Units Window

282 Approved Lists

Table 6.19 Maintain Destination for Lab Units Window - Fields


Destination Lab Yes Drop-down menu. The Destination Lab where the lab unit exists that will perform the test.

-

Lab Unit Yes

Drop-down menu. Lab unit that will perform testing. Associated here to a destination lab.

-

Bypass Destination

Receive Yes

Check box. Selection determines whether a sample will bypass this destination lab and need to be received in the lab unit directly.

-

Bypass Lab Unit Receive

Yes Check box. Indicates whether a sample can bypass this lab unit to record sample test results.

-


DESTINATION LAB: Drop-down menu of all Destination Labs in system. This list and designation is maintained in the Qualified Labs window of SiteManager. A Destination Lab may have several Lab Units associated to it with separate lines in this window. LAB UNIT: Drop-down menu of all testing Lab Units in system. This list and designation is maintained in the Qualified Labs window of SiteManager. A Lab Unit may only be assigned to one Destination Lab. BYPASS DESTINATION RECEIVE: Checkbox to be selected if sample receiving by the Destination Lab unit is not desired. Sample will be available directly for receiving in the LIMS Receive Sample in Lab Unit window. BYPASS LAB UNIT RECEIVE: Checkbox to be selected if sample receiving by the Lab Unit is not desired. Sample will be available directly for data entry in the LIMS Enter Test Results window.

6.5.1.2 Reference Table The table below explains the interrelationship between destination labs and labs where test are assigned to qualified labs.

Table 6.20 Qualified Labs Table

Labs shaded in yellow are destination labs entered only in top header (subpart). Labs shaded in turquoise are units that perform and have tests assigned to them

Destination Lab Name (50 characters)

DL Lab ID (10 char)

Lab Unit Name (50 characters)

Lab Unit ID (10 char)

Bypass Destination

Lab

Bypass Lab Unit


Region 1 Limon R1LimonDL Region 1 Limon Lab R1LimonLab Yes Yes

Region 1 Tunnel R1TunnelDL Region 1 Tunnel Lab R1TunelLab Yes Yes


Region 2 Pueblo R2PuebloDL Region 2 Pueblo Lab R2PueblLab Yes Yes


(Last update 2/16/2012)

6.6 Qualified Labs Report Window

SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > APPROVED LISTS REPORTS > QUALIFIED LABS REPORT

Use the Qualified Labs Report window to display general laboratory information, laboratory qualifications, and expiration dates. Generate by Geographic Area, Qualification Type, and Days to Expiration. This report is hard coded into SiteManager-Materials. It cannot be modified except for inserting globally name of state.




Region 2 Lamar R2LamarDL Region 2 Lamar Lab R2LamarLab Yes Yes


Region 3 Grand Junction R3GrdJctDL Region 3 Grand Junction

Lab R3GrJctLab Yes Yes

Region 3 Glenwood R3GlnwdDL Region 3 Glenwood Lab R3GlnwdLab Yes Yes

Region 3 Craig R3CraigDL Region 3 Craig Lab R3CraigLab Yes Yes


Region 4 Evans R4EvansDL Region 4 Evans Lab R4EvansLab Yes No

Region 4 Boulder R4BouldrDL Region 4 Boulder Lab R4BouldLab Yes No

Region 4 Sterling R4SterlgDL Region 4 Sterling Lab R4SterlLab Yes No

Region 4 Loveland R4LovlndDL Region 4 Loveland Lab R4LvlndLab Yes No

Region 4 Mobile R4MobileDL Region 4 Mobile Lab R4MobilLab Yes No

Region 5 Durango R5DuragoDL Region 5 Durango Lab R5DurgoLab Yes Yes

Region 5 Alamosa R5AlamsaDL Region 5 Alamosa Lab R5AlmsaLab Yes Yes



Statewide Field StatFildDL Statewide Field Lab FieldLab Yes Yes

Central Laboratory Denver

CLDenverDL Euro/Bituminous Lab EuroLab Yes No

Flexible Pavement Lab FlexLab Yes No

Physical Properties Lab PhPrLab Yes No

Concrete Lab ConcLab Yes No

Chemical Lab ChemLab Yes No


284 Approved Lists

6.6.1 Qualified Labs Report Panels

Figure 6.7 Qualified Labs Report Selections Window

Figure 6.8 Qualified Labs Report Window


Table 6.21 Qualified Labs Report Window - Fields


Header information

RPT ID Report ID.

USER User accessing the report.

DATE Date the user accessed the report.

PAGE Page number and total number of pages in the report.

Lab information

Lab Name Full name of the lab.

Lab ID Uniquely identifies a lab. Agency-defined.

Geographic Area Where the lab is located. Agency-defined.

Telephone Number Phone number for the lab.

Qualifications

Type Type of qualification.

Method Method of qualification used..

Authority Authority by which the qualification was judged.

Expiration Date Date the qualification expires.

Tests

Test Method Uniquely identifies a test template / tests that may be completed by the lab.

Test Description Full name and/or description of the selected test template.

6.7 Material User Window

SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > APPROVED LISTS > MATERIAL USER

Use the Material User window to create, modify, and delete general material user classifications. In SiteManager, material users can be samplers and/or testers. If the person will need to use the SiteManager application, first use the User Security window to set up that person as a SiteManager user before defining them as a material user in the Material User window. If not defined as a SiteManager user first, other SiteManager users will only be able to select their names on sample records as a sampler or tester and maintain their qualifications, but that person will not be able to log onto SiteManager. If the person will be a tester and/or sampler, first use the Material User window to classify the user as a sampler and/or tester. Then, use the Sampler Qualifications window and/or Tester Qualifications window to record details of their qualifications. The Material User window displays the information from the Sampler Qualifications window and Tester Qualifications windows. Note: Specify a user as a Global Tester in the Material User window to override the settings on the Tester Qualifications window and designate the user as a tester for any test. At this time CDOT will not designate anyone as a Global Tester.

286 Approved Lists

Security Procedure: CDOT update authority for this window will be limited to the Technical Support, IT System Administration, Central Lab Pavement Design Program, and Central Lab Unit Groups (Binder, Flexible Pavement and Chemical, Concrete/Physical Properties, and Soils). CDOT inquiry authority for this window should be available to all SiteManager Material users.

Functional Procedure: CDOT will utilize this window to record SiteManager/LIMS Material Users. Top header (subpart) shows a Material User’s User ID, User Name, and their designation as a SM User, Sampler, Tester, and/or Global Tester. At this time CDOT will not designate anyone as a Global Tester. The second subpart simply displays sampling and testing qualifications maintained in the Sampler Qualifications and Tester Qualifications windows.

Reports: No automated SiteManager reports exist for this window. No CDOT reports are available for this window. A report of tester qualifications approaching expiration will be available from the Tester Qualifications window data.

6.7.1 Material User Panel

Figure 6.9 Material User Window


Table 6.22 Material User Window - Fields


Material User Information (General)

User ID Yes

Auto-populated from open file search lens selection. Uniquely identifies the SiteManager Material User.

8

User Name N/A Auto-populated from the User ID. 50

Geographical Area No Drop-down menu. (CDOT will not use). -

SM Security User Yes

Check box, Auto-populated from and maintained in the User Security window. Indicates whether the user is a SiteManager Security user.

-

Tester Yes

Check box. Selection determines whether the user may be selected as a sampler on sample records.

-

Sampler Yes

Check box. Selection determines whether the user may be selected as a tester on sample records.

-

Global Tester Yes

Check box. Selection determines whether the user is a global tester. CDOT will not use Global Tester.

-

Sampler Qualifications pane

Type N/A Auto-populated from Sampler Qualifications window. -

Level N/A Auto-populated from Sampler Qualifications window. -

Method N/A Auto-populated from Sampler Qualifications window. -

Effective Date N/A Auto-populated from Sampler Qualifications window. -

Expiration Date N/A Auto-populated from Sampler Qualifications window. -

Active Ind N/A Auto-populated from Sampler Qualifications window. Indicates whether the individual is active in the system.

-

Tester Qualifications pane

Type N/A Auto-populated from Tester Qualifications window. -

Level N/A Auto-populated from Tester Qualifications window. -

Authority N/A Auto-populated from Tester Qualifications window. -

Effective Date N/A Auto-populated from Tester Qualifications window. -

Expiration Date N/A Auto-populated from Tester Qualifications window. -

Active Ind N/A Auto-populated from Tester Qualifications window. Indicates whether the individual is active in the system.

-

6.7.1.1 Required Fields USER ID: Uniquely identifies a SM Materials user. This ID will be auto populated when the SiteManager account is created. USER NAME: User’s full name auto populated from USER ID. SM SECURITY USER: Checkbox will be marked if user is a SiteManager User. SAMPLER: Checkbox to be selected if user is to be entered and maintained in the Sampler Qualifications window.

288 Approved Lists

TESTER: Checkbox to be selected if user is to be entered and maintained in the Tester Qualifications window. GLOBAL TESTER: Checkbox to be selected if user is a Global Tester. At this time CDOT will not designate anyone as a Global Tester. Note: All other fields (in Sampler Qualifications and Tester Qualifications panes) are auto-populated and present the data for this user that has been maintained in the Sampler Qualifications and Tester Qualifications windows.

6.7.1.2 CDOT will not use Fields CDOT will not use the following field: Geographic Area.


REMARKS CDOT has no specific use for this field, although this is available for use as needed. Mixed case. ADDRESS CDOT will not use at this time.

GENERIC FIELDS CDOT will not use.

PROCESS STATUS This window is available almost system wide by selecting Process Status from the Services menu. The window consists of two tab pages: Regular and Scheduled. REGULAR TAB The Regular tab page lists Distributed Processing Services (DPS) submitted processes; that is, Report Template Facility (RTF) custom report processes, SiteManager PowerBuilder reports, and background or batch processes. Here, authorized users can see the current status of submitted processes, delete submitted or complete jobs, or drill down to view or print the output produced by completed or failed processes. SCHEDULED TAB The Scheduled tab page lists DPS submitted processes; that is, RTF custom report processes, SiteManager PowerBuilder reports, and background or batch processes. Here, authorized users can see the current status of submitted processes, delete submitted or complete jobs, or drill down to view or print the output produced by completed or failed processes. The processes listed on the Scheduled tab are those processes which have be set to run on a specific schedule by an authorized user. Standard SiteManager window and tab-level security applies to the scheduled tab page window. Only those processes to which the user has been assigned security access will be presented on the displayed list.

Training Comments:

Accounts will need to be processed through the normal process that is in existence for construction:


Account request form will need to be submitted to the CDOT Service Desk, along with an access agreement.

The forms will be forwarded to the Program and Project Analysis Unit for account creation. If the group, sampler/tester is checked, the material user window will be updated to include the user as a Sampler and/or Tester.

Notification of the account creation will include Central Lab Pavement Design Unit and appropriate Region Materials Office.

6.8 Sampler Qualifications Window

SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > APPROVED LISTS > SAMPLER QUALIFICATIONS

Use the Sampler Qualifications window to manage a sampler’s qualifications. Use the Material User window to classify a user as a sampler, before any sampler qualifications can be established in the Sampler Qualifications window. Add and maintain specific details regarding the qualifications of the sampler in the Sampler Qualifications window. Information from the Sampler Qualifications window appears in the Material Users window.

Security Procedure: CDOT update authority for this window will be limited to the Technical Support, IT System Administration, Central Lab Pavement Design Program, the Region Materials Office, and the Central Lab Unit Groups (Binder, Flexible Pavement and Chemical, Concrete/Physical Properties, and Soils). CDOT inquiry authority for this window should be available to all SiteManager Material users.

Functional Procedure: CDOT will utilize this window to record qualified samplers. Individuals performing sampling of certain types of materials for CDOT must be included in this window to have their samples recorded in SiteManager/LIMS. The window associates a CDOT qualified individual with the types of materials they are approved to sample. Top header (subpart) shows a sampler’s User ID, User Name, and their designation as a SM User, Sampler, Tester, and/or Global Tester. At this time CDOT will not designate anyone as a Global Tester. The second subpart shows Type, Level, and Method of qualification with Effective and Expiration Dates and an “active” indicator. This subpart is utilized to maintain the sampler’s association with materials they are qualified to sample. The Type is a Material Category designated and maintained in the Material Information window. The Level is the certifying body associated with groups of materials as required by the CDOT Field Materials Manual (FMM), e.g. “ACI”, “LabCAT” and “WAQTC”. The Method for CDOT qualifications is CP-10 from the FMM. A separate line for each combination of material categories (Type) and certifying bodies (Level) shall be maintained for the sampling of certain, controlled materials that a User is qualified to perform. The only Material Categories (Type) currently requiring qualified samplers are Aggregate, Asphalt, Concrete, and Soil. Aggregate and Asphalt (Types) will be associated with the Level “LabCAT”. Concrete (Type) will be associated with the Level “ACI”. Soil (Type) will be associated with the Level “WAQTC”.

Reports: No automated SiteManager reports exist for this window. No CDOT reports are available for this window.

290 Approved Lists

6.8.1 Sampler Qualifications Panel

Figure 6.10 Sampler Qualifications Window


Table 6.23 Sampler Qualifications Window – Fields



User ID Yes Auto-populated from open file search lens selection. Uniquely identifies the sampler.

-

User Name N/A Auto-populated from the User ID. -

Geographic Area

No Drop-down menu. (CDOT will not use). -

SM Security User

N/A Auto-populated from the Material User window. Indicates whether the user is a SiteManager user.

-

Sampler N/A Auto-populated from and maintained in the Material User window. Determines whether the user may be selected as a sampler on sample records.

-

Tester N/A Auto-populated from and maintained in the Material User window. Determines whether the user may be selected as a tester on sample records.

-

Global Tester N/A

Auto-populated from and maintained in the Material User window. Indicates whether the user is a global tester. If selected, user may perform all tests regardless of qualifications. CDOT will not use Global Tester.

-

Sampler Qualifications (Detail)

Type Yes Drop-down menu. Type of material the sampler is qualified to sample. Displays the material categories as maintained in the Material Information window.

Level Yes Drop-down menu. Certifying agency the sampler has received certification from.

Method Yes Drop-down menu. Method of qualification (FMM CP-10).

Effective Date Yes Free-form date field. Date the qualification begins to be valid. Defaults to the current date.

Expiration Date

Yes Free-form date field. Date the qualification is no longer valid.

Active Ind N/A Auto-populated Active Indicator. Indicates whether the qualification is active.

6.8.1.1 Required Fields USER ID: Uniquely identifies a SM Materials user. This ID will be in the format required by the User Security window during set-up as a SiteManager user. USER NAME: User’s full name. SM SECURITY USER: Checkbox indicates if user is a SiteManager User. SAMPLER: Checkbox indicates if user is a qualified sampler and could be entered and maintained in the Sampler Qualifications window. TESTER: Checkbox indicates if user is a qualified tester and must be entered and maintained in the Tester Qualifications window.

292 Approved Lists

GLOBAL TESTER: Checkbox indicates if user is a Global Tester. At this time CDOT will not designate anyone as a Global Tester. TYPE: Drop-down menu of material categories maintained in the Material Information window. Certain material codes are grouped into certain categories in order to require qualified sampling. Only Aggregate, Asphalt, Concrete, and Soil will be used.

Code Table = MATLCATG – Category of Material

(Table codes and descriptions are not displayed here due to being numerous and related to material being sampled.)

LEVEL: Drop-down menu of certifying agencies approved by CDOT for sampling and testing certification. Selections are ACI, LabCAT, WAQTC, AMRL, and General.

Code Table = QUALEV – Qualification Level

Code Description

ACI ACI

LABC LabCAT

WAQT WAQTC

AMRL AMRL

GEN General

METHOD: Drop-down menu of method of qualification as required by the CDOT Field Materials Manual. Only selection is CP-10.

Code Table = QUALMETH – Qualification Method

Code Description

CP10 CP-10

EFFECTIVE DATE: Free form date field to indicate the date the qualification begins. Defaults to current date but may be set to any effective date. EXPIRATION DATE: Free form date field to indicate the date the qualification will expire and no longer be valid. After this date sampler will no longer be available for selection as sampler for materials requiring qualified sampling. This date may be updated prior to expiration. If this date is reached, and the active indicator turns to “N”, this record is no longer editable and a new line will have to be created. ACTIVE INDICATOR: Indicates whether listed qualification is active per effective and expiration dates.

6.8.1.2 CDOT will not use Fields CDOT will not use the following field: Geographic Area.



REMARKS CDOT has no specific use for this field, although this is available for use as needed. Mixed case.

ADDRESS CDOT will not use at this time.



MATERIAL USER The Material User window appears.

COPY RECORDS Copies a new record to assign a New Material Code to the existing bid item.

Training Comments: The only Material Categories (Type) currently requiring qualified samplers are Aggregate, Asphalt, Concrete, and Soil. Aggregate and Asphalt (Types) will be associated with the Level “LabCAT”. Concrete (Type) will be associated with the Level “ACI”. Soil (Type) will be associated with the Level “WAQTC”.

6.9 Tester Qualifications Window

SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > APPROVED LISTS > TESTER QUALIFICATIONS

Use the Tester Qualifications window to manage a tester’s qualifications. Use the Material User window to classify a user as a tester, before any tester qualifications can be established in the Tester Qualifications window. Add and maintain specific details regarding the qualifications of the tester in the Tester

294 Approved Lists

Qualifications window. The Material User window will display the information from the Tester Qualifications window. Note: When users are marked as a Global Tester in the Material User window, this over-rides the settings on the Tester Qualifications window and allows the user to be designated as a tester for any test, regardless of the qualifications specified on the Tester Qualifications window. At this time CDOT will not designate anyone as a Global Tester.

Security Procedure: CDOT update authority for this window will be limited to the Technical Support, IT System Administration, the Central Lab Pavement Design Program, the Region Materials Office, and the Central Lab Unit Groups (Binder, Flexible Pavement and Chemical, Concrete/Physical Properties, and Soils). CDOT inquiry authority for this window should be available to all SiteManager Material users.

Functional Procedure: CDOT will utilize this window to record qualified testers. Individuals performing testing for CDOT must be included in this window to have tests assigned to them and those test results recorded in SiteManager/LIMS. The window associates a CDOT qualified individual with the types of tests they are approved to perform. Top header (subpart) shows a tester’s User ID, User Name, and their designation as a SM User, Sampler, Tester, and/or Global Tester. At this time CDOT will not designate anyone as a Global Tester. The second subpart shows Type, Level, and Authority of qualification with Effective and Expiration Dates and an “active” indicator. This subpart is utilized to maintain the tester’s association with certifications they possess related to procedures they are qualified to perform. The Type is a specific certification achieved, e.g. “ACI Field 1”, “LabCAT B” and “WAQTC Embankment & Base”. The Level is the certifying body associated with groups of materials as required by the CDOT Field Materials Manual (FMM), e.g. “ACI”, “LabCAT” and “WAQTC”. The Authority for CDOT testing qualifications is CP-10 from the FMM. A separate line for each combination of specific certifications (Type) and certifying bodies (Level) shall be maintained for all testing a User is qualified to perform. Note: all Testers are to have the certification “General” for both the Type and Level. This ensures the Tester has the qualification to any test beyond the specific certification. The third subpart shows test procedures the tester is qualified to perform. Samples requiring certain assigned tests will only be available to testers having those required procedures recorded in this window. This subpart is utilized to maintain the tester’s association with any CDOT procedures they are qualified to perform from the certifications they possess. This is accomplished by selecting/highlighting the final subpart and then selecting the “new” icon in the toolbar which brings up the “select tests” window of test templates for all procedures performed by CDOT.

Reports: No automated SiteManager reports exist for this window. A CDOT report of tester qualifications that are within 2 months of expiration may be generated.

6.9.1 Tester Qualifications Panel


Figure 6.11 Tester Qualifications Window

296 Approved Lists

Table 6.24 Tester Qualifications Window – Fields



User ID Yes Auto-populated from open file search lens selection. Uniquely identifies the tester.

-

User Name N/A Auto-populated from the User ID -

Geographic Area

No Drop-down menu. (CDOT will not use) -

SM Security User

N/A Check box, Auto-populated from the Material User window. Indicates whether the user is a SiteManager Security user.

-

Sampler N/A Check box, Auto-populated from and maintained in the Material User window. Determines whether the user may be selected as a sampler on sample records.

-

Tester N/A Check box, Auto-populated from and maintained in the Material User window. Determines whether the user may be selected as a tester on sample records.

-

Global Tester

N/A Check box, Auto-populated from and maintained in the Material User window. Indicates whether the user is a global tester. At this time CDOT will not use Global Tester.

-

Qualification pane

Type Yes Drop-down menu. Specific certification achieved.

Level Yes Drop-down menu. Certifying agency the tester has received certification from.

Authority Yes Drop-down menu. Authority of qualification (FMM CP-10).

Effective Date

Yes Free-form date field. Date the qualification begins to be valid. Defaults to the current date.

Expiration Date

Yes Free-form date field. Date the qualification is no longer valid.

Active Ind N/A Auto-populated Active Indicator. Indicates whether the qualification is active.

Test pane

Test Meth Yes Choose keys selection from “new” icon. Uniquely identifies a test method that the tester is qualified to perform.

Test Description

N/A Auto-populated from the Test Method. Full name and/or description of the selected test template.

6.9.1.1 Required Fields USER ID: Uniquely identifies a SM Materials user. This ID will be in the format required by the User Security window during set-up as a SiteManager user. USER NAME: User’s full name. SM SECURITY USER: Checkbox indicates if user is a SiteManager User. SAMPLER: Checkbox indicates if user is a qualified sampler and must be entered and maintained in the Sampler Qualifications window


TESTER: Checkbox indicates if user is a qualified tester and must be entered and maintained in the Tester Qualifications window. GLOBAL TESTER: Checkbox indicates if user is a Global Tester. At this time CDOT will not designate anyone as a Global Tester.

TYPE: Drop-down menu of specific certifications achieved. Selections are ACI Field I, ACI Agg I, ACI Agg II, ACI Lab I, ACI Lab II, ACI Strength, AMRL, General, LabCAT A, LabCAT B, LabCAT C, LabCAT E and WAQTC Emb. & Base. Type “General” covers all others tests not associated with the specific personnel qualification type as listed for that individual. Code Table = TSTPQUAL – Test Personnel Qualification Type

Code Description

ACF1 ACI Field I

ACA1 ACI Agg I

ACA2 ACI Agg II

ACL1 ACI Lab I

ACL2 ACI Lab II

ACS ACI Strength

AMRL AMRL

GEN General

WAQE WAQTC Emb. & Base

LABA LabCAT A

LABB LabCAT B

LABC LabCAT C

LABE LabCAT E

LEVEL: Drop-down menu of certifying agencies approved by CDOT for sampling and testing certification. Selections are ACI, LabCAT, WAQTC, AMRL, and General.

Code Table = QUALEV – Qualification Level

Code Description

ACI ACI

LABC LabCAT

WAQT WAQTC

AMRL AMRL

GEN General

AUTHORITY: Drop-down menu of authority of qualification as required by the CDOT Field Materials Manual. Only selection is CP-10.

298 Approved Lists

Code Table = QUALAUTH – Qualification Authority

Code Description

CP10 CP-10

EFFECTIVE DATE: Free form date field to indicate the date the qualification begins. Defaults to current date but may be set to any effective date. EXPIRATION DATE: Free form date field to indicate the date the qualification will expire and no longer be valid. After this date tester will no longer be available for selection to test materials requiring qualified testing. This date may be updated prior to expiration upon re-certification. If this date is reached, and the active indicator turns to “N”, this record is no longer editable and a new line will have to be created upon re-certification. “General” may have an Expiration Date of 1/1/2049. ACTIVE INDICATOR: Indicates whether listed qualification is active per effective and expiration dates. TEST METHOD: Field is populated from the new record selection in toolbar. Selections available are numerous and represent tests performed by CDOT. These tests are maintained in the Material Test Template window. Tests qualified by certain Type and Level combinations must be listed here for the tester to be able to perform and record procedures required on sample records. TEST DESCRIPTION: Auto-populated from the selection of Test Method. Full name and/or description of the selected test template.


CDOT will not use the following field: Geographic Area.



ADDRESS CDOT will not use at this time.


PROCESS STATUS This window is available almost system wide by selecting Process Status from the Services menu. The window consists of two tab pages: Regular and Scheduled. REGULAR TAB The Regular tab page lists Distributed Processing Services (DPS) submitted processes; that is, Report Template Facility (RTF) custom report processes, SiteManager PowerBuilder reports, and background or batch processes. Here, authorized users can see the current status of submitted processes, delete submitted or complete jobs, or drill down to view or print the output produced by completed or failed processes.


SCHEDULED TAB The Scheduled tab page lists DPS submitted processes; that is, RTF custom report processes, SiteManager PowerBuilder reports, and background or batch processes. Here, authorized users can see the current status of submitted processes, delete submitted or complete jobs, or drill down to view or print the output produced by completed or failed processes. The processes listed on the Scheduled tab are those processes which have be set to run on a specific schedule by an authorized user. Standard SiteManager window and tab-level security applies to the scheduled tab page window. Only those processes to which the user has been assigned security access will be presented on the displayed list.

MATERIAL USER The Material User window appears.

COPY RECORDS Copies a new record to assign a New Material Code to the existing bid item.

6.9.2 Tests Associated to Qualification Type

The tables show what tests are assigned to the qualification type.

Table 6.25 Tests Assigned to ACI Aggregate Level I (ACA1)










300 Approved Lists

Table 6.26 Tests Assigned to ACI Aggregate Level II (ACA2)












Table 6.27 Tests Assigned to ACI Field Grade I (ACF1)









Table 6.28 Tests Assigned to ACI Concrete Laboratory Level I (ACL1)

















Table 6.29 Tests Assigned to ACI Concrete Laboratory Level II (ACL2)

Test Method

Description






302 Approved Lists

Table 6.30 Tests Assigned to ACI Concrete Strength (ACS)










Table 6.31 Tests Assigned to LabCAT A (LABA)





Table 6.32 Tests Assigned to LabCAT B (LABB)














Table 6.33 Tests Assigned to LabCAT C (LABC)






Table 6.34 Tests Assigned to LabCAT E (LABE)

















304 Approved Lists

Table 6.35 Tests Assigned to WAQTC Embankment and Base (WAQE)













Table 6.36 Tests Assigned to General (GEN)


































306 Approved Lists









CP77 Determination of Macro-texture of a Pavement Surface


































T97-QC Flex Strength of Conc; Beam w/ Third-Pt Loading – 28 Day


































308 Approved Lists





(Last updated 06/19/2013) The AMRL tests are all tests that the Central Laboratory programs perform. The Central Laboratory is the “umbrella” for the certification by AMRL for the rest of the state labs.


Table 6.37 Tests Assigned to AMRL (AMRL)



































310 Approved Lists




































312 Approved Lists




















































(Last updated 06/19/2013) The table below shows tests that should not exist in SiteManager – Materials. These test methods are VOIDED. The tests were determined to be non-essential. They may have been deleted, labeled obsolete, duplicated, and redundant, defined as sample preparation only, definition of terms only, combined into other tests, inspection of a material with no testing, unknown test method, etc. Testers should not be assigned any of these tests.

314 Approved Lists

Table 6.38 Voided Tests


C110 Physical Testing of Quicklime, Hydrated Lime, and Limestone

C25 Chemical Analysis of Limestone, Quicklime, and Hydrated Lime

C266 Time Setting of Hydraulic-Cement Paste by Gillmore Needles

C977 Quicklime and Hydrated Lime for Soil Stabilization

CP31X Sieve Analysis of Aggregates – Extracted Aggregates

CP33 Determining the Percent of Elongated and Flat Particles in Natural Gravel Used in Truck Escape Ramps

CP36 Determination of Purity of Rock Salt

CP47 Rejuvenating Agent Evaluation Procedure

CP48 Determination of the Voids in the Mineral Aggregate (VMA)

CP60 Determining Surface Moisture in Fine and Coarse Aggregates

CP65 Evaluating Low Strength Test Results of Concrete Cylinders

CP68 Determining Portland Cement Concrete Pavement Thickness

CP69 Estimating the In-Place Concrete Strength by a Maturity Method

CP74 Operating Inertial Profilers and Evaluating Pavement Profiles

CPL2215 Effect of Heat and Air on a Moving Film of Asphalt

CPL3102 Determination of Resistance Value at Equilibrium

CPL3103 Specific Gravity of Soils

CPL4101 Preparing Concrete Blocks for Testing Sealants, for Joints and Cracks

CPL4201 Determining the Potential Alkali Reactivity of Aggregates (Accelerated Mortar Bar Method)

CPL4202 Determining Potential Alkali Reactivity of Combinations of Cementitious Materials and Aggregate (Accelerated Mortar Bar Method)

CPL5110 Resilient Modulus Test (MR)

CPL5117 Superpave Design for Hot Mix Asphalt

CPL5924 Rotational Capacity Test of Bolt Fastener Assemblies with Lengths Shorter than 2 3/4 Inch

CPL5925 Rotational Capacity Test of Bolt Fastener Assemblies with Lengths 2 3/4 Inch and Longer

CPL5926 Installation/Verification Test of Bolt Assemblies

D113 Ductility of Bituminous Materials

D139 Float Test for Bituminous Materials

D1985 Preparing Concrete Blocks for Testing Sealants, for Joints and Cracks

D2006 Characteristic Groups in Rubber Extender and Processing Oils by the Precipitation Method

D2170 Kinematic Viscosity of Asphalts (Bitumens)

D2397 Standard Specification for Cationic Emulsified Asphalt

D2435 One-Dimensional Consolidation Properties of Soils Using Incremental Loading

D3289 Density of Semi-Solid and Solid Bituminous Materials (Nickel Crucible Method)

D3406 Joint Sealant, Hot-Applied, Elastomeric-Type, for Portland Cement Concrete Pavements

D4124 Separation of Asphalt into Four Fractions



D445 Kinematic Viscosity of Transparent and Opaque Liquids (and Calculation of Dynamic Viscosity)

D4767 Consolidated Undrained Triaxial Compression Test for Cohesive Soils

D4867 Effect of Moisture on Asphalt Concrete Paving Mixtures

D4972 pH of Soils

D5 Penetration of Bituminous Materials

D5078 Crack Filler, Hot-Applied, for Asphalt Concrete and Portland Cement Concrete Pavements

D6 Loss on Heating of Oil and Asphaltic Compounds

D70 Density of Semi-Solid Bituminous Materials (Pycnometer Method)

D71 Relative Density of Solid Pitch and Asphalt (Displacement Method)

D88 Saybolt Viscosity

M148 Liquid Membrane-Forming Compounds for Curing Concrete

M203 Steel Strand, Uncoated Seven-Wire for Concrete Reinforcement

M226 Viscosity-Graded Asphalt Cement

M320 Performance-Graded Asphalt Binder

R28 Accelerated Aging of Asphalt Binder Using a Pressurized Aging Vessel (PAV)

R29 Grading or Verifying the Performance Grade of an Asphalt Binder

RED LINE

T104 Soundness of Aggregate by Use of Sodium Sulfate or Magnesium Sulfate

T107 Autoclave Expansion of Portland Cement

T129 Normal Consistency of Hydraulic Cement

T137 Air Content of Hydraulic Cement Mortar

T153 Fineness of Hydraulic Cement by Air Permeability Apparatus

T154 Time of Setting of Hydraulic Cement Paste by Gillmore Needles

T155 Water Retention by Concrete Curing Materials

T160 Length Change of Hardened Hydraulic Cement Mortar and Concrete

T161 Resistance of Concrete to Rapid Freezing and Thawing

T164 Quantitative Extraction of Asphalt Binder from Hot-Mix Asphalt (HMA)

T176 Plastic Fines in Graded Aggregates and Soils by Use of the Sand Equivalent Test

T179 Effect of Heat and Air on Asphalt Materials (Thin-Film Oven Test)

T182 Coating and Stripping of Bitumen-Aggregate Mixtures

T190 Resistance R-Value and Expansion Pressure of Compacted Soils

T198 Splitting Tensile Strength of Cylindrical Concrete Specimens

T199 Air Content of Freshly Mixed Concrete by the Chace Indicator

T201 Kinematic Viscosity of Asphalts (Bitumens)

T202 Viscosity of Asphalts by Vacuum Capillary Viscometer

T227 Density, Relative Density (Specific Gravity), or API Gravity of Crude Petroleum and Liquid Petroleum Products by Hydrometer Method

T240 Effect of Heat and Air on a Moving Film of Asphalt (Rolling Thin-Film Oven Test)

316 Approved Lists


T245 Resistance to Plastic Flow of Bituminous Mixtures Using Marshall Apparatus

T291 Determining Water-Soluble Chloride Ion Content in Soils


T303 Accelerated Detection of Potentially Deleterious Expansion of Mortar Bars Due to Alkali-Silica Reaction

T314 Determining the Fracture Properties of Asphalt Binder in Direct Tension (DT)

T42 Preformed Expansion Joint Filler for Concrete Construction

T44 Solubility of Bituminous Materials

T48 Flash and Fire Points by Cleveland Open Cup

T59 Testing Emulsified Asphalts

T68 Tension Testing of Metallic Materials

T78 Distillation of Cutback Asphaltic (Bituminous) Products

T80 Rockwell Hardness and Rockwell Superficial Hardness of Metallic Materials

T88 Particle Size Analysis of Soils

Universal Calculation of Uniformity Coefficient, Coefficient of Curvature, and Effective Particle Size at Different Percentages

(Last updated 6/19/2013) Note: Test Methods may appear in any of these database tables.

1. LIMS_DEF_TEST_ASSIGN - default test assignments 2. LIMS_SMPL_TST2 - used when a test method is assigned to a sample 3. T_CONT_STREQ - contract sampling and testing requirements 4. T_MATL_TST - test method assignment to material codes 5. T_SMPL_TST - test methods selected for a sample 6. T_STREQUIREMENT - global sampling and testing requirements

Training Comments: When a Type of certification is selected in the 2nd data window, it will populate the tests that are associated to that type of certification in the 3rd data window automatically.

6.10 LIMS Maintain Lab Users Window

LIMS Navigation LIMS NAVIGATION PANEL > LIMS > MAINTAIN LAB USERS - OR – LIMS NAVIGATION PANEL > SYSTEM ADMIN > MAINTAIN LAB USERS

In LIMS, use the Maintain Lab Users window to assign lab unit privileges to existing SiteManager users. Before a user can access a lab unit’s work queue, assign the user to the lab unit using this window.

Security Procedure:


CDOT update authority for this window will be limited to the Technical Support, IT System Administration, and the Central Lab Pavement Design Program.

Functional Procedure: In LIMS, CDOT will utilize this window to maintain the staff assigned to particular lab units in order for them to enter test data into LIMS. The Maintain Lab Users window displays the labs defined as lab units in the Maintain Destination Labs window. The list of users in the Available Users pane comes from the SiteManager security users. Top header (subpart) shows all lab units maintained in the system. The lower two subparts show all SiteManager security users (left) and all users assigned to the selected lab (right). To add users to a lab unit, first select the correct lab to be maintained in the upper subpart, then select users from the available users list and click the Add Users button. To remove any users associated to a lab unit, select them from the Lab Users list and click the Remove Users button.

Reports: No automated SiteManager reports exist for this window. No CDOT reports are available for this window.

6.10.1 Maintain Lab Users Panel

Figure 6.12 Maintain Lab Users Window

318 Approved Lists

Table 6.39 Maintain Lab Users Window - Fields


Select Lab Unit area

Lab ID Yes

Auto-populated from data in Qualified Labs window. Uniquely identifies a lab. Select line to maintain users.

-

Lab Name N/A Auto-populated from the Lab ID -

Geographic Area No

Auto-populated from the Lab ID. (CDOT does not use)

-

Lab Contact Person

N/A Auto-populated from the Lab ID. Name of the contact person assigned to the lab.

-

Available Users pane

User ID Yes

Auto-populated from data in Material User window. List contains all users not already assigned to the lab.

-

User Name N/A

Auto-populated from the User ID. Full name of a user available to be assigned to the lab.

-

Central Office N/A Central office indicator. (CDOT does not use) -

Level 2 Office N/A Level 2 office indicator. (CDOT does not use) -

Level 3 Office N/A Level 3 office indicator. (CDOT does not use) -

Level 4 Office N/A Level 4 office indicator. (CDOT does not use)

Lab Users pane

User ID Yes

Auto-populated data from Material User window for users already assigned to the lab.

-

User Name N/A

Auto-populated from the User ID. Full name of a user assigned to the lab.

-

6.10.1.1 Required fields LAB ID: Uniquely identifies a CDOT Lab in SiteManager. This ID will be auto populated when a lab is created in the Qualified Labs window. Select a lab line to view and edit users. LAB NAME: Lab’s full name auto populated from Lab ID. LAB CONTACT PERSON: Contact name auto-populated from Lab ID. USER ID (AVAILABLE USERS PANE): Uniquely identifies the SiteManager Material User. This ID will be auto populated to this selection list when the SiteManager account is created. This pane displays all users not assigned to the selected lab unit. USER NAME (AVAILABLE USERS PANE): User’s full name auto populated from USER ID. USER ID (LAB USERS PANE): Uniquely identifies the SiteManager Material User. This pane displays all users assigned to the selected lab unit. USER NAME (LAB USERS PANE): User’s full name auto populated from USER ID.



CDOT will not use the following fields: Geographic Area, Central Office, Level 2 Office, Level 3 Office, & Level 4 Office.

6.11 Test and Fee Schedule Window

SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > APPROVED LISTS > TEST AND FEE SCHEDULE

Use the Test and Fee Schedule window to maintain testing fee information.

Security Procedure: CDOT update authority for this window will be limited to the Technical Support, IT System Administration, and the Central Lab Pavement Design Program. CDOT inquiry authority for this window should be available to all SiteManager Material users.

Functional Procedure: The Test and Fee Schedule will only be applied to the laboratories in the Central Laboratory at this time.

6.11.1 Test and Fee Schedule Panel

Figure 6.13 Test and Fee Schedule Window

320 Approved Lists

Table 6.40 Test and Fee Schedule Window - Fields


Test Method ID for a test. Agency-defined.

Test Description Description of the test.

Charge Amount Amount (positive number) charged to perform the test.

Billing Code Pertains to the test. Agency-defined.



6.12 Test and Fee Schedule Report Window

SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > APPROVED LISTS REPORTS > TEST AND FEE SCHEDULE REPORT

Use the Test and Fee Schedule Report window to display testing fee information. This report is hard coded into SiteManager-Materials. It cannot be modified except for inserting globally name of state.

6.12.1 Test and Fee Schedule Report Panels

Figure 6.14 Report Criteria Window


Figure 6.15 Test and Fee Schedule Report Window

Table 6.41 Test and Fee Schedule Report Window - Fields


Test Method Uniquely identifies a test template or the standard AASHTO tests included in SiteManager.

Test Description Descriptive name given to the test template or the standard AASHTO tests included in SiteManager.

Charge Amount Displays the amount (positive number) charged to perform the test.

Billing Code Pertains to the test. Agency-defined.

AASHTO Indc Displays whether or not the test template is an AASHTO test.

Template Type Indc Indicates the type of template (that is, (B)asic, (T)est Specification, or (M)ix Design).


PROCESS STATUS This window is available almost system wide by selecting Process Status from the Services menu. The window consists of two tab pages: Regular and Scheduled. REGULAR TAB The Regular tab page lists Distributed Processing Services (DPS) submitted processes; that is, Report Template Facility (RTF) custom report processes, SiteManager PowerBuilder reports, and background or batch processes. Here, authorized users can see the current status of submitted processes, delete submitted or complete jobs, or drill down to view or print the output produced by completed or failed processes. SCHEDULED TAB The Scheduled tab page lists DPS submitted processes; that is, RTF custom report processes, SiteManager PowerBuilder reports, and background or batch processes. Here, authorized users can see the current status of submitted processes, delete submitted or complete jobs, or drill down to view or print the output produced by completed or failed processes. The processes listed on the Scheduled tab are those processes which have be set to run on a specific schedule by an authorized user.

322 Approved Lists

Standard SiteManager window and tab-level security applies to the scheduled tab page window. Only those processes to which the user has been assigned security access will be presented on the displayed list.

EXPORT Used to export to a text file.

6.13 Calibrated Equipment Window

SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > APPROVED LISTS > CALIBRATED EQUIPMENT

Use the Calibrated Equipment window to add and modify calibration information for laboratory equipment. *CDOT IS NOT PRESENTLY USING THIS WINDOW FOR MATERIALS FUNCTIONALITY

(12/29/2010 PRM) Security Procedure: CDOT update authority for this window will be limited to the Technical Support and IT System Administration. CDOT inquiry authority for this window should be available to all SiteManager Material users.

Functional Procedure: CDOT will not utilize this window at this time.

6.13.1 Calibrated Equipment Panel

Figure 6.16 Calibrated Equipment Window


Table 6.42 Calibrated Equipment Window - Fields


Serial Number Serial Number ID for the calibrated equipment.

Status Indicates the status of the calibrated equipment (for example, in use,

available, surplus, and so on).

Manufacturer Name Manufacturer of the equipment.

Lab Id Uniquely identifies the testing laboratory of the equipment. Agency-defined.

Description Explanation of the calibrated equipment.

Calibration Authority Pertains to the official body responsible for calibrating the equipment.

Calibration Type Identifies the kind of calibration.

Geographic Area Physical location of the lab. Agency-defined.

Calibration Method Method of calibration.

Document Reference Identifies the document containing detail information.

Calibration Date Date the equipment was calibrated.

Expiration Date Final day of the valid equipment calibration.

Model Number Model of the equipment.




324 Approved Lists

6.14 Welder Window

SiteManager Navigation MAIN PANEL > MATERIALS MANAGEMENT > APPROVED LISTS > WELDERS

Use the Welder window to add and modify welder personnel and their qualifications. *CDOT IS NOT PRESENTLY USING THIS WINDOW FOR MATERIALS FUNCTIONALITY

(12/29/2010 PRM) Edits to this document will occur when the window’s use is implemented.

Security Procedure: CDOT update authority for this window will be limited to the Technical Support and IT System Administration.

Functional Procedure: CDOT will not utilize this window at this time.

6.14.1 Welder Panel

Figure 6.17 Welder Window


Table 6.43 Welder Window - Fields


Welder ID Uniquely identifies the welder. Agency-defined.

Welder Name Name of the Welder.

Type Type of welder (for example, Field, Shop, and so on).

Geographic Area Geographical unit where the welder is located. Agency-defined.

Weld Process Process that the welder is qualified to perform.

Weld Position Position the welder is qualified to perform on the given process.

Weld Type Type of welding the welder is qualified to perform.

Sample ID Sample on which the welder qualified.


ADDRESS Address of Welder.



SECTION 7 CDOT’s Application for Reporting (CAR)

328 Application for Reporting (CAR)

7.1 Introduction All SiteManager Materials reports are located on a CDOT website. None of the reports can be accessed through SiteManager. The reports pull data from SiteManager. These reports are not forms. The user cannot input data directly onto the reports. Data must be in SiteManager for the reports to be populated. BusinessObjects Enterprise is the website where the reports reside. BusinessObjects Enterprise comes with InfoView, a web desktop that acts as a window to a range of useful business information about CDOT. From InfoView, you can access Crystal reports, Voyager workspaces, Web Intelligence documents, Desktop Intelligence documents, and other objects, and organize them to suit your preferences. All the SiteManager Materials reports were developed with the software called Crystal Reports. The Governor's Office of Information Technology, CDOT Construction Applications Unit (OIT) must develop these reports and place them in InfoView. See the Section titled “Creation of Reports” on how to submit reports for the development by OIT. It is beneficial to read the Help guide located in the CAR website.

7.2 Accessing Reports ERP (SAP) Authorization Request Form (CDOT Form # 1387) is required to be approved before using CAR Trns*port reports. Open CDOT’s main page in Windows Internet Explorer. Click on the SAP Portal.

Figure 7.1 Front Page – CDOT Internet


Log in by using your Windows username and password.

Figure 7.2 Log On SAP NetWeaver Portal

Click on the Reports tab on CDOT portal welcome screen.

Figure 7.3 CDOT Portal Welcome Screen


Click on CAR in CDOT reporting portal screen.

Figure 7.4 CDOT Reporting Portal Screen

Navigate to the Trns*port folder. The Trns*port folder is where all the SiteManager Materials reports reside.

Figure 7.5 Listings of SiteManager Materials Reports


7.3 Printing a Report From CAR

Figure 7.6 Print a Report Using the Export Button

The following are instruction for how to print a CAR report.

1. In CAR, open the report. 2. On the toolbar, click the Export button. 3. In the File Format field, confirm PDF is selected. 4. Confirm the Page Range is All Pages. If needed, you can select specific pages. 5. Click the Export button. 6. Click the Save button. 7. Select the location where you will save the file. 8. In the File name field, type a name. For future reference, include the date the report was

generated in the file name. 9. Click the Save button. 10. Close the report. 11. Navigate to the location of the saved report and double-click the report. 12. Open the File menu and click Print. 13. Select your printing options and click the Print button.

7.4 Types of Reports The development of reports is an on-going affair. The reports are categorized according to their use. The Approved Products List (APL) and the Qualified Manufacturers List (QML) are used to populate the approved products website. This website is managed by the Central Laboratory Pavement Design Unit, Product Evaluation Coordinator.


The CODE reports are used to list the interdependences of Line Numbers, Bid Item Codes, Material Codes and required tests and documentation. Generally, these reports are used in the creation and checking of the 250 report and CERT report before use in construction. This is done by Central Laboratory Pavement Design Unit, Documentation Manager. The Checklist reports are for the construction sampler and tester to meet the frequency of required samples and tests. Contractor’s certification documentation is also included. All the samplers and testers may use the reports. The HMA and PCC reports are project specific. The Project Specific Asphalt Job Mix Formula Report has the same data as the traditional Form 43. The Concrete Mix Design Report has the same data as the traditional Form 1373.

7.5 Additional Resources

Figure 7.7 Online Training for CAR

There are additional resources for you to learn more about using CAR. From the CDOT intranet, click the link SAP Portal.

1. Enter your Windows Username and Password. 2. Click the Reports tab. 3. Click the link Online Training for CAR. 4. Click either On-Line Class, or click Work Instructions.

From the On-Line Class page, available options are:

Section 1 – Reporting Overview Section 2 – Basic Reporting Section 3 – Interacting with the Report Section 4 – Personalizing the CAR System


From the Work Instructions page, available options are: Create Favorites in CAR Log On and Log Off of CAR Print/Export a CAR Report Run a CAR Report on Demand Run CAR Report Instance Using Basic Navigation Set Up Preferences In CAR


SECTION 8 System Operational Parameters

336 System Operational Parameters

8.1 System Operational Parameters Starting with version 3.9a-2, SiteManager provides enhanced functionality to allow transportation agencies more usability and flexibly in defining their contract sampling & testing requirements for materials. Important Terms to Know Sample – Provides a record of the specific sample details of a material. A sample has a one to one relationship to a material, meaning only one material can be recorded on a sample. Test – Provides a record of the individual tests performed on material for a sample. A test has a one-to many relationship with a sample/material, meaning a single sample can have multiple tests associated with it. As such, a single sample may meet multiple sampling and test requirements for a material. The document titled SiteManager Materials System Operational Parameters, 20 pages long describes in detail the following table. The table is a summary of decisions that CDOT made. The Parameter Number references the section in the document that explains in detail what the parameter does. Last updated to this manual was on 2/24/2012.


Table 8.1 System Operational Parameter

Ref Parameter Decision Set In

SiteManager Comments

3.1 Allow Material unit edit N 1/26/2010

3.2 Display Approved Source Required N 1/26/2010

3.3 Acceptance Method required for Sampling and Testing Y 1/26/2010

3.4 Sample Type required for Sampling & Testing Y 1/26/2010

3.5 Test Method required for Sampling & Testing Y 1/26/2010

3.6 Producer/Supplier required for Sampling and Testing N 1/26/2010

3.7 Material Discrepancy Accept Sample By B 1/26/2010

3.8 Material Discrepancy Accept Sample Status 1 COMP (Complete) 1/26/2010

3.8 Material Discrepancy Accept Sample Status 2 Accept and Reduce Price

Can't set until this value is added to the SMPLSTAT code table

3.8 Material Discrepancy Accept Sample Status 3 ? Will CDOT use a third status?

3.9 Sampling & Testing Req Criteria Priority 1 ST 1/26/2010

3.9 Sampling & Testing Req Criteria Priority 2 AM 1/26/2010

3.9 Sampling & Testing Req Criteria Priority 3 TM 1/26/2010

3.9 Sampling & Testing Req Criteria Priority 4 PS 1/26/2010

3.10 Material Discrepancy Payment Calculation N 1/26/2010

3.11 Material Discrepancy Payment Calculation Item Default N 1/26/2010

3.12 Use Satisf. Represented Matrl Qty in Discrepancies Process Y 1/26/2010

Also need customization from NYSDOT to make this work

3.13 Require Cont Item Smpl Represented Qty N 1/26/2010

3.14 Auto-authorize VOID samples Y 1/26/2010

3.15 Auto Generate Sample ID Y 1/26/2010

3.16 Default Sample Status PEND (Pending) 1/26/2010

3.17 Define Office Lock Level 3 1/26/2010

3.18 Enable LIMS Application Y 1/26/2010

3.19 Enable Unauthorized Sample Y 1/26/2010

3.20 LIMS Acceptance Method for AutoFinalize <blank> 1/26/2010

3.21 LIMS Acceptance Method for Void Sample VOID Can't set until this value is added to the ACPTMETH code table

3.22 LIMS Default Test Status 05 1/26/2010

3.23 LIMS Field for Equipment Serial Nbr DropDown F2 3/24/2010

Refer to Materials Test Template subcommittee Updated by Katie based on the Material Test Template Committee meeting minutes from 2/22/10.

338 System Operational Parameters

Ref Parameter Decision Set In

SiteManager Comments

3.24 Default Sample Material Unit English 1/27/2010

3.25 LIMS Remark Code Type to be Used for Retest Retest

Can't set until code table is populated

3.26 LIMS Sample Status for AutoFinalize <blank> 1/27/2010

3.27 LIMS Sample Status For In Testing TEST 1/27/2010

3.28 LIMS Sample Status For Logged LOGD 1/27/2010

3.29 LIMS Sample Status For Pre Auth PREA 1/27/2010

3.30 LIMS Sample Status for Received RECV 1/27/2010

3.31 LIMS Template Monitor Field For Test Results F1 3/24/2010

Refer to Materials Test Template subcommittee (CDOT won't use this, at least initially) Updated by Katie based on the Material Test Template Committee meeting minutes from 2/22/10. This field will be used to identify if the test is within specs, but will not initially be tied to the Auto Finalize process.

3.32 LIMS Test Status For Back To Lab <use system default> 1/27/2010

3.33 LIMS Test Status For Cancel <use system default> 1/27/2010

3.34 LIMS Test Status For Completed <use system default> 1/27/2010

3.35 LIMS Test Status for Lab Supervsr Approval <use system default> 1/27/2010

3.36 LIMS Test Status for Line Supervsr Approval <use system default> 1/27/2010

3.37 LIMS Test Status for ReQueue <use system default> 1/27/2010

3.38 LIMS Test Status for Retest in Queue <use system default> 1/27/2010

3.39 LIMS Test Status for Waiting Retest <use system default> 1/27/2010

3.40 Allow Custom PCC Record Template Y 1/27/2010

3.41 Allow Custom SUPERPAVE Record Template Y 1/27/2010

3.42 Allow Sample Limited Access Lock ? Refer to LIMS subcommittee

3.43 Allow Sample User Lock N 1/27/2010

3.44 Default Sample Security No Lock 1/27/2010

3.45 Limited Access Sample Group ? TBD by LIMS subcommittee

3.46 Limited Access Standalone Group <blank> 1/27/2010 CDOT won't use standalone mode


SECTION 9 Security Groups

340 Security Groups

9.1 Security Groups Your system administrator grants access to SiteManager LIMS windows and panels by assigning security groups to users. Your SiteManager user ID, when assigned to a security group, determines the windows to which you have access. Most users will belong to only one security group, but on occasion, a user may need to have access to more than one group. If your user ID is assigned to only one group, LIMS displays the Navigation Panel with the functions available to that security group. If you log on with a user ID assigned to multiple security groups, SiteManager LIMS will prompt you to select a security group from the Select Group window before displaying the Navigation Panel.

9.1.1 Group Definitions

Technical Support This group consists of subject matter experts in Site Manager from the Contracts and Market Analysis Branch. Help Desk Typical staffing in this group comes from the Headquarters office for the help desk. This group can setup passwords and reset passwords. Information Technology (IT) System Administration This group consists of personnel from Information Technology Office. This group can update all system administration tables. Pavement Design Program The personnel that make up this group are all the people that work in the Pavement Design Program of the Materials and Geotechnical Branch. Regional Materials Office People in this group are the Region Materials Engineers, Assistant Materials Engineer, Independent Assurance Testers and Regional Lab Managers. The RMEs are usually Professional Engineers Level II and their assistants are either an Engineer-In-Training II or III or a Professional Engineer I. The regional lab managers are typically Engineer Physical Science Technicians level III. Each region has at least one person in each of the six regional materials laboratories that does the independent check of materials on CDOT construction projects as their primary job duties. They are usually classified as an Engineer Physical Science Technician Level III. Along with these individuals, a backup independent tester is usually classified as an Engineer Physical Science Technician Level II or higher. CDOT Managers Typical staffing in this group comes from the regional Program Engineers and Resident Engineer along with the Area Engineers from Staff Services. Program Engineers are classified as a Professional Engineer III and Resident Engineers are classified as a Professional Engineers II. If requested, the Regional Transportation Directors and Business Office personnel would be permitted. They are usually classified as a Professional Engineer III or higher. Personnel from the Business Offices are usually classified as Account Technicians level III or higher. General Professionals III or higher could be part of this group of business personnel. CDOT Samplers and Testers


This group only consists of full time and part time CDOT employees that will be performing materials tests on CDOT projects. They are usually classified as Engineer Physical Science Assistant or Technicians level I, II or III. These are regional people however; Central Laboratory has a few such as Geotechnical Engineers and Drill Crew members. Consultant Testers Members of this group consist of consultant employees that will be materials testers working on CDOT projects. CDOT and Consultant Project Engineers The people that make up this group are the managers of CDOT construction projects. They are usually classified as an Engineer-In-Training II or III, Professional Engineer I or a Civil Engineering Project Manager level I or II. Binder, Flexible Pavement and Chemical Group This group consists of personnel from the Materials and Geotechnical Branch in the Flexible Pavement Program. They are the subject matter experts in hot mix asphalt, asphalt cement binder and chemical tests. Concrete and Physical Properties Group The people in this group consist of staff from the Materials and Geotechnical Branch in the Concrete and Physical Properties Program. They are the subject matter experts in concrete, chemical and the physical properties of construction materials. Soils Group Members of this group are from the Materials and Geotechnical Branch in the Soils Program. They are the subject matter experts in soils. Finals Engineers People in this group are the six Region Finals Engineers. They are usually classified as an Engineer Physical Science Technician Level III, but this varies throughout the state. They are responsible for reviewing all the documentation from CDOT construction projects and closing the files. Pavement Management The people in this group consist of staff from the Materials and Geotechnical Branch in the Pavement Management Program along with the six Region Pavement Managers in the regional laboratories.

342 Security Groups

9.1.2 Security Group Matrix

The security group matrix associates the groups with the windows and tabs that can be updated, inquired, or not to be seen. This matrix was last updated on 5/4/2012.

In SiteManager, windows can be assigned as Update (U), Inquire (I), or Not Seen (N). In LIMS, windows can be assigned as Update (U), or Not Seen (N). If a group should not have access to make changes to the window, the

group will be unable to see the window in LIMS.

Table 9.1 Security Group Matrix

344 Security Groups


9.2 Group Security Window

SiteManager Navigation MAIN PANEL > SYSTEM ADMINISTRATION > GROUP SECURITY

Use the Group Security window to do the following:

Define a group with an ID number.

Describe the group.

Specify the Group Type as Regular, Batch or Standalone. Define the rights of the group at four system levels:

Use the SiteManager Nav Group area to specify access rights to the Main Panel icons. Options include: Yes or No.

Use the Window Name area to specify access rights to a window. Options include: Update, Inquiry or No rights.

Use the Tab Label/Services Menu Nav area to specify access rights to a tab or Services menu choices. Options include: Update, Inquiry or No rights.

Use the Column Label area to specify access rights to the column (field) level. Options include: Update, Inquiry or No rights.

9.2.1 Group Security Panel

346 Security Groups

Figure 9.1 Group Security Window


Table 9.2 Group Security Window - Fields


Group ID Uniquely identifies the group. 8-character maximum. Agency-defined

Description Name of the group. 40-character maximum.

Group Type Regular, Standalone, and Batch are the three types of security groups that may be created.

Copy from Group Name of the group with rights to be copied to the new group.

SiteManager Nav Group A scrollable list of all the icons in the SiteManager Main Panel.

Access Select either Yes or No to specify group’s access to icons.

Window Name Name of the windows associated to the icon selected in the navigation group.

Access Describes the group’s access to windows as update, inquiry or no rights.

Tab Label Name of the tab(s) associated to the window selected in Window Name.

Access Describes the group’s access to tab (s) associated to the window in window name as update, inquiry or no rights.

Column Label Name of the column(s) associated to the window selected in Window Name.

Access Describes the group’s access to column (s) associated to the window in Window Name as update, inquiry or no rights.

9.2.1.1 Procedure Handled by System IT Technical Support.

9.3 Maintain Group Security Window

SiteManager Navigation NAVIGATION PANEL > SYSTEM ADMIN > GROUP SECURITY

Use the Maintain Group Security window to define the rights for SiteManager security groups to access LIMS navigation panels and windows. The Select Group area displays all SiteManager security groups. The Available Window Privileges area displays a list of all panels and windows as pre-defined in the LIMS database. Granting access to a window automatically grants access to the navigation panel on which the icon for the window resides. To add panel or windows rights to a security group, select the Panel/Window combination from the Available Window Privileges list and click the ADD ACCESS button. To remove panel or windows rights from a security group, select the Panel/Window combination from the Assigned Window Privileges list and click on the REMOVE ACCESS button. Important! Access rights, if granted, are always Update rights. The Sample Information View has two levels of security. First, grant access at the window (icon) level by adding the View Only panel. Then selectively grant access to the tabs available on the window by selected one or more of the Sample Information View* panels.

348 Security Groups

Note: If users log into LIMS using the SMADMIN group, they will have update access to all the tabs and window in LIMS. In other words, the group security settings for the SMADMIN group will be overridden by the LIMS application to allow full access to all LIMS windows.

9.3.1 Maintain Group Security Panel

Figure 9.2 Maintain Group Security Window


Table 9.3 Maintain Group Security - Fields


Group ID Uniquely identifies a group as defined in SiteManager. Agency-defined. Alpha-numeric.

Group Description Describes the group as defined in SiteManager.

Available Window Privileges pane

Panel Name Name of all panels and windows located on the Navigation Panel window or the View-Only Sample Information window that have not been assigned to the selected group.

Window Title Identifies the name of the window associated with the panel excluding the Sample Information Views* panel. In this case, the window title represents one of the panels available on the View-Only Sample Information window.

Assigned Window Privileges pane

Panel Name Name of all panels and windows that have been assigned to this group.

Window Title Identifies the name of the windows associated with the assigned panel excluding the Sample Information Views* panel. In this case, the window title represents one of the panels available on the View-Only Sample Information window.


9.4 User Security Window

SiteManager Navigation MAIN PANEL > SYSTEM ADMINISTRATION > USER SECURITY

Use the User Security window to create, update, or delete user information. Functions of this window include:

Create a new user and user ID.

Update user detail information.

Assign new and existing users to groups (or assign their rights).

Remove new and existing users from groups (or revoke their rights).

Reset passwords.

Delete users from SiteManager.

Authorize vendor personnel to access SiteManager.

9.4.1 User Security Panel

350 Security Groups

Figure 9.3 User Security Window


Table 9.4 User Security Window - Fields


User ID Uniquely identifies a person within an agency. Agency-defined. Searchable. Required. User IDs should not be created to differ only by letter case (for example, MLEE, mlee, or mLEE).

Name User name.

SSN Social Security Number. SIN in Canada.

Title Job Title of the person to be used in SiteManager.

Active User’s status. (‘X’ =Active; Blank = Inactive). Required.

Supervisor User’s Supervisor’s user ID, name or initials.

Home Phone User’s home telephone number.

Work Phone User’s phone number. Specify the office/workplace phone number.

Ext User’s office/workplace telephone extension number.

Fax User’s office/workplace fax number.

Vendor Prsnl Ind Vendor Personnel Indicator. Select to indicate that this user is a non-agency employee.

Vendor ID ID for the vendor. Agency-defined.

Vendor Prsnl ID Vendor’s employee identification number

Global Contract Access Defines the user’s contract information access Select to provide access to all contracts. Access is related to the User’s place of work such as General, Division, District or Area as defined by the agency.

Area Engineer User is either an area engineer or a non-engineer.

Default RTF Library Report library that should be the default for the user.

General Office code of the user such as level 1 or Central HQ. Agency-defined.

Division Division office code of the user such as Level 2. Agency-defined.

District District office code of the user such as Level 3. Agency-defined.

Area (or Residency) Area office code of the user. Agency-defined.

DataBase Login ID ID used to log the user in to the database.

DataBase Password Password used to log the user in to the database.

9.4.1.1 Procedure TBD

9.5 System Tables Maintenance Window SiteManager Navigation

MAIN PANEL > SYSTEM ADMINISTRATION > SYSTEM TABLES MAINTENANCE

Use the System Tables Maintenance window to maintain both the code tables and error messages in SiteManager.

352 Security Groups

9.5.1 Code Table Panel

Use the Code Table panel to add, modify, delete and query the code tables and corresponding entries. Table identification and table name are user-specified columns. Available to System Administrators only. Note: The system operational parameter Code Table Modify Ind defaults to No. If changed to Yes, you may add, modify and delete all code tables. Select from three types of code tables: System, User and Change.

System - Contain system processing codes. No modifications allowed.

User - Contain user-defined codes. Can add, modify and delete the codes and descriptions. Default.

Change - Can change descriptions, but not code changes - or - can add or delete new codes, but cannot modify the existing codes or descriptions. All code tables that are loaded by the PES/LAS reference load files are of Change type, but are set to disallow users from deleting the codes. Warning! Although you may modify the descriptions in Change code tables, it is not advisable. The next reference file load will overwrite any updates you made. If you still desire changes to the descriptions, make them in PES/LAS. The next reference load will include the changed descriptions.

Adding New Tables When adding new tables, User is the default table type.

Deleting Codes and Tables SiteManager does not prompt the user to confirm deletion. If you delete all codes in the table, the system automatically deletes the table. To undo an accidental delete and restore the previous state, click the Cancel button.

Table Type Functions System

Add New Code: No.

Modify Code: No.

Delete a Table: No. Change - Pre-Installation (pre-existing code)

Add New Code: n/a.

Modify Code: Limited to Code Description.

Delete a Table: No. Change - After Installation (newly added)

Add New Code: Yes.

Modify Code: Yes - Can modify only newly added code. Cannot modify any pre-installation code.

Delete a Table: Can delete only newly added code. Cannot delete any pre-existing installation code.

User


Add New Code: Yes.

Modify Code: Yes.

Delete a Table: Yes.

Figure 9.4 System Tables Maintenance Window - Code Table Panel

Table 9.5 System Tables Maintenance Window - Code Table Panel – Fields


Table ID Uniquely identifies the code table.

Table Name Describes the code table.

Table Type System, user or change. System type cannot be changed. User type can be fully defined. Change type can be added to.

Code ID Uniquely identifies the code for the selected Table ID. Alphanumeric.

Description Describes the code.

9.5.2 Error Message Panel

Use the Error Message panel to do the following:

View the messages used by the system.

Modify and add new messages to the database.

Delete messages.

Specify which messages SiteManager logs and suppresses.

354 Security Groups

Figure 9.5 System Tables Maintenance Window - Error Message Panel


Table 9.6 System Tables Maintenance Window - Error Message Panel - Fields


Upper pane

Message Number See ‘Number’ in lower pane.

Type See ‘Type’ in lower pane.

Log Ind See ‘Message Log Ind.’ in lower pane.

Detail Message See ‘Text’ in lower pane.

Lower pane

Number Message number. Those less than 1000 will be treated as PowerBuilder related messages. Those above 9000 are treated as Fatal SQL Errors.

Type Types of messages include:

Informational

Warning

Error

Fatal Error

Informational

Not errors; only provide information.

Use the Suppress Ind to indicate whether or not the message can be suppressed by the user. The system will not display the message if the Suppressible Indicator is On and the application-level suppress indicator is On. The application-level suppress indicator is stored in the .INI file.

Range of numbers: 1000 through 2999.

Warning

Error occurred to warn the user.

Use to allow the user to continue with an understanding of the outcome. Suppress Ind is disabled.


Error

Error occurred as a result of another window not being processed.

Use to restrict the user from continuing to use the functional component. Message should be logged. Suppress Ind is disabled.


Fatal Error

Error occurred due to software flaws or a database connection being lost.

All fatal messages are logged by the system. Message will be logged and the Suppress Ind is disabled.


Message Log Ind Message Log Indicator. Indicates whether the message needs to be logged.

Type of Buttons Determines what choices are made available when the message is displayed. Button combinations include:

OK

356 Security Groups


OK, Cancel

Yes, No

Yes, No, Cancel

Retry, Cancel

Abort, Retry, Cancel

Suppress Ind Suppressible Indicator. Use to indicate whether or not the message can be suppressed by the user. System will not display the message if selected and the application-level suppressible indicator is selected.

Title Title displayed on the message window for each message. (Default value: &frametitle displays main window’s title as the title of the message window. If user enters another title, that title will appear when that message is displayed.

Default Button Should not be modified. Number corresponds to the button position in the list of buttons for the selected Type of Button.

Text Actual displayed message. It may contain the % sign, followed by a number, where the sign % indicates that a value can be substituted in its place at run time. The number following the % sign indicates the parameter position within the message. For example, if the message text is Contract %1 cannot be deleted, %1 will be substituted by the contract number at run time.

Error Trap Function For System Administrators Note: For information about the Error Trap function in the DBA Utility, refer to the System Manager’s Guide, DBA utility, Error Trap function topic, or the Help topic. Use the Error Trap function to define which application-level error (Warning and Informational) messages the system will display to users. Also, use the Error Trap function to revise messages globally (for example from English to French). Limitations:

Error and Fatal Error Messages with ID numbers 1000 or below cannot be changed or suppressed and are always logged.

Informational and Warning messages with ID numbers 1001 or above can be changed or suppressed.



9.6 Contract Archival Window

SiteManager Navigation MAIN PANEL > SYSTEM ADMINISTRATION > CONTRACT ARCHIVAL WINDOW

CDOT will not use at this time. Use the Contract Archival Window to archive one or more contracts to a flat file for off-line storage. Displays only contracts with Complete status. SiteManager cannot archive contracts with any other status or with pending critical data, such as daily work reports or change orders. List is not limited by the user’s contract authority and will contain all completed contracts. Filter the list based on user-selected criteria (for example, Contract final date.)

9.6.1 Contract Archival Panel

Figure 9.6 Contract Archival Window

358 Security Groups

Table 9.7 Contract Archival Window - Fields



Contract Description Description of the contract.

Contract Status Indicates the current status of a contract (for example, Pending, Active, Complete, Archived).

Original Contract Amount

Original bid amount of the contract.

Final Contract Amount Current amount of the contract (original bid amount plus approved change orders).

Date Let Date on which the contract was let.

Date Work Began Date on which the contract work began.

Date Final Date on which the contract was finalized.

9.6.1.1 Procedure CDOT does not archive contracts in SiteManager, so this window will not be used. Completed contract data is left in the database to facilitate historical queries.

9.7 Contract Restore Window

SiteManager Navigation MAIN PANEL > SYSTEM ADMINISTRATION > CONTRACT RESTORE WINDOW

CDOT will not use at this time. Use the Contract Restore window to restore a previously archived contract. The window displays a list of the archived contracts in the appropriate directory on the network by descending archival date. From the list of archived contracts, select a contract to be restored. You may restore only one contract at a time. SiteManager delivers an inbox message to inform you that the restore process was completed successfully. After restoration, the contract data also remains in the archive file and the contract number remains in this list. Note: Archived records follow the current table layout at the time of archiving for each of the individual tables. If database tables changed between archiving and restoring, the archived data cannot be restored automatically. The archived contract data must conform to any new format before it can be restored. If a column name was changed or a column was deleted, massage the data or the archive and restore function may require a change. To print the list of archived contracts, from the Services menu, click the Print Archival List choice to print in a standard report format.

9.7.1 Contract Restore Panel


Figure 9.7 Contract Restore Window

Table 9.8 Contract Restore Window - Fields



Contract Description Description of the Contract.

Contract Status Indicates the current status of a contract (for example, Pending, Active, Complete, Archived).

Original Contract Amount

Original bid amount of the contract.

Final Contract Amount Current amount of the contract (original bid amount plus approved change orders).

Date Let Date on which the contract was let.

Date Work Began Date on which the contract work began.

Date Final Date on which the contract was finalized.

Archival Date Date of archival of the contract.

User ID User ID of the user who requested the contract be archived.

Arch File Name Archive File Name. Name of the file that the archived data is stored.

Delay Restoration Select to postpone restoration until a time specified for the scheduled job.

9.7.1.1 Procedure

360 Security Groups

CDOT does not archive contracts in SiteManager, so this window will not be used. Completed contract data is left in the database to facilitate historical queries.

9.8 Process Security Window

SiteManager Navigation MAIN PANEL > SYSTEM ADMINISTRATION > PROCESS SECURITY

Use the Process Security window to assign access to security groups that will need to run processes. Grant access rights to enable the process to display on a Process List window for a functional area available to a security group. The only processes available are those specifically assigned to the SiteManager functional area. Any user with access rights can run the process. At least one security group must be assigned access rights to each process. Security access for processes are implemented at two levels.

Basic SiteManager window access rights to control access to the Define Custom Process maintenance, Process List, and Process Security windows.

Individual access rights that limit which specific SiteManager functional areas users can access.

9.8.1 Process Security Panel

Figure 9.8 Process Security Window


Table 9.9 Process Security - Fields


Process ID Uniquely identifies the process.

Job Type Defines the type of process. Either custom or standard.

Process Description Describes the process.

Group List pane

Group ID Uniquely identifies a security group.

Description Describes a security group.

Associated Groups pane

Group ID Uniquely identifies a security group.

Description Describes a security group.


9.9 Define Custom Process Window

SiteManager Navigation MAIN PANEL > SYSTEM ADMINISTRATION > DEFINE PROCESS

CDOT will not use at this time. Use the Define Custom Process window to create, modify and delete agency-defined executables or custom RTF processes. Also, upload and download report templates as necessary. Design a custom process to display a list of records at process execution for users to select either single or multiple records from a specific database table to be used in the execution of the process. This functionality is known as Subsets. Selects from a list of data Subsets (such as Contract or Contract Estimate) and designate whether or not multiple records may be chosen on the list by selecting the Multiple Select check box.

9.9.1 General Panel Use the General panel to view and edit information about a SiteManager process, such as its name and description and the SiteManager functional area(s) to which it is assigned. To create a process, enter a Process ID and a Process Description. Associate at least one functional area with the process.

362 Security Groups

Figure 9.9 Define Custom Process Window - General Panel


Table 9.10 Define Custom Process Window - General Panel - Fields


Process ID Name identifier of the custom process. Displays on the appropriate Process List window as a process ID. User-entered. Required.

Process Type Processes created by the user are defaulted to Custom. SiteManager-provided processes are designated as Standard. Custom process types may run any executable file. Standard process types must always be executed as a SiteManager background process.

Process Description Description of the custom report. Displays on the appropriate Process List window as a process description. User-entered. Required.

Subset Designates the subset of records to be used in running the process.

Multiple Select Select the Multiple Select checkbox when the process template processes multiple subset records. Do not select it when the process will pass only a single row selection from the subsetting list window.

Example: If a process is designed to be generated for a single estimate, vendor, or project, then the multiple select box should not be selected, which means that the users running this process can select only one row of the subset table when they run the process.

Function ID Functional area(s) to which the process is assigned. Identifiers are as follows:

CA – Contract Administration

CP – Contractor Payments

DWR – Daily Work Reports

CO – Change Order

CR – Civil Rights

AC – Accessories

SA – System Administration

MM – Materials Management

PZ – Pipeline

Associated Functions Functional area(s) that have been assigned.

9.9.2 Parameters Panel Parameters are values that are entered by the user when the process is run. The user-entered parameter values select the data for the process function(s) based on that value. Up to ten (10) parameters may be specified for an individual process. Parameters are optional and are not required to define or run a process. When at least one processing parameter is specified, the process will display a parameter detail window when the process is selected to run. The parameter detail window will display the labels and defaults defined by the user on this panel, so it is especially important for Parameter Labels to be as specific as possible.

364 Security Groups

Each process may have between one and ten optional parameters associated with it that are presented to the user to accept or change before the process executes. On the Parameter panel, the user may enter custom parameter names, parameter labels, and default values. If at least one processing parameter is specified, the process will present a parameter detail window when users select it for execution. The parameter detail window will display the labels and defaults as defined.

Figure 9.10 Define Custom Process Window - Parameters Panel

Table 9.11 Define Custom Process Window - Parameters Panel - Fields


Parameter Name Specifies the identifier the RTF templates will use when users attempt to access the value of the parameter. Name must exactly match the name used in the templates. Required.

Parameter Type Denotes whether the specified parameter is a string, numeric, or date type.

Parameter Label Specifies the label to be shown on the parameter detail window when the process is run. Should be as specific as possible for ease of use. Required.

Default Value Value to initially populate the parameter when the window is opened by the user. Unless this is changed by the user at the time the process is run, it is the value that will be submitted to the process for its associated parameter. Optional.


9.9.3 Templates Panel

Use the Templates panel to view a list of RTF templates that will be accessed in the execution of the process. For a process to be considered an RTF report, there must be at least one template associated with the process.

Figure 9.11 Define Custom Process Window - Templates Panel

Table 9.12 Define Custom Process Window - Templates Panel - Fields


Templates The name of the template the process can access. At least one template must be entered to create an RTF report. For other types of processes, this is not required.

Description Required field for RTF reports. This is a user-entered textual description of the template.

Page Size Page size of the custom report.

Output File File name of the output file.

File Type A drop-down list from which the user may choose sequential or print.

9.9.4 Programs Panel Use the Programs panel to view the list of programs a process can initiate.

366 Security Groups

The Programs panel specifies which executable file(s) will be used to run the process. Executable files must be listed in the order in which they need to be run. The Command Line field may be searched using the search feature, if the Job Type is standard. Tip! RTF Templates require the program 'rtfdriv'. The RTF driver is capable of generating a TXT or an HTML report for an RTF template. Add this program to the process at the time the process is defined.

Figure 9.12 Define Custom Process Window - Programs Panel

Table 9.13 Define Custom Process Window - Programs Panel - Fields


Command Line Name of the file that the process can access. Name that DPS uses to locate the physical file. For a custom program, the command is user-entered. For a standard program, the search function may be used. Required.

Job Type Identifies the type of program. Options include standard and custom.

9.9.5 Files Panel Use the Files panel to view the list of output files that are required for a custom process. The output files for a custom process include files for the reports generated, as well as system files. Each defined output file must be assigned a descriptive name that the custom process references it by, and a file name that the file is to be saved as. Add the file 'PARMFILE' to the process at the time the process is defined.


Figure 9.13 Define Custom Process Window - Files Panel

Table 9.14 Define Custom Process Window - Files Panel - Fields


Logical Name Name of the file to be assigned when the process creates the file. Name that DPS uses to locate the physical file. User-entered. Required.

Physical Name Descriptive name assigned by the process and used to reference the output file. User-entered. Required.

9.9.5.1 Procedure CDOT hasn’t identified any custom processes necessary for SiteManager Materials or LIMS, so CDOT will not use this window for SiteManager Materials at this time.


SECTION 10 Test Templates

370 Test Templates

10.1 Material Test Template Procedure and Guidelines

SiteManager Navigation MAIN PANEL > SYSTEM ADMINISTRATION > TEMPLATES > MATERIAL TEST TEMPLATES

10.1.1 Material Test Template Procedure

The Material Test Templates that will be used in SiteManager LIMS will be defined and developed by the Material Test Template Subcommittee and CDOT IT. The Material Test Template Subcommittee is responsible for identifying the templates that should be developed. The progress of the development of each test template will be tracked in the Material Test Template Tracker with the following phases:

Unassigned

Assigned

Design

Review

IT

Testing

Complete

Unassigned: A test template in phase “Unassigned” has been identified as a template that is needed, but has not yet been assigned to a member of the Material Test Template subcommittee member to design.

Assigned: A test template in phase “Assigned” has been assigned to the Material Test Template subcommittee member to design. However, the design work has not yet begun.

Design: During the “Design” phase of the Template Development process, the Material Test Template Subcommittee member should complete the Test Method Spreadsheet (Ex. T304.xls), which is located in the Draft Test Template folder on SharePoint. The first folder tab in the spreadsheet should include all fields that should be saved to the SiteManager database in the order they should be reviewed, when viewing the test results in a column format. Do not add columns to this folder tab. The second folder tab (GUI) should include notes to IT in regards to formatting. This should include which fields should be hidden, calculations, special instructions (conditional text fields), tab order, etc. If available, copy examples or screen shots of existing forms into the spreadsheet. When creating a template, if a specification template is needed, identify the z template in the template spreadsheet by naming it z<test method>.1 (i.e. zT304.1, zT304.2….zT304.A). The designer should then email the Material Test Template Subcommittee leader with the requested z templates. The Subcommittee leader will then assign the requested number of z templates in the Tracker spreadsheet and create the z templates and put them in the Draft folder. When the spreadsheet goes to IT, if there are z Templates, then IT should import the z templates before importing the material test template from the spreadsheet. When the designer is complete with the spreadsheet, it should be saved to the Draft Material Test Templates folder in SharePoint and mark the template as Review in the Tracker spreadsheet.


Review: The Designer should solicit input from people who are most familiar with the test for a review before it is sent out to the Material Test Template Committee. CC the Subcommittee leader (Steve). Send email out to the subcommittee and give a week for comments. Comments should go the designer, not into the spreadsheet. At the end of the Review period, the Subcommittee leader will email IT with the following subject line to include the test name with the associated test when the spreadsheet is approved. There is no need to enter additional information in the email body as long as no additional information is required. For example:

To: [email protected]; [email protected]; Cc: [email protected] Subject: AASHTO T 304 Ready for Development

IT: When the spreadsheet is deemed reviewed, the Material Test Template can be changed to Phase “IT”. This is an indication that the template is ready for IT to import into SiteManager. When the Material Test Template is in the Phase “IT” and IT has been notified via email that it is ready for development, IT will update the IT column in the “Material Test Template TRACKER” spreadsheet to include the developer’s name. For Example: Giselle Martin Bill Moore

IT will update the “Test Template” spreadsheet “Supporting Documentation” tab with the following information (DATE OF IT LOCK STATUS 3/10/2010) to define lock status of Test Template. As of this status No Additional changes allowed without prior MIT approval. IT will copy the Test Template spreadsheet into IT’s source code repository (Subversion). IT will start the develop templates to be available for testing within the development platform. Once IT has completed the Test Template it will email Test Template Subcommittee Chair that it is now ready for the “Testing” phase with the following subject line to include test name with the associated test when it the spreadsheet is approved. No need to enter additional information in the email body as long as no additional information is required. For example:

To: [email protected] Cc: [email protected]; [email protected]; [email protected] [email protected] Subject: AASHTO T 304 Ready for Testing

Testing: What process will be used?

o Assign to a material. (Do you want to use the actual material or a “dummy material”? Do you want to put this in the training environment?)

o Add the tests. o Put Specifications. o Put the material on a sample. o Assign the test on the test folder tab. Enter View Test Results. o What environment will be used for testing?









372 Test Templates

When testing, check the following: o Does it work? o How does it look? o Tab Order? o Sample Review column format (need LIMS) o LIMS enter test results window (Need LIMS)

Complete: Template has been assigned, designed, reviewed, created within SiteManager, and tested.

10.1.2 Guidelines

The following guidelines are meant as a starting point for the “look and feel” of all templates. Although the designer has the ultimate responsibility of creating the layout for each template, these guidelines should be used to ensure a consistent look of CDOT’s templates within SiteManager. Please see example screenshot at the end of this section for reference. General Font Type: MS Sans Serif Font Size: 8pt (unless otherwise noted) Font Color: Black (unless otherwise noted) Background Color: Gray In-Spec / Out-of-Spec / No-Spec Box

Placement Notes: Top right corner of screen

Vertically aligned with Method Number

Print-Page Button

3D, “button” style

Placement Notes: Directly under, and horizontally sized to match “In-Spec / Out-of-Spec / No-

Spec” Box

Method Number (i.e. “AASHTO T 304”)

Font Size: 8pt

Font Case: ALL CAPS

Font Color: Black

Originating Field: B10, GUI Mockup Tab

Placement Notes: Top left corner of screen. Vertically aligned with top of “In-Spec / Out-of-Spec /

No-Spec Box”

Method Title (i.e. “Uncompacted Void Content of Fine Aggregate”)

Font Size: 12pt, Bold

Font Case: Mixed

Font Color: Black

Originating Field: C10, GUI Mockup Tab

Placement Notes: Directly under Designation Number, left-justified. Wrapped to 2 or 3 lines (if

needed), approximately 60 characters per line (so as not to overlap “In-Spec / Out-of-Spec / No-

Spec Box”

“Requires Additional Methods”


Font Size: 8pt

Font Case: Mixed

Font Color: Black

Originating Field: Any additional methods will be listed in B11, GUI Mockup Tab

Placement Notes: Only visible if applicable (shown in the example below for placement purposes

only). Left-justified. Vertically aligned with bottom of “Print Page” button

Labels on Data Window (i.e. “Weight of Measure”)

Font Size: 8pt

Font Case: Mixed

Font Color: Black

Placement Notes: Per individual “field layout” on GUI Mockup and/or Supporting Documentation

tabs

Data-Entry Boxes in Data Window

3D, “recessed” style box

Background Color: White

Font Size: 8pt

Font Case: Mixed

Font Color: Black

Calculated Field Boxes in Data Window

3D, “recessed” style box

Background Color: Gray

Font Size: 8pt

Font Case: Mixed

Font Color: Black

Tester Alert Fields (i.e. “TEST RESULTS DIFFER BY MORE THAN 0.37%”)

Font Size: 8pt, Bold

Font Case: ALL CAPS

Font Color: Red

Placement Notes: Per individual “field layout” on GUI Mockup and/or Supporting Documentation

tabs. Only visible when certain criteria are met (for example when two calculated field must be

within a certain tolerance)

374 Test Templates

Figure 10.1 Test Template Example

10.1.3 Material Test Template Design Forms

Figure 10.2 Definition Tab

Material Test Template Design Form

REF

Today's Date: 20120308

Table: t_tst_fee_schd

tst_meth tst_nbr tst_desc chrg_amt bill_cd fld_tst_ind aashto_ind templt_typ_ind last_modfd_uid last_modfd_dt

0 N N T CDOTSYS 20120308

Table: t_tst_templt_attr

tst_meth tst_fld_sn rel_tst_meth tst_fld_lbl tst_fld_data_t tst_fld_len tst_fld_unt tst_fld_exprs tst_fld_ind mix_dsn_tbl_nm mix_dsn_col_nm last_modfd_uid last_modfd_dt

500 Test Method Revision Date AN 4 CDOTSYS 20120308

501 Reserved NU 1 NU 8.5 CDOTSYS 20120308



504 Reserved CO 1 CO 8.5 504 CDOTSYS 20120308



507 Reserved AN 1 AN 60 CDOTSYS 20120308



1 Spec Status(IN=1 OUT=2 NONE=3) NU 1 CDOTSYS 20120308

2 Equipment AN 60 CDOTSYS 20120308

3 Remarks AN 60 CDOTSYS 20120308

Export SQL ScriptInstructions:1. Complete the Field Definitions on this spreadsheet2. Save spreadsheet with the Test Method as the file name

3. Click on the Export SQL Script button to generate a script which can be used to import the rows directly into the database4. In SiteManager highlight the test method in the Material Test Template definition window and click the Generate Icon5. In SiteManager export the template SRD file using the Services menu option

6. Import the template SRD file into PowerBuilder and customize7. Export the modified template SRD from PowerBuilder8. In SiteManager import the modified template SRD file using the Services menu option in the Material Test Template

definition window


Figure 10.3 GUI Mockup (Upper Section) Tab

Figure 10.4 GUI Mockup (Lower Section) Tab

Figure 10.5 Dropdowns

Figure 10.6 zSpecification Template Design Form

Template GUI Mockup

FULL TEMPLATE TITLE:

FIELD LAYOUT:

Instructions:1. In the box below write the field number in the general location where it should appear on screen.2. If any fields are to be hidden from view write the field number under the HIDDEN FIELDS section.

3. Additional notes about the field can be added as a remark on the cell or in the Additional Notes section.

Ensure all fields are listed

HIDDEN FIELDS

500

501

502

503

504

505

506

507

508

509

2

Additional Notes

Field Note

DataType Description Indicator Description TemplateType Description Units Description Bill Code Description

AN AlphaNumeric Y Yes B Basic Blank Spaces Blank Spaces

NU Numeric N No M Mix Design ABC123 ABC123

CO Computed Blank Spaces T Test Specification ETC ETC

LA Label

zSpecification Template Design Form

Table: t_tst_fee_schd Today's Date: 20120308

tst_meth tst_nbr tst_desc chrg_amt bill_cd fld_tst_ind aashto_ind templt_typ_ind last_modfd_uid last_modfd_dt

0 N N B CDOTSYS 20120308

Table: t_tst_templt_attr

tst_meth tst_fld_sn rel_tst_meth tst_fld_lbl tst_fld_data_t tst_fld_len tst_fld_unt tst_fld_exprs tst_fld_ind mix_dsn_tbl_nm mix_dsn_col_nm last_modfd_uid last_modfd_dt

1 Specification NU 1 CDOTSYS 20120308

Export SQL Script

376 Test Templates

10.1.4 Material Test Template Revision Process

The following are reasons that a template in use in the production environment would undergo a revision and a new template created.

Change to a calculation Field added to a template Field deleted from a template New calculation required by bad data

Revised templates will have a different naming convention than initial templates. The revision will be reflected in the template title. The following is an example of this template revision naming convention.

Initial Template: CP 48 First Revision: CP48aa Second Revision: CP48ab Third Revision: CP48ac Forth Revision, etc.

If the old template will still be available to use, the Test Method will be listed at the beginning of each description. If the old template will not be available for future use, it should be made inactive as soon as possible. When a template is revised, but its z template is unchanged, the same z template name will be used. If the z template specs change, that will be addressed by the Effective Date of the z template and the values. Therefore, z templates of revised test templates should NOT be deleted. The Revision Date on the test template will be the date it is accepted after review before it is put into production. The Template Revision Tracker spreadsheet will be stored on SharePoint. It will track the date of change that required the revision, description of the change that required the revision, date the MAC approved it, and where detail of change can be found. As of November 2012, no staff had yet been assigned to develop and maintain this spreadsheet.


10.2 Material Test Template Design – Quick Reference Guide Download the design form for the test you are working on.

Design Form (Definition Tab):

1. Open the design form. Click YES to enable macros when prompted. Select the Definition tab if it is not already selected.

2. The test method, test number and test description in row 10 will already be filled in with the

appropriate information.

tst_meth:

Enter test method; ex. T304. 7 characters max. Total of 10 characters is allowed but 3 characters are required for the zTemplate names.

tst_nbr: The test number that has been assigned to the test method. It is found in the Material_Test_Template_TRACKER.xls.

tst_desc: The test title. Only 30 characters max allowed. If the test title is longer than 30, abbreviate it here and put the complete title on the GUI Mockup tab.

charg_amt: For the test charge amount. Left blank for now.

bill_cd: For the test billing code. Left blank for now.

fld_tst_ind: Set to Y if the test will ever be performed in the field.

aashto_ind: Y if this is an AASHTO test method.

templt_typ_ind: All test templates will be “T” (select from dropdown)

last_modfd_uid: CDOTSYS. Do not edit.

378 Test Templates

last_modfd_dt: Date will auto populate. Do not edit.

Template Field Definitions

3. A separate row is needed to define each field on the template. Another row can be added by typing the test method name in the first empty cell. Type the test method name in field 28 which opens the row for entry.

4. Fill in the field label, type, length, and unit for each row.

The tst_fld_sn is the field number. The spreadsheet will automatically put this in so do not edit the field. The numbering for the fields you add will start at 4. The fields are often referred to as F4, F5, F6, etc. If you have fields which will be common in many different test templates it will be advantagous later for custom reports to make them the same row, or F field, in all of the templates. If a global specifiction will exist for the field then enter the zTemplate spec name in the rel_tst_meth column for that field. Be sure to use the correct format: zTestName.1, zTestName.2, etc. The same zTemplate name can be used for multiple fields on the template if the fields are similar and have the exact same spec values. Detailed information on other types of specifications is shown at the end of this document in the Handling Specifications section.

The tst_fld_lbl is the description of the field in the template. This is the default description that will show for the field but can be customized later using PowerBuilder. If you have a series of fields in a table style format remember to reference that in the field description. For example Weight 1, Weight 2, Weight 3, etc. The tst_fld_data_t sets the type of data. Choose from the following:

AN: Alphanumeric CO: Computed (calculations) NU: Numeric

The tst_fld_len field sets the length or precision of the field. Alphanumeric fields can be a max of 60 characters long. For numeric or computed fields this is the decimal precision: 2.1 means 2 number to the left of the decimal and one number to the right of the decimal. The tst_fld_unit will not be used. Specify the units desired for the field on the GUI Mockup tab.

5. Continue to define all remaining fields for the template.


Design Form (GUI Mockup):

6. When completed continue to the GUI Mockup tab and enter the fields as they should approximately appear on the completed template. This is also where additional labels or text fields can be specified.

7. Computed fields that are not required to be saved to the database can be added in by a

developer in PowerBuilder. Specify the need for those fields here. These are typically used when you only want to show a value to the user performing the test but do not wish to save that value. They are also used for holding interim calculations.

8. At the bottom notes about specific fields can be added, such as formatting or formulas.

9. Supporting documentation (scans of existing forms, existing spreadsheets, images, etc.) can be added to the Supporting Documentation tab

380 Test Templates

Handling Specifications The easiest spec to account for is a global spec. The spec values are tied to the material using the template and zTemplate. This allows for a spec to be different for each material that uses same template. Set up of the global spec is outlined in Step 4 above. A mix design spec is more complex to model. It will require 3 fields to be defined on the template:

1. Template Result This will be the value (either Calculated or Numeric field) that is derived from the user’s interaction with the template. Could be the R value or VMA for example.

2. Mix Design Value This is the value from the Mix Design associated to the sample which would be the Contract’s mix. This will be a computed field. A custom function will be needed to pull the mix design value from the mix associated to the sample.

3. Deviation field with zTemplate spec If a deviation needs to be checked between what the template result and the mix design value is then this can be accomplished through a zTemplate. A computed field will be needed that will calculate the deviation between 1 and 2. Tie a zTemplate to this computed field using the rel_tst_meth column just as a global spec outlined in Step 4 above. The min and max values will be set up as the limits of the deviation (-1.2 to 1.2, for example).

This method will also account for Project Special Provisions which are regarding mix designs since the mix will be set up for each Contract.


SECTION 11 Creation of Reports

382 Creation of Reports

11.1 Report Procedures and Guidelines

REPORT PROCESS OVERVIEW

Before SiteManager – Materials CDOT had quite a few forms. Through time, the hard copy forms were individually created in spreadsheets. Many of those forms and spreadsheets are now incorporated into SiteManager – Materials. CDOT’s position is that SiteManager – Materials is an electronic warehouse of date storage. Most every day operations are electronically done. Reviewing of individual data records are also electronically done. But, reports are necessary for required hard copy signatures. They are also helpful to summarizing or compiling datasets for review. Graphing is another advantage of reports. So there is still a mixture of electronic data and hard copy reports. Individuals or groups should send request of reports to the Central Laboratory’s Pavement Design Program for review. The Pavement Design Program will review and check for completeness. After review, the request will be forward to Governor’s Office of Information Technology (OIT) for coding and creation. The requester will perform the testing. The requester will have to accept the report as being complete and final.

11.1.1 Reporting Requirements

The Pavement Design Program will review the requested report. The submitting individual or group will need to submit a template for the review. The template shall include the following: Title: The title of the report as you want to see printed on each page. Sub-Title: The Sub-Title that you want to see printed under the Title on the report. Description of Report: Description of what the reports function is and what the report is used for. Gives the user a better understanding of what the report does. Define Reporting Parameters: Identify the reporting selection criteria for the data collection. Example select by Contact ID and by date range. Define how you want the data to be selected for the report. If nothing is identified then the default selection is ALL with no exceptions. Do you want to exclude any data on the report? If so, identify what you want to be exclude and how in detail. Special Requirements:

Any special reporting requirements that the developer should be aware of. Such as formulas to calculate equations.

Are there any special formatting or file format requirements.

Are there any Federal or Regulatory requirements for the report. Frequency:

How often is the report expected to be run. Monthly, Daily etc. Security: Who can run the report? Can anyone run the report or only a select group of people? Regions? Managers? Output Format:


Outline how you want the report to look. Identify each column heading and field you want printed on the report. Identify where the data resides in the new SM Materials/LIMS database for each field you want printed on the report. If it is a calculated field please document how the field is calculated under the formula column below. Below is an example of a Report Layout.

Figure 11.1 Description/Layout

Enter each Column/Field on the report below identifying where it is in the SM Materials/LIMS database. This can be done in attached screen shots identifying the fields but if you know the table name and column name from the table that you want to see printed then please complete the table below. COMMENT: Pavement Design Program can provide the Requester with examples of current reports, drawn out by hand. Screen shots would be helpful to identify where the data is coming from (field mapping).


Table 11.1 Example of Report Column Definitions Used on Report

Column/Field Id Format Report Field

Table ID Formula


11.1.2 Report Formatting

Font and report’s title is explained.

Figure 11.2 Report Formatting


11.1.3.1 Report Procedure Before SiteManager Was Implemented The Reports that will be used in SiteManager LIMS will be defined by the various Subcommittee’s to be reviewed by the Reporting Subcommittee and development by CDOT IT. The Reporting Subcommittee is responsible for identifying and tracking the reporting process in how reports should be developed along with reporting standards. The progress of the development of each report will be tracked in the Reporting Tracker Spreadsheet located on SharePoint with the following phases:

Unassigned

Assigned

Design

Region 2

Characters

Contract ID

15 Characters

CDOT Logo Font = 10

Title Font = 18

Project Data Font = 8

Used Arial Font

Characters detemined by typing W's across fields

Status + Title - Sample Status is optional

, below is what I put in the Generic Template Definitions tab.

6 default Title SMPLSTAT and

t_tst_fee_schd

Varies tst_desc NA

Subheading Example


Title


Status + Title (Sample Status is used when

applicable but is optional must specify if wanted printed)

Location 60 Characters

2 Lines for location (60 Characters)

Project No.

13 Characters

Display "Preliminary" for

SMPLSTAT: Pending, Logged,

Pending Authorization, Received,

and In Testing. Display " " for

SMPLSTAT: Complete. Display

"VOID" for SMPLSTAT: Void and Fail

(Fail should not be a choice for

CDOT). Display the previous text

before "Test Description for

Template" and adjust the text and

cell size to fit.

Date Sampled Sampled by: Material Description

Item No. Field Id. No. Mix Design No. Lot No.


Review

IT

Testing

Complete

Unassigned: A report in phase “Unassigned” has been identified as a template that is needed, but has not yet been assigned to a member of the subcommittee member to design.

Assigned: A report in phase “Assigned” has been assigned to a Developer to develop. The report has been approved by the MIT and the Reporting Subcommittee then forwarded to the Reporting Subcommittee Chair for resource assignment.

Design: During the “Design” phase of the Template Development process, the Subcommittee member should complete the Reporting Requirements Spreadsheet, which is located in the ‘Reports > Procedure Docs’ folder on SharePoint.

Review: During the “Review” phase of the Reporting Development process, the Subcommittee member should complete the Reporting Requirements Spreadsheet, which is located in the ‘Reports > Procedure Docs’ folder on SharePoint.

IT: A report in phase “IT” has been identified as a report that has been approved and forwarded to IT for development. IT resources have been assigned to report and updated in the Tracking Spreadsheet.

Testing: A report in the phase “Testing” has been developed and ready for User Acceptance Testing by originating Subcommittee. IT phase is complete.

Complete: A report in the phase “Complete” is fully tested and signed off from all Subcommittee member’s and the MIT. The report is approved for implementation and production. The first folder tab in the spreadsheet should include all fields that should be saved to the SiteManager database in the order they should be reviewed, when viewing the test results in a column format. The Report Design Process will be initiated by each Subcommittee. Each Subcommittee requesting a report is responsible for defining their reporting requirements by completing the ‘Reporting Requirements’ template. Once the ‘Reporting Requirements’ template and all associated design documentation have been completed by the Subcommittee, the Subcommittee Chair will submit the reporting requirements to the MIT Chair, Jay Goldbaum, Pavement Design Program Manager. The MIT Chair will forward the Reporting Requirements information to:

Initial to the Committee Chairs for review and comments from their members of the various Subcommittee’s.

Once the reporting requirements are complete they will be sent out to the MIT Committee members for final review and approval. MIT Committee members will have a week to review and approve reporting requirements and priorities.


Once the MIT has approved the reporting requirements, the Reporting Subcommittee will be notified by Jay via email that the Report is approved for Development.

If the MIT has questions, the Reporting Requirements will be forwarded back to the Subcommittee. If there are any unresolved issues during the MIT Committee review process they will be forwarded to the Core Team for resolution by the IT Chair.

Reports will be prioritized at the Subcommittee level prior to the Reporting Subcommittee.

MIT determines the final prioritization.

Once MIT has approved the report for development, it will be forwarded to the Reporting Subcommittee.

Reports will be tracked via the tracking spreadsheet under the Report Subcommittee’s folder on SharePoint. The Reporting Subcommittee will perform final design and analysis of reporting requirements. Once the Reporting Subcommittee has reviewed the reporting requirements, the report will be assigned to a developer based on the assigned reporting priority. During report development, developers will communicate with the appropriate Subcommittee to clarify any questions as needed. Once the report has been developed and tested by the developer, the Reporting Committee Chair will notify the appropriate Subcommittee Chair that the report is ready for user-acceptance testing and signoff by their Subcommittee. Once the Subcommittee has signed off on the report, the Subcommittee Chairperson will notify the Testing Subcommittee Chairperson that the report is ready for final testing and approval prior to implementation into production. Each report will be developed based on the report classification with the following priorities:

High

Medium

Low

High A report prioritized as “High” has the highest priority for development and will be developed before any Medium or Low priority reports.

Medium A report prioritized as “Medium” has been identified as a template that is needed, but has not yet been assigned to a member of the Material Test Template subcommittee member to design.

Low A report prioritized as “Low” has the lowest priority for development and will not be developed until all High and Medium reports have been completed.

11.1.3.2 Report Design Process Before SiteManager Was Implemented Design Phase Subcommittee members will provide the Reporting Subcommittee their reporting requirements and design of the report. The Subcommittee will be responsible to complete the Reporting Requirements Template outlining their requirements for each requested report identifying how the report should appear.


Subcommittees can provide the Reporting Subcommittee with examples of current reports, drawn out by hand. Screen shots would be helpful to identify where the data is coming from (field mapping). The Subcommittee should show how it wants the report to look when it is printed. IT is available for assistance as needs arise by Subcommittee’s.

Subcommittee Chairs are responsible for completing the Reporting Requirements Template and submitting them to MIT. Subcommittee’s requesting a report should attempt to identify all fields and formulas required for calculations on the report. Font, header and footer standards are outlined on SharePoint. Reports will be created and saved in a PDF format and/or Microsoft Excel spreadsheet. They will be able to be printed for all SiteManager (ASIDE: Currently SiteManager Accessories prints all reports…is this going to change for the Materials module?) Material’s users statewide in all regions.

Develop Report We will be developing reports in Crystal Reports in our current SiteManager development environment by internal ITO staff. Developers will prioritize based off of MIT outlined priorities and Reporting Subcommittee decisions.

Testing Developer will sign-off their unit testing and notify Subcommittee member when report is ready for user acceptance testing. Subcommittee will test and signoff on the report when they are satisfied that it meets the requirements. Once the Subcommittee has signed-off on the report the Testing Subcommittee will then perform final system testing prior to implementation.


SECTION 12 Answers to Possible Questions

390 Answers to Possible Questions

12.1 Introduction The following reference material was developed for SiteManager users so that they can understand how information is coded in SiteManager.

12.2 Crystal Ball used for Construction This reference material was developed by John Kacinski for SiteManager users. Please refer to this section prior to calling the CDOT HQ Materials Documentation Unit for clarification. The Documentation Unit notes that the following assumptions were made in SiteManager/LIMS in order populate the new Report # 250 in CAR for all CDOT projects regardless of location, Geology, Standard Special Provision requirements, OR “Construction Methods” to be used. The following is a partial list of the Test Method #s that you may be on an SAP, CAR report, such as the new Report # 250, “Material Testing for Default Bid Items Report”, the “Certification Checklist Report”, OR the future Report # 379 for IAT tests. The Material Testing for Default Bid Items Report, and the Certification Checklist Report: These reports pull from the Bid Item Numbers provided during the CDOT bid process on the Construction end. Material codes were associated to each Bid Item Number ever created by the Engineering Estimates and Market Analysis squad in order to decide whether testable materials are present in the Bid Item Number. There may be more than one material code designated for a Bid Item Number with Incidental Items, or when the Designer has called out an item “as included in the cost of the work”, meaning that additional materials other the obvious one needed to be identified for testing (Example: SMA has a material code 403.02.03.06 for Stone Matrix Asphalt, a 703.06.01.00 for Aggregate Mineral Filler and/or Fiber, as well as a 712.03.01.00 for Hydrated Lime.). Tests were then associated to the identified material components within the Bid Item. Location & Geology: These items vary throughout CDOT’s Regions. The Denver Metropolitan Area may never perform a Rock Correction on an Embankment material, unless Shale is encountered, and the adjacent Foothills may never see an Embankment material without a Rock Correction. In SiteManager/LIMS the Report # 250 will list tests for both Soil and Rock Embankment materials. For projects with both Rocky and Sandy materials this works great, but in all other cases, the tester will have to refer to Page 2 of the Form # 473 to explain why no tests were taken (Example: No Rock Corrections were performed, due to sandy material on site.). QA/IA Schedules & Standard Special Provision Requirements: The 2013 FMM QA/IA Schedules list 403 HMA along with a list of Gradation specification tests. The “Material Testing Default Bid Items Report” is non-project specific (not tied to a Subaccount or Contract ID#). If the Bid Item Number selected is for an HMA, then it should be noted that it was assumed that in the future all HMA projects will be bid w/Voids Acceptance in mind, and the Test Method #s, and Rate/Frequency encoded are based on the most current Voids Acceptance Standard Special Provision. If the Bid Item Number selected is for an SMA, it was assumed that in the future all SMA projects will contain PG 76-28 and be bid w/Gradation Acceptance in mind, and the Test Method #s, and Rate/Frequency are therefore based on the most current Gradation Acceptance Test Methods as specified by Project Special Provision. If the Bid Item Number selected is for Item 412 PCCP, it was assumed that in the future all PCCP projects will be bid w/Flexural Strength Acceptance in mind, and the Test Method #s, and Rate/Frequency are therefore based on the most current Flexural Strength Acceptance Standard Project Special Provision. The creator of the Report #250, at the Documentation Unit will review your plans, and specs in advance, adjust the list of Test Method #s and Rate/Frequency for your specific project. If the


Designer is not clear what he wants, then phone calls will need to be placed to a head tester or Regional Lab Manager for better information. “Construction Methods” to be Used: Some Designers leave it up to the Contractor whether or not structures, such as Inlets and Manholes are Cast-in-Place or Precast. Many projects start out assuming they will use only one of these methods, and end up building both. Precast items are not controlled by QA tests, but instead typically are required to be taken off of the approved CDOT QML list of precast manufacturers. The following assumptions were made during coding: All Manholes (storm or sanitary) are precast, and all Inlets are cast-in-place. This decision was made with the creator of the Report # 250 in mind, as well as the field tester. If in the field all Manholes are actually cast-in-place, then material codes will need to be added and Test Method #s associated to them (call the Documentation Unit for questions on this). If in the field all Inlets are actually precast, then Page 2 of the Form # 473 will require a one line explanation for the lack of tests (Example: Inlets were Precast, therefore no QA/IA tests were required.).

12.3 Test Numbers in SiteManager vs. in the FMM (03/08/13) This reference material was developed by John Kacinski for SiteManager users. Please refer to this section prior to calling the CDOT HQ Materials Documentation Unit for clarification. The following is a partial list of Test Method numbers that you may be able to add or view in SiteManager to a Sample, OR that may be on an SAP, CAR report, such as the new Report # 250: C109-28, C109-7, C109-I; ACCOST; C39-28, C39-56, C39-7, C39-I; CERT; CP31S; CP31X (or in the future CP31HMA); CP44L; CP48aa; CP85C; CPL 5120C; T106-28, T106-7, T106-I; T24-28, T24-56, T24-I; T59-21; T97-28, T97-7, T97-I You probably have noticed that the above list of Test Method #s varies slightly from what is listed in your FMM, and the QA & IA Frequency Guide Schedules. In some instances we use more than one of the same Test Method #, where previously there was only one Test Method in hardcopy format. EXPLANATIONS: Time: Certain Test Methods, such as used with concrete, or grout, are performed at specified intervals. The 28 day breaks are shown as -28; 7 day breaks are shown as -7; the “Informational” concrete compressive cylinders requested by the Contractor for form stripping, or early access of traffic to PCC are shown as –I; and if previous 28 day breaks test results were low, then you may have the Concrete or Field Lab break a set of cylinders or cubes at 56 days, which is shown as -56. Ex.: C109-28, C109-7, C109-I; C39-28, C39-56, C39-7, C39-I; T106-28, T106-7, T106-I; T24-28, T24-56, T24-I; T97-28, T97-7, T97-I QPM software work-a-round: ACCOST was created to handle the QA/QC Incentive/Disincentive calculations when the PG grade Asphalt Cement is paid for under Bid Item 411 (typically only used in Regions 3 & 5). COCs and CTRs: CERT was created as a Test Method # to enable quantities written on multiple hard copy COCs and CTRs to be entered, and a cumulative record can be kept for your Contract ID #. Revisions: CP48aa was included to describe what a Revision may look like. As the CPs, CPLs, ASTM, and AASHTO procedures are revised, so must the software be similarly updated, and an alphabetic


Revision tracking system such as aa will allow for more procedure changes to be made (or corrections to the software to be made as errors are discovered) within the space provided. Correction Factors: CP85C & CPL 5120C: In previous years the FMM’s QA & IA Frequency Guide Schedules may not have actually listed every behind the scenes preparation or process, such as the use of Correction Factors. In the examples provided the C stands for Correction Factor (and NOT Method C). Special Use of the Same Test Method Numbers: CP31S = Gradation performed after splitting the sample on the No. 4 sieve. CP31X (or in the future CP31HMA) = Gradation to be used for all 403 HMA (& SMA) Bid Item Numbers; CP44L = Longitudinal Joint Density (as opposed to In-Place Density elsewhere; T59-21 is not actually a “named” Test Method #, it refers to p. T59-21 within AASHTO D244 of the AASHTO Standard Specifications, Part II. This was used to define Weight / Gallon of Emulsified Asphalt, since the Bit. Lab does not use all of D244, and T59-21 just records a value (Seasoned testers know that -## after an AASHTO or ASTM procedure number represents the last revision date, and 1921 & 2021 is not reasonable. Yes, even we can’t catch everything that gets slipped in.)

12.4 SM Rate per Freq vs. FMM QA IA Schedule (03/11/13) This reference material was developed by John Kacinski for SiteManager users. Please refer to this section prior to calling the CDOT HQ Materials Documentation Unit for clarification. Several workarounds were required to code SiteManager/LIMS to emulate the FMM QA & IA Schedules. The Documentation Unit wants to point out a few of these differences that will be seen when entering sample and test data, or when reading an SAP, CAR report such as the new Report # 250. The following is a partial list of some problems that needed to be addressed, as well as a short explanation of the solutions used. IA Rate/Frequency: SiteManager/LIMS was originally designed for QA data entry only. CDOT has determined a way to also use it for IA data entry. In SiteManager the total QA and IA tests will be added together, so a “work-a-round” within the coding was to use a Rate=ZERO, so there is a ZERO/Frequency used for the required IA tests calculated from the Bid Item Number’s Bid Quantity. In the future a SAP, CAR 379 Report will sort these ZEROs out and replace them with a ONE for the IA Rate to calculate a correct “estimate” of IA tests. (In SiteManager when a “new” IA test requirement is added to the Report # 379 you will skip past the Rate (which on a new test method entry will already appear as a Zero) and only enter the Frequency, so that all IA Rate/Frequencies will be coded as ZERO/Frequency.) Example: For Gradation Specification projects IA testers know that Item 403 HMA gradations (CP31X) are run at a Rate/Frequency of 1/10,000 TONS, in accordance with the 2013 FMM IA Schedule. Think of the number of QA tests that you wish to perform as an IAT tester (ZERO, IAT testers do not perform QA tests), and so you are asked to use ZERO/10,000 TONS when creating the Report # 379. Rate/Frequency Notes that are based on Time within the QA & IA Schedules: In SiteManager/LIMS for QA you will see 99,999/1 used to indicate a time frequency, such as one/day, one per mix, one/project OR three/day, one/five batches; your CAR Reports will display */* so that field personnel do not question if we changed the QA Schedule with SiteManager/LIMS. (In SiteManager/LIMS for IA you will see 0/9,999,999 used to indicate a time frequency.) Multiple Rate/Frequency Notes: As an example, on an Item 412 PCCP “Compressive Strength” project C39-28 is used for Compressive Strength 28 day cylinder breaks. The 2013 FMM QA Schedule shows


the Item 412 Rate/Frequency as 1/day, 1/5,000 SY AND 3/Mix Design. The computer will only accept one Rate/Frequency, and so 1/5,000 SY was used in this particular coding example. However this does NOT preclude the field tester from doing his job, reading the FMM , as well as the QA and IA Schedules, and testing at those time Rate/Frequencies, but the field tester is off of the radar as far as the Report 250’s tracking ability. (This is no different than the current Form 250, which is an estimate of minimum materials testing.) Material Specifications: Min/Max Ranges will appear on certain Sampler/Tester screens representing either the specific allowable limits of the CP, CPL, AASHTO, or ASTM procedures, OR as defined by the Standard Specifications Item 700 Section, OR as required by the Standard Special Provisions. When Min/Max Ranges are coded to any number may be used between -99,999,999 and +99,999,999. (ASIDE: The use of – or + 99,999,999 signifies a null value or no value. When using this, the Min/Max numerical field box in the procedure’s windows should disappear. This means that the results will be compared to a true numerical Min/Max and not a place holder of spaces signifying a null value; SiteManager/LIMS does not recognize null values, it uses them as numerical zeros.)


This page intentionally left blank.