User Manual

UK DCP 3.1

Measuring Road Pavement Strength and

Designing Low Volume Sealed Roads using the

Dynamic Cone Penetrometer

Simon Done and Piouslin Samuel

Unpublished Project Report
UPR/IE/76/06
Project Record No R7783
PROJECT REPORT UPR/IE/76/06

Measuring Road Pavement Strength and Designing Low Volume

Sealed Roads using the Dynamic Cone Penetrometer

Piouslin Samuel and Simon Done

Sector: Transport

Theme: T2: Reduce overall transport cost by cost effective road

rehabilitation andmaintenance

Project Title: Environmentally Optimised Design

Project Reference: R7783

Approvals

Project Manager

Quality Reviewed
Copyright TRL Limited April 2006
This document has been prepared as part of a project funded by the UK Department for
International Development (DFID) for the benefit of developing countries. The views
expressed are not necessarily those of DFID.

The Transport Research Laboratory and TRL are trading names of TRL Limited, a member of the Transport
Research Foundation Group of Companies.
TRL Limited. Registered in England, Number 3142272. Registered Office: Old Wokingham Road,
Crowthorne, Berkshire, RG45 6AU, United Kingdom.
ACKNOWLEDGEMENTS

The development of UK DCP software has been based upon the responses received to
a questionnaire distributed to the members of the International Focus Group (IFG). We
are extremely grateful to those who took the time to complete the questionnaire and
return it to us. We are also grateful to Yogita Maini of DFID, Phil Page-Green of CSIR,
South Africa, and Dr Simon Gillett of Roughton International who reviewed the project
and provided useful feedback. The TRL team responsible for analysing the
questionnaires, designing the software, writing the user manual and making UK DCP 3.1
available were Piouslin Samuel, Colin Jones, Simon Done, Dr John Rolt, Dave Weston
and Trevor Bradbury. Dr Stephen Morris and his team from Tessella Support Service
wrote this software.
April 2006
Contents
1 Introduction
1.1 The DCP
1.2 UK DCP 3.1
2 Installation
2.1 Obtaining UK DCP 3.1
2.2 Installing UK DCP 3.1
2.2.1 Installation from CD
2.2.2 Installation from Transport Links website
2.3 Uninstalling UK DCP 3.1
3 Start up
3.1 Run UK DCP 3.1
3.1.1 Start a new project
3.1.2 Open an existing project
3.1.3 Closing a project and exiting UK DCP 3.1.
3.2 Project Manager
3.2.1 Test Status
3.2.2 Design Status
4 Test data input
4.1 Introduction
4.2 Site details
4.3 Upper layers
4.3.1 Layers removed
4.3.2 Upper layer details
4.4 Penetration data
4.4.1 Site details summary
4.4.2 Penetration data
4.5 Set-Up
4.5.1 CBR Calculation
4.5.2 CBR Adjustment Factor (for moisture)
4.5.3 Analysis
4.5.4 Display Options
4.6 Alternative methods for inputting data
4.6.1 Merge
4.6.2 Import
5 Layer analysis
5.1 Introduction
5.2 Analysing Test layers
 5.3 Automatic layer analysis
5.4 Manual layer analysis
5.5 Analysis of drilled and very strong layers
5.5.1 Drilled layers
5.5.2 Very strong layers
6 Structural Number calculation
6.1 Introduction
6.1.1 Upper layers
6.1.2 Base and Sub-base Test layers
6.1.3 Subgrade Test layers
6.2 Calculating the Structural Number
6.2.1 Upper layers
6.2.2 Test layers
6.2.3 SN Calculation Buttons
6.2.4 Pavement Strength
7 Query
7.1 Introduction
1.1 Making a Query
7.1.1 Query Parameter
7.1.2 Tests Included
7.1.3 Query Type
7.1.4 Display Options
7.2 Displaying the Query results
7.2.1 Structural Number
7.2.2 Layer or Pavement Thickness
7.2.3 CBR
8 Sectioning
8.1 Introduction
8.2 Sections box
8.2.1 Parameters
8.2.2 Tests Included
8.2.3 Sections buttons
8.3 Sectioning a project
8.3.1 Determine Sections by parameter
8.3.2 Determine DCP Sections for the project
9 Design data input
9.1 Survey Data
9.2 Design & Costs Data
10 Design Sections
10.1 Introduction
10.2 Displaying available design data
 10.3 Defining Design Sections
10.4 Design Section Properties
11 Pavement Design
11.1 Introduction
11.2 Pavement design box
11.3 Design: Section box
11.3.1 Design Options
11.3.2 Cross Section
11.3.3 Existing Pavement
11.3.4 Parameters to use with design catalogue
11.3.5 Proposed Pavement
11.3.6 Carriageway Surfacing and Materials
11.3.7 Shoulder Surfacing and Materials
11.4 Buttons
11.5 Estimation of quantities
12 Reporting
12.1 Introduction
12.2 Penetration Data report
12.3 Layer Strength Analysis report
12.4 Tests Summary report
12.5 Section Summary report
12.6 DCP Section Properties report
12.7 Pavement Design report
12.8 Bill of Quantities report
12.9 Maintenance report
13 References
Appendix A: DCP Test Data Form
Appendix B: Survey Data Sheet
List of Figures
Figure 1.1 DCP instrument
Figure 3.1 Flash Screen
Figure 3.2 Welcome box
Figure 3.3 Project Manager (without test data)
Figure 3.4 Project Manager (with test data and completed analysis)
Figure 3.5 Project Manager (with test data and completed design)
Figure 4.1 Test Details box
Figure 4.2 Illustration of Upper layers, Test layers and Removed layers
Figure 4.3 Penetration Data box (with test data)
Figure 4.4 Penetration Data box (with a drilled layer and an extension rod)
Figure 4.5 Set-up Options box
Figure 4.6 Project Manager (showing that test data has been input)
Figure 5.1 How Automatic analysis works
Figure 5.2 Layer boundaries box using Automatic analysis
Figure 5.3 Project Manager (showing that test data has been analysed)
Figure 5.4 Layer Boundaries box using Manual layer analysis
Figure 5.5 Project Manager (showing that test data has been analysed)
Figure 5.6 Double intersections
Figure 5.7 Negative gradient
Figure 5.8 Line does not intersect the line of test points
Figure 5.9 Line drawn parallel to its intended position
Figure 5.10 Line moved laterally to its intended position
Figure 5.11 Lines overlap but do not intersect
Figure 5.12 Automatic analysis of a drilled layer
Figure 5.13 Manual analysis of a drilled layer and the use of gaps
Figure 5.14 Automatic analysis of a very strong layer
Figure 5.15 Manual analysis of a very strong layer and the use of gaps
Figure 6.1 SN Calculation box (before calculating SNs)
Figure 6.2 Layer Boundaries box
Figure 6.3 Adjusted Penetration Data box
Figure 6.4 CBR chart box
Figure 6.5 SN calculation box (after calculations are complete)
Figure 6.6 Project Manager (showing that SNs have been calculated)
Figure 7.1 Query box
Figure 7.2 Structural Number histogram
Figure 7.3 Layer Thickness histogram
Figure 7.4 CBR histogram (Minimum)
Figure 7.5 CBR histogram (Less Than)
Figure 8.1 Sections box (before sectioning)
Figure 8.2 Uniform Sections box
Figure 8.3 Histogram of sectioning data
Figure 8.4 Uniform Sections box (with one section boundary added)
Figure 8.5 Sections box (after Sectioning)
Figure 8.6 Section Summary box
Figure 8.7 DCP Section Properties box
Figure 8.8 Section Summary box (with one DCP Section boundary added)
Figure 8.9 Project Manager (showing that DCP Sections have been defined)
Figure 9.1 Survey Data box (without data)
Figure 9.2 Survey Data box (with data)
Figure 9.3 Project Manager box (after entering survey data)
Figure 9.4 Design & Costs Data box (with data)
Figure 10.1 Design Sections box
Figure 10.2 Design Section Legend
Figure 10.3 Design Section box (with CBR)
Figure 10.4 Design Section Properties
Figure 10.5 Project Manager Box (after Design Sections have been defined)
Figure 11.1 Message on statistical parameters
Figure 11.2 Pavement design box – before designing
Figure 11.3 Design (Section box)
Figure 11.4 Design catalogue (2<N<4)
Figure 11.5 Design catalogue (N>4)
Figure 11.6 Pavement design box – after design
Figure 11.7 Project Manager (after pavement design)
Figure 12.1 Export box
Figure 12.2 Penetration Data Report
Figure 12.3 Layer Strength Analysis report
Figure 12.4 Test Summary Report
Figure 12.5 Section Summary Report
Figure 12.6 DCP Section Properties Report
Figure 12.7 Pavement Design Report
Figure 12.8 Bill of Quantities Report
Figure 12.9 Maintenance Report
List of Tables

Table 4.1 Penetration rate-CBR relationships

Table 4.2 CBR Adjustment Factors
Table 4.3 Effect of moisture adjustment factor on Subgrade CBR
Table 5.1 Example of penetration data and cumulative sum analysis
Table 6.1 CBR-Strength Coefficient (a) relationships
Table 11.1 Subgrade CBR

List of Boxes
Box 1.1 Key points to know before using UK DCP 3.1
Box 4.1 Recording the removal of very thick Upper layers
Box 4.2 Calculating adjusted penetration data
Box 5.1 Should penetration data be analysed automatically or manually?
Box 5.2 Corrected analysis of deep surface texture and disturbed soil
Box 5.3 Analysis of a drilled layer
Box 5.4 Analysis of a very strong but penetrable layer
Box 6.1 The importance of checking the layer analysis against CBR Chart
Box 9.1 Recording of variations within data interval
Box 9.2 Determination of design traffic
Box 10.1 Determination of Design Sections
Box 11.1 Reassigning existing pavement layers
1 Introduction
When required to design improvement works, a pavement engineer needs to know the
environment in which the road is located, the details of the pavement layers and the
current condition of the road. These details are normally collected in stages, beginning
with a desk study and field survey, progressing to non destructive testing and finally, if
necessary, to destructive testing and laboratory studies.

The initial survey along the road helps to find changes, if any, in the surfacing, geometry,
land use, drainage, and the crown height along the road and the influence that any of
these may have, jointly or individually, on the pavement.

In some cases the quickest and easiest way of assessing the thickness and strength of
pavement layers is to inspect the design drawings or the as-built records made during
construction. However, designs indicate only the intended construction and as-built
records are often only an approximation of the construction work carried out.
Furthermore, both designs and as-built records give no information as to what has
happened to the pavement since construction and the condition it is currently in. To give
useful information, it is therefore necessary to investigate the current pavement condition.

A common method of pavement investigation is to dig test pits at suitable intervals along
the road. These are very useful as pavement thicknesses can be measured and material
can be removed for testing in a laboratory. However, test pits are time consuming and
expensive to dig and reinstate and as a result are rarely dug at intervals of less than 2-3
kilometres. The Dynamic Cone Penetrometer (DCP) (Figure 1.1) is a quicker and
cheaper way of investigating the pavement which allows tests to be carried out at much
more frequent intervals.

After the road and the environment in which it is located have been surveyed and the
condition of the pavement layers has been investigated, the road can be divided into
sections which are uniform in a variety of characteristics and for each of which
improvements can be appropriately designed.

UK DCP 3.1 software is designed for two categories of user: those who wish to analyse
DCP data; and those who need to produce design for lengths of sealed roads used as
spot improvements on low trafficked roads. Chapters 1 to 3 describe functions, such as
installation, which are common to all users. Chapters 4 to 8 describe the analysis of
DCP data and Chapters 9 to 11 describe pavement design. Finally, Chapter 12
describes the reports which both categories of user may wish to produce. The contents
of each Chapter are described in the following table.
Chapter Title Description
1 Introduction
2 Installation Obtain and install UK DCP 3.1.
3 Start up Run UK DCP 3.1 and open a new or existing project. The term
‘project’ refers to a set of related sites, at each of which a
penetration test has been carried out and which will be analysed
together. In normal use, a project will be a single road or a
shorter length of uniform construction.
4 Test data Input site details and penetration data for the tests within a
input project.
5 Layer Analyse the penetration data from a test to identify and
analysis determine the thicknesses of the distinct Test layers within the
pavement. Penetration data can be analysed manually or
automatically.
6 Structural Assign the Test layers to specific pavement layers and calculate
Number the Structural Number of each pavement layer.
calculation
7 Query Produce histograms of strengths and pavement layer
thicknesses along the project.
8 Sectioning Divide the project into sections which are uniform in thickness
and/or strength.
9 Design data Input road condition, structures condition, surface gravel
input thickness, crown height details, road geometry, land use, design
standard, costs and traffic details of a project.
10 Design Divide the project into sections which are uniform in a variety of
Sections characteristics.
11 Pavement Design the pavement improvement for a low volume road.
Design
12 Reporting Produce reports of the analysis and design process for printing
and/or export.
1.1 The DCP
Tests using the DCP (Figure 1.1) generate data which can be analysed to produce
accurate information on in situ pavement layer thicknesses and strengths. Tests can be
carried out very rapidly and test sites can be reinstated extremely easily. When used
for design purposes DCP testing should be carried out when the road pavement is
considered to be in wettest condition. A typical DCP test team of 3 people may be able
to carry out 20 tests in a day at a spacing of between 50 and 500 metres. The DCP can
give information of sufficient quality and quantity to allow the pavement strength to be
estimated and improvement works to be designed. Results from DCP tests can also be
used to decide the most suitable positions to excavate test pits to gather additional
information.

The DCP consists of a cone fixed to the bottom of a vertical rod. A hammer is repeatedly
lifted and dropped onto a coupling at the mid-height of the rod to deliver a standard
impact, or ‘blow’, to the cone and drive it into the pavement. A vertical scale alongside
the rod is used to measure the depth of penetration of the cone. The penetration and the
number of blows are recorded on a Test Data Form, shown inAppendix A: DCP Test
Data Form. The penetration per blow, the ‘penetration rate’, is recorded as the cone is
driven into the pavement and used to calculate the strength of the material through
which the cone is passing. A change in penetration rate indicates a change in strength
between materials, thus allowing layers to be identified and the thickness and strength of
each to be determined. These layers are then grouped together into the pavement layers
of base, sub-base and subgrade, guided by test pit or as-built records if available.

The DCP cannot penetrate some strong materials such as hot mix asphalt or cement
treated bases. These layers must be removed before the test can begin and their
strength assessed using different criteria.

The strengths of all layers can then be combined into a Structural Number for each
pavement layer and the entire pavement structure. Where tests are repeated along the
pavement, a longitudinal picture of the pavement can be produced which allows changes
in construction and condition to be identified. These changes can then be used to divide
the road into uniform sections for each of which expected lifetimes can be estimated and
improvements designed.
 Figure 1.1 DCP instrument
1.2 UK DCP 3.1
UK DCP 3.1 has two main functions: the analysis of DCP data; and the use of the DCP
results to design lengths of sealed roads used as spot improvements on low trafficked
roads. For design purposes it is important that the DCP testing be carried out when the
pavement is at its highest moisture content, and hence in its weakest condition.

The design of these sections of sealed roads is based upon research carried out on
roads with design traffic of less than 1 million equivalent standard axles in dry areas
of Zimbabwe, Botswana and Malawi. These areas have a Weinert N value of more than
2. The design function of UK DCP 3.1 should therefore not be used for roads at higher
design traffic or in other climatic regions. It should also be used with care when used in
other countries outside those in which the design charts were developed.

The design function within UK DCP 3.1 compares the strength and thickness of the
existing pavement with a pavement shown in a design catalogue and, using layers of the
existing pavement as layers in the proposed pavement. If material in the existing
pavement is to be used as a base or sub-base in the proposed new pavement, it is
recommended that soaked CBR tests are carried out to accurately determine its strength.

DCP data can be collected from flexible pavements constructed with unbound materials.
Very little difficulty is experienced with the penetration of granular pavement layers or
lightly stabilised material. It is, however, often not possible to penetrate coarse granular
materials, material stabilised with a high percentage of cement or thick layers of
bituminous material. In such cases it is necessary to cut a core or drill a hole through the
impenetrable layer and collect DCP penetration data in the underlying material. Because
penetration data cannot be recorded for a cored or drilled layer, it is necessary to
estimate and manually input into UK DCP 3.1 the strength coefficient for the layer.

UK DCP 3.1 cannot analyse penetration data which includes two drilled layers below the
surface. If it proves necessary to drill twice, it is recommended that a test is repeated or
that the test result be analysed manually.

Thin bituminous layers, such as a surface dressing, can be penetrated by the DCP,
although the data is not used to calculate the strength of such layers, and therefore the
strength coefficient of these layers must also be estimated and manually input.

UK DCP 3.1 is not intended to replace normal engineering judgment. It is intended for
users who already have a thorough understanding of DCP analysis and pavement
design. The user must be aware of the limitations of this program as described here and,
most importantly, must understand that poor data will lead to incorrect results.

The DCP instrument with an extension rod of 400 mm can be used to a depth of 1200
mm. Although the instrument can be extended beyond this depth, with additional
extension rods or an extension road longer than 400 mm, it is not recommended that this
is done as friction between the rod and the soil can give unreliable data. Indeed, if the
rod cannot be rotated by hand during a penetration test, it is probable that friction is too
high, in which case the test should be repeated. UK DCP 3.1 accepts penetration data to
a maximum depth of 1500 mm.

UK DCP 3.1 cannot produce designs when no DCP data is available, although it can be
used to estimate the cost of simply providing a layer of gravel.

UK DCP 3.1 was written in Visual Basic and uses a Microsoft Access database to store
the data, although it is not necessary for Microsoft Access itself to be installed on the
computer. UK DCP 3.1 will run on Windows 98, NT, 2000 and XP operating systems
and ideally requires a computer with a minimum specification of 400 MHz, 64 MB of
memory and 45 MB of free disk space, although it should still run successfully, albeit
slightly more slowly, on a computer of lower specification.
UK DCP 3.1 replaces version 2.2 which was released by TRL in May 2004, the main
change being the addition of the design function for low volume sealed roads.
Although UK DCP 3.1 cannot open files which were created using version 2.2, a merge
function has been provided which allows files created using version 2.2 to be merged
into version 3.1 and for analysis and design to continue. UK DCP 3.1 is available free of
charge to all who wish to use it.

No warranty can be given on the validity of results and the ultimate responsibility for
acceptance and subsequent use of any results lies solely with the user. TRL Limited
cannot accept any liability for any error or omission.
 Box 1.1 Key points to know before using UK DCP 3.1

Context sensitive help is available at all stages. This manual can also be displayed and printed
through the Help menu at the top of the main window.

Data, analysis and results do not have to be saved manually. Whenever a box is closed, its
contents are automatically saved.

Only one set of penetration tests, a ‘project’, can be opened at any one time, but many of those
tests can be examined simultaneously and compared.

When a number of windows and boxes are open, they can be selected for display using the
Window menu at the top of the main window.

In this manual all software images have been taken from two projects, Crowthorne Road project
illustrating the DCP analysis and Bracknell Road project illustrating the design.
2 Installation
2.1 Obtaining UK DCP 3.1
UK DCP 3.1 can be obtained on a CD from TRL:

TRL Limited
Crowthorne House
Nine Mile Ride
Wokingham
Berkshire
RG40 3GA
United Kingdom

Tel: + 44 (0) 1344 770187

Fax: +44 (0) 1344 770356
Email: [email protected]
Web: www.trl.co.uk

Alternatively, UK DCP 3.1 is available as a download from the Transport Links website.
The address of this website is www.transport-links.org/ukdcp

2.2 Installing UK DCP 3.1

UK DCP 3.1 can read files created using earlier versions of the software, using the
Merge function. All earlier versions of UK DCP should therefore be uninstalled before UK
DCP 3.1 is installed.

2.2.1 Installation from CD

This procedure will install UK DCP 3.1, all necessary third party software and help files
onto the user’s computer. For computers with Windows 2000 or NT, follow steps 1 to 3
below. For computers with Windows 98 follow steps 1 to 5.

1. Insert the CD. The installation will begin automatically.

2. When prompted, select the directory in which UK DCP 3.1 will be installed. By
default, ‘C:\Program Files\ukdcp’ is selected.
3. When the setup program is complete, a new item, ‘ukdcp 3.1’, will be added to the
Start/Programs menu.
4. Open the UK DCP 3.1 folder on the CD and double-click the file named
‘MDAC_TYP.exe’.
5. When this setup program is complete, reboot the computer.

2.2.2 Installation from Transport Links website

The procedure to download all relevant files and install UK DCP 3.1, all necessary third
party software and help files onto the user’s computer from the Transport Links website
is very simple. Click on UKDCP Installer. Downloading and installation will take place
automatically. For computers with Windows 98, it is then necessary to click
on ‘MDAC_TYP.exe’, wait for the setup programme to finish and reboot the computer.
2.3 Uninstalling UK DCP 3.1
This procedure will uninstall UK DCP 3.1 from the user’s computer. It may vary slightly
depending upon which Windows operating system is installed on the computer.

1. Select Settings from the Start menu.

2. Select Control Panel.
3. Double-click Add or Remove Programs.
4. Highlight the version of ukdcp to be removed.
5. Click Change/Remove.
6. This will not completely delete all files. When uninstallation is complete, open
Windows Explorer and then navigate to the folder in which UK DCP 3.1 was
installed. Delete the folder and its contents. If the warning “Renaming, moving or
deleting ‘ukdcp’ could make some programs not work. Are you sure that you
want to do this?” is generated, click Yes and continue with the deletion.
3 Start up
This chapter describes how to run UK DCP 3.1 and introduces the Project Manager.
3.1 Run UK DCP 3.1
UK DCP 3.1 can be run by either clicking a desktop icon or through the Programs menu
on the Start button. After a brief Flash screen (Figure 3.1), the Main window will open
with a Welcome box (Figure 3.2). The Welcome box allows a new or existing project to
be opened and also contains a list of the most recently used projects. The same options
are available in the File menu at the top of the main window.

Figure 3.1 Flash Screen

 Figure 3.2 Welcome box

3.1.1 Start a new project

Click New Project in the Welcome box or in the File menu at the top of the main window.
This will generate a Save New Project As box. Give a name to the new project, select a
folder in which to save it and click Save. The project will be automatically given a .ukdcp
file extension and saved in the selected folder. An empty Project Manager box
(Figure 3.3) will open for the new project with its name at the top. Since only one project
can be open within UK DCP 3.1 at any time, if a project is currently open and a new
project is named and saved, a message will be generated seeking confirmation that the
current project should be closed. If Yes is clicked, the current project will be closed and a
new project opened.
 Figure 3.3 Project Manager (without test data)

3.1.2 Open an existing project

Click Open Existing Project in the Welcome box or Open Project in the File menu at the
top of the main window. This will generate an Open Existing Project box in which the file
of the required project can be found and selected. Highlight the file and click Open. A
Project Manager filled with the existing data and analysis will open (Figure 3.4) shows a
Project Manager of a project whose DCP data has been fully analysed). Alternatively,
double-click on the required file in the Recent Files list in the Welcome box or in the File
menu and the Project Manager will open. Since only one project can be open within UK
DCP 3.1 at any time, if a project is currently open and an existing project is selected, a
message will be generated seeking confirmation that the current project should be
closed. If Yes is clicked, the current project will be closed and the selected project
opened.

Figure 3.4 Project Manager (with test data and completed analysis)

3.1.3 Closing a project and exiting UK DCP 3.1.

Only one project can be run by UK DCP 3.1 at any time. To close a project,
click Close in the Project Manager. A box will be generated seeking confirmation.
Click Yes to close the project. To exit UK DCP 3.1, click Exit in the File menu at the top
of the main window. A box will be generated seeking confirmation. Click Yes to exit.

3.2 Project Manager

The Project Manager has two panels: Test Status and Design Status. The Test Status
panel is used to analyse DCP data, including penetration data input, layer analysis and
strength calculation. The Design Status panel is used to design low volume sealed roads,
including survey and cost data input, design section analysis and design production.
Both panels are described below.

There are two buttons in the Project Manager common to the analysis and the design
functions.

Help Open this manual on the screen at the appropriate section.

Close Close the project. UK DCP 3.1 remains open so that another project can be opened
and analysed. A warning message is generated. Click Yes to continue.
 3.2.1 Test Status

The Test Status panel is used to analyse DCP data, including penetration data input,
layer analysis and strength calculation. Each row in the table in the Test Status panel
(shown completed in Figure 3.4) represents one penetration test and shows the
progress that has been made in analysing that data. The table has five columns.

Test number Tests are automatically numbered in chainage order from 1 upwards. If more
than one test is carried out at the same chainage, they are ordered according
to their location (carriageway; shoulder; verge; lay-by / other –
see 4.2 below). If more than one test is carried out at the same chainage in
the carriageway, they are ordered according to their lane number and offset. If
more than one test is carried out at the same chainage off the carriageway,
they are ordered according to their offset. There is no limit to the number of
tests that can be entered in a single project. If a test is added out of sequence
or deleted, the numbering is automatically corrected.
Chainage The chainage at which the test was carried out, measured in kilometres.
(km)
Analysis The date when the test data was analysed to identify layers. The cell is blank
if the data has not yet been analysed.
SN The date when the Structural Numbers of the pavement layers were
calculation calculated. The cell is blank if these have not yet been calculated.
Sectioning The date when DCP Sections were determined for the project. The cell is
blank if the project has not yet been sectioned.

There are nine buttons in the Test Status panel associated with DCP data input and
analysis. Warning messages are generated in response to Delete and Reset. In each
case, click Yes to continue with the operation.

Set-Up Record, review or edit information about how a selected test was carried
out, analysed and displayed. This button is inactive if tests are being
reviewed, edited or analysed.
Add Input data from a new test into the Test Status table.
Delete Delete a selected test from the Test Status table. This button is inactive if
tests are being reviewed, edited or analysed.
Reset Remove the layer analysis, Structural Number calculation and DCP
Sections from all tests in the project.
Data Review or edit the details of a selected test.
Analyse Identify layers from the data of a selected test.
Calculate SN Calculate the Structural Numbers of the pavement of a selected test. This
button is inactive if layers have not yet been identified from the test data.
Query Graphically present the strengths and layer thicknesses along the length of
an entire project. This button is inactive unless Structural Numbers have
been calculated for six or more tests in the project.
Section Divide a project into DCP Sections according to a selection of strength and
layer thickness parameters. This button is inactive unless Structural
Numbers have been calculated for six or more tests in the project.
 3.2.2 Design Status

The Design Status panel is used to design low volume sealed roads, including survey
and cost data input, division into Design Sections and design production. Each row in
the table in the Design Status panel (shown completed in Figure 3.5) represents the
survey data from a single Data Sheet and shows the progress that has been made in
producing the design. The use of the Design Status panel and the design process are
described in Chapters 9 to 11.

Figure 3.5 Project Manager (with test data and completed design)
The Design Status table has five columns.

Data Sheet Data Sheets are automatically numbered in chainage order from 1 upwards. If
a Data Sheet is added out of sequence or deleted, the numbering is
automatically corrected.
From (km) The start chainage of the Data Sheet in kilometres.
To (km) The end chainage of the Data Sheet in kilometres.
Design The date when Design Sections were determined for the project. The cell is
Sections blank if these have not yet been determined.
Pavement The date when the pavement design was produced. The cell is blank if this has
Design not yet been done.

There are six buttons in the Design Status panel associated with pavement design.

Add Survey Enter data from a new survey Data Sheet into the Design Status table.
Data
Delete Delete a selected Survey Data Sheet from the Design Status table.
Survey Data
Design & Enter or edit Design Standards, Traffic and Costs data for the entire project.
Costs Data
Survey Data Review or edit the details of a selected data sheet.

Design Divide the project into design sections. This button is inactive if DCP Sections
Sections have not yet been determined or if the entered survey data does not cover the
entire project length.
Pavement Produce a design. This button is inactive if Design Sections have not yet been
Design identified.
4 Test data input
4.1 Introduction
This chapter describes how to input data for the penetration tests within a project.

For each penetration test, the following are required.

• Site details – information about the site where the test was carried out.
• Upper layers – information about the upper layers which cannot be analysed by a
DCP.
• Penetration data – data which records the number of blows of the DCP and the
depth of penetration
• Set-Up – information about how each test is carried out, analysed and displayed.

To input data from a new test, click Add in the Project Manager. To review or edit data
from a test which has already been inputted, highlight the test in the Project Manager
and click Data. Both actions will bring up the Test Details box (Figure 4.1) for that test. At
any point during data input, Cancel can be clicked to cancel the entered information.
This will generate a box asking if the changes that have been made should be saved.
Clicking No will cancel any changes that were made.

Data may be input using alternative methods. These are described in 4.6 below.

Figure 4.1 Test Details box

4.2 Site details

The top panel of the Test Details box is titled Site details and records information about
the site where the test was carried out. The panel has a number of fields. These are
mandatory (M), optional (O) or filled in automatically (A).
Test A This field is filled in automatically according to the chainage and
number location of the test, as described in 3.2 above.
Chainage M It is important that all tests within a project use the same chainage
(km) datum.
Location M Although penetration tests are normally carried out in the carriageway
of a road, it may be necessary to measure the strength of the
construction off the carriageway line. When results are analysed, it
will be necessary to distinguish between these locations so that, for
example, carriageway improvement works are not designed using
layer strengths measured in a soft verge. Therefore, using the pull-
down menu, select the location of the test from carriageway,
shoulder, verge and lay-by / other. Carriageway is the default
location.
Lane O It may be necessary to record in which lane of a road a test was
number made. Thus this field may be required if tests are being carried out on
a road with more than one lane in each direction. Any normal local
convention can be used for numbering lanes.
Offset O This refers to the offset from a datum line along the road. It is normal
(m) to use the carriageway edge as the datum, although the centre line of
the road could be used instead.
Direction O This is the traffic direction of the lane where the tests are being
carried out. Direction does not need to be recorded on a single lane
road. The field is limited to 25 characters.
Zero M The zero error is the reading on the vertical scale of the DCP when
error the cone is sitting on a flat surface and is a result of the way in which
(mm) the instrument is manufactured and assembled. The zero error is
measured by placing the DCP on a smooth, level, hard surface,
lowering the cone to the surface and reading the scale. This should
be done whenever the DCP is prepared for use and, ideally, before
every new series of tests. The zero error should be entered for every
test.
Test date M This defaults to today’s date if this is the first test in a project.
Otherwise the date entered for the previous test will appear. In both
cases, the default date can be changed using the pull down calendar.
Remarks O These can be either typed or copied and pasted as required. The
field is limited to 60 characters.

If the details of a test have already been entered, click Edit to be able to make changes,
although if the data has already been analysed, a box will be generated warning that
editing the data will delete this analysis.
4.3 Upper layers
UK DCP 3.1 uses penetration data to calculate the strength of most pavement layers.
However, some layers are too thin, strong or impenetrable for relationships between
penetration rate and strength to be derived. In this case, the strength of the layer is
assessed from the type of the layer and its condition. This applies to layer types such as:
Surface
• Thin bituminous seal
• Hot mix asphalt
• Concrete
• Other surface
Base
• Cement treated base
• Bituminous base
• Coarse granular base (such as Water Bound Macadam)

Since these layers are always found at the top of a pavement, they are referred to as
Upper Layers. Layers whose strength can be calculated from penetration data are
referred to as Test Layers.

The calculation of layer and pavement strength for Upper layers and Test layers is
explained in detail in 6.1 below.

The bottom panel of the Test Details box (Figure 4.1) is titled Upper layers. A selection
must be made and a table must be completed.

4.3.1 Layers removed

Although Upper layers such as a thin bituminous seal can be penetrated by a DCP,
some layers, such as hot mix asphalt or a cement treated base cannot be penetrated. It
is necessary to remove these layers by drilling or cutting out before the test can be
carried out. When inputting data, the number of upper layers which were removed
should be entered. UK DCP 3.1 can accept the removal of 0, 1 or 2 layers. If more than
two have been removed, it is necessary to group them into two or fewer removed layers.
Figure 4.2 illustrates the differences between Upper layers, Test layers and removed
layers for a variety of pavement constructions.
Unpaved
Upper Layers
Test Layers

Thin Bituminous Seal

HMA
One layer removed
No layers removed
HMA
Base
Two layers removed
a)
b)
c)
d)
Concrete
e)

Pavement a) is unpaved. All layers can be analysed using penetration data. In this respect there
are no Upper layers, although in subsequent stages, such as the SN Calculation box,
 described in 6.2 below, and the Penetration Data Report, described in 12.2 below,
Unpaved will be recorded as an Upper layer so that the user is reminded of the surface
type.
Pavement b) has a thin bituminous seal over a granular base. The thin seal cannot be analysed
using penetration data and is therefore an Upper layer. Since the material can be
penetrated by a DCP cone, it is not necessary to remove the layer. Therefore for this test
there is one Upper layer but it is not removed.
Pavement c) has an HMA surface over a granular base. The HMA cannot be analysed using
penetration data and is therefore an Upper layer. The material cannot be penetrated by a
DCP cone and so must be removed. Therefore for this test, there is one Upper layer and
it is removed.
Pavement d) has a concrete surface over a granular base. As for pavement c), the concrete is an
impenetrable Upper layer and must be removed. However, rigid pavements are not
analysed using Structural Numbers and therefore, although UK DCP 3.1 calculates the
Structural Numbers, only the strengths of the individual Test layers can be used.
Pavement e) has an HMA surface over a base such as water bound macadam. Both layers are
impenetrable. Therefore for this test, there are two Upper layers and both are removed.
Figure 4.2 Illustration of Upper layers, Test layers and Removed layers

4.3.2 Upper layer details

For each Upper layer, the following information must be entered into the table.

Layer This will be prompted according to the number of layers which have been
removed. If 0 or 1 Upper layers have been removed, only one layer will be prompted
and will be defined as Surface. If two Upper layers have been removed, two layers
will be prompted. The first will be defined as Surface and the second as Base.
Type Options will be offered from the list in 4.3 according to whether the layer is a surface
or a base and whether or not the layer has been removed. If no Upper layers have
been removed, Unpaved will also be offered as an option. Gravel and earth surfaces
can be analysed using penetration data and so are not technically Upper layers, but
will be recorded as such so that the surface type will be listed when reports are
generated. If the layer is Unpaved, the final three columns are automatically left grey
and inactive since the layer will be analysed using penetration data rather than
condition. If the layer is concrete, the final two columns are automatically left grey
and inactive since rigid pavements are not analysed using Structural Numbers.
Surface In unpaved roads, the moisture content of the surface can influence the penetration
moisture rate. A dry surface will provide more resistance than a wet surface. An adjustment to
the penetration rate based on the surface moisture content is therefore necessary. If
the surface type is unpaved, default surface moisture of wet will be automatically
entered. A click on the cell will offer 5 different options: wet; moderate; dry; very dry;
and unknown. If the surface type is other than unpaved, the cell is grey and inactive.
Thickness Thicker layers contribute more strength to the pavement. UK DCP 3.1 will generate a
(mm) prompt if the value is too high or low for that type of layer. If the layer is a thin
bituminous seal, a default thickness of 20 mm will be automatically
entered. Box 4.1 provides guidance on how to record the removal of very thick Upper
layers.
Condition The observed condition of a surface layer is used to determine its strength
coefficient. If the condition is known, use the pull down menu to select a condition.
Then click in the strength coefficient box and the value will be entered
automatically. If condition is unknown, or it is already known which strength
 coefficient to use, enter a condition of ‘Unknown’ and then manually enter the
value. If there are two Upper layers, it is often difficult to assess the condition of the
base. Therefore a condition of Unknown is automatically generated for the base and
the strength coefficient must be entered manually.
Strength The strength coefficient is required to calculate the contribution of the layer to the
coefficient strength or Structural Number of the pavement. It can be entered manually or
generated automatically from the condition of the layer. If it is entered manually, UK
DCP 3.1 checks that it is within a realistic range for the layer type selected.

Box 4.1 Recording the removal of very thick Upper layers

UK DCP 3.1 can be used to analyse granular layers underneath thin or thick bituminous surfacing.
The maximum allowable thickness of HMA or bituminous layer is 350 mm since this is a normal
upper limit for this material type. However, if a greater thickness of asphalt is removed before the
DCP can be used, it is recommended that it is recorded in two layers; a surface layer of HMA with
its observed condition and automatically generated strength coefficient followed by a base layer
of bituminous material with unknown condition and a strength coefficient manually entered to be
equal to that of the surface layer. The maximum total thickness of the removed asphalt is
therefore 700 mm which should be sufficient for all roads.

There are five buttons below the Upper Layer panel.

Help Open this manual on the screen at the appropriate section.

Penetration Open a Penetration Data box so that test data can be entered.
Data Clicking this button also checks that all data entered into the
Test Details box is valid. Any invalid entries must be corrected
before the Penetration Data box can be opened.
Cancel Close the box and return to the Project Manager without saving
the changes that have been made since the box was created or
opened for editing. A box is generated seeking confirmation that
the changes should be saved.
Edit Visible if Edit the data in the box. If the current data has already been
data has used to identify layers, a box will be generated warning that
already been editing the data will delete this analysis.
entered and
Close saved Return to the Project Manager without making any edits.
4.4 Penetration data
After completing the Test Details box with Site details and Upper layer information,
click Penetration Data to open an empty Penetration Data box. This box has two panels.

Figure 4.3 Penetration Data box (with test data)

4.4.1 Site details summary

This panel provides a summary of the site details which have already been entered.
These details cannot be edited.

4.4.2 Penetration data

During a DCP test, the cone is driven into the pavement under repeated blows. The
record from a test consists of a number of test points. At each test point the number of
blows since the last test point is recorded and the total penetration of the cone is
measured.

It is recommended that the penetration of the cone should be measured at increments of

about 10 mm. However, it is usually easier to measure penetration after a set number of
blows. It is therefore necessary to change the number of blows between measurements
according to the strength of the layer being penetrated. For good quality granular bases,
measurements every 5 or 10 blows are normally sufficient, but for weaker sub-bases
and subgrades, measurements every 1 or 2 blows may be required. There is no
disadvantage in taking too many readings but if too few are taken, there is a danger that
weak spots will be missed and layer boundaries will be difficult to identify.
This data is entered into the table in this panel. Each row in the table represents one test
point. The table has four columns.

Point The number of each test point. If a point is inserted or deleted, the numbering is
number automatically corrected. A maximum of 250 test points can be entered for each
DCP test. If more than 250 have been recorded, it is likely that the cone hit an
impenetrable object such as a stone, in which case the data is of no use.
Blows The number of blows given to the cone to drive it from the previous point to the
current point. The number of blows at the first test point is automatically set at
zero. A maximum of 25 blows are permitted between each test point. If more
blows are given, changes in depth are likely to be too high for useful results to be
calculated.
Penetration The depth at the current point, as read off the DCP scale. The depth of the first
depth (mm) test point, the ‘initial reading’, is recorded before any blows have been given.
Since the zero error (see above) is measured when the DCP is placed on a
smooth and level surface, it is impossible for the initial reading to be less than the
zero error. The initial reading also includes the thickness of all removed layers. It
will not be accepted if it is less than the sum of the zero error and the thicknesses
of the removed layers as if so, it is likely to be an error. Note that in Figure 4.3 the
initial reading (78) is greater than the sum of the zero error (33) and the thickness
of the removed layer (40). A maximum penetration depth of 1500 mm is allowed. If
the cone has penetrated further than this, it is likely that friction along the rod is
significantly reducing the penetration rate of the cone, in which case the data is
unreliable and should not be used.
Comments Comments are entered automatically if an impenetrable layer was drilled or if an
extension rod was used (see below).

Box 4.2 Calculating adjusted penetration data

In order to analyse a penetration test, two corrections to the recorded depths are necessary.
• The zero error is subtracted from all depths.
• The length of an extension rod where used, is added to the depths of all test points recorded
after the rod was fitted.
UK DCP 3.1 makes these corrections automatically. The corrected data is referred to as ‘adjusted
data’.

To the right of the table are three buttons. These are used when entering or deleting
penetration data.

Insert Insert a test point into the data. Highlight the row below which the new test is required
and click Insert. Then enter the data from the new test point into the empty row.
Delete Delete a test point. Highlight the test point to be deleted and click Delete. The first test
point cannot be deleted.
Paste This button is used to transfer the penetration data of one test from a spreadsheet into
the panel, for example if the data was entered on site into a palm top or other device.
The data should be entered into the spreadsheet in two columns: incremental blows
and total depth (mm). Highlight and copy the two columns. Then return to UK DCP 3.1
and click Paste. It is not necessary to position the cursor in the first row before
 clicking Paste.

Penetration data can also be entered manually. On the first row type the penetration
depth before any blows have been given and then use Tab or Enter on the keyboard to
enter data in one cell after another.

There are six buttons below the table.

Help Open this manual on the screen at the appropriate section.

Test Return to the Test Details box.
Details
OK Save the data entered into the Test Details and Penetration Data
boxes and return to the Project Manager. If the test was a new
test, a further Test Details box will be generated. If the test had
been entered earlier and the data was being reviewed or edited, a
further box is not generated.
Cancel Close the box and return to the Project Manager without saving
the changes that have been made since the box was created or
opened for editing. A box is generated seeking confirmation that
the changes should be saved.
Edit Visible if Edit the penetration data. If the current data has already been
data has used to identify layers, a warning will be generated that editing the
already data will delete this analysis.
been
Close entered Return to the Project Manager without making any edits.
and saved
A comment will be entered automatically if a layer was drilled or an extension rod was
used.

Drilled layer

If an impenetrable layer has been drilled, the penetration data will include one point
recorded before the DCP was removed and another point recorded after the layer was
drilled. There will be a difference in depth between these points, although no blows will
have been recorded. If this data is pasted from a spreadsheet, a comment will
automatically appear in the Comment column stating ‘Layer Drilled’ (seeFigure 4.4). If
data is edited or a point is inserted or deleted to give a depth difference with no recorded
blows, a prompt will ask if a layer has been drilled. If Yes is clicked, the same comment
is entered; if Nois clicked, the Blows entry is deleted and should be re-entered. Drilled
layers are recorded and presented in later stages of the analysis. Only one drilled layer
can be recorded in a test. If two layers were drilled to achieve the desired penetration
depth, it is likely that the material was excessively disturbed, in which case the data is
unreliable and should not be used.

Extension rod

In normal operation, a DCP can penetrate to 800 mm. It is possible to add an extension
rod to allow the DCP to penetrate further. In this case, one point will be recorded before
the DCP was removed and another after the extended DCP was reinserted. The second
point will have a numerically lower reading than the first, and no blows will have been
recorded. If this data is pasted from a spreadsheet, a comment will automatically appear
stating ‘Extension Rod Added’ (see Figure 4.4). If data is edited or a point is inserted or
deleted to give a point with no blows and an apparent reduction in depth, a prompt will
ask if an extension rod has been added. If Yes is clicked, the same comment will appear;
if No is clicked, the Blows entry is deleted and should be re-entered. UK DCP 3.1 will
take account of the use of an extension rod, determine the length of the rod from the
difference between the two depth readings and adjust the penetration data accordingly.
Only one layer can be recorded as being due to the use of an extension rod since if
further extension rods are used, it is likely that friction along the rod is significantly
reducing the penetration rate of the cone, in which case the data is unreliable and should
not be used.
 Figure 4.4 Penetration Data box (with a drilled layer and an extension rod)

4.5 Set-Up
Set-Up is used to record information about how each test is carried out, analysed and
displayed.

It is recommended that the set-up function is used as follows. After data from the first
test of a project has been added to the Project Manager, highlight the test and click Set-
Up in the Project Manager or in the Modules menu at the top of the main window. This
will display the Set-Up Options box (Figure 4.5) for the first test. The box will contain a
number of default settings. Make any changes as required and click Update Set-Up to
save these changes and return to the Project Manager. This will assign that set-up
information to the first test. As further tests are added, they will be automatically
assigned the same set-up information. If at any stage the Set-Up information is changed
and updated, this new set-up information will be assigned to all subsequent tests. To
revert to the default set-up information, click Defaultand then Update Set-Up.
 Figure 4.5 Set-up Options box

If a number of tests have been added to the Project Manager, or even if analysis of the
data has already begun, it is possible to return to the Project Manager and change the
Set-Up information for a single test. This may be done if a chosen method of analysis or
display is unsuitable for the data. Highlight the test, click Set-Up, make the required
changes and click Update Set-Up. If analysis of that test has already been carried out, a
box is generated warning that the analysis will be deleted. It should be noted that if more
tests are added, they will retain this updated Set-Up information.

There are four buttons in the Set-Up Options box.

Help Open this manual on the screen at the appropriate section.

Default Revert to the default set-up information, as defined below.
Update Set-Up Save amended set-up information, as described above.
Cancel Close Set-Up and return to the Project Manager without saving any
changes.

The Set-Up Options box has four panels.

4.5.1 CBR Calculation

The strengths of Test layers are calculated by converting the penetration rate (mm per
blow) to a California Bearing Ratio (CBR) value and then from the CBR value to a
strength coefficient and finally to a Structural Number. A number of relationships
between penetration rate and CBR value have been derived and are given in Table 4.1.
Some of these are used when the DCP cone has an angle of 60°, others when the cone
has an angle of 30°. The relationship and the cone angle are selected on this panel. The
user’s organisation should provide guidance as to which relationship should be used or
whether a new relationship for the local conditions should be developed. The default is
the TRL relationship for a 60° cone.

The conversion of CBR value to strength coefficient and Structural Number is described
in Chapter 6.

Table 4.1 Penetration rate-CBR relationships

Cone Name of relationship Relationship

angle
(1)
60° cone TRL Log10(CBR) = 2.48 – 1.057 Log10(pen rate)

(2) -1.27
Kleyn (pen rate > 2 CBR = 410 (pen rate)
mm/blow)

Kleyn (pen rate ≤ 2

(3) 2
CBR = 66.66 (pen rate) – 330 (pen rate) + 563.33
mm/blow)

Expansive Clay Log10(CBR) = 2.315 – 0.858 Log10(pen rate)

(4)
Method
(5)
100% Planings Log10(CBR) = 1.83 – 0.95 Log10(pen rate)

50% Planings Log10(CBR) = 2.51 – 1.38 Log10(pen rate)

User-Defined Log10(CBR) = [constant] – [coefficient] Log10(pen rate)

Constant and Coefficient can be defined by the user
(6)
30° cone Smith and Pratt Log10(CBR) = 2.555 – 1.145 Log10(pen rate)

User-Defined Log10(CBR) = [constant] – [coefficient] Log10(pen rate)

Constant and Coefficient can be defined by the user
(pen rate is the penetration rate measured in millimetres per blow)

Layers can be identified either automatically by UK DCP 3.1 or manually by the user.
This panel allows the method of identification to be selected. The default is automatic
analysis.

4.5.2 CBR Adjustment Factor (for moisture)

DCP penetration data obtained from the upper layers of an unpaved road will vary
throughout the year as the moisture content of the layers changes with rainfall. For
design purposes, DCP testing should be carried out when the road pavement at its
weakest, ie, when the subgrade is at its highest moisture content. However, this may not
be possible and the DCP results from unpaved roads at other times of the year will over-
estimate the strength of the pavement materials, in particular the upper layers. Therefore
the strength of the pavement layers must be adjusted to reflect the strength of the
pavement layers when they are under a bituminous surfacing.

To adjust the strength of the pavement layers for the affect of moisture content of the
layer at the time of testing click in the “Adjust CBR for surface moisture?” box shown in
Figure 4.5. This will enter default values for the wet, moderate, dry, very dry and
unknown boxes as shown in Table 4.2. The default values of the CBR Adjustment Factor
are based upon the approximate ratio between CBR values at the moisture content
when tested to the CBR value at OMC (Mod AASHTO). To change the default value,
click the box and type in the new value. UK DCP 3.1 will accept any value between 0.30
and 1.00.

The CBR Adjustment Factors are applied to unpaved roads on the assumption that the
effect of moisture will be a maximum at the top surface and will reduce linearly to zero at
a depth of 1000 mm.

Table 4.2 CBR Adjustment Factors

Surface Ratio of field Default CBR

Moisture moisture content to Adjustment Factor
Optimum Moisture
Content
(Modified AASHTO)
Wet 1 1.00
Moderate 0.75 0.71
Dry 0.5 0.51
Very dry 0.25 0.37
Not assessed or - 0.5
difficult to assess

Table 4.3 compares the effect of four different moisture regimes (wet, moderate, dry and
very dry) on the same DCP penetration data from a pavement with 3 layers at a test
location(7). It can be seen that the influence of moisture on the top layer is more than that
of bottom layers.

Table 4.3 Effect of moisture adjustment factor on CBR of pavement layers

Layer Thickness Depth Surface Penetration CBR % Adjustment CBR %

number (mm) to the moisture rate (before factor (after
centre adjustment) adjustment)
(mm)
1 100 50 Wet 2.3 124 1.00 124
2 300 200 Wet 6.74 40 1.00 40
3 600 600 Wet 13.9 19 1.00 19
1 100 50 Moderate 2.3 124 0.71 91
2 300 200 Moderate 6.74 40 0.71 31
3 600 600 Moderate 13.9 19 0.71 17
1 100 50 Dry 2.3 124 0.51 67
2 300 200 Dry 6.74 40 0.51 24
3 600 600 Dry 13.9 19 0.51 15
1 100 50 Very Dry 2.3 124 0.35 48
2 300 200 Very Dry 6.74 40 0.35 19
3 600 600 Very Dry 13.9 19 0.35 14
 4.5.3 Analysis
Layers can be identified either automatically by UK DCP 3.1 or manually by the user.
This panel allows the method of identification to be selected. The default is automatic
analysis.

4.5.4 Display Options

When penetration data is being analysed, a graph of penetration depth against the
number of blows given to the DCP is used to identify layers of different materials and the
boundaries between them. The remaining two panels allow changes to be made to this
graph which may help in identifying layers.

Design Thickness

It is sometimes difficult to identify layers from a penetration graph and, even if layers can
be seen, it can be difficult to be sure whether the layer is part of the base, sub-base or
subgrade. If actual information on materials and layer thicknesses is available, layer
identification from penetration data can be much easier. This information can come from
records made when the pavement was being constructed or from test pits dug alongside
and within the project. Neither source of information will accurately predict the layers at
each test site, but they can provide useful guidance. If as-built or test pit information is
available, click in the As-Built Thickness Known? box and enter the recorded
thicknesses for the Surface, Base and Sub-base. These will be displayed on the
penetration graphs, as shown in, for example,Figure 5.2 and Figure 5.4. The default is to
not display as-built thicknesses.

Display

Different colours are used to indicate different elements of the penetration graph. They
can be changed if required, for example if a printer does not print a particular colour well.
The defaults are Data Point – dark green; Test Layers – dark blue; underside of Upper
Layers – bright blue; Drilled Layer – red.

After data from penetration tests has been input, the Project Manager is as shown in
Figure 4.6.
 Figure 4.6 Project Manager (showing that test data has been input)

4.6 Alternative methods for inputting data

4.6.1 Merge
The merge function allows the data and the analysis of two projects to be combined into
a single project. After opening the first file, click Merge in the File menu at the top of
the main window and select the second file. UK DCP 3.1 will then combine the data and
analysis from the second project into the first project. Any sectioning analysis in either
project will be deleted, any test which is at the same chainage, location, lane number
and offset as a test in the first project will not be combined, any survey data (as
described in Section 9.1) in the second project which overlaps with survey data in the
first project will not be combined, and if the first project has design and costs data (as
described in Section 9.2) all design and costs data in the second project will not be
combined. UK DCP 3.1 will generate a message summarising what data and analysis
has been combined during the merge.
The merge function also allows the analysis of a project created using UK DCP 2.2 to be
continued using UK DCP 3.1. This is done as follows. Open an empty project in UK DCP
3.1, merge the project created using UK DCP 2.2 and continue the analysis. When a
project is merged into an empty project, any sectioning analysis will be retained.

4.6.2 Import
The import function allows test data, including site details, upper layer data and
penetration data, and from more than one test if necessary, to be imported from a
spreadsheet into UK DCP 3.1. This function facilitates the inputing of large quantities of
data by a team into a single project for analysis.

The spreadsheet can be opened by clicking New Import Worksheet in the Help menu at
the top of the main window and can then be saved and distributed as required. The
spreadsheet has eight pre-prepared columns but more can be added if necessary. The
spreadsheet also contains guidance on the required format of the data.

To import the data from a spreadsheet, click Import test data in the File menu at the top
of the main window and select the required file. The data is imported, although any test
in the import spreadsheet which is at the same chainage, location, lane number and
offset as a test already in the project will not be imported and a message stating this will
be generated.

Associated with Import is an Export function, also in the File menu in the main window,
which allows the test data from a project to be saved in a spreadsheet.
5 Layer analysis
5.1 Introduction
A typical graph of penetration depth against the cumulative number of blows given to the
DCP shows a line of varying gradient. The gradient is equal to the penetration rate of the
cone as it is driven into the pavement.

For Test layers, it is possible to derive relationships (4.5.1) between the penetration rate
and the strength of the material through which the cone is passing. The gradient of the
line can therefore be used to calculate the material strength. Changes in the gradient of
the line indicate boundaries between materials of different strengths and hence the
thicknesses of layers of different strengths.

Upper layers are often too thin, strong or impenetrable for their strength to be
determined from the penetration rate. Instead, the strength of an Upper layer is
estimated from the type of the layer and its condition, and its thickness is taken from as-
built records, test pit data or by measuring the thickness of a layer removed during the
DCP test.

This chapter describes how the thicknesses of Test layers are determined from
penetration graphs; Chapter 6 then describes how the strengths of Upper layers and
Test layers are calculated.

The penetration graph can be analysed automatically or manually according to the

selection made when defining Set-Up information (0).
5.2 Analysing Test layers
Begin layer analysis from the Project Manager. Highlight a test which has not yet been
analysed and click Analyse in the Project Manager or in the Modules menu at the top of
the main window.

This will open a Layer Boundaries box. It contains a graph of adjusted penetration depth
(data adjustment is explained in Box 4.2 Calculating adjusted penetration data
against the cumulative number of blows given to the DCP. All test points are plotted
onto the graph. The gradient of the line of test points is the penetration rate of the cone
and hence the strength of the material at that depth. A shallow gradient indicates strong
material, a steep gradient indicates weak material and changes in gradient indicate a
layer boundary between Test layers of different strengths.

The other information displayed on the graph depends upon whether layer analysis will
be carried out automatically or manually. These two alternatives are compared
in Box 5.1 and described in detail below.
 Box 5.1 Should penetration data be analysed automatically or manually?

UK DCP 3.1 allows penetration plots to be analysed automatically or manually. Each method has
advantages and disadvantages.

Automatic analysis

Advantages
Quicker than manual analysis.

Disadvantages
The user has no control over where layer boundaries are located.
Assigns CBR to a drilled layer.

Summary
Automatically identified layer boundaries of a complex plot may be located inappropriately.
Automatic analysis is therefore recommended when the penetration plot has a simple shape.

Manual analysis

Advantages
User has more control over where layer boundaries are located.
The use of gaps can improve the analysis of drilled and strong layers.

Disadvantages
Slower than automatic analysis.

Summary
Manual analysis is recommended when the penetration plot has a complex shape, the analysis of
which the user would like to have some control over. It is also recommended if an atypical item
such as a large stone slowed down the penetration or had to be drilled.

5.3 Automatic layer analysis

The automatic layer analysis procedure first calculates the penetration rate at each test
point and the average penetration rate for the entire test. For each test point it then
calculates the value of the average rate minus the rate at that point. These values are
then summed in turn starting at the first test to find the cumulative difference sum at
each point. By the nature of the calculation, this sum will be zero at the final test point. At
one point this sum will reach a maximum absolute value. The depth of the point at which
the sum reaches this maximum value is defined as the first Test layer boundary. This
procedure has a similar effect to drawing a straight line from the first point to the last
point and finding the depth of the intermediate point which is furthest from this straight
line (as shown in Figure 5.1).
 Figure 5.1 How Automatic analysis works

The procedure is then repeated for the test points above this first boundary and for the
points below it. In this way the second and third boundaries can be identified. The
procedure is repeated until the points between any two boundaries do not exhibit
sufficient fluctuation from a straight line to allow a further boundary to be identified with
any degree of confidence. An automatically analysed penetration plot is shown in Figure
5.2.
 Figure 5.2 Layer boundaries box using Automatic analysis

To illustrate automatic layer analysis, Table 5.1 contains penetration data to a depth of
225 mm. The data is analysed in the table to show how a change from strong to weaker
material can be identified at a depth of 75 mm. Figure 5.1 contains a graph of the data in
this table. It shows how the point with the greatest cumulative difference sum is also the
point which lies furthest from a straight line from the first point to the last point. The first
Test layer boundary has been automatically generated and is shown on the graph.

Table 5.1 Example of penetration data and cumulative sum analysis

Point Blows Adjusted pen Pen rate Av. Pen Av. Pen rate – Cumulative
depth (mm/blow) rate pen rate difference sum
1 0 0
2 5 14 2.8 4.5 1.7 1.7
3 5 29 3.0 4.5 1.5 3.2
4 5 46 3.4 4.5 1.1 4.3
5 5 62 3.2 4.5 1.3 5.6
6 5 75 2.6 4.5 1.9 7.5 ← maximum value
7 5 107 6.4 4.5 -1.9 5.6
8 5 133 5.2 4.5 -0.7 4.9
9 5 164 6.2 4.5 -1.7 3.2
10 5 196 6.4 4.5 -1.9 1.3
11 5 225 5.8 4.5 -1.3 0

Five points should be noted when using automatic layer analysis.

• Boundaries can be identified only at depths corresponding to actual test points.
 • The strength of a layer is calculated by the gradient of a straight line from the
intersection of its upper boundary with the line of test points to the intersection of
its lower boundary with the line of test points.
• There are three situations where minor corrections are made to the analysis in
order to prevent inaccurate calculation of the thickness of the first Test layer.
These are described in Box 5.2.
• Box 5.3 Analysis of a drilled layer below recommends when automatic layer
analysis should be used for penetration data containing drilled layers.
• Box 5.4 Analysis of a very strong but penetrable layer below recommends when
automatic layer analysis should be used for penetration data containing strong
but penetrable layers.

The following items are displayed in the Layer Boundaries box if automatic layer analysis
has been selected. The colours of some of the items depend upon selection made when
defining Set-Up information.

Maximum When the box is opened, a message will be generated giving the maximum
layers number of Test layers which can be identified from the data using the above
message procedure. Click OK to delete this message. If 10 Test layers can be identified
(the limit set by UK DCP 3.1), a message is not generated.
First layer The first layer boundary identified using the above procedure is shown with a
boundary horizontal line.
Number of The number in this box is the number of Test layers currently being shown.
Layers field Clicking the Up and Down arrows increases and decreases this number and
adds or removes layer boundaries from the graph. The number can be
increased up to the number which was shown in the Maximum layers
message. Unless a drilled layer is present, this number is initially 2.
Upper layer A dashed line indicates the underside of the Upper Layers.
line
Drilled If a layer has been drilled, it will be marked on the graph with two horizontal
layers dotted lines, but the first automatic layer will not be shown. The Number of
Layers field will therefore initially show 3, the portion above the drilled layer,
the drilled layer itself and the portion below. An automatically analysed drilled
layer is shown inFigure 5.12 below.
As-built If as-built or test pit information was entered into the Set-Up of the test (4.5.4),
layers these layers are shown, separated by dotted lines.
Show A check box is provided to allow gridlines to be displayed or removed.
Gridlines
Adjusted Click this button to generate a box showing the penetration data (Figure 6.3).
Data button This data has been adjusted as described in Box 4.2 Calculating adjusted
penetration data
. The box also includes the average penetration rate between successive
points. This box is generated to guide the identification of Test layers and
cannot be edited.
Help button This button opens this manual on the screen at the appropriate section.
OK button This is used to accept and save the layer boundaries and return to the Project
Manager.
Cancel This is used to cancel the analysis. If changes have been made to the
button analysis, a box is generated which offers an opportunity to save the changes.
Layer When the cursor is placed over the graph, a small box is generated. This box
descriptions gives the number of the Test layer, its thickness (mm) and the average
penetration rate for the layer.
Point When the cursor is placed over a test point, a small box is generated. This box
descriptions gives the cumulative blows and the adjusted depth of the point.

Add or remove layer boundaries from the graph until satisfied that the data has been
adequately analysed. In Figure 5.2 five Test layers appear sufficient. Adding further
layers does not increase the precision of the analysis. Note that identified Test layers
matching previously defined as-built layers is a useful check on the analysis.

Click OK to save the analysis and return to the Project Manager. It will be seen (Figure
5.3) that today’s date will be in the Analysis column for that test.
 Figure 5.3 Project Manager (showing that test data has been analysed)

It is possible to examine the graph and possibly edit the analysis of a test for which
layers have already been identified. Highlight the test in the Project Manager and
click Analyse. The Layer Boundaries box will be opened and the penetration graph will
be shown, but Edit must be clicked before changes can be made to the number of Test
layers. When Edit is clicked, if SN Calculations have already been carried out, a warning
appears that SN Calculation data, and possibly Sectioning data will be deleted. If it is not
necessary to edit the analysis, click Close to return to the Project Manager.

Box 5.2 Corrected analysis of deep surface texture and disturbed soil
There are three situations where automatic layer analysis makes assumptions about the adjusted
penetration data and makes minor corrections in order to prevent the inaccurate calculation of the
thickness of the first Test layer (as explained in Box 4.2). These three situations are described
below. In each case, it is important to understand how a simple automatic routine without these
assumptions or a manual interpretation of the penetration graph would produce the inaccuracy.

1. If an earth, gravel or thin bituminous surface has a deep texture or surface voids, the initial
position of the DCP cone may be slightly below the actual road surface. UK DCP 3.1 assumes
the road surface to be at an adjusted penetration of zero and calculates the layer strength from
the penetration rate after penetration began.

2. If base material sticks to an impenetrable layer as it is removed, as is often the case with HMA
and a granular base, the initial position of the DCP cone may be below the actual top surface of
the base. UK DCP 3.1 assumes the top surface of the base layer to be at an adjusted penetration
equal to the measured thickness of the removed layer and calculates the layer strength from the
penetration rate after penetration began.

3. If base material is loosened by an impenetrable layer as it is removed, the first one or two
blows to the DCP will penetrate much more quickly through the loose material than later blows in
the unloosened material. UK DCP 3.1 ignores the penetration rate in the loose material, assumes
the top surface of the base layer to be at an adjusted penetration equal to the measured
thickness of the removed layer and calculates the layer strength from the penetration rate below
the loose material.

As a result of point 3, it is recommended that after a layer has been removed, the first two
penetration readings are taken after only one or two blows.

5.4 Manual layer analysis

Test layer boundaries are identified as follows. UK DCP 3.1 allows a number of straight
lines to be drawn along approximately straight portions of the graph. Test layer
boundaries will be generated at each point where these lines intersect. A manually
analysed penetration plot is shown in Figure 5.4.
 Figure 5.4 Layer Boundaries box using Manual layer analysis

Four points should be noted when using manual layer analysis.

• Boundaries can be identified at any depth at which lines intersect.
• The strength of a layer is calculated by the gradient of the straight line drawn
onto the plot. Various techniques allow the user more control over layer thickness
than is possible with automatic layer analysis. These are described below.
• Box 5.3 Analysis of a drilled layer below recommends when manual layer
analysis should be used for penetration data containing drilled layers.
• Box 5.4 Analysis of a very strong but penetrable layer below recommends when
manual layer analysis should be used for penetration data containing strong but
penetrable layers.

The following items are displayed in the Layer Boundaries box if manual layer analysis
has been selected. The colours of some of the items depend upon selection made when
defining Set-Up information.

Number of The number in this box is the number of Test layers identified. As a new
Layers field interesting straight line is drawn, the number in this field increases by one.
Upper layer A dashed line indicates the underside of the Upper Layers.
line
Drilled If a layer has been drilled, it will be marked on the graph with two horizontal
layers dotted lines.
As-built If as-built or test pit information was entered into the Set-Up of the test (4.5.4),
layers these layers are shown, separated by dotted lines.
Show A check box is provided to allow gridlines to be displayed or removed.
Gridlines
Zoom box A pull down menu allows the graph to be magnified so that lines can be more
accurately placed.
Adjusted Click this button to generate a box showing the penetration data (Figure 6.3).
Data button This data has been adjusted as described in Box 4.2 Calculating adjusted
penetration data
The box also includes the average penetration rate between successive
points. This box is generated to guide the identification of Test layers and
cannot be edited.
Add Line Click this button to draw a straight line. Then click and hold at one end of the
button intended line. Drag the cursor to the end of the intended line and release.
Double click on a line to delete it.
Display Click this button to generate layer boundaries where the straight lines
Layers intersect. After layer boundaries have been generated, an additional straight
button line can be added, allowing the user to be satisfied with the analysis of a
portion of the graph before completing the analysis. As the new line is drawn,
the previously generated layer boundaries disappear.
Remove Click this button to remove all straight lines and layer boundaries.
Layers
button
Help button This button opens this manual on the screen at the appropriate section.
OK button This is used to accept and save the layer boundaries and return to the Project
Manager.
Cancel This is used to cancel the analysis. If changes have been made to the
button analysis, a box is generated which offers an opportunity to save the changes.
Layer When the cursor is placed over the graph, a small box is generated. This box
descriptions gives the number of the Test layer, its thickness (mm) and the average
penetration rate for the layer.
Point When the cursor is placed over a test point, a small box is generated. This box
descriptions gives the cumulative blows and the adjusted depth of the point.
Study the graph and model it as a series of straight lines. Click Add Line and draw lines
along each reasonably straight portion. These lines should form a series of
interconnecting lines, although gaps may be deliberately left in certain situations.
Click Display Layers to generate the Test layer boundaries. In Figure 5.4 five straight
lines seem to represent the graph sufficiently accurately, although an important check is
described below in
Box 6.1 The importance of checking the layer analysis against CBR Chart. Note the
closeness of the Test layers to the previously defined as-built layers and the similarity of
the result to that derived using automatic analysis (Figure 5.2).

Click OK to save the analysis and return to the Project Manager. It will be seen (Figure
5.5) that today’s date will be in the Analysis column for that test.
 Figure 5.5 Project Manager (showing that test data has been analysed)

To edit the analysis of a test for which layers have already been identified, highlight the
test in the Project Manager and click Analyse. The Layer Boundaries box will be opened
and the penetration graph will be shown, but Edit must be clicked before changes can be
made to the number of Test layers. When Edit is clicked, if SN Calculations have already
been carried out, a warning appears that SN Calculation data, and possibly Sectioning
data will be deleted. If it is not necessary to edit the analysis, click Close to return to the
Project Manager.
In most cases, manual layer identification is straightforward. However, there are a
number of hints and techniques which should be noted. They are illustrated in the figures
below.

Double Figure 5.6 If a graph has a sudden change of gradient, the boundary can
intersections be identified using only two straight lines. However, if a graph
has a gradual change of gradient, three or more short lines may
be required. If these lines are drawn too long, it may occur that
one line has two or more intersections. In this case, boundaries
may be generated at unintended intersections. It is
recommended that double intersections are avoided.
Negative Figure 5.7 Since penetration graphs always have a gradient from top left to
gradients bottom right, a line in the opposite direction will not be
accepted.
Intersecting Figure 5.8 A line which does not cross the line of test points will not be
the line of accepted.
points
Moving a Figure 5.9 If a line does not exactly match a portion of the graph, it can be
line Figure 5.10 moved laterally by clicking, holding and dragging.

Overlapping Figure 5.11 If a line overlaps but does not intersect another line, a warning
lines message is generated and the line is deleted.
Gaps Figure 5.12 The use of non-intersecting lines can assist in the analysis of
between Figure 5.13 drilled and very strong layers. Their use is described in detail
lines in 5.5 below.
Figure 5.14
Figure 5.15
 Figure 5.6 Double intersections

Three straight lines have been drawn and both true intersections have been ringed. The
lower intersection has been correctly identified, but the upper intersection has been
missed in favour of a false intersection. The lines should be removed by double-clicking
and shorter lines drawn to prevent double intersections.

Figure 5.7 Negative gradient

Lines with negative gradient will not be accepted. After clicking OK, the line will be
deleted and should be redrawn.
 Figure 5.8 Line does not intersect the line of test points

Straight lines which do not cross the line of test points will not be accepted. After
clicking OK, the line will be deleted and should be redrawn.

Figure 5.9 Line drawn parallel to its intended position

Note that if the line does not cross the line of test points, it will not be accepted.
 Figure 5.10 Line moved laterally to its intended position

The line in Figure 5.9 has been moved and layers boundaries have been generated at
the intersections.

Figure 5.11 Lines overlap but do not intersect

Lines which overlap without intersection will not be accepted. After clicking OK, the line
will be deleted and should be redrawn.

5.5 Analysis of drilled and very strong layers

If two manually drawn lines do not intersect, the boundary will be generated at a depth
midway between the two end points. Drawing non-intersecting lines can be useful in the
analysis of a drilled layer, a very strong but penetrable layer or an obstacle such as a
stone.
The following figures and boxes describe how these examples are analysed differently
under automatic and manual analysis and how the most appropriate method should be
chosen.

5.5.1 Drilled layers

Figure 5.12 Automatic analysis of a drilled layer

When analysed automatically, the drilled layer is defined as a distinct Test layer. Later,
during the calculation of Structural Numbers, a CBR value should be manually assigned
to this layer. In Figure 5.12 four Test layers have been identified, one of them the drilled
layer.

Figure 5.13 Manual analysis of a drilled layer and the use of gaps

When analysed manually, the drilled layer is not defined as a distinct Test layer. A
boundary can be identified in the middle of the drilled layer. This is done by terminating
the drawn lines at the upper and lower surfaces of the drilled layer and so generating a
boundary midway between the two end points. The strengths of the two layers are
calculated from the gradients of the drawn lines, thus eliminating the influence of the
drilled layer on the analysis. In Figure 5.13 only three Test layers have been identified,
the thickness of the drilled layer being divided equally between base and sub-base.

Box 5.3 Analysis of a drilled layer

Automatic analysis identifies a drilled layer as distinct and assigns a strength coefficient. Manual
analysis with the use of gaps can eliminate the influence of the drilled layer on the subsequent
analysis. Therefore automatic analysis should be used when, for example, a strongly stabilised
pavement layer had to be drilled, while manual analysis should be used when an isolated and
atypical item such as a large stone had to be drilled.

5.5.2 Very strong layers

 Figure 5.14 Automatic analysis of a very strong layer

When analysed automatically, the very strong but penetrable layer is likely to be defined
as a distinct Test layer. Later, during the calculation of Structural Numbers, a high
strength coefficient will be assigned to this layer. In Figure 5.14 four Test layers have
been defined, one of them the very strong layer.
 Figure 5.15 Manual analysis of a very strong layer and the use of gaps

When analysed manually, the very strong but penetrable layer does not have to be
defined as a distinct Test layer. A boundary can be identified in the middle of the strong
layer. This is done by terminating the drawn lines at the upper and lower surfaces of the
strong layer, generating a boundary midway between the two end points. The strengths
of the two layers are calculated from the gradients of the drawn lines, thus eliminating
the influence of the very strong layer on the analysis. In Figure 5.15 only three Test
layers have been identified, the thickness of the very strong layer in this case being
allocated to the sub-base.

Box 5.4 Analysis of a very strong but penetrable layer

Automatic analysis identifies a very strong but penetrable layer as distinct layers. Manual analysis
with the use of gaps can eliminate the influence of this layer on the subsequent analysis.
Therefore automatic analysis should be used when a very strong layer is known to be present
within the pavement, while manual analysis should be used when it is likely that a stone caused
an obstruction to the cone.
6 Structural Number calculation
6.1 Introduction
Assessing the strength of a pavement is difficult. Most pavements have several layers
and for each one many different characteristics can be measured: thickness, modulus,
CBR and so on. These values can be combined in many different ways. The concept of
a Structural Number (8) (SN) was developed during the AASHO Road Test research as a
single number which would indicate the strength and durability of an entire pavement
and which would be internationally recognised. The concept was developed for the
analysis of flexible pavements; rigid pavements are not analysed using Structural
Numbers.

Over time, the concept has expanded. The original term, SN, was calculated from the
imported surface, base and sub-base layers. The modified Structural Number (9) (SNC)
was then introduced to include the effect of the subgrade. However, it was realised that
because the subgrade contribution to SNC is independent of its depth, redefining
subgrade material as sub-base gives a higher SNC. Tests were carried out and the
adjusted Structural Number (10) (SNP) was developed. This adjusts the contribution of the
sub-base and subgrade according to their depth and eliminates this potential source of
error.

This chapter describes how to calculate the Structural Number of each pavement
layer. It provides the equations used to calculate SN and SNC, although those used to
calculate SNP are too extensive to be included here.

6.1.1 Upper layers

Upper layers are layers at the top of the pavement which are too thin, strong or
impenetrable for relationships between penetration rate and strength to be derived. The
contribution of an Upper layer to the Structural Number of a pavement is its strength
coefficient multiplied by its thickness. The strength coefficient is assessed from the type
of the layer and its condition, as described in 4.3.2 above.

6.1.2 Base and Sub-base Test layers

The contribution of a Base and Sub-base layer to the Structural Number of a pavement
is its strength coefficient multiplied by its thickness.

SN = Σ aidi

where: i is a summation over layers

ai is a strength coefficient for each layer
di is the thickness of each layer measured in inches

The strength coefficient of a layer can be calculated from its CBR value, which is
calculated from the penetration rate as described in 4.5.1 above.

The relationship between CBR and strength coefficient depends upon the layer and the
material. These relationships are given in Table 6.1.
Table 6.1 CBR-Strength Coefficient (a) relationships

Pavement Relationship
Layer
2 3
Base a = 0.0001 [29.14 (CBR) – 0.1977 (CBR) + 0.00045 (CBR) ]
(11)
This relationship is also used for a gravel or earth surface layer .
2 3
Cement CBR > a = 0.00016 [29.14 (CBR) – 0.1977 (CBR) + 0.00045 (CBR) ]
treated 70%
base
CBR < a = 0. Tests have shown that a cement treated base with a CBR
70% less than 70 has minimal effective strength.
2
Sub-base a = 0.184 Log10(CBR) – 0.0444 (Log10(CBR)) – 0.075

6.1.3 Subgrade Test layers

The contribution of the Subgrade to the Structural Number of a pavement is referred to
as SNG and is calculated directly from CBR without the need for an intermediate
strength coefficient. SNG is a function of the CBR of the entire subgrade, rather than any
layers into which the subgrade can be divided. A procedure to identify the layers which
have the greatest influence within the subgrade and derive the aggregate subgrade CBR
in a manner which reflects engineering judgement has therefore been devised and is
included in UK DCP 3.1.

The relationship between subgrade CBR and SNG is as follows.

SNG = 3.51 Log10(CBR) – 0.85 Log10(CBR)2 – 1.43

6.2 Calculating the Structural Number
Begin the Structural Number calculation from the Project Manager. Highlight a test for
which Structural Numbers have not yet been calculated and click Calculate SN in the
Project Manager or in the Modules menu at the top of the main window. This button is
inactive if the selected test has not yet been analysed.

This will generate an SN Calculation box (Figure 6.1). This box has three panels and five
buttons, although the third panel is not visible until the second panel has been
completed.

It is possible to view the results and possibly edit the analysis of a test for which
Structural Numbers have already been calculated. Highlight the test in the Project
Manager and click Calculate SN. The results will be shown, but Edit must be clicked
before changes can be made. When Edit is clicked, if the project has already been
sectioned, a warning appears that sectioning results will be deleted if editing continues.
 Figure 6.1 SN Calculation box (before calculating SNs)

6.2.1 Upper layers

This panel displays the Upper layers as defined in 4.3 above. For each Upper layer, the
information below is presented and cannot be edited. If the surface is gravel or earth, it
will be recorded in this panel, but since it will be analysed as a Test layer using
penetration data, its depth, thickness and strength coefficient are automatically left blank
in this panel. If the surface is concrete, the strength coefficient is automatically left blank
as rigid pavements are not analysed using Structural Numbers.

Number UK DCP 3.1 can accept a maximum of two Upper layers.

Position The uppermost Upper layer is automatically defined as Surface. If a
second Upper layer is present, it is automatically defined as Base.
Type The layer type, as described in 4.3.2.
Thickness (mm) The thickness of each layer.
Depth (mm) The depth to the underside of each layer.
Strength The determination of the strength coefficient of Upper layers was
coefficient described in4.3.2.
 6.2.2 Test layers
This panel displays the Test layers as defined in 4.3 above. For each Test layer, six
items of information are required. Four items are filled in automatically (A) and two must
be entered manually (M).

Number A Test layers are automatically numbered sequentially from 1. A

drilled layer will be indicated with a ‘D’.
CBR (%) A This is calculated from the penetration rate using the selected
relationship as described in 4.5.1. The CBR value of a drilled layer
defaults to the average of the adjacent layers but can be edited.
Thickness A The thickness of each Test layer was determined from the layer
(mm) analysis.
Depth A The depth to the underside of each layer.
(mm)
Position M A Test layer can be defined as being part of one of the following
pavement layers: base, cement treated base, sub-base or
subgrade. This will determine which relationship of those described
in 6.1.2 and6.1.3 will be used to derive the strength coefficient from
the CBR value. For each Test layer, use the pull down menu to
select from these four options and to automatically calculate the
strength coefficient of that test layer. Gravel and earth surfaces
should be defined as Base. As layers are defined, UK DCP 3.1 will
not permit layers in illogical positions, such as a base below a sub-
base. UK DCP 3.1 will also generate a message if a base layer is
directly above the subgrade of if the first Test layer is defined as
subgrade, although these arrangements will be allowed. When a
layer is defined, high CBR values are automatically reduced to a
limiting value as follows. Base, Cement treated base and Sub-base:
150; Subgrade: 50. These limiting values are applied because
higher CBR values do not give a significant increase in the
Structural Number and it is inappropriate to give over-emphasis to
these strong layers in graphical or tabular reports. The limiting
values are used in all subsequent calculations and reports,
although the original figure is also retained in this box for record
purposes.
Strength M This is calculated automatically when the position of the test layer
coefficient has been entered. If the layer is defined as subgrade, the strength
coefficient field will be grey and inactive since the contribution of
the subgrade to SN, SNC and SNP is calculated directly from CBR
and does not require a strength coefficient.
 6.2.3 SN Calculation Buttons
Five buttons are present in the SN Calculation box.

Help Open this manual on the screen at the appropriate section.

Layer Open a Layer Boundaries box (Figure 6.2) as described in Chapter 5. This graph
Boundaries can be used to guide the assignment of positions to each Test layer and cannot be
edited. Within the Layer Boundaries box, Adjusted Data can be clicked to generate
a box showing the adjusted penetration data (Figure 6.3), including the penetration
rate between points, as described in Box 4.2 above.
CBR Chart Open a logarithmic chart (Figure 6.4) of CBR against depth for individual test points
and the Test layers as already identified. This chart can be used to check that the
line of the layers’ CBRs approximately follows the test points. If it does not, repeat
the layer analysis, perhaps changing from automatic to manual analysis or
improving manual analysis further so that the user has more control over where
boundaries are located. This checking process is described in more detail in
Box 6.1 The importance of checking the layer analysis against CBR Chart. The
chart cannot be edited. The chart displays CBR values as originally calculated,
rather than the values limited to 150 or 50 as described above. Drilled layers are
shown as a gap in the CBR line.
SN Calculate Structural Numbers from the information in the first two panels. This
button is unavailable until both panels have been completed. A third panel
containing the Structural Numbers will appear when the button is clicked.
Cancel Cancel the SN calculation and return to the Project Manager. A box is generated
which offers an opportunity to save the identified boundaries.

Figure 6.2 Layer Boundaries box

Figure 6.3 Adjusted Penetration Data box

Figure 6.4 CBR chart box

 Box 6.1 The importance of checking the layer analysis against CBR Chart
The CBR chart helps to ensure whether the layer analysis done is satisfactory or not. In Figure
6.2 the portion from 520 to 800 mm has been identified using automatic analysis as a single layer.
However, the CBR Chart shows that although a single CBR value has been calculated for this
layer, the CBR values vary within this layer.

If the CBR value varies considerably within a layer, it may be decided to reanalyse the data,
perhaps changing from automatic analysis to manual analysis in order to divide the layer into
thinner layers, and with different CBR value.

It is recommended that the CBR chart is checked after each test has been analysed.
 6.2.4 Pavement Strength
After completing the Test layers panel with positions and strength coefficients, click SN.
This will generate a third panel in the SN Calculation box, titled Pavement Strength
(Figure 6.5). This panel contains a table which gives the calculated Structural Number
contributions from each pavement layer as described in 6.1 above.

Figure 6.5 SN calculation box (after calculations are complete)

Before moving to the third panel, the following should be noted in the second panel of
Figure 6.5.
• Positions have been selected to match those shown in Figure 6.2.
• The CBR values of layers 1 and 7 have been reduced to their respective limiting
values.
• The CBR value of drilled layer 5 has been manually set to a value in between layer
4 and layer 6.
• Strength coefficients are not required for layers 6 and 7 as they are in the subgrade.
The third panel contains a table with the following information.

Layer This column lists each of the four pavement layers and the entire pavement.
SN This column gives the contribution of each pavement layer to SN. This is the
Structural Number of imported layers, so there is no value for the subgrade.
SNC This column gives the contribution of each pavement layer to SNC. For the
surface, base and sub-base, these are the same values as for SN. For the
subgrade, this is the value SNG.
SNP This column gives the contribution of each pavement layer to the depth adjusted
SNP. This adjustment applies to only the sub-base and subgrade, so the values
for the surface and base are the same as for SN and SNC.

Two additional buttons appear when the third panel is generated.

Edit Remove the Pavement Strength panel and edit the information in the Test layers
panel.
OK Save the results, close the SN Calculation box and any other associated boxes and
return to the Project Manager. It will be seen (Figure 6.6) that today’s date will be in
the SN calculation column for that test.

After data from penetration tests has been used to calculate Structural Numbers, the
Project Manager is as shown in Figure 6.6. Note that the Query and Section buttons are
active if Structural Numbers have been calculated for all tests.
Figure 6.6 Project Manager (showing that SNs have been calculated)
7 Query
7.1 Introduction
The Query function is used to produce histograms of strengths and thicknesses along
the project. These histograms display trends and patterns and have three specific uses.

• The histograms can identify any unusually high or low values which may have
arisen from errors during data input or analysis. If these are found, the user can
return to the suspect test and correct any errors instead of sectioning the project
using flawed data.
• The histograms can identify any areas of inadequate pavement along the project,
whether this is due to a layer with a low CBR value, or a layer which appears to
have been constructed too thin. It is important to consider these areas of
weakness when assessing the performance of a pavement or designing
improvement works.
• Although a project is sectioned using cumulative difference sum graphs, patterns
can often be seen in the histograms which can improve the accuracy of
determining where section boundaries should be set.

The Query function is inactive until there are two or more tests for which Structural
Numbers have been calculated. When the function becomes active, it will operate upon
only those calculated tests.

Since the function will operate on all calculated tests, if the user has completed the
Structural Number calculations for all tests but wishes to carry out a query using only a
proportion of the tests, it is recommended that the file is copied and renamed and then,
for each test which is not required, the layer analysis is opened, edited and closed. This
has the effect of deleting the Structural Number calculation and so removing it from the
Query function. The original file should therefore be seen as the master file and repeated
copies should be made to allow different alternatives to be queried without losing any
original data or calculation.

This chapter describes the use of the Query function.

1.1 Making a Query

Begin a query from the Project Manager. Click Query in the Project Manager or in the
Modules menu at the top of the main window. This will open a Query box (Figure 7.1).
The box has four panels.
Figure 7.1 Query box
 7.1.1 Query Parameter
In the first panel, select one parameter from the following to display in the histogram.
• SN
• SNC
• SNP

• Surface Thickness
• Base Thickness
• Sub-base Thickness
• Pavement Thickness

• CBR (Base)
• CBR (Sub-base)
• CBR (Subgrade)

7.1.2 Tests Included

The location of a test is a mandatory field when site details are input. Since strengths
and thicknesses are likely to be different in, for example, the carriageway and the verge,
it may not be informative to display these values on the same histogram. Therefore the
tests from which the histogram will be formed should be selected from the following
locations.
• All locations
• Carriageway only (individual lanes may be selected)
• Shoulder only
• Verge only
• Lay-by / other only

If this selection gives less than two tests for display, a warning message is shown and
the query cannot be made.

7.1.3 Query Type

This panel is used to identify minimum or low values on the histograms. The selection
operates differently depending on which parameter is to be displayed and is described in
7.3.1 to 7.3.3 below.

7.1.4 Display Options

This panel is used to select whether the horizontal scale of the histogram will be
Chainage or Test number. In some projects more than one test may be carried out at a
particular chainage, for instance in different lanes. If Chainage is selected, the results
from these tests will be shown at slightly different chainages so that the user can see the
results more clearly. The first test, by Test number, will be shown at the recorded
chainage, the second will be shown at the recorded chainage plus one metre, the third at
the recorded chainage plus two metres and so on. Although Zoom can be used to
distinguish between the columns more clearly, they may still appear to be close together,
particularly so for CBR histograms which contain more information than Structural
Number and thickness histograms. If this is the case, it is recommended that a
histogram is displayed by Test Number.
7.2 Displaying the Query results
After the four panels have been completed, click Query to display the required histogram.
The appearance of the histogram and the way in which low and minimum values are
shown varies according to the parameter that is being displayed.
 7.2.1 Structural Number
The Structural Number histogram (Figure 7.2) shows a series of columns, arranged by
chainage or test number, whose height is determined by SN, SNC or SNP. The scales of
the histogram are set automatically to best display the selected information.

The Query Type selection can be used if the user wants to check that, for example, the
Structural Number is above a specified value at every test site. To do this, a Less
Than value should be entered in the third panel of the Query box. A warning will be
generated if the entered value is outside a realistic range. This value is shown as a blue
dotted horizontal line on the histogram. The columns of those tests whose Structural
Number is above the value are shown in yellow and the columns of those tests whose
Structural Number is below the value are shown in orange. A message above the
histogram indicates at how many sites the Structural Number is below the value.

Figure 7.2 Structural Number histogram

Three items are available below the histogram.

Help Open this manual on the screen at the appropriate section.

Zoom Zoom allows the horizontal scale to be changed so that more detail is visible. If the
box Zoom value is greater than 100, a horizontal scroll bar is provided. Zoom is useful if
more than one test was carried out at a particular chainage and the columns are
displayed by chainage.
Close Return to the Project Manager.

When the cursor is placed over a column, its value is displayed in a small box.

A histogram can be printed by clicking Print in the File menu at the top of the main
window. It can be exported as a bitmap by clicking Export in the File menu.
Both Print and Export are available by right-clicking on the histogram.

7.2.2 Layer or Pavement Thickness

The Thickness histogram (Figure 7.3) shows a series of columns, arranged by chainage
or test number, whose height is determined by the thickness of the specified layer. The
scales of the histogram are set automatically to best display the selected information.

The Query Type selection can be used if the user wants to check that, for example, a
layer or the entire pavement is thicker than a specified value at every test site. To do this,
a Less Than value should be entered in the third panel of the Query box. A warning will
be generated if the entered value is outside a realistic range. This value is shown as a
blue dotted horizontal line on the histogram. The columns of those tests whose selected
layer or pavement is thicker than the value are shown in yellow and the columns of those
tests whose selected layer or pavement is thinner than the value are shown in orange. A
message above the histogram indicates at how many sites the layer or pavement is
thinner than the value.

Figure 7.3 Layer Thickness histogram

Three items are available below the histogram.

Help Open this manual on the screen at the appropriate section.

Zoom Zoom allows the horizontal scale to be changed so that more detail is visible. If the
box Zoom value is greater than 100, a horizontal scroll bar is provided. Zoom is useful if
more than one test was carried out at a particular chainage and the columns are
displayed by chainage.
Close Return to the Project Manager.

When the cursor is placed over a column, its value is displayed in a small box.

A histogram can be printed by clicking Print in the File menu at the top of the main
window. It can be exported as a bitmap by clicking Export in the File menu.
Both Print and Export are available by right-clicking on the histogram.

7.2.3 CBR
The CBR histogram shows a series of columns, arranged by chainage or test number.
The vertical scale is downwards. Each column is broken into pieces, each piece
representing one Test layer within the base, sub-base or subgrade. The length of each
piece represents the thickness of the Test layer that it represents. The CBR value of that
Test layer, reduced if necessary to its limiting value of 150 or 50 as described in 6.2.2, is
placed at the mid-point of each piece. Thus if CBR (Base) has been queried and three of
the Test layers identified from the penetration data had been defined as part of the Base,
the column would have three pieces, each one with its CBR value up to a maximum of
150. The scales of the histogram are set automatically to best display the selected
information.

The Query Type selection can be used in two ways.

Minimum (Figure 7.4)

The user wants to identify the Test layer within each test which has the lowest CBR
value. To do this, Minimum should be selected in the third panel of the Query box. The
piece of each column which represents the Test layer with the lowest CBR value is
shown in orange and all other pieces are shown in yellow. If two Test layers have the
same CBR value and that value is the minimum of the test, both pieces are shown in
orange.
Figure 7.4 CBR histogram (Minimum)
Less Than (Figure 7.5)

The user wants to check that all Test layers within a pavement layer have a CBR value
(reduced if necessary to its limiting value of 150 or 50) greater than a specified value at
every test site. To do this, aLess Than value should be entered in the third panel of the
Query box. A warning will be generated if the entered value is outside a realistic range.
The pieces of columns which represent Test layers whose CBR is above the value are
shown in yellow and the pieces of columns which represent Test layers whose CBR is
below the value are shown in orange.

Figure 7.5 CBR histogram (Less Than)

Three items are available below the histogram.

Help Open this manual on the screen at the appropriate section.

Zoom Zoom allows the horizontal scale to be changed so that more detail is visible. If the
box Zoom value is greater than 100, a horizontal scroll bar is provided. Zoom is useful if
more than one test was carried out at a particular chainage and the columns are
displayed by chainage.
Close Return to the Project Manager.
A histogram can be printed by clicking Print in the File menu at the top of the main
window. It can be exported as a bitmap by clicking Export in the File menu.
Both Print and Export are available by right-clicking on the histogram.
8 Sectioning
8.1 Introduction
The Sectioning function is used to divide the project into sections, referred to as DCP
Sections, each of which has pavement layers of reasonably uniform strength and
thickness and which is different from its adjacent sections.

Sectioning is carried out using a cumulative difference sum graph and can be based
upon one or more of a number of parameters, normally strengths and layer thicknesses.
A cumulative difference sum graph is produced as follows. UK DCP 3.1 averages the
selected parameter over the length of the project and then, for each test site, calculates
the value of the average minus the parameter at that site. These values are then
summed in turn starting at the first test to find the cumulative difference sum at each site
and the sum is plotted against chainage for the entire project. This is a similar process to
that described in 5.3 and Table 4.1. By the nature of the calculation, the cumulative
difference sum graph will be zero at the final test site. Cumulative difference sum graphs
often take a sawtooth form, where a line of constant gradient represents a section where
the parameter is uniform. Lines drawn at the peaks and troughs of the sawtooth
represent the boundaries between uniform DCP sections.

A project can be sectioned using more than one parameter. After sectioning has been
carried out using each selected parameter, a bar chart can be generated which shows
the sections derived from each parameter alongside each other. The user can then
compare the sections and define the DCP Sections of the project. These DCP Sections
can then be used to assess the performance of the pavement or design improvement
works.

The Sectioning function is inactive until there are six or more tests for which Structural
Numbers have been calculated. When the function becomes active, it will operate upon
only those calculated tests.

Since the function will operate on all calculated tests, if the user has completed the
Structural Number calculations for all tests but wishes to section the project using only a
proportion of the tests, it is recommended that the file is copied and renamed and then,
for each test which is not required, the layer analysis is opened, edited and closed. This
has the effect of deleting the Structural Number calculation and so removing it from the
Sectioning function. The original file should therefore be seen as the master file and
repeated copies should be made to allow different alternatives to be sectioned without
losing any original data or calculation.

This chapter describes the use of the Sectioning function.

8.2 Sections box
Sectioning is carried out from the Sections box (Figure 8.1). Open this box by
clicking Section in the Project Manager or in the Modules menu at the top of the main
window. The Sections box has two panels and several buttons.

Figure 8.1 Sections box (before sectioning)

8.2.1 Parameters
This panel contains a table and two buttons.

The table indicates which parameters have been used to section the project and the
number of sections which were derived from each selected parameter. Sectioning can
be carried out using one or more of nine parameters.
• CBR (Base)
• CBR (Sub-Base)
• CBR (Subgrade)

• SN
• SNP

• Surface Thickness
• Base Thickness
• Sub-base Thickness
• Pavement Thickness
Two buttons are present in the Parameters panel.

Determine Section a project using a selected parameter. Its use is described in 8.3.1 below.
Sections
Summary Compare the sections derived from each selected parameter. It is not available
until sectioning has been carried out using at least one parameter. Its use is
described in8.3.2 below.

8.2.2 Tests Included

The location of a test is a mandatory field when the Site details for that test are entered
(4.2). Since strengths and thicknesses are likely to be different in, for example, the
carriageway and the verge, it may not be useful to section a project using results from all
locations. Therefore the tests which will be used for sectioning should be selected from
the following locations.
• All locations
• Carriageway only (individual lanes may be selected)
• Shoulder only
• Verge only
• Lay-by / other only
If the selected location has less than six tests, it is unlikely that sectioning will produce
useful results and a warning message is generated stating that at least six tests are
required. Since all sectioning must be carried out using the same data, once sectioning
has begun, it is not possible to change the choice of tests and the panel is inactive.

8.2.3 Sections buttons

There are six buttons at the bottom of the Sections box. Their use is described briefly
below.
Help Open this manual on the screen at the appropriate section.
Reset Allow the project to be reanalysed using tests in a different
location. This button is active after sectioning has begun
or Edit has been clicked.
OK Accept the sectioning by parameter. This activates
the Summarybutton and allows DCP Sections to be identified.
Cancel Cancel the analysis which has just been carried out and return to
the Project Manager.
Edit Visible if Edit the sectioning analysis. Clicking this button allows the project
the project to be reanalysed using the same tests.
has already
Close been Click this button to return to save the sectioning analysis and
sectioned return to the Project Manager. If DCP Sections have been
and saved determined, it will be seen (Figure 8.9) that today’s date will be in
the Sectioning column for all tests.
8.3 Sectioning a project
There are two stages to dividing a project into DCP Sections. Firstly, the project is
sectioned using, one after the other, each of the parameters which are deemed to be
significant. Parameter selection depends upon the modes of failure which may have
been identified and the parameters upon which the improvement works will be designed;
guidance should be obtained from the user’s organisation. Secondly, these sections are
compared and DCP Sections defined which best combine the single parameter sections.

8.3.1 Determine Sections by parameter

Open the Sections box from the Project Manager. In the Tests Included panel, select the
location of the tests to be used for sectioning. Then highlight a significant parameter in
the table and click Determine Sections. This will generate a Uniform Sections box
(Figure 8.2).

Figure 8.2 Uniform Sections box

The Uniform Sections box contains the cumulative difference sum graph, as explained
in 8.1 above, for the selected parameter and seven items below the graph which are
used to section the project.
Help Open this manual on the screen at the appropriate section.
Show A check box is provided to allow gridlines to be displayed or removed.
Gridlines
Zoom box Zoom allows the horizontal scale to be changed so that more detail is
visible. If the Zoom value is greater than 100, a horizontal scroll bar is
generated.
Show If the peaks and troughs of the cumulative difference sum graph are not clear,
Histogram a histogram can help to identify section boundaries. Click this button to display
a Histogram box (Figure 8.3) containing a histogram of the selected parameter
against chainage. The height of each column represents the value of the
parameter at that test point. In the case of CBR values, if the base, sub-base
or subgrade comprise more than one Test layer, the CBR values of these Test
layers (limited to 150 or 50 as described in 6.2.2) are combined to give an
aggregate value. Within the base and sub-base, the Test layers are weighted
according to their thicknesses but within the subgrade, the Test layers are
combined by the procedure referred to in 6.1.3 which derives an aggregate
subgrade CBR in a manner which reflects engineering judgement. If a test
was carried out at a chainage, but the parameter was zero, for example if
CBR (Sub-base) is selected, but no sub-base was identified, a bold line along
the horizontal scale will be seen at that chainage. If no test was carried out,
only the fainter chainage scale will be visible. Within the Histogram
box, Help opens this manual on the screen, Zoomallows more detail to be
seen and Close returns to the graph. When the cursor is placed over a
column, its value is displayed in a small box.
Add Section Click the button and then click and hold the cursor on the white portion of the
graph. A vertical line will appear. Move the line until it is at a point where the
gradient of the graph, and hence the parameter, makes a significant change.
Since the cumulative difference sum is calculated from the lower chainages on
the left towards the right, it is more accurate for a boundary to be placed
midway between a peak or trough and the point to its immediate right than
exactly at the peak or trough. Release the button to fix the section boundary.
Add more boundaries as required. If a boundary is misplaced, it can be re-
clicked and dragged or double-clicked and deleted. A graph with one section
boundary added is shown in Figure8.4. Since it is very rare for a cumulative
difference sum graph to be a perfect sawtooth, the user’s organisation should
produce guidance regarding how finely the project should be sectioned. Each
parameter must be divided into at least two sections; it cannot be left as a
single section.
OK Save the sectioning and return to the Sections box. A number in the table
alongside the parameter will show into how many sections the project has
been divided for that parameter. Another significant parameter can then be
highlighted for sectioning.
Cancel Cancel the sectioning and return to the Sections box.
 Figure 8.3 Histogram of sectioning data

This histogram displays the same data that was used to generate Figure 8.2.
 Figure 8.4 Uniform Sections box (with one section boundary added)

After the project has been sectioned using all of the significant parameters, click OK in
the Sections box. The Summary button becomes active. The Sections box is as shown
in Figure 8.5. In this case, design has focussed on the base layer.
 Figure 8.5 Sections box (after Sectioning)

8.3.2 Determine DCP Sections for the project

The sectioning from all of the significant parameters can now be compared and DCP
Sections defined. Click Summary in the Sections box to display a Section Summary box
(Figure 8.6). The Summarybutton will be enabled only after the uniform sectioning has
been saved.
 Figure 8.6 Section Summary box

The Section Summary box contains a series of parallel horizontal bars, one bar for each
selected parameter, as indicated on the left hand scale. Each bar extends from the
chainage of the first included test to the chainage of the last included test. On each bar,
every section boundary is marked with a bold line and the sections are coloured
alternately yellow and orange. A value in the centre of each section is the average value
of the relevant parameter for all tests in the section. The user should compare these
bars in order to define the DCP Sections of the project.

There are eight items below the horizontal bars.

Help Open this manual on the screen at the appropriate section.

Zoom box Zoom allows the horizontal scale to be changed so that more detail is
visible. If the Zoom value is greater than 100, a horizontal scroll bar is
provided.
DCP This button is available after the first DCP Section boundary has been
Section accepted. Click this button to generate a DCP Section Properties box
Properties (Figure 8.7) containing a table of DCP Section information. For each
Design Section, the table gives its start and end chainages, its length,
the number of tests within it, and a statistical analysis of each of the
nine parameters. Lower tenth percentile values are not calculated for
layer thicknesses, or for any parameter if there are less than seven
tests in a Design Section. The user should note that if a parameter in
a section has a value of zero, or if it is allocated a value of zero for an
absent layer, the statistical analysis will use this zero. Therefore
 averages and lower tenth percentiles may be lower than expected. To
identify these zeroes, and possibly delete or reanalyse a test,
examine the minimum values for each parameter. Within the DCP
Section Properties box, Help opens this manual on the screen
and Close returns to the Section Summary box.
Add DCP This button is used to add a DCP Section boundary to the series of
Section horizontal bars. Click the button and then click and hold the cursor on
the white portion of the graph. A vertical line will appear. Move the line
until it is at a point which best represents a change in the overall
properties of the project. Release the button to fix the DCP Section
boundary. Add more boundaries as required. If a boundary is
misplaced, it can be re-clicked and dragged or double-clicked and
deleted. It may be that all selected parameters have been sectioned
at a similar point, in which case a boundary should be placed in their
midst, but if the sections are dispersed, guidance from the user’s
organisation may be required to determine which parameters may
take precedence and where the DCP Section boundary should be
placed. Guidance should also be produced regarding how finely the
project should be sectioned. A chart with one DCP Section boundary
added is shown in Figure 8.8. It is possible to not add a DCP Section
boundary and leave an entire project as a single DCP Section.
OK Accept the DCP Sections and enable the DCP Section
Properties andClose buttons. Click Close to return to the Sections box
and then clickClose in the Sections box to return to the Project
Manager. It will be seen (Figure 8.9) that today’s date will be in the
Sectioning column for all tests in the project.
Cancel Cancel the sectioning and return to the Sections box.
Edit Visible if Edit the sectioning analysis.
the
project
Close has Click this button to return to the Sections box.
already
been
sectioned
and saved
Figure 8.7 DCP Section Properties box
 Figure 8.8 Section Summary box (with one DCP Section boundary added)

The addition of the Design Sections marks the end of the analysis of the penetration
data. After data from penetration tests has been used to define Design Sections for the
project, the Project Manager is as shown in Figure 8.9.
Figure 8.9 Project Manager (showing that DCP Sections have been defined)
9 Design data input

The purpose of pavement design is to limit the stresses induced in the subgrade by
traffic to a safe level at which subgrade deformation is insignificant and the pavement
layers do not deteriorate to any serious level within a specified period of time. Therefore,
if a road is to be rehabilitated, improved or constructed, the design and also the cost of
the required works depend upon a wide range of information. This includes the following.

• The detailed condition of the pavement

• The current overall condition of the road
• The nature of the road
• The required standard of the finished road
• The costs of the required activities

The use of DCP penetration data to determine the detailed condition of the pavement
has been described in Chapters 4 to 8. In this Chapter, Section 9.1 describes how the
current condition and nature of the road are entered and Section 9.2 describes how the
required road standard and activity costs are entered. This data can also be transferred
from one project to another using the Merge function as described in 4.6.1.

An alternative use of data relating to the overall condition and nature of the road is to
decide where DCP tests should be carried out in order to more fully investigate sites
where failure is more likely. In this case, design data can be entered before DCP test
data is entered and analysed.

9.1 Survey Data

The following elements of road condition and road nature can be entered into UK DCP
3.1.

Element Reason for recording the information

A road in poor overall condition, in terms of the

Road condition road itself and the side drains, may require
more urgent repair than one in good condition.
Type and condition of any structures along the Damaged structures will need to be repaired.
road
A gravel road with a thin layer may need to be
Surface gravel thickness
regravelled.
Crown height: the height difference between
A dry pavement and surface require
the crown of the road and the base of the side
less maintenance and repair. It is important to
drains (or the adjacent land if no side drains
ensure that the road surface has sufficient
are present)
height above the maximum water level.
The height difference between the crown of the
road and the maximum water level during flood
Gradient of side slopes Gradient affects the quantity of required work.
The required work depends upon whether or
Road type not the road is engineered and whether or not a
gravel layer is present.
Carriageway width
The current shape and size of the road affect
Shoulder width
the quantity of required work.
Cross section profile
A gravel road can be very unhealthy and
The presence of people living nearby
unsafe for those living nearby and may justify a
sealed surface.
Unpaved sharp bends can be dangerous for
The presence of sharp bends
traffic and may justify a less slippery sealed
surface.
Unpaved steep slopes can be dangerous if
The presence of steep slope
slippery and may erode during rainfall, justifying
a sealed surface.

This data is recorded during a survey along the road on a series of Survey Data Sheets,
as shown in Appendix B: Survey Data Sheet. Each Survey Data Sheet contains
condition and other information from a road interval, up to 5 km long, for which the final
seven variables in the above table are constant. If any of these seven variables change
significantly along the project, a new Data Sheet should be used. Some data may not be
available during a survey, for example the flood height when surveyed in the dry season;
in this case, it is necessary to talk with local residents.

To enter the data recorded on the Survey Data Sheets into UK DCP 3.1, click Add
Survey Data in the Design Status panel of the Project Manager. This will bring up the
Survey Data box (Figure 9.1). To edit a Survey Data box that has already been entered,
select the Data Sheet and click Survey Data.
 Figure 9.1 Survey Data box (without data)

There are six panels in the Survey Data box. Data is entered as follows. Some of the
fields are mandatory, some are optional and some are filled in automatically.

Data Interval Enter the start and end chainage, up to 3 decimal places, of the road interval
covered by this Survey Data Sheet. The Start chainage defaults to the End
chainage of a previous Sheet but can be edited. The maximum interval that
can be covered by each Sheet is 5 km. UK DCP 3.1 will check that there is no
overlap between successive intervals. Today’s date, or the date of the
previous Sheet, is entered automatically but can be edited. Click Accept to
continue to the next panels.
Road Condition Using From (km) and To (km), the road interval can be divided into up to ten
short lengths, each with a different overall condition. From (km) is set
automatically and cannot be edited. These short lengths are set automatically
at 10% of the interval length, but can be edited. If ten short lengths are used,
the To (km) of the tenth length will automatically be set to the end chainage of
 the Data Interval. For each short length, assign a condition to the road and to
the side drain in the worst condition (from very good, good, average, poor and
very poor) using the pull-down menus. Click Add to add another short length
and Delete to delete a short length. When the condition of the entire road
interval has been assigned, move on to the next panel.Box 9.1 describes how
a road interval may be divided into short lengths. It is important that consistent
definitions of carriageway and drain condition are produced and followed by all
those using UK DCP 3.1.
Structures For each structure within the road interval, enter its chainage, its type (from
Condition drift, culvert, vented drift, minor bridge and large bridge) and its overall
condition. Click Insert to add another structure and Delete to delete a
structure. When all structures in the interval have been described, move on to
the next panel.
Surface Gravel For each point at which gravel thickness was measured along a gravel road,
Thickness enter its chainage and the thickness.
Crown Height, Using From (km) and To (km), the road interval can be divided into up to ten
Flood Risk and short lengths, each with different values for crown height, flood risk and side
Slope slope gradient. From (km) is set automatically and cannot be edited. These
short lengths are set automatically at 10% of the interval length, but can be
edited. If ten short lengths are used, the To (km) of the tenth length will
automatically be set to the end chainage of the Data Interval. For each short
length, enter the average crown height, the height difference between the
crown of the road and the maximum water level during flood and horizontal
component of the side slope. If water does not flood the side drains or the
surrounding land, it is not necessary to enter a value for flood risk. If water
floods above the crown of the road, the height of the water should be entered
as a negative value. The flood risk value may be between -5 and +5 metres.
The horizontal component of the side slope must be between 0.5 and 3.
Click Add to add another short length and Delete to delete a short length.
When the entire road interval has been described, move on to the next
panel. Box 9.1 describes how a road interval may be divided into short lengths.
Road Geometry This panel contains the seven variables which are constant over the entire
and Land Use road interval. Typing values or using pull-down menus, enter the road type
(unengineered earth, engineered earth or engineered gravel), the carriageway
width (between 2 and 10 metres), with shoulder width (between 0 and 5
metres), the cross section profile (cut, fill, cut and fill, sidelong ground or
none), whether or not people live within approximately 100 metres of the road,
whether or not there are a number of sharp bends in the road interval and
whether or not there are steep slopes within the road interval.

Figure 9.2 shows a completed Survey Data box.

 Figure 9.2 Survey Data box (with data)

There are five buttons below the panels.

Help Open this manual on the screen at the appropriate section.

Export Export all the fields from the Data Sheet into a CSV format file for use in a spreadsheet.
Edit This button is visible if data has already been entered and saved. Click this button to edit data in
the box. If the current data has already been used either to determine design sections or to
produce pavement design, a box will be generated warning that editing will delete these design
sections and pavement design.
Cancel At any point during data input, click this to cancel the entered information. This will generate a box
asking if the changes that have been made should be saved. Clicking No will cancel any changes
that were made. If a new, automatically generated Survey Data box is not required, click Cancel to
delete it.
OK This is used to save the data entered for a road interval, return to the Project Manager and open a
Survey Data box for the next portion of the project. If any item or portion of the road interval has
not been fully described, a warning message will appear and the omitted data must be entered
before the road interval will be accepted.
Figure 9.3 shows a Project Manager after a number of Survey Data boxes have been
completed. ‘From’ and ‘To’ columns of the Design Status table are filled automatically
with Data Sheet numbers and the start and end chainages of the saved Survey Data
Sheets. Dated will be added in the remaining columns as the design progresses. More
Survey Data Sheets can be entered by clicking Add Survey Databutton.

Figure 9.3 Project Manager box (after entering survey data)

 Box 9.1 Recording of variations within data interval
Often it will be necessary to record variation in road or drain condition or crown height within a
road interval. The Survey Data box shown in Figure 9.2 is therefore designed to record up to a
maximum of 10 short lengths within the road interval. However, it is not possible to set a fixed
short length which will be suitable for all projects. Some users may prefer to use a road interval of
1 km and record the variation in condition and crown height every 100 metres; others may prefer
a road interval of 2 km with variation every 500 metres. In some cases different data intervals
may have to be used within a project, depending upon the variability of the road. The road interval
length and the short lengths within the road interval largely depend on the site condition and the
level of accuracy the user like have.

The Road Condition and Crown Height panels in UK DCP 3.1 have been designed to allow this
flexibility. If the road interval of a Data Sheet is, say, from 0 to 1 km, UK DCP 3.1 will
automatically enter ‘From (km)’ and ‘To (km)’ of the first row of both these tables as 0.000 and
0.100 km, assuming that recoding the deviations in every 10 % of the data interval is preferable. If
this is acceptable, UK DCP 3.1 will automatically enter 0.100 and 0.200 km for the next row and
continue for the entire road interval. UK DCP 3.1 will not add a row to enter a value beyond the 1
km in this case.

It is possible to change the ‘To (km)’ value. This can be done by three different ways. The first
and preferable way is to change the value in the first row before adding the second row. For an
interval of 0 to 1 km, the first row will be filled automatically with values 0 km and 0.100 km. If
variations are captured for every 0.200 km length within a data interval, change 0.100 to 0.200
and click Enter. All subsequent rows will now be added to capture variations of 0.200 km length.

The value can also be changed in an intermediate row. If variations have been captured for the
first three rows for 0.100 km, and 0.300 km for other rows then change the default value in the
fourth row from 0.400 km to 0.600 km. UK DCP 3.1 will automatically enter 0.900 km and 1.000
km for the subsequent rows.

After entering variations in 10 rows, if the second row (from 0.100 km to 0.200 km) is deleted, UK
DCP 3.1 will reset the first row and second row from 0 km to 0.150 km and the second row from
0.150 km to 0.300 km

9.2 Design & Costs Data

The following elements of required road standard and activity costs can be entered into
UK DCP 3.1.

Element Reason for recording the information

Cross section dimensions The required shape and size of the road affect the quantity of
required work.
Weinert N value The climate of the region in which the road is located affects the
design of the pavement. In UK DCP 3.1, climate is indicated by a
(12)
Weinert N value . UK DCP 3.1 should be used only where the
Weinert N value is more than 2.
Design life The required design life of the road, the volume of traffic that the
Traffic level and growth road is expected to carry and the loading of the heavy vehicles
rate affect the design of the pavement. Care should be taken when
 Equivalent Standard Axle estimating the annual traffic growth rate as a high rate will give
(esa) load of the heavy conservative and possibly expensive designs.
vehicles
Costs The cost of each work activity will affect the total cost of the
recommended improvements.

This data is entered in a Design and Costs Data box. Unlike the Survey Data box which
is used to record condition and road nature data for a series of road intervals with the
project, the Design and Costs Data box records details for the entire project length,
although some of the traffic data can be divided into shorter intervals.

To enter the data into UK DCP 3.1 or to edit data which has already been entered,
click Design and Costs Data in the Design Status panel of the Project Manager. This will
bring up the Design and Costs Data box (Figure 9.4).

There are four panels in the Design and Costs Data box. Data is entered as follows.
Some of the fields are mandatory, some are optional and some are filled in automatically.

Design Standards Three cross sections (A, B & C) may be defined for use later in the design process.
Default values are provided automatically but carriageway width can be edited within
the ranges 6-15, 3.5-12 and 3-7 metres respectively, shoulder width for all three cross
sections can be edited to any value up to 4 metres and slope for all three cross
sections can be edited to any value between 1:1 and 1:3 (only entering the horizontal
component). Select the Weinert N value for the region in which the road is located (2
to 4 or >4). Enter the required design life of the road. This is set automatically to 10
years but can be edited to between 5 and 20 years.
Traffic Parameters Enter the expected annual percentage growth rate of the traffic (between 0 and 10).
(13)
This will be used for normal and generated traffic . Enter the year when the road will
be opened for traffic. Enter the average Equivalent Standard Axle (esa) value for
heavy vehicles which will use the road. This is set automatically to 1 but can be edited
to any value between 0 and 10.
Traffic If the traffic level changes significantly along the project, perhaps at a junction, use
From (km) and To (km) to divide the project into intervals for each of which different
traffic levels can be defined. For each interval, enter the following data. Enter the year
in which a traffic count was carried out for which the data is available. Enter the two-
way motorised Annual Average Daily Traffic (AADT). Enter the daily two-way level of
non-motorised traffic (NMT). Enter the percentage of the motorised traffic which is
classed as heavy vehicles. This value is set automatically to 35 but can be edited to
between 0 and 100. If it is expected that traffic will be generated by the new or
improve road, select Yes from the pull-down menu and enter the year when the
generated traffic is expected to begin and the two-way motorised AADT it will begin at.
The final three figures are calculated automatically: for single lane roads, the design
traffic is the total two-way traffic over the design life; for two lane roads, the design
traffic is half of the two-way value; and for intermediate width roads, the design traffic
is 80% of the two-way value. This is explained more fully in Box 9.2. Click Add to add
another traffic interval and Delete to delete an interval.
Costs Enter the currency which will be used for all cost calculations. Unit rates can be
entered for up to 14 different activities: 6 surfaces, 5 bases, sub-base, selected fill and
subgrade. UK DCP 3.1 is able to identify the optimum design by calculating the cost of
all possible designs that meet the design requirements and selecting the design with
the lowest cost. UK DCP 3.1 can produce designs which are based on 14 different
activities: 6 surfaces, 5 bases, sub-base, selected fill and subgrade, but for costs to be
compared, the rate for each activity should be entered. These rates can be entered
later in the design process but since this may cause earlier calculations and designs to
 be deleted, it is recommended that if comparative costs will be required, rates for all
activities are entered at this first opportunity

Figure 9.4 shows a completed Design and Costs Data box.

Figure 9.4 Design & Costs Data box (with data)

There are up to six buttons below the panels.

Help Open this manual on the screen at the appropriate section

Edit (visible if Click Edit to change the data, review or input data. If the current data has
data has already already been used either to determine design sections or to produce
been entered and pavement design, a box will be generated warning that editing will delete
saved) these design sections and pavement design.
Close (visible if Return to the Project Manager without making any edits
data has already
been entered and
saved)
Reset Reset removes all data from the Design and Costs Data box.
 OK This is used to accept and save the data
Cancel At any point during data input, click this to cancel the entered information.

Box 9.2 Determination of design traffic

A pavement is normally designed to carry a specific traffic loading. It is therefore necessary to
assess the expected loading over the lifetime of the road. The process involved a number of
steps.

The first step is to estimate the Annual Average Daily Traffic (AADT) currently using the road.
This includes cars, light goods vehicle, heavy goods vehicles and buses. Since the load imposed
on a pavement by a vehicle is proportional to the axle load to the power of 4-4.5, loads imposed
by light vehicles are insignificant. Therefore the percentage of heavy vehicles, with an unladen
mass of at least 5,000 kg, which will be using the road among the total number of vehicles should
be determined. It is suggested that a 7 day count of all vehicles is carried out and the percentage
of this total that is heavy is estimated. If it is difficult to do this, it is suggested that the default
value of 35% is used.

It is necessary to estimate the loading of each heavy vehicle using the road. A two axle heavy
vehicle with 8 tonnes on each axle imposes an Equivalent Standard Axle (esa) load of 2. UK DCP
3.1 will use a default esa value of 1 for each heavy vehicle but this can be edited to any value
between 0 and 10.

In order to determine the number of vehicles that will be using the road it is essential to estimate
the growth rate. This can be done in a number of ways: extrapolating time series traffic data;
equating vehicle growth to population growth, equating vehicle growth to GDP growth or a
combination of these. It is recommended that a variety of methods are assessed.

The percentage of heavy vehicles, the esa value per heavy vehicle and the growth rate are the
three important parameters when estimating design traffic. Although it is very difficult to precisely
determine these parameters, it is necessary to note that inaccurate values will result in the
increase or decrease the traffic loading and result in over or under design.
10 Design Sections
10.1 Introduction
This Chapter describes how the project can be divided into sections, referred to as
Design Sections, each of which is reasonably uniform in a wide variety of characteristics
and which is different from its adjacent sections. Each Design Section may require a
different level of investigation or design approach from its adjacent sections.

Design Sections can be defined using DCP results and survey data in order to design
improvements. Alternatively they can be defined using overall condition and other survey
data, as described in Chapter 9, in order to focus a DCP investigation on the sites where
overall condition is worse of where failure appears to be more likely.

If the Survey Data, described in Chapter 9, is continuous with no gaps, the Design
Sections button is active in the Design Status panel of the Project Manager. Click this
button to display the Design Sections box, as shown in Figure 10.1.
 Figure 10.1 Design Sections box

The Design Sections box has three parts: a bar chart which displays all available design
and survey data, a series of filters which can be used to select which data is displayed
and several buttons which are used to define Design Sections. The bar chart can be
printed or exported by a right click and selecting either print or export.

10.2 Displaying available design data

The bar chart displays the available design and survey data with a series of horizontal
bars, one bar for each item or parameter. Each bar, extending over the chainage for
which data is available, is coloured green, grey or red according to the value, condition
or type of the parameter at that chainage, and letters or numbers are also added when
necessary. The Average subgrade CBR bar is shown divided at any DCP Section
boundary at which the average CBR changes from one category to another.

All parameters, and how they are displayed, are given in the Legend, which can be
generated by clicking the Legend button in the Design Section box and which is shown
in Figure 10.2.

Figure 10.2 Design Section Legend

The Legend uses the following abbreviations.

Road Type UE Unengineered Earth

EE Engineered Earth
EG Engineered Gravel
Carriageway and Drainage condition 1 Very good
2 Good
 3 Average
4 Poor
5 Very poor
Cross Section Profile C Cut
F Fill
C&F Cut and Fill
S Sidelong Ground
N None or unknown

Below the bar chart are a series of filters which can be used to change the display of
Carriageway and Drainage condition, Crown height and Height from flood level. These
filters can be used to focus attention on the parts of a project whose condition is most
critical or which are most at risk from drainage related problems. Since it is
recommended that all roads are constructed with a pavement at least 750 mm above the
highest likely water level, if a limiting value of less than 750 mm is selected to display
Crown height and Height from flood level, a warning message will be generated.

A final filter can be used to select the type of traffic which is displayed: the design traffic
for different widths of road; the daily motorised traffic or the daily non-motorised traffic.

10.3 Defining Design Sections

Design Sections are defined by identifying where the combined set of design data and
other parameters change sufficiently to justify a different level of investigation or design
approach.

Design Sections are defined using the buttons at the bottom of the Design Sections box,
as described below.

In addition, UK DCP 3.1 automatically adds Design Sections, indicated with dotted lines,
at points where the road types differ. Such lines cannot be moved or deleted. Figure
10.3 shows a Design Section added where the road type changes.

Add Design Section This button is used to add a Design Section boundary to the series of
horizontal bars. Click the button and then click on the bar chart. A vertical line
will appear. Drag the line until it is at a point where the parameters change
significantly. Add more Design Section boundaries as required. If a boundary is
misplaced, it can be clicked and dragged or double-clicked and deleted.
OK This is used to accept the Design Sections and enable the Design Section
Properties and Close buttons. If no Design Section is added either by the user
or by UK DCP 3.1, clicking OK will consider the project length as a single
Design Section.
Design Section Properties This button is available after a Design Section has been saved. Click this
button to generate a Design Section Properties box (Figure 10.4) containing
the value and variability of each parameter in each Design Section.
Cancel Cancel the selected Design Sections and return to the Project Manager.

Edit Edit the Design Sections. If pavement design has been carried out, a warning
Visible after Design is generated that editing the Design Sections will delete the pavement.
Sections have been
Close defined and saved Close the Design Sections box and return to the Project Manager. Today’s
 date will appear in the Design Sections column in the Design Status panel for
all the data sheets in the project, as shown in Figure 10.5.

Figure 10.3 Design Section box (with CBR)

Box 10.1 provides additional guidance on how to define Design Sections, although in all
cases, the organisation operating UK DCP 3.1 should ensure that all those using it follow
consistent procedures and practice.

UK DCP 3.1 will generate a warning message if any design section has two different
traffic ranges, as thickness of pavement might change based on traffic loading.

Box 10.1 Determination of Design Sections

The variability of a wide range of parameters along the road should be taken into account in the
design process. UK DCP 3.1 displays the variability of these parameters along the project length.
The following issues are relevant when defining Design Sections.
Design traffic: This is estimated from the number of million Equivalent Standard Axles (mesa) that
are expected to use the road during the design life. Since UK DCP 3.1 design charts present
pavement designs of different thicknesses for seven traffic categories, it is recommend that
Design Sections are defined firstly on the basis of traffic.

Subgrade strength: Sections with lower subgrade CBR will normally require a stronger and
thicker layer than will sections with high subgrade CBR. Since UK DCP 3.1 design charts present
pavement designs for different subgrade CBR values, it is recommended that Design Sections
are defined secondly on the basis of subgrade strength. For this, it is necessary that DCP data
has been entered and analysed and DCP Sections defined.

Minimising cost: Defining long Design Sections and designing the improvement for the most
critical part of each section may result in expensive designs. In order to minimise costs, Design
Sections should be as short as possible while remaining practical for construction. For example, if
crown height is inadequate over a small proportion of a Design Section, it may be worthwhile
returning to the Design Sections box and defining more Design Section boundaries to achieve a
more economical design.

Land use: Where people are living close to the road, typically within 100 metres, sealing may be
required in order to protect their health from dust and increase safety. In areas with sharp bends
and steep slopes, materials of low PI and widening may be required.

10.4 Design Section Properties

The Design Section Properties box is shown in Figure 10.4. It gives the value, and in
some cases the variability, of each parameter in each Design Section. The proportions
of each parameter can be useful in deciding whether the Design Section should be
improved with a single design or divided further, by clicking Edit in the Design Sections
box, to achieve a more economical design.

Some parameters are given only if they might indicate a problem with the road. For
instance, carriageway condition is given only when average, poor or very poor; the
proportion of a Design Section in very good or good condition is not shown.
Figure 10.4 Design Section Properties
Figure 10.5 Project Manager Box (after Design Sections have been defined)
11 Pavement Design
11.1 Introduction
UK DCP 3.1 allows the user to design pavement improvements based on DCP
penetration data and other information relating to the overall condition of the road, the
nature of the road and the required standard of the finished road, although if DCP data is
unavailable, design may continue with a more limited range of design alternatives.

One of three design alternatives should be selected for each Design Section: Upgrading,
which allows the pavement to be structurally designed with a sealed surface and which
is available if DCP Sections have been defined; Gravelling in response to a currently thin
gravel surface; and Routine Maintenance if no other work is required. Upgrading is not
available if DCP Sections have not yet been defined.

The design process can begin after Design Sections have been defined and
the Pavement Design button in the Project Manager has become active. Click this button.

If DCP data is available, a box will be generated which describes how the default key
design parameters of layer thickness and layer CBR are determined according to the
number of DCP tests in each Design Section, the reasoning being that the fewer tests
have been carried out, the less confident we can be in the results and the more
conservatively we should select the design value from the available results. This box is
shown in Figure 11.1.

Figure 11.1 Message on statistical parameters

11.2 Pavement design box

Click OK to open the Pavement design box, as shown in Figure 11.2.
 Figure 11.2 Pavement design box – before designing

The Pavement design box contains a table and three buttons. Each row of the table
contains information relating to one Design Section. The table has nine columns, all of
which are completed automatically during the design process.

Section number Design Sections are ordered numerically

Start and End (km) Start and end chainage of each Design Section

Length (km) The length of each Design Section

No of tests The number of DCP tests carried out in each Design Section. If DCP Sections
have not yet been defined, a zero will be shown.
Statistical The way in which the thickness of each layer will be determined. The default is
parameter (Thickness) chosen automatically according to the number of DCP tests in the Design Section,
but this can be edited by clicking in the cell and using the down arrow to select an
th th
alternative from the mean, lower 25 percentile, lower 10 percentile and
th
minimum.If the lower 25 percentile is used for less than 5 tests or the lower
th
10 percentile is used for less than 11 tests, the result may be inaccurate. If DCP
sections have not yet been defined, this cell will be inactive.
Statistical parameter The way in which the CBR value of each layer will be determined. The default is
(CBR) chosen automatically according to the number of DCP tests in the Design Section,
but this can be edited by clicking in the cell and using the down arrow to select an
th th
alternative from the mean, lower 25 percentile, lower 10 percentile and
th
minimum.If the lower 25 percentile is used for less than 5 tests or the lower
th
10 percentile is used for less than 11 tests, the result may be inaccurate. If DCP
sections have not yet been defined, this cell will be inactive.
Proposed option The cell is completed automatically later in the design process from the three
alternatives of Upgrading, Gravelling and Routine Maintenance.
Cost (Currency 000’s) This cell is completed automatically later in the design process with the calculated
cost of the selected design, although a cost is not calculated for the
routinemaintenance alternative.

11.3 Design: Section box

Select a Design Section row in the Pavement design box and click Design. A Design:
Section box, as shown in Figure 11.3, will open for the selected Design Section. If the
design traffic is zero or greater than 3 million equivalent standard axles, DCP data is not
available, DCP Sections have not yet been defined or subgrade was not identified in any
of the DCP tests, a warning message will be generated and the Upgrading design option
will not be available.

Figure 11.3 Design (Section box)

The box has seven panels and a number of buttons which allow the design to be
completed.

11.3.1 Design Options

One of three design alternatives should be selected for each Design Section: Upgrading,
which allows the pavement to be structurally designed with a sealed surface; Gravelling
in response to a currently thin gravel surface; and Routine Maintenance if no other work
is required. Upgrading is not available if DCP Sections have not been defined

11.3.2 Cross Section

Up to three cross sections were defined during the Design and Costs Data entry stage.
Select which cross section should be used for the design. Wider cross sections will
require more material and will cost more to construct.
 11.3.3 Existing Pavement
This panel displays the thickness and CBR value of the base and sub-base layers
derived from the DCP data using the statistical parameters described above. If a base or
sub-base was not defined in every test in the Design Section, a zero will be seen in the
relevant cell.

The design process is based upon comparing the current pavement with the required
pavement for a defined traffic and subgrade strength. If the layers of the current
pavement are weaker than the required pavement, it may be necessary to reassign a
base layer as sub-base or subgrade or a sub-base layer as subgrade so that it meets
the required specification, and then to add higher strength material on top in order to
produce the required pavement. This panel allows layers to be reassigned as required.

The required pavement is seen by clicking the Design Catalogue button. This generates
an array of pavements, each of which is appropriate for a combination of design traffic
and subgrade strength. After selecting the appropriate pavement, reassign the current
pavement layers by clicking the down arrow in the third column of this panel.
Box 11.1 below provides guidance on how to reassign pavement layers.

If a current pavement layer will carry out the same function (base, sub-base or subgrade)
in the proposed pavement, it is recommended that this is identified in the appropriate cell
in the Reassign column.

Box 11.1 Reassigning existing pavement layers

The design process within UK DCP 3.1 involves comparing current base and sub-base layers
with the required layers in the proposed pavement and, based on their strength and thickness,
reassigning them as base, sub-base or subgrade in the proposed pavement. This comparison
requires the thickness and strength of different pavement layers from the analysis of DCP data,
the condition data of the road and a catalogue of pavement designs which are appropriate for a
range of design traffic levels and subgrade strengths. If during this process the material in the
existing pavement is to be used as a base or sub-base in the proposed pavement design, it is
recommended that the DCP tests be checked using destructive sampling and laboratory soaked
CBR tests to ensure the material conforms to the appropriate design chart.

Working upwards from the upper surface of the subgrade, the current and the proposed
pavements are compared. The first layer of the proposed pavement is observed: this may be the
sub-base or selected fill. Its thickness and strength are noted. The first layer of the current
pavement is examined. Is it as thick as the proposed layer and is its strength as high? If its
strength is too low, it cannot be equivalent to the proposed layer and must therefore be assumed
to form part of the subgrade and the next layer up should be examined for thickness and
strength. If its strength is sufficient but the layer is too thin, it can be equivalent to the proposed
layer, but its thickness must be increased by incorporating a portion of the next layer up. Although
UK DCP 3.1 does not allow a layer to be split and a portion to be incorporated into the layer
below and a portion retained for use in higher layers, the user may choose to adopt this approach
and keep track of the layers and their partial reassignment on paper. If the strength and thickness
are sufficient, the two layers are equivalent and the comparison can proceed to the next layer up
in each pavement.

After the first layer of the proposed pavement has been matched with one or more layers of the
current pavement, the second layer up of the proposed pavement is compared with the remaining
layers, or portions of layers, of the current pavement in the same manner as above. This process
continues until there are no more unmatched layers in the current pavement.

It is then necessary to match the layers in the proposed pavement by adding new layers to the
current pavement of the required strength.

For example, consider a road in an area with a Weinert N value of more than 4 with subgrade of
CBR 6% and a design traffic of 1 mesa. The current pavement has a 100 mm base of CBR 50%
and a 180 mm sub-base of CBR 30%. For the design traffic of 1 mesa and subgrade of CBR 6%,
the Design Catalogue recommends a 200 mm thick base layer of CBR 80% and 275 mm of sub-
base of CBR 30%. Comparing the current and proposed pavements, the sub-base in the
proposed pavement must be matched with firstly the 180 mm of sub-base in the current
pavement and secondly the 100 mm of base. Therefore a new base layer of 200 mm and of CBR
80% must be added to provide a complete match to the proposed pavement.

It is noted that this method is unable to compare a thin strong layer with a thick weak layer. UK
DCP 3.1 recommends that for a current layer to be comparable with a required layer, it must have
at least the thickness and at least the strength of the required layer. If comparison between a thin
strong layer and a thick weak layer is required, the user should use other techniques which are
beyond the scope of this Manual.

11.3.4 Parameters to use with design catalogue

The required pavement is selected from the Design Catalogue according to the design
traffic and the subgrade strength. The design traffic is calculated from the traffic data and
the cross section which has been selected for the design (since traffic which overlaps
the centre line on a narrow carriageway raises the design traffic). If the cross section is
changed and the design traffic increases above 3 million equivalent standard axles, a
warning message will be generated and the Upgrading design option will not be
available. The subgrade strength is calculated according to design traffic and the
number of DCP tests in the Design Section according to Table 11.1.

Table 11.1 Subgrade CBR

Design traffic
No of tests Statistical parameter for subgrade CBR
(mesa)

>5 Mean CBR excluding tests with zero CBR

<0.3
up to 5 Minimum CBR excluding tests with zero CBR

>5 25th percentile excluding tests with zero CBR

0.3 - 0.5
up to 5 Minimum CBR excluding tests with zero CBR

>10 10th percentile excluding tests with zero CBR

> 0.5
up to 10 Minimum CBR excluding tests with zero CBR
 11.3.5 Proposed Pavement
After comparing the current pavement layers with those of the proposed pavement, it
may be necessary to add new layers to the pavement to match the required design. The
table in this panel allows new layers to be added.

The lower portion of the table displays the current layers of the pavement including the
outcome of any reassignment. Complete the upper portion of the table with the required
thickness of each new layer. If a layer cannot be added, for example, if a current base
layer has been reassigned as a sub-base, it will not be possible to add fill or improve the
subgrade and the cells will therefore be grey and inactive. Subgrade improvement refers
to the depth of current weak subgrade material which is stabilised in situ. At this stage
material strength is not considered.

The final row of the table displays the current total of the designed pavement, including
reassigned and new layers.

11.3.6 Carriageway Surfacing and Materials

After adding new layers of specified thicknesses to the pavement, it is necessary to
specify their strength. Since it is assumed that sub-base and fill always have CBR values
of 30% and 15% respectively, it is necessary to specify the strength of only the base
(from 80%, 65%, 55%, 45% and gravel wearing course), taking this from the required
pavement in the Design Catalogue. This panel allows this strength to be entered. The
panel also allows a bituminous surfacing to be selected for the carriageway and, if
gravelling has been selected as a design option, allows the gravel thickness to be
specified. A warning will be generated if the total gravel thickness is less than 150 mm.

11.3.7 Shoulder Surfacing and Materials

The final part of the design process is to select which surfacing type, if any, will be used
on the shoulder, its width (up to the value given in the selected cross section) and, when
necessary, its thickness and which material will be used as fill to provide any necessary
additional width. This panel allows these selections to be made. If the shoulder is paved,
the designed base and sub-base layers will be extended into the shoulder, otherwise the
entire shoulder will be constructed using the selected fill.

11.4 Buttons
A number of buttons are present in Design: Section box.

Help Opens this Manual at the appropriate section

Design Opens one of the two Design Catalogues, as shown
Catalogue in Figure 11.4 or Figure11.5 depending on the Weinert N value of the
region in which the road is located. Both charts show an array of
pavements, each of which is appropriate for a combination of design traffic
and subgrade strength.
Design Opens the Design Sections box for review to ensure that the proposed
Sections pavement is suitable for the road environment.
OK Checks that all necessary information has been entered and saves the
design. This also checks that the design has sufficient crown height.
Cancel Closes the Design: Section box and returns to the Pavement design box
without saving the changes that have been made since the box was
created or opened for editing. A box is generated seeking confirmation
that the changes should be saved.
Edit Allows editing of a pavement design which has already been completed
Closes the Design: Section box and returns to the Pavement design box.
Close The final two columns of the Pavement design box will now be complete
with the selected design option and the cost of the design for the section
which has just been carried out.

Figure 11.4 Design catalogue (2<N<4)

 Figure 11.5 Design catalogue (N>4)

Click OK followed by Close to return to the Pavement design box. The final two columns
of the Pavement design box, as shown in Figure 11.6, will now be complete with the
selected design option and the cost of the design for the section which has just been
carried out. In the case of Figure 11.6, designs have been completed for all three Design
Sections.

Figure 11.6 Pavement design box – after design

The Pavement design box can be closed, saving the completed work, before a design
has been produced for all Design Sections. When designs have been produced for all
Design Sections, it is possible to produce various reports as described in Chapter 12.
Click Close in the Pavement design box to return to the Project Manager. Today’s date
will be seen under Pavement Design in the Design Status panel (Figure 11.7).

Figure 11.7 Project Manager (after pavement design)

11.5 Estimation of quantities

Most aspects of the cost estimation have been covered above. Regarding formation,
quantities and costs are estimated separately for the selected fill and subgrade
improvement. Subgrade improvement is estimated on the assumption that the specified
thickness of the current subgrade will be processed with lime or cement.
12 Reporting
12.1 Introduction
The final function of UK DCP 3.1 is the production of reports both for printing or export.
All reports are selected from the Report menu at the top of the main window. They can
be zoomed-in by double clicking with the left button and zoomed-out by double-clicking
with the right button.

There are seven buttons at the bottom of each report.

Help Open this manual on the screen at the appropriate section.

Reset Returns to the top of the first page of the selected report.
Back If a report occupies more than one page, this button displays the previous page.
Next If a report occupies more than one page, this button displays the next page.
Print Generate a standard Print box. Select the printer and page and print as normal.
Export Generate an Export box (Figure 12.1). The report can be exported in one of four
formats: Windows Metafile (for use as a non-editable image), HTML (for use in a
website), Clipboard (for temporary storage and pasting) and CSV (for use in a
spreadsheet). Select the required format and click OK. Click Help to open this manual
on the screen and Cancel to return to the report. Note that reports which are
incompatible with a spreadsheet cannot be exported in CSV format. Note also that
exporting as a metafile or with the clipboard will export only the current page.
Close Close the report.

Figure 12.1 Export box

UK DCP 3.1 can produce eight reports at various stages during the analysis, calculation
and design process. Some reports contain information from just one test; others contain
information from an entire project.
12.2 Penetration Data report
This report (Figure 12.2) can be produced after the penetration data has been entered.
Click Penetration Data in the Report menu and select the range of tests to be included in
the report.

Figure 12.2 Penetration Data Report

The Report has the following six elements.

• A header showing the UK DCP version number, the title of the report and the
project name.
• A summary of test details, cone angle, and upper layer information.
• A table of original penetration data, including the penetration rate between points.
• Remarks if any were entered in the Site Details panel during data input.
• Information about drilled layers and the use of an extension rod.
• A footer showing when the report was produced and the page number of the
report. This report may occupy more than one page.
12.3 Layer Strength Analysis report

Click Layer Strength Analysis in the Report menu and select the range of tests to be
included in the report. If the Structural Numbers have been calculated, they will be
displayed (Figure 12.3); if only layer analysis has been carried out, only layer
thicknesses and strengths will be displayed; if layer analysis has not yet been carried out,
a report cannot be produced for that test. As this report is not compatible with a
spreadsheet, it cannot be exported in CSV format.

Figure 12.3 Layer Strength Analysis report

The Report may include up to nine elements, depending on how far the analysis and
calculations have progressed.
• A header showing the UK DCP version number, the title of the report and the
project name.
• A summary of test details, cone angle, and information relating to the upper layer.
• A Layer Boundaries Chart.
• A CBR Chart showing the CBR value of each test point and the CBR value of
each identified layer.
• A Layer Properties table showing number, penetration rate, CBR (%) (not
reduced to its limiting value of 150 or 50), thickness, depth to underside of layer,
position (Base, Sub-base, etc), strength coefficient and SN, SNC and SNP for
each Test layer. Note that SNC and SNP of the subgrade is not given in this
table as these are composite values for the subgrade and cannot be calculated
for separate subgrade Test layers.
• A Pavement Strength table showing SN, SNC and SNP for each pavement layer
and for the entire pavement.
• The relationship which was used to convert the penetration rate to a CBR value,
from those listed in 4.5.1.
• Space for the name of the producer of the report to be written.
• A footer showing when the report was produced and that it occupies a single
page.
12.4 Tests Summary report
This report (Figure 12.4) can be produced at any stage in the analysis and design
process. The report displays as much information as is available for each test.
Click Tests Summary in the Report menu.

Figure 12.4 Test Summary Report

The Report has the following three elements.

• A header showing the UK DCP version number, the title of the report and the
project name.
• A table summarising the test details, Upper layers and Test layers and calculated
pavement strengths of each test in the project.
• A footer showing when the report was produced and the page number of the
report. This report may occupy more than one page.
12.5 Section Summary report
This report (Figure ) can be produced after DCP Sections have been defined.
Click Section Summary in the Report menu. As this report is not compatible with a
spreadsheet, it cannot be exported in CSV format.

Figure 12.5 Section Summary Report

The Report has the following five elements.

• A header showing the UK DCP version number, the title of the report and the
project name.
• A summary of the number of tests used for the sectioning and where they were
located.
• A chart containing a series of parallel horizontal bars, one for each parameter
used when sectioning the project, and bold perpendicular lines to show where
DCP Section boundaries have been defined. The chart is the same as the chart
in the Section Summary box in Figure 8.8.
• Space for the name of the producer of the report to be written.
• A footer showing when the report was produced and that it occupies a single
page.
12.6 DCP Section Properties report
This report (Figure 12.6) can be produced after DCP Sections have been defined.
Click DCP Section Properties in the Report menu.

Figure 12.6 DCP Section Properties Report

The Report has the following four elements.

• A header showing the UK DCP version number, the title of the report and the
project name.
• A summary of the number of tests used for the sectioning and where they were
located.
• A table showing, for each Design Section, the start and end chainages, its length,
the number of test within it, and a statistical analysis of nine strength and
thickness parameters. This table is similar to that in the DCP Section Properties
box in Figure 8.7.
• A footer showing when the report was produced and the page number of the
report. This report may occupy more than one page.
12.7 Pavement Design report
This report (Figure ) can be produced after the design has been completed for all Design
Sections. Click Pavement Design in the Report menu.

Figure 12.7 Pavement Design Report

The Report has the following four elements.

• A header showing the UK DCP version number, the title of the report and the
project name.
• The Design Life of the project and the Weinert N value of the region.
• A large table containing the following information for each Design Section:
section dimensions, number of DCP tests and road type; intended degree of
improvement; traffic details; existing pavement details; proposed cross section
details; and the designed pavement improvements including layer types and
thicknesses and any necessary reassigned layers.
• A footer showing when the report was produced and the page number of the
report. This report may occupy more than one page.
12.8 Bill of Quantities report
This report (Figure ) can be produced after producing design for all the Design Sections.
Click Bill of Quantities in the Report menu.

Figure 12.8 Bill of Quantities Report

The Report has the following four elements.

• A header showing the UK DCP version number, the title of the report and the
project name.
• A summary of the number of sections in the project and the project cost.
• A table containing the following information for each Design Section: start
chainage; end chainage; required activities; for each activity, the quantity and
costs; and, for each Design Section, the total cost.
• A footer showing when the report was produced and the page number of the
report. This report may occupy more than one page.
12.9 Maintenance report

This report (Figure ) can be produced after adding Survey Data. Click Maintenance
Report in the Report menu.

Figure 12.9 Maintenance Report

The Report has the following four elements.
• A header showing the UK DCP version number, the title of the report and the
project name.
• A summary of the project length and number of structures within the project.
• A Drainage table showing the chainage along the road, condition of drain and the
preferred action.
• A Structures table showing the chainage, structure type, condition and the
preferred action.
• A footer showing when the report was produced and the page number of the
report. This report may occupy more than one page.
13 References
1. Jones C R and J Rolt (1991). Operating instructions for the TRL dynamic cone
penetrometer (2nd edition). Information Note. Crowthorne: Transport Research
Laboratory
2. User Manual, WinDCP 5.0 software, 2001. CSIR, South Africa
3. Kleyn K G & P F Savage (1982). The application of the pavement DCP to determine
the bearing properties and performance of Road Pavements. International Symposium
on Bearing Capacity of Roads and Airfields. Trondheim, Norway
4. Transport and Road Research Laboratory (1990). A users manual for a program to
analyse dynamic cone penetrometer data. Overseas Road Note 8. Transport Research
Laboratory, Crowthorne
5. MacNeil D J and D P Steele (2002). Granular and bituminous planings mixtures for
capping. TRL Report TRL523. TRL Limited, Crowthorne, UK
6. Smith R B and Pratt D N (1983). A field study of in situ California bearing ratio and
dynamic cone penetrometer testing for road subgrade investigations. Australian Road
Research 13(4) December 1983 pp285-294. (Australian Road Research Board)
7. Van Zyl, A T Visser and J A du Plessis (1995). Guidelines for Structural Design of
Low-Volume Rural Roads in Southern Africa. Conference proceedings of sixth
International Conference on Low-Volume Roads, Minneapolis, Minnesota, Volume 2.
Transportation Research Board, USA
8. American Association of State Highway and Transportation Officials (AASHTO)
(1993). AASHTO guide for design of pavement structures. Washington DC: AASHTO
9. Hodges J W, J Rolt and T.E Jones (1975). The Kenya road transport cost study:
research on road deterioration. TRRL Research Report LR 673.Transport and Road
Research Laboratory, Crowthorne,UK
10. Rolt J and C C Parkman (2000). Characterisation of Pavement Strength in
HDM III and changes adopted for HDM-4. 10th International Conference of the Road
Engineering Association of Asia andAustralia
11. Morosiuk G, M J Riley, W D O Paterson, J B Odoki, J P Covarrubibus
(2000). Modelling road deterioration and works effects. Volume 6 of the HDM 4 series of
publications. PIARC ISOHDM
12. Gourley C S and P A K Greening (1999). Performance of Low Volume Sealed
Roads: Results and Recommendations from Studies in Southern Africa. TRL Project
Report PR/OSC/167/99, Transport Research Laboratory, Crowthorne, UK.
13. Department of Roads, Ministry of Transport & Energy, Government
of Zimbabwe (1998). A Pocket Guide to Road Design for Low-Volume
Roads. Harare, Zimbabwe.
Appendix A: DCP Test Data Form
Appendix B: Survey Data Sheet