Contents:
The results of OPILE analyses can be exported in a number of ways, including:
A customisable report to Microsoft Word. A customisable report to Microsoft Excel. Direct copying and pasting of information to other programs. Production of a pile model for input to structural analyses.
A customisable report to Microsoft Word.
A customisable report to Microsoft Excel.
Direct copying and pasting of information to other programs.
Production of a pile model for input to structural analyses.
The advantage of producing a report into Word or Excel is that these reports do not require specialised knowledge of OPILE in order to be able to interpret the results. Therefore, they are ideal for providing results to colleagues. The following sections explain how the reporting processes work.
The Word reporter creates a file in Microsoft Word which summarises the OPILE analyses that have been carried out. This type of report production enables easy development of input for reports or it can be used to pass results on to colleagues. It is controlled by a series of options, however generally the default report file should prove adequate. It reports the input parameters, including pile properties, axial and lateral soil inputs, axial capacity, pile response curves and the output of load-displacement analyses. Word Reporter produces a format would not require special knowledge of the software in order to determine how the pile analyses had been carried out and it is considerably easier to read than the text file formats often produced by similar software.
The Word report which is output will be placed into the same directory as the current OPILE file that is open. The report may require some editing for aesthetic reasons before it is used elsewhere. The report is based upon the report template (OPILE Output Template.dot) which is contained within the OPILE program directory. This report template can be customised by users and this customisation might include things such as the company logo.
The actual output of the Word report is primarily controlled in two separate places. The first is the Word tab in the reporter dialogue box, where override values to the title, template and folder where the file is written can be entered. There is also the option to control the way that text boxes, combo boxes and check boxes are output. In OPILE many text boxes and combo boxes turn yellow if input is required or used. The two options (see picture above) are to output the contents of these controls regardless of whether they are used in the current analysis, or to only output the contents of the controls that are actually used in the analyses.
The other place which controls the output of the report are the check boxes which are selected under the Analysis Options section in the main OPILE window. Where one of these check boxes is checked the relevant output will be included in the Word report.
Note: Previous versions of OPILE required Microsoft Word 2003 to create the reports. Changes have now been made and OPILE has no dependency on Microsoft Word and it does not need to be installed, apart from to view the reports that are created.
The Excel reporter exports the results of OPILE analyses into a Microsoft Excel file. The Excel file is generated from a customisable template file (Report Excel Template.xls) which is contained within the OPILE program directory. This template can be customised to produce OPILE results formatted for inclusion into reports. It is still possible to use the Excel exporter even if Excel is not installed, and the files it produces should be readable by any version from Excel 2003 onwards.
The actual output of the Excel report is primarily controlled in two separate places. The first is the Excel tab in the reporter dialogue box, where override values to the title, template and folder where the file is written can be entered. There is also the option to control the way that text boxes, combo boxes and check boxes are output. In OPILE many text boxes and combo boxes turn yellow if input is required or used. The two options (see picture above) are to output the contents of these controls regardless of whether they are used in the current analysis, or to only output the contents of the controls that are actually used in the analyses.
The other place which controls the output of the report are the check boxes which are selected under the Analysis Options section in the main OPILE window. Where one of these check boxes is checked the relevant output will be included in the Excel report.
In generating the Excel report OPILE makes extensive use of “Named Ranges” within Excel and it is to these that information will be written. The use of named ranges, rather than cell references, means that users can layout the Excel report as they wish it to appear. If OPILE does not find the named range when it attempts to write something to Excel then that data will not be written, neither should this cause an error. The worksheet names in Excel can also be changed. If the named range in Excel is too small for the information to be pasted from OPILE then some data will be missing. The named ranges can be moved around within Excel (by dragging or cutting and pasting) to customise the report.
By default OPILE will use its own default Excel template stored in the program directory, however, OPILE will also allow the selection of a particular report template to use. For example, an Excel report may be customised for a particular project and it may be required to base all project reports on that modified template. Additionally the report can be customised by the inclusion of plots of the data as required.
The Excel report will be written to the same folder as the current OPILE file, however, it is also possible to specify an alternative directory.
In order to write the information the parameter and the named range is given below:
OPILE parameter name
OPILE Tab
Type of output
number of rows
Number of columns
Named range in Excel template
Date
General
Text
1
Project Title
Project
Client
Engineer
Location
Project No
Project_No
Notes
Pile Penetration
Penetration
Pile Length
Full_Length
Use a different length to the penetration
Boolean
UseDiffLengthToPenetration
General Scour
GeneralScour
Local Scour
LocalScour
Overburden Reduction Depth
OverburdenReductionDept
Pile Property Data
Grid
10
11
Prop_Data
Annular Area Override
AnnularAreaOverride
Total Pile Weight
TotPileW
Material Property Data
5
Mat_Data
TZ, QZ Curves and Axial Capacity
AnAxCurves
Auto Generate Axial Load Cases
AutoAxLoad
Axial Load Displacement Response
AxLDResp
PY Curves
AnLatCurves
Auto Generate Lateral Load Cases
AutoLatLoad
Lateral Load Displacement Response
LatLDResp
Soil Resistance to Driving
AnSRD
Conductor Mode
ConductorMode
Retain Old Results
RetainOldResults
Iteration Limit
IterationLimit
Uncouple TZ/QZ and PY Generation from Load Displacement Response
UncoupleLDResp
Analysis Notes
AnalysisNotes
Include Border on Charts
InclBorder
Include Location Box on Charts
InclLocation
Include Project Number Box on Charts
InclProjectNo
Include Project Name Box on Charts
InclProject
Include Client Name Box on Charts
InclClient
Reshape Chart for Copying
ChartReshape
Axial Capaity Units
UnitAxCap
End Bearing Units
UnitEndBearing
Axial Soil Input Data
Axial Soil
100
24
AxialSoil
K Sand Compression
K_Comp
K Sand Tension
K_Tens
Sand Friction Multiplier
SandFrictionMultiplier
Clay Friction Multiplier
ClayFrictionMultiplier
ICP Base Condition
ICPBaseCondition
TZ Method
TZMethod
CPT Diameter
CPTDiam
Pile roughness
Pile_Roughness
TMod
ZMod (TZ Curve)
ZMod
Optional End Bearing Limit
OptEndLimit
Optional Skin Friction Limit
OptSkinLimit
zpeak/D
ZpeakOverD
Clay Alpha
ClayALPHA
QMod
ZMod (QZ Curves)
ZqMod
Clay Exp 1
ClayExp1
Clay Exp 2
ClayExp2
IP Lower Limit
IPLowerLimit
IP Upper Limit
IPUpperLimit
IP Divisor
IPDivisor
IP Subtractor
IPSubtractor
n for PSI>1.0
nForPSI
Smooth Plugged End Bearing
CorrectEndBearing
Plugged End Bearing Correction - Above Distance
EndBearingAboveDistance
Plugged End Bearing Correction - Below Distance
EndBearingBelowDistance
Plugged End Bearing Correction - Increment
EndBearingIncrement
Smooth Unplugged End Bearing
CorrectEndBearing_U
Unplugged End Bearing Correction - Above Distance
EndBearingAboveDistance_U
Unplugged End Bearing Correction - Below Distance
EndBearingBelowDistance_U
Unplugged End Bearing Correction - Increment
EndBearingIncrement_U
Lateral Soil Input Data
Lateral Soil
27
LateralSoil
Cyclic or Static
CyclicOrStatic
P Modifier
PMod
Y Modifier
YMod
Stiff CLAYAPI Factor
StiffCLAYFactor
Stiff CLAYAPI Limit Strength
StiffCLAYStrength
Rock Mass Shear Strength as Fraction of UCS
RockMassStrengthAsPercent
Fragio Transition Depth
FragioTransitionDepth
x0 for Wesselink and Dunnavant
x0
Dunnavant Cycles
DunnavantCycles
Rock Reese97 Krm
RockReeseKrm
Rock Reese97 Top Depth of Rock Layer
RockReeseTopOfRock
Novello Cycles
NovelloCycles
Allow Y Shifts
AllowYShifts
Manually define Xr
Manually_Define_Xr
Manually defined Xr value
Manual_Xr
Modify Y for large diameter piles
Modify_Y_LargeDiameterPile
SRD Soil Input Data
SRD Soil
25
SRDSoil
Main SRD Method
SRD_MAIN
K_STEVENS
Nu - Rock
STEVENS_NU
Upper Bound Residual Lambda - Clay
UB_LAMBDA_RES
Lower Bound Residual Lambda - Clay
LB_LAMBDA_RES
Upper Bound Lambda Maximum - Clay
UB_LAMBDA_MAX
Lower Bound Lambda Maximum - Clay
LB_LAMBDA_MAX
Upper Bound Residual Lambda - Sand, Rock
UB_LAMBDA_RES_SAND
Lower Bound Residual Lambda - Sand, Rock
LB_LAMBDA_RES_SAND
Upper Bound Lambda Maximum - Sand, Rock
UB_LAMBDA_MAX_SAND
Lower Bound Lambda Maximum - Sand, Rock
LB_LAMBDA_MAX_SAND
Colliat Non Degradation Length
COLLIAT_DEGR
ALM Upper Bound Factor
ALM_UBFACTOR
ALM Factor on Sand Friction
ALMFactorSandFriction
ALM Factor on Clay Friction
ALMFactorClayFriction
Include Effect of Installation Weight
InclInstalWeight
Weight 1
HAMMER_WEIGHT1
Weight 2
HAMMER_WEIGHT2
Weight 3
HAMMER_WEIGHT3
Plugged Skin Factor - Sand (UB)
STEVENS_NC_SKINF
Plugged Nc - Clay (UB)
STEVENS_NC
Plugged End Factor - Sand (UB)
STEVENS_UB_END
Unplugged UB Skin Factor
STEVENS_CORUBSAND
Unplugged LB Skin Factor
STEVENS_CORDLBSAND
SRD Custom Input
SRDCustom
Auto Generate Pile Grid
Custom Input
AutoGenPileGrid
Default Grid Increment
DefaultGridIncr
Custom Lateral Grid
200
7
LatGrid
Custom Axial Grid
AxGrid
Custom SRD Grid
SRDGrid
T/Tmax and Z/D Values for TZ Calculation in Clay (API 2000)
8
2
ValTZClay
T/Tmax and Z/D Values for TZ Calculation in Sand (API 2000)
ValTZSand
T/Tmax and Z/Zpeak Values for TZ Calculation in Clay (API RP2GEO)
ValTZClay_RP2GEO
T/Tmax and Z/Zpeak Values for TZ Calculation in Sand (API RP2GEO)
ValTZSand_RP2GEO
Q/Qmax and Z/D Values for QZ Calculation in Clay and Sand (API 2000 and API RP2GEO)
ValQZ
Z/D Values for Axial Load Generation
ValAxOther
P/Pmax and Y/Yc Values for Static PY Calculation in Clay
ValPY
P/Pmax and Y/Yc Values for Cyclic PY Calculation in Clay
ValPY_C
P/Pmax and Y/Yc Values for Cyclic PY Calculation in Clay (Reduced Capacity Zone)
ValPY_C_RedCap
Y/D Values for PY Calculation and Lateral Load Generation
ValLatOther
Custom TZ Curve 1
TZCurve1
Custom TZ Curve 2
TZCurve2
Custom TZ Curve 3
TZCurve3
Custom QZ Curve 1
QZCurve1
Custom QZ Curve 2
QZCurve2
Custom QZ Curve 3
QZCurve3
Custom PY Curve 1
PYCurve1
Custom PY Curve 2
PYCurve2
Custom PY Curve 3
PYCurve3
Locate Axial response Peaks
Load Cases
LocateAxRespPeaks
Include Pile Weight in Axial Analysis
InclPileWeightinAxAn
Type of Load Cases
LCType
Initial Displacement
InitDisp
Displacement Interval for Peaks
DispIntervalPeaks
Iterations to Find Peaks
ItPeaks
Distinct Compression Peak Found Before 0.05D Displacement
CompPeak
Peak Tension Load
PeakTens
Axial Load Cases Input
AxialLoad
Rotation
Grid Point
GridPoint
Axial Load for Lateral Analysis
AxLoadForLatAn
Lateral Load Cases Input
6
LatLoad
TZ Curves - Combined
TZ Curves
400
13
TZCurves
TZ Mid Element Depth
TZDepth
T Points
TZCurvesT
Z Points (TZ)
TZCurvesZ
Top Depth Limit TZ Curves
TZTopDepth
Lower Depth Limit TZ Curves
TZLowerDepth
QZ Curves - Combined
QZ Curves
QZCurves
QZ Mid Element Depth
QZDepth
Q Points
QZCurvesQ
Z Points (QZ)
QZCurvesZ
Top Depth Limit QZ Curves
QZTopDepth
Lower Depth Limit QZ Curves
QZLowerDepth
PY Curves - Combined - Cyclic
12
PYCurvesCYCLIC
PY Curves - Combined - Static
PYCurvesSTATIC
PY Mid Element Depth - Cyclic
PYCyclicDepth
P Points - Cyclic
9
PYCyclicP
Y Points - Cyclic
PYCyclicY
PY Mid Element Depth - Static
PYStaticDepth
P Points - Static
PYStaticP
Y Points - Static
PYStaticY
Top Depth Limit PY Curves
PYTopDepth
Lower Depth Limit PY Curves
PYLowerDepth
Plot Static or Cyclic PY Curves
PYPlotCyclicStatic
AxCap (All Penetrations)
AXCAP
AxCap
AxCap Details (Final Penetration)
Axcap_Single
End Bearing
600
Axcap_End
Skin Friction
4
Axcap_Skin
Overburden
Axcap_Overburden
SRD Output
SRD
SRDOutput
SRD Summary
SRDSummary
SRD Summary Depth
SRDSymmaryDepth
Full Axial Output - Selected Load Case
AXIAL OUTPUT
AxSelectedLC
Full Axial Output - Single Case
AxialFullOutput
Axial Selected Grip Point
AxSelectedGridPoint
Axial Summary
AxialSummaryOutput
Full Axial Output - All Load Cases
10000
Axial_ALL_Cases
Full Lateral Output - Selected Load Case
LATERAL OUTPUT
LatSelectedLC
Full Lateral Output - Single Case
LatFullOutput
Lateral Selected Grip Point
LatSelectedGridPoint
Lateral Summary
LatSummaryOutput
Full Lateral Output - All Load Cases
Lat_ALL_Cases
Sand Replacement Methods
ALLCAP
ALLCAP_Comparison_Sand
Clay Replacement Methods
ALLCAP_Comparison_Clay
Target penetrations
ALLCAP_TargetPenetration
Summary of ALLCAP - Target Penetration 1
ALLCAP_Summary_1
Summary of ALLCAP - Target Penetration 2
ALLCAP_Summary_2
Summary of ALLCAP - Target Penetration 3
ALLCAP_Summary_3
Summary of ALLCAP - Target Penetration 4
ALLCAP_Summary_4
Summary of ALLCAP - Target Penetration 5
ALLCAP_Summary_5
Summary of ALLCAP - Target Penetration 6
ALLCAP_Summary_6
Skin Friction (Single) - Replacement 1
ALLCAP_Single_Friction_1
Skin Friction (Single) - Replacement 2
ALLCAP_Single_Friction_2
Skin Friction (Single) - Replacement 3
ALLCAP_Single_Friction_3
Skin Friction (Single) - Replacement 4
ALLCAP_Single_Friction_4
Skin Friction (Single) - Replacement 5
ALLCAP_Single_Friction_5
Skin Friction (Single) - Replacement 6
ALLCAP_Single_Friction_6
Cumulative Friction Capacity (Single) - Replacement 1
ALLCAP_Single_Cap_1
Cumulative Friction Capacity (Single) - Replacement 2
ALLCAP_Single_Cap_2
Cumulative Friction Capacity (Single) - Replacement 3
ALLCAP_Single_Cap_3
Cumulative Friction Capacity (Single) - Replacement 4
ALLCAP_Single_Cap_4
Cumulative Friction Capacity (Single) - Replacement 5
ALLCAP_Single_Cap_5
Cumulative Friction Capacity (Single) - Replacement 6
ALLCAP_Single_Cap_6
Total Capacity (All penetrations)
PROWEAP
ALLCAP_All_Caps
Source Folder for WEAP Files
WEAP_FOLDER
WEAP Output File Extension
WEAP_FILE_TYPE
Weap Line Identifier
WEAP_LINEID
Number of Lines To Jump Forward
WEAP_NOLINEJUMPS
WEAP File Import
WEAP_FILE_IMP
WEAP_PILE_LENGTH
WEAP_PILE_PENETRATION
Steel Area
WEAP_STEEL_AREA
Hammer
WEAP_HAMMER
Shaft Quake
WEAP_SHAFT_QUAKE
Tip Quake
WEAP_TIP_QUAKE
Shaft Damping
WEAP_SHAFT_DAMPING
Tip Damping
WEAP_TIP_DAMPING
Percent Shaft Resistance
WEAP_SHAFT_RESISTANCE
Source Folder for Driving Records
WEAP_RECORDS_FILE
Driving File Selected for Import
WEAP_DRIVING_FILES
File Delimiter
WEAP_DELIMITER
Row Containing Column Headers
WEAP_ROW_COL_HEADERS
Row Where Import Begins
WEAP_ROW_IMPORT_START
Blow Number
WEAP_COL_BN
Length of Pile in Soil
WEAP_COL_EL
Energy Column (EMX) Averaged
WEAP_COL_EMX
Refusal Criteria
WEAP_PLOTTING_REFUSAL_CRIT
CSX (Max in Increment)
WEAP_COL_CSX
TSX (Max in Increment)
WEAP_COL_TSX
Delete Existing Driving Records
WEAP_DEL_EX_REC
Imported WEAP Results
2000
WEAP_IMP
Imported Driving Records
18
WEAP_RECORD
Axial Chart Warning
AXIAL_WARNING
The structural modelling module in OPILE that can be used to output pile models (i.e. pile parameters, TZ, QZ and PY curves) for input to various structural analyses packages. There are various options that can be used with this, such as the option to include load cases if the structural analysis package allows analysis of a single pile. This means that results of OPILE can be readily compared.
The module outputs the pile model into a text file and the pile response curves are output into the exact format and units which a particular package requires. This saves the, usually quite tedious, process of converting the curves and then either manipulating through software such as Excel or even retyping them in by hand!
Currently the only software which is seamlessly supported is Sacs, although in the interests of developing our software we would be happy to discuss the output of pile models to other publicy available structural analysis software. USFOS is also supported, although this has been tested less and should only be used with some caution.
File description is a text box that allows entry of some descriptive text specifically for the pile model generation. Normally the other information which is entered about an OPILE analysis is included as comments within the pile model file.
There is an option to include load cases, where applicable, if the structural analyses package allows analysis of a single pile. If load cases are included they are extracted from the lateral and axial load case tables. Note that currently only loads applied at the pile head should be included, as not all analysis packages accept loads applied elsewhere on the pile. In addition torsional load cases are not included.
The minimum depth for QZ curves is included as an option to help prevent execessively long structural model files being generated. For instance it might be desirable to define the minimum depth for QZ curves to be 10m above the pile tip, that way only QZ curves for the last 10m of the pile penetration will be generated.
The soil model number is included if it is possible that more than one pile model (each with different soil stratigraphies) will be defined for the same jacket analyses. Using a different soil model number should allow the structural software to differentiate between the models.
It is always recommended that some comparison is made between the output from the structural analysis software and the results of OPILE to ensure that the conversion has been made correctly. There may be some small differences due to the calculation methods implemented in the various software packages that are available.
Batch Control allows the continuous processing or/and reporting of a list of OPILE files. The start a batch run, the Path & Name of the batch run template needs to be provided. The standard batch run procedure consists of:
opening a OPILE file listed in the batch run template, runs “Analyse”, and “Compare Capacities” (*), saves and closes the OPILE file (i)
opening a OPILE file listed in the batch run template,
runs “Analyse”, and “Compare Capacities” (*),
saves and closes the OPILE file (i)
This procedure is repeated as long as all listed files are processed.
(*) only when a target penetration and a replacement combination are provided in the ALLCAP tab.
Alternatives: Within the Batch Control, the user can include the generation of Word or Excel reports for each file.
Requirements for Batch Run Template:
The standard OPILE Batch Run Template (OPILE Batch Run Template.xlsx) is contained within the OPILE program directory. As minimum, the template needs to contain the following Name Variables: Input_Path : OPILE looks in this cell for the path of the listed OPILE files Output_Path : OPILE looks in this cell for the path where to save the OPILE files (when it is the same as the input path, the OPILE files will be overwritten) Title_List : OPILE looks below this cell for the list of OPILE file names RunNo : OPILE looks in this cell for the number of OPILE files the Batch run should contain.
The standard OPILE Batch Run Template (OPILE Batch Run Template.xlsx) is contained within the OPILE program directory.
As minimum, the template needs to contain the following Name Variables:
Input_Path : OPILE looks in this cell for the path of the listed OPILE files
Output_Path : OPILE looks in this cell for the path where to save the OPILE files (when it is the same as the input path, the OPILE files will be overwritten)
Title_List : OPILE looks below this cell for the list of OPILE file names
RunNo : OPILE looks in this cell for the number of OPILE files the Batch run should contain.
Optional named variables are:
Include_List : OPILE will look below this cell, with the same amount of rows below the Title_List cell, and include or not the file in the batch run (this will not change the number in RunNo) Date_List : OPILE will write below this cell, with the same amount of rows below the Title_List cell, the date of the most recent Run
Include_List : OPILE will look below this cell, with the same amount of rows below the Title_List cell, and include or not the file in the batch run (this will not change the number in RunNo)
Date_List : OPILE will write below this cell, with the same amount of rows below the Title_List cell, the date of the most recent Run
By including the necessary named variables into the same Sheet, any Excel file can be used as source of a Batch Run file, as long as the Sheet with the named variables is the ‘active sheet’ when opening the file.