Pontis 5.1.2 User Manual PDF
Pontis 5.1.2 User Manual PDF
2 Users Manual
September 2011
Prepared for AASHTO 444 North Capitol Street, N.W., Suite 249 Washington, D.C. 20001
Prepared by
T A B L E
O F
C O N T E N T S
Table of Contents
CHAPTER 1
1-1 1-2 1-2 1-2 1-3 1-4 1-4 1-8 1-9 Getting Started with Pontis 1.1 What is Pontis? Overview Software Characteristics Major Functions Pontis Modules Pontis Work Flow 1.2 Whats New in Version 4.5 1.3 Whats New in Version 5.1.2
CHAPTER
Inventory and Inspection Data Management 3.1 Important Concepts Representation of Structures Environments Condition Measurement 3.2 Overview of Pontis Inventory and Inspection Data (Version 4.5) Inspection Tab Cards Data Review and Update Procedure 3.3 Adding a New Structure (Version 4.5) Assigning Unique IDs Identifying Structure Units, Elements and Environments Preparing Other Data Creating a New Structure Entering and Updating Structure Unit Information Entering and Updating Roadway Information Entering and Updating NBI and Appraisal Information Creating Elements for the Structure
3-1 3-2 3-2 3-3 3-3 3-4 3-4 3-6 3-8 3-8 3-8 3-8 3-8 3-10 3-11 3-12 3-12
1.4 System Installation and Data Loading Overview (Version 4.5) 1-9 Installation Procedure 1-10 Getting Data Into Pontis 1-11 Configuration and Customization 1-14 1.5 System Installation and Data Loading Overview (Version 5.1.2) 1-16 Installation Procedure 1-17 Getting Data into Pontis 1-17 Configuration and Customization 1-20 1.6 Documentation Guide 1-24
3.4 Reviewing and Updating Inspection Schedules (Version 4.5) 3-14 Updating Inspection Planning and Scheduling Information 3-14 Reviewing Existing Inspection Scheduling Information 3-17 3.5 Entering Inspection Information (Version 4.5) Creating a New Inspection Modifying Element Information Entering Condition Information and Inspector Notes Entering Inspector Work Candidates Entering Agency Information Entering Multimedia Document Links Updating Inventory, Appraisal and Schedule Information Updating the Pontis Models to Reflect New Inspections 3.6 Using Paper Forms for Inspection Data Entry (Version 4.5) 3.7 Calculating NBI Ratings from Element Conditions (Version 4.5) 3.8 Calculating Sufficiency Ratings (Version 4.5) 3.9 Performing Data Validation (Version 4.5) 3.10 Deleting an Inspection (Version 4.5) 3.11 Deleting a Structure (Version 4.5) 3.12 Exporting Inventory and Inspection Data (Version 4.5) Exporting NBI Files Exporting or Checking Out PDI Files 3.13 Check-In/Check-Out Procedures for Field Inspections (Version 4.5) 3.14 Inspection Reports (Version 4.5) 3.15 Overview of Inventory and Inspection Data (Version 5.1.2) 3-18 3-18 3-19 3-20 3-21 3-25 3-25 3-27 3-27 3-28 3-29 3-31 3-34 3-35 3-36 3-37 3-37 3-38 3-39 3-41 3-43
CHAPTER
System Basics 2.1 Logging On (Version 4.5) 2.2 The Pontis Desktop (Version 4.5) Selecting a Module Parts of the Desktop 2.3 Finding and Selecting Structures (Version 4.5) Finding a Structure Looking at a Subset of Structures 2.4 Viewing and Printing Pontis Reports (Version 4.5) 2.5 Logging On (Version 5.1.2) 2.6 The Pontis Desktop Selecting a Module Parts of the Desktop
2-1 2-2 2-3 2-3 2-3 2-12 2-12 2-13 2-15 2-17 2-18 2-18 2-18
2.7 Finding and Selecting Structures (Version 5.1.2)2-25 Finding a Structure with Filters 2-25 Finding Structures with Layouts 2-31 2.8 Viewing and Printing Pontis Reports (Version 5.1.2) 2.9 Site Map (Version 5.1.2) 2-37 39
ii
T A B L E
O F
C O N T E N T S
Inspection Tab Data Review and Update Procedure 3.16 Adding a New Structure (Version 5.1.2) Assigning Unique IDs Identifying Structure Units, Elements and Environments Preparing Other Data Creating a New Structure Entering and Updating Structure Unit Information Entering and Updating Roadway Information Entering and Updating NBI and Appraisal Information Creating Elements for the Structure
Developing Cost Models 4.4 Running the Preservation Optimization 4.5 Health Index Targeting 4.6 Reviewing Preservation Results 4.7 Preservation Results Reports
CHAPTER
Bridge Program Simulation 3-50 3-50 5.1 Overview of the Simulation Developing a Network Improvement Strategy Developing a Program 5.2 Developing Functional Improvement Policy Standards Defining Standards in a Policy Set Determination of Improvement Needs 5.3 Modifying Improvement Benefits and Costs Entering Cost and Benefit Assumptions for a Cost Set
3.17 Reviewing and Updating Inspection Schedules (Version 5.1.2) 3-53 Updating Inspection Planning and Scheduling Information 3-53 Reviewing Existing Inspection Scheduling Information 3-55 3.18 Entering Inspection Information (Version 5.1.2) 3-56 Creating a New Inspection 3-56 Modifying Element Information 3-57 Entering Condition Information and Inspector Notes 3-58 Entering Inspector Work Candidates 3-59 Entering Agency Information 3-61 Entering Multimedia Document Links 3-63 Updating Inventory, Appraisal and Schedule Information 3-64 Updating the Pontis Models to Reflect New Inspections 3-64 3.19 Using Paper Forms for Inspection Data Entry (Version 5.1.2) 3.20 Calculating NBI Ratings from Element Conditions (Version 5.1.2) 3-65 3-65
5.4 Modifying Improvement Modeling Assumptions 5-10 Defining Assumptions in an Improvement Set 5-10 5.5 Entering Simulation Rules Overview of Simulation Rules Building Blocks of Rules Application of Rules Defining Scoping Rules Defining Look Ahead Rules Defining Major Rehab Rules Defining Agency Policy Rules 5.6 Developing a Budget 5.7 Defining and Running Scenarios Creating a New Scenario Modifying Scenario Information Running a Scenario Deleting a Scenario 5.8 Analyzing Scenario Results Overview Using the Results Module 5.9 Program Simulation Reports 5-12 5-12 5-13 5-13 5-14 5-16 5-17 5-19 5-22 5-24 5-25 5-25 5-28 5-29 5-30 5-30 5-30 5-34
3.21 Calculating Sufficiency Ratings (Version 5.1.2) 3-65 3.22 Performing Data Validation (Version 5.1.2) 3.23 Deleting an Inspection (Version 5.1.2) 3.24 Deleting a Structure (Version 5.1.2) 3.25 Exporting Inventory and Inspection Data (Version 5.1.2) Exporting NBI Files Exporting XML Files Exporting or Checking Out PDI Files 3.26 Check-In/Check-Out Procedures for Field Inspections (Version 5.1.2) 3.27 Inspection Reports (Version 5.1.2) 3-67 3-69 3-70 3-71 3-71 3-71 3-72 3-73 3-76
CHAPTER
Project Planning
6-1
CHAPTER
6.1 Project Planning Fundamentals 6-2 Project Planning Terminology 6-2 Relationship Between Programs and Scenarios 6-2 The Project Planning Desktop 6-4 4-1 4-3 4-4 4-4 4-4 4-10 4-10 6.2 Setting up Funding Sources Creating a New Funding Source Modifying Funding Source Information 6.3 Setting up Programs Creating a New Program Modifying Program Information 6.4 Reviewing Work Candidates Overview of the Work Candidates Tab Finding and Selecting Work Candidates 6-10 6-10 6-11 6-12 6-12 6-14 6-15 6-15 6-16
Developing an Optimal Preservation Policy 4.1 Overview of Pontis Preservation Models 4.2 Modifying Deterioration Models Introduction to Pontis Deterioration Models Developing Deterioration Models 4.3 Modifying Cost Models Introduction to Pontis Cost Models
iii
T A B L E
O F
C O N T E N T S
6.5 Creating Projects 6-20 Creating Projects for Individual Bridges from Work Candidates 6-20 Creating Multi-Bridge Projects from Work Candidates 6-22 Batch Mode: Automatically Generating Projects from Work Candidates 6-23 Creating Projects Without Using Work Candidates 6-25 6.6 Using the Bridge Analysis Screen Reviewing Needs and Work for a Structure Running a Bridge Analysis Simulation Creating Projects from the Bridge Analysis Screen 6-29 6-29 6-30 6-31
7.12 Pontis Database Administration (Version 5.1.2) 7-30 7.13 Viewing and Modifying Data Field Coding (Version 5.1.2) 7-32
7.14 Viewing and Modifying Element Specifications (Version 5.1.2) 7-34 7.15 Viewing and Modifying Environment, Materials and Element Classification Definitions (Version 5.1.2) 7-37 7.16 Viewing and Modifying Action Definitions (Version 5.1.2) Modifying Action Type Definitions Modifying Flexible Action Definitions 7.17 Viewing and Modifying Configurable Options (Version 5.1.2) 7-39 7-39 7-40 7-41
6.7 Reviewing Projects 6-32 Finding a Project 6-32 Selecting Which Projects Appear on the Project List 6-32 6.8 Ranking Projects 6.9 Viewing and Updating Project Information Updating Project Information Adding, Removing, and Moving Project Work Items Using the Tree Deleting Projects Using the Shift Button to Change Information for Groups of Projects Combining Projects Splitting Projects 6.10 Project Reports 6-34 6-36 6-36 6-36 6-37 6-37 6-38 6-40 6-42
7.18 Viewing and Modifying the Cost Index (Version 5.1.2) 7-42 7.19 Using the Pontis Formula Editor (Version 5.1.2) 7-44 Trigger Fields 7-44 Maintaining Formula Sets 7-44 7.20 Configuring Export Options (Version 5.1.2) 7.21 Modifying the Data Dictionary (Version 5.1.2) 7-47 7-48
7.22 Removing Bridge Checked Out Status (Version 5.1.2) 7-50 7.23 Renumbering the Bridge Brkey (Version 5.1.2) 7-51 7.24 Configuring the Pontis 5.1.2 Application Logger (Version 5.1.2) 7-52
7.25 Configuring Navigation & Field Level Security (Version 5.1.2) 7-53 7.26 Configuration Reports 7-58
CHAPTER
Configuring and Customizing Pontis 7.1 Configuration Module Overview (Version 4.5)
7-1 7-2
CHAPTER
7.2 Setting Up Pontis Users and Privileges (Version 4.5) 7-3 7.3 Viewing and Modifying Data Field Coding (Version 4.5) 7-5
Navigation and Field Level Security 8.1 Customizing Standard Inspection Screens 8.2 Creating Agency Inspection Screens 8.3 Creating Agency Non-Inspection Screens 8.4 Creating Role-Based Security Profiles 8.5 Applying Navigational Security
7.4 Viewing and Modifying Element Specifications (Version 4.5) 7-7 7.5 Viewing and Modifying Environment, Materials and Element Classification Definitions (Version 4.5) 7-11 7.6 Viewing and Modifying Action Definitions (Version 4.5) Modifying Action Type Definitions Modifying Flexible Action Definitions 7.7 Viewing and Modifying Configurable Options (Version 4.5) 7-13 7-13 7-13 7-16
7.8 Viewing and Modifying the Cost Index (Version 4.5) 7-17 7.9 Using the Pontis Formula Editor (Version 4.5) Trigger Fields Maintaining Formula Sets 7.10 Configuring and Customizing Pontis (Version 5.1.2) 7.11 Setting Up Pontis Users and Privileges (Version 5.1.2) 7-19 7-19 7-19 7-22 7-25
iv
Our agency has received a copy of the new Pontis Installation CD, and we want to know how to get started with the system. What can this software do for us? What has changed since the last version? How do we install it? How do we get our data into it? How can it be customized for our particular needs? Where do we look for more information? Which functions are supported by which version?
he Pontis Users Manual is organized to include content for both Pontis 4.5 and the new version, Pontis 5.1.2. While Pontis 5.1.2 is the newer version, it only implements the inventory and inspection aspects of Pontis, while version 4.5 is still necessary for needs assessment, strategy development and project and program development. Future versions of Pontis 5.1.2 will incorporate all Pontis 4.5 functionality. This manual includes text to explain and clarify the differences between Pontis 4.5 and 5.1.2. This chapter provides an overview of the Pontis bridge management system, and describes the steps involved to install the system, load data, and set common configuration options. It presents a workflow chart which shows the sequence of activities for using Pontis. It concludes with a guide on where to look in the documentation for help on using specific features of the system.
1-1
G E T T I N G
S T A R T E D
W I T H
P O N T I S
Software Characteristics
Pontis 4.5 is a traditional Windows desktop application, whereas Pontis 5.1.2 is a web application. Pontis 4.5 can only be installed on the desktop, while Pontis 5.1.2 can be installed on a web server using Microsofts Internet Information Services (IIS) to serve Pontis over the web. Pontis 5.1.2 can also be installed on the desktop because the Workstation version of Pontis 5.1.2 comes with the Cassini Web server which can run locally. Pontis can be configured in the following ways: Workstation (4.5 and 5.1.2) this configuration, sometimes known as Stand-alone, has both the database and the application on a local computer. Pontis 5.1.2 uses the Cassini web server to allow Pontis to run locally and to look and feel like a desktop application. Client-Server (4.5 and 5.1.2) - this configuration is a multi-user configuration, with the database installed on a server and the application installed on several client computers. For Pontis 5.1.2, this means that separate installations of Pontis 5.1.2 Workstation are installed on different computers and all speak to the same database on a separate server.
1-2
G E T T I N G
S T A R T E D
W I T H
P O N T I S
Server (5.1.2 only) this configuration, sometimes known as a thin-client configuration, consists of Pontis installed on a web server, with clients (users) connecting to Pontis via Internet Explorer. In this configuration, the database is usually on a separate database server and which is in communication with the web server.
Pontis 4.4 was developed in a combination of Sybase PowerBuilder 9 and Microsoft Visual C++. Pontis 5.1.2 was developed in Microsoft Visual Studio 2005 against the .NET Framework 2.0, using C# as the programming language. Both versions database management functions use Microsoft Open Data Base Connectivity (ODBC) to allow for use of different database technologies and to facilitate integration with enterprise databases. Pontis 4.5 supports Oracle 9i, Sybase Adaptive Server Anywhere 8 and 9, and Microsoft SQL Server 2000 databases. Pontis 5.1.2 supports Oracle 10g, Oracle 11g, Oracle 10g Express, Microsoft SQL Server 2005, Microsoft SQL Server 2008, Microsoft SQL Server 2005 Express, and SQL Server 2008 Express databases. The reporting features of Pontis 4.5 were developed using the Sybase InfoMaker application. An InfoMaker license is distributed to each Pontis 4.5 licensee in order to provide the capability to develop custom reports and screens.
Major Functions
By using a combination of Pontis 4.5 and Pontis 5.1.2, Pontis supports the entire bridge management life cycle, including: Establishing an accurate inventory of structure information Integration and data exchange with existing enterprise information systems Scheduling and conducting structure inspections Entering inspection data Importing data from external inspection data collection systems Producing required National Bridge Inventory (NBI) files Producing Structure, Inventory and Appraisal (SI&A) and other inspection reports Developing structure deterioration and cost models based on agency historical data and experience Developing long-range, network-wide policies for structure preservation and improvement reflecting economic considerations and agency standards Assessing current and future preservation and improvement needs Evaluating alternative investment scenarios, based on structure condition and performance, and benefit/cost considerations
Inventory (5.1.2):
Inspection
(5.1.2):
1-3
G E T T I N G
S T A R T E D
W I T H
P O N T I S
Developing projects to address inspector work recommendations and agency policies and standards Evaluating impacts of project alternatives on structure performance Project ranking Developing budget-constrained programs of projects Tracking project status and completion
Pontis Modules
Pontis is organized into seven modules: The Inspection Module (5.1.2) is used to maintain inventory and inspection information about structures. The Project Planning Module (4.5) provides a flexible set of tools to assist with project development. It allows you to view needs for each structure, and analyze future structure performance for different assumptions about what work will be done. It helps you to schedule projects for individual structures, define budget-constrained programs of structure projects, and record information about projects that have been completed. The Programming Module (4.5) is used to set up structure improvement policies and standards, and to define and run simulations of alternative multi-year, budget-constrained program scenarios. The Preservation Module (4.5) is used to develop and run models for determining the optimal long-term preservation policy that minimizes life cycle costs while keeping elements out of risk of failure. The Results Module (4.5 and 5.1.2) is used to view graphical reports on the predicted network costs and performance associated with different scenarios and programs of projects. The Gateway Module (5.1.2) is used to import and export data between Pontis and other systems. The Configuration Module (5.1.2) is used to customize Pontis according to the needs of individual agencies.
1-4
G E T T I N G
S T A R T E D
W I T H
P O N T I S
The lower block is concerned with ongoing use of Pontis. Each activity is assigned a letter for reference purposes, and to provide a general indication of the sequence of steps for using Pontis. Major clusters of activity are: A-C: System Setup. This cluster includes installing the system, setting up a database, and configuring and customizing the system to add custom structure elements, custom data items, screens, forms and reports. Activity D Import NBI, PDI may be used to set up an initial database. D-G: Inventory and Inspection. This cluster includes updating inventory information, planning and conducting inspections, entering inspection data and entering recommended work candidates into Pontis. These activities may involve importing data from field computers running Pontis or external inspection data programs, producing NBI files, and exporting data from Pontis into other systems. Data import and export activities are included here because this is where most agencies will use them. However, these are generic capabilities that may be used in support of other activities. The arrow from Activity R Define, Schedule and Track Projects, to Activity F - Export NBI, PDI, XML indicates that many agencies will want to export project information from Pontis for use in other systems. H-J: Preservation and Improvement Policies (Pontis 4.5 only). This cluster consists of preparatory steps for running the Pontis program scenario simulation, that are typically done initially after Pontis is implemented, and then reviewed and updated on a fairly infrequent basis. It includes (a) developing preservation cost and deterioration models and running an optimization model to produce a least long term cost preservation policy and (b) development of improvement policy standards and model parameters. There is an arrow from activity E - Update Inventory and Inspection Data to indicate that deterioration models can be updated based on inspection history information. K-M: Scenario Simulation (Pontis 4.5 only). This cluster involves defining sets of rules and other parameters governing how the scenario simulation will recommend work, and running simulations for specified budgets and timeframes. N-R: Project Development (Pontis 4.5 only). This cluster consists of activities related to defining and scheduling projects. These include reviewing work candidates that were recommended by inspectors, together with the work candidates resulting from running Pontis scenario simulations; analyzing candidates for specific structures, setting up projects, assigning priorities to projects, and tracking project status and cost information. The workflow diagram includes a feedback loop from activity R Define, Schedule and Track Projects to activity M Run Scenario Simulations. This reflects the fact that there are dependencies between the scenario simulation and project development activity clusters. Pontis is designed so that users can initially specify projects prior to running a simulation. The simulation is then able to incorporate the impacts and costs of these projects and recommend other work that does not duplicate them. Once the simulation is run, additional projects may be created based on the results. Finally, the option is provided to simulate an entire program of structure projects (without recommending any additional work) in order to predict the impacts of an agencys planned program on performance.
1-5
G E T T I N G
S T A R T E D
W I T H
P O N T I S
S. Reporting. This is a general utility available at any point in the Pontis workflow process. However, it will most commonly be used to support the inspection, scenario analysis and project development activities (labeled E, M and R respectively).
1-6
G E T T I N G
S T A R T E D
W I T H
P O N T I S
1-7
G E T T I N G
S T A R T E D
W I T H
P O N T I S
1-8
G E T T I N G
S T A R T E D
W I T H
P O N T I S
Load Rating Review Field: A new check box labeled Load Rating Review Recommended has been added on the Load Ratings side tab of the Appraisal tab in the Inspection module specifying that the load rating should be reviewed.
1-9
G E T T I N G
S T A R T E D
W I T H
P O N T I S
the Pontis Technical Manual. For details concerning how to integrate Pontis with Virtis and Opis, refer to the BRIDGEWare Startup Guide published separately. The following steps are necessary to get started with Pontis: Install the software Set up a Pontis 4.5 database for your agency Configure and customize the system
Installation Procedure
Pontis 4.5 may be installed as a stand-alone application on a single computer or as a workgroup application over a network. If you are installing Pontis to run over a network or if you plan to use an Oracle database, consult the Technical Manual for detailed installation instructions. The following instructions are for single computer installation, using the Sybase Adaptive Server Anywhere database. 1. Verify that your computer meets the minimum requirements for operating system, processor, memory and disk space. The current recommended (and minimum) configuration is: Intel Pentium III, 500+ MHz, 128+ MB RAM (Minimum: Intel Pentium II; 300 MHz, 64 MB RAM); Windows 2000 or Windows XP; Hard Drive with 300+ MB free disk space; Microsoft-compatible mouse or other pointing device; CD ROM; Windows compatible laser, inkjet or standard dot matrix printer; and SVGA 15 color monitor (800x600 pixels). 2. Close all open applications. 3. Insert the Pontis 4.5 Installation CD into your CD-ROM drive. 4. Review the README.TXT file, provided on the Pontis 4.5 Installation CD prior to proceeding with the installation. 5. Click Start-Run, and type D:\ SETUP for CD installation (substitute the correct CD drive letter) in the Open box. 6. Follow all on-screen instructions. 7. Fill in the Registration Information screen, and click the Next button to continue.
1-10
G E T T I N G
S T A R T E D
W I T H
P O N T I S
8. When you reach the Select Components screen, select the Pontis program, the two Adaptive Server Sample Databases (sample data to use in order to become familiar with Pontis), and the Adaptive Server Anywhere Working Database (an empty database in which youll load your agencys data). You may reinstall Pontis later to get any additional components you did not originally install. 9. When you reach the Select Installation Type screen, select Full Installation to install the standard Pontis system. If you are installing Pontis on a portable computer for recording structure inspection information only, select the Pontis Lite installation option. This includes only the Inspection and Gateway modules. 10. When you reach the Select Programs Folder screen, choose the default. 11. At the Ready to Install! screen click Next. The installation will proceed using the options you have selected. 12. Click the Finish button. 13. Follow the instructions in Chapter 2 to log on to the system (using one of the sample databases) and make sure that your installation was successful.
Pontis 4.5 may be installed directly over Pontis 4.3.1 or Pontis 4.4 or may be installed on a machine without a previous version of Pontis by running the program Setup.exe on the Pontis 4.5 installation CD. It is not necessary to have the Pontis 4.3.1 or 4.4 CD when installing Pontis 4.5, as all necessary files are included. You should back up any user libraries or other user-modified files prior to installing 4.5 over a 4.3.1 installation, and then restore these files following installation. You will need to run a set of database scripts to upgrade a Pontis 4.3.1 database to 4.5. Please contact Pontis Support for assistance running the scripts. The scripts are installed to the \DB\UPGRADE431TO44 folder within the Pontis root directory. The scripts can be run in any order, but some are specifically intended for either a Sybase Adaptive Server Anywhere (ASA) or Oracle database. All can be run on either a standalone or integrated BRIDGEWare database. You should backup your database(s) before running the scripts. Below is a description of each: Update431to44_asa.sql Update431to44_ora.sql Updates a Pontis 4.3.1 database to 4.4 for ASA. Updates a Pontis 4.3.1 database to 4.4 for Oracle.
Oracle users should log in as the schema owner when running the upgrade scripts. If you have customized security on your database your database administrator will need to ensure that existing users are given access to the new tables created using the scripts.
1-11
G E T T I N G
S T A R T E D
W I T H
P O N T I S
If you have not yet brought any data into Pontis, there are several ways for getting data into the system: Loading an NBI file to bring in basic inventory data. Preparing and importing a Pontis Data Interchange (PDI) file, which is an ASCII text file with a specially designed format (see the Technical Manual for further information). Preparing a set of custom database scripts or pipelines to move information from existing databases into Pontis. (This should be done by your system administrator, using Pontis database documentation in the Technical Manual.). Using the Pontis data entry screens to manually input the data.
Procedures for loading NBI1 and PDI files into Pontis are described below. Chapter 3 provides instructions on how to enter inventory and inspection information into Pontis. To Load an NBI file into Pontis: 1. Open Pontis and select the Gateway module. 2. Click the Import button. The Import Data window will appear. 3. Select NBI File from the Import What? list. 4. Use the Browse button to navigate to the path and file name for the NBI file you wish to import. 5. If you already have data in your database that you want to update, be sure that the Update Only option is checked. When checked (the default), the NBI data loading procedure will update data in the existing bridge table. If you have data that you want to completely replace, deselect the Update Only option. If Update Only is not selected, all structures in the table will be deleted before the new NBI data is loaded. 6. If the Always Create New Inspections option is checked (the default), new inspections will be created for all imported structures, even if inspections already exist for those structures. Inspection data will need to be entered into the new records. If this option is not selected, the most recent inspection for each bridge will be updated. 7. Select either the Metric or English radio button depending on the unit of measure used in your data. 8. Click Import.
See Appendix B for a description of the NBI file format and a guide to where each NBI item is located on the Pontis data entry screens.
1-12
G E T T I N G
S T A R T E D
W I T H
P O N T I S
9. You will be prompted to confirm the name of the file to import. Click Yes. 10. You will be prompted to confirm that you wish to continue with the import. Click OK. 11. At the end of the import you will be informed whether the import succeeded or not. Click OK as needed once you have read the message(s). Then click on the Cancel button to exit the Import Data window. 12. Check structures in the Inspection module to verify that the data was imported as expected. Note: See the Technical Manual for information on how NBI data fields are converted to Pontis fields. To Import a Pontis Data Interchange (PDI) File: PDI files can be created by exporting data from Pontis in PDI format. In addition, the PDI format is well-documented (in the Technical Manual) so that other systems can be programmed to produce PDI files for import into Pontis.
Note: You will not be able to import most PDI files generated from Pontis 3.x, since the database structure has changed significantly.
1. Get into Pontis and select the Gateway module. 2. Click the Import button. The Import Data window will appear. 3. Select Pontis Data Interchange File (PDI) from the Import What? list. 4. Use the Browse button to navigate to the path and file name for the Pontis 4 PDI file you wish to import. 5. Click Import. 6. You will be prompted to confirm the name of the file to import. Click Yes. 7. You will be prompted to confirm that you wish to continue with the import. Click OK. 8. At the end of the import you will be informed whether the import succeeded or not. Click OK as needed once you have read the message(s). Then click on the Cancel button to exit the Import Data window. 9. Verify that the data was imported as expected.
A Note on Missing Values
When you view records that you have imported into Pontis, you will notice missing values in various fields. This is to be expected these fields have missing values because they have no counterpart fields in your data source from which to draw data. Missing values appear as negative numbers (usually -1), symbols such as #, _ or @, labels such as Unknown, or the date
1-13
G E T T I N G
S T A R T E D
W I T H
P O N T I S
01/01/1901. Missing values can either be ignored (if the data elements are not used), filled in manually in the data entry screens (see Chapter 3), or filled in with defaults via SQL scripts or with Pontis formulas (see Chapter 7 and the Technical Manual for instructions on the Pontis formula feature.)
While none of these steps are required for using Pontis, all users will want to customize pick lists to show the appropriate listings of districts, administrative areas, counties, and census place codes. The procedure for doing this is described below. Other configuration and customization options are described in Chapter 7, or in the Technical Manual. Note: if you have developed custom forms and reports for Pontis 3.x, these forms and reports must be modified in order to work with the Pontis 4 data structure. See the Technical Manual for further information.
Importing Parameters
The Pontis database includes a parameters table which stores allowable values for different database columns, including important location categories such as counties, census place codes, districts, and administrative areas. Information in this table is used to create pick lists for certain fields, and for data validation. Parameter values can be manually modified in a data entry screen, or imported from a text file. To manually edit parameter values: 1. Select the Configuration module from the Pontis Desktop. 2. Select the Parameters tab card. 3. From the Parameters window, select the Table Name and Field Name that you will be updating. To find out the name of a field on any Pontis data entry screen or structure list, right-click on it, and choose Field Definition from the menu that appears. The table and
1-14
G E T T I N G
S T A R T E D
W I T H
P O N T I S
column names and the characteristics of the field will be listed. Click the Details button within the Field Definition window for a detailed description of the field. 4. Make changes or additions in the Parameter Values & Labels window. 5. Save additions and changes by clicking on the Save button in the upper right-hand corner of the window. To import parameter values from delimited text files:
Example: You want to import lists of counties, districts and place codes (cities) in your state.
1. Prepare three comma-delimited ASCII files (*.ASC) which list counties, place codes, and districts. Each row will include information for one county, place code or district. Each row should contain first the NBI code, then a short text label for the code, followed by a longer descriptive label for the code. Surround each of these three items with double quotes and separate each item (including its double quotes) from the next with a comma. (Note: The double quotes are straight double quotes, not opening or closing double quotes.) The brief text label must be less than 24 characters. If you do not need a longer description, just repeat the brief text label in the third column. COUNTY.ASC
"bridge", "county" "10", "Charleston", "Charleston" "11", "Cherokee", "Cherokee" "12", "Chester", "Chester" "13", "Clare", "Clare"
DISTRICT.ASC
"bridge", "district" "01", "District 1", "District 1" "01", "District 1", "District 1" "01", "District 1", "District 1"
PLACES.ASC
"bridge", "placecode" "01900", "Appleton", "Appleton" "03430", "Aynor", "Aynor" "03790", "Bamberg", "Bamberg" "04060", "Barnwell", "Barnwell"
1-15
G E T T I N G
S T A R T E D
W I T H
P O N T I S
3. The first line in each file should consist of the table name followed by a column name; both enclosed in double quotes and separated by a comma. The table and column names can be taken from the Pontis Data Dictionary report config004_data_dictionary. The data dictionary can also be viewed on-line in the database reference section of the help system. You can find out the name of a specific field on the Pontis data entry screens (tab cards) by right-clicking on the field, and then choosing Field Definition from the menu that appears. The table and column names and the characteristics of the field will be listed. Click Details for a detailed description of the field. 4. Get into Pontis and select the Gateway module. 5. Click on the Import button. The Import Data window will appear. 6. Select "Parameters from the Import What? selection list. 7. Use the Browse button to navigate to the path and file name for the parameter file you wish to import. 8. Select the parameter you are importing from the Parameter selection list (e.g., bridge: district, bridge: county, bridge:placecode). 9. Click Import. 10. You will be prompted to confirm the name of the file to import. Click Yes. 11. You will be prompted to confirm that you wish to continue with the import. Click OK. 12. At the end of the import you will be informed whether the import succeeded or not. Click OK once you have read the message(s). Then click on the Cancel button to exit the Import Data window. 13. Check the values of the appropriate field name for the parameter just imported to verify the new values imported correctly.
1-16
G E T T I N G
S T A R T E D
W I T H
P O N T I S
Install the software Set up a Pontis 5.1.2 database for your agency Configure and customize the system
Installation Procedure
Select an installation type by opening the Pontis Installation Guide and clicking on Pontis Installation and Configuration > Start Installation Process Here > Select an Installation. From here, look at the installation matrix to help you decide what type of installation you need and click on the proper links to find instructions for your installation type. The installation matrix also provides instructions for users who have previous installations of Pontis.
Please refer to the Pontis Installation Guide. Click on Pontis Installation and Configuration > Start Installation Process Here > Select an Installation. Find your current installation type and click on the link (in the column labeled Recommendations and Installation Links) that refers to an Existing Pontis Database. Follow the instructions you see after clicking the link.
For New Users of Pontis
If you have not yet brought any data into Pontis, there are several ways for getting data into the system: Loading an NBI file to bring in basic inventory data. Preparing and importing a Pontis Data Interchange (PDI) file, which is an ASCII text file with a specially designed format (see the Technical Manual for further information). Preparing a set of custom database scripts or pipelines to move information from existing databases into Pontis. (This should be done by your system administrator, using Pontis database documentation in the Technical Manual.). Using the Pontis data entry screens to manually input the data.
Procedures for loading NBI2 and PDI files into Pontis are described below. Chapter 3 provides instructions on how to enter inventory and inspection information into Pontis. To Load an NBI file into Pontis:
See Appendix B for a description of the NBI file format and a guide to where each NBI item is located on the Pontis data entry screens.
1-17
G E T T I N G
S T A R T E D
W I T H
P O N T I S
1. Refer to the Pontis Installation Guide and click on Pontis Installation and Configuration > Start Installation Process Here > Post-Installation Configuration > Importing Sample Data. 2. Open Pontis and select the Gateway tab. 3. Click the Import task. The Import Data screen will appear. 4. Select NBI File from the Import What? list. 5. Use the Browse button to navigate to the path and file name for the NBI file you wish to import. 6. If you already have data in your database that you want to update, be sure that the Update Only option is checked. When checked (the default), the NBI data loading procedure will update data in the existing bridge table. If you have data that you want to completely replace, deselect the Update Only option. If Update Only is not selected, all structures in the table will be deleted before the new NBI data is loaded. 7. If the Always Create New Inspections option is checked (the default), new inspections will be created for all imported structures, even if inspections already exist for those structures. Inspection data will need to be entered into the new records. If this option is not selected, the most recent inspection for each bridge will be updated. 8. If the Update and Create Inspection As Needed option is checked (the default), then the Pontis will update the existing inspection only if an inspection is found with a matching date, otherwise a new inspection is created. 9. If the Do Not Update or Create Any Inspections option is checked, then inspection data will not be updated or created, unless a new bridge is inserted. 10. Select either the Metric or English radio button depending on the unit of measure used in your data. 11. Click Import. 12. You will see a message that the import is running. 13. At the end of the import you will be informed whether the import succeeded or not. 14. Click on the Bridges tab and select the relevant bridges to verify that the data was imported as expected. Note: See the Technical Manual for information on how NBI data fields are converted to Pontis fields.
1-18
G E T T I N G
S T A R T E D
W I T H
P O N T I S
To Import a Pontis Data Interchange (PDI) File: PDI files can be created by exporting data from Pontis in PDI format. In addition, the PDI format is well-documented (in the Technical Manual) so that other systems can be programmed to produce PDI files for import into Pontis.
Note: You will not be able to import most PDI files generated from Pontis 3.x or older versions of Pontis, since the database structure has changed significantly.
1. Get into Pontis and select the Gateway tab. 2. Click the Import task. The Import Data window will appear. 3. Select Pontis Data Interchange File (PDI) from the Import What? list. 4. Use the Browse button to navigate to the path and file name for the Pontis 5.1.2 PDI file you wish to import. 5. Click Import. 6. You will see a message that the import is running. 7. At the end of the import you will be informed whether the import succeeded or not. 8. Verify that the data was imported as expected.
A Note on Missing Values
When you view records that you have imported into Pontis, you will notice missing values in various fields. This is to be expected these fields have missing values because they have no counterpart fields in your data source from which to draw data. Missing values appear as negative numbers (usually -1), symbols such as #, _ or @, labels such as Unknown, or the date 01/01/1901. Missing values can either be ignored (if the data elements are not used), filled in manually in the data entry screens (see Chapter 3), or filled in with defaults via SQL scripts or with Pontis formulas (see Chapter 7 and the Technical Manual for instructions on the Pontis formula feature.)
1-19
G E T T I N G
S T A R T E D
W I T H
P O N T I S
While none of these steps are required for using Pontis 5.1.2, all users will want to customize pick lists to show the appropriate listings of districts, administrative areas, counties, and census place codes. The procedure for doing this is described below. Other configuration and customization options are described in Chapter 7, or in the Technical Manual. Note: If you have developed custom forms for Pontis 4.5, these forms will not function in the Pontis 5.1.2 environment due to fact that Pontis 5.1.2 is now an ASP.NET web application.
Creating Parameters
The Pontis database includes a parameters table which stores allowable values for different database columns, including important location categories such as counties, census place codes, districts, and administrative areas. Information in this table is used to create pick lists for certain fields, and for data validation. Parameter values can be manually modified in a data entry screen. To manually edit parameter values: 1. Select the Admin tab. 2. Select the Parameters task. 3. From the Parameters window, select the Table Name and Field Name that you will be updating. To find out the name of a field on any Pontis data entry screen or structure list, hover over the field or, in the case of pick lists, over the fields label. The table and column names and the characteristics of the field will be displayed. 4. Make changes or additions in the Parameter Values and Labels window. 5. Save additions and changes by clicking on the Save button in the lower left-hand corner of the window.
1-20
G E T T I N G
S T A R T E D
W I T H
P O N T I S
Importing Parameters
This section describes how to import parameters from a text file in PDI format. To create parameter value lists to import:
Example: You want to import lists of counties in your state.
1. Copy the \PontisModules\Agency_Import_PARAMTRS_Template.pdi file from Disk 3 to another location where you can edit it. Since you are copying from a DVD, please make the file editable by removing its read-only status. 2. Open the copied file in notepad or some other text editor that can save in text format. 3. Look at the section that describes the structure of the parameters table. It looks like this: TABLE paramtrs DATE(YYYY/MM/DD)
COLUMN table_name COLUMN field_name COLUMN parmvalue COLUMN shortdesc COLUMN longdesc COLUMN misvalflg COLUMN helpid END DEFINITIONS 4. The section lets you know that this PDI file is concerned with a table called paramtrs and will have several columns, beginning with table_name and ending with helpid .
1-21
G E T T I N G
S T A R T E D
W I T H
P O N T I S
5. Look at the text below the BEGIN DATA section that looks like this: TABLE PARAMTRS "bridge" "county" "089" "Sanders" "-1" "_" "-1" TABLE PARAMTRS "bridge" "county" "081" "Ravalli" "-1" "_" "-1" 6. There are two seprate data entries here, and each is formatted using the same structure as described above. The first data entry will put bridge in the table_name column and county in the field_name column, etc. 7. The columns are used as follows: a. table_name lists the table that contains the coded value you are storing that needs to be looked up in the paramtrs table. In our example, we are importing counties, and the coded value for a county is stored in the bridge table, so the value of the table_name field would be bridge. b. field_name lists the field (column) name of the coded value you are storing that needs to be looked up in the paramtrs table. In our example, we are importing counties, and the coded value for a county is stored in the county field of the bridge table, so the value of the field_name field would be county.
1-22
G E T T I N G
S T A R T E D
W I T H
P O N T I S
c. parmvalue lists the code that matches the value stored in the table and column referenced in the two fields above. To continue the example, a county named Sanders has a parameter value of 089. The value 089 is stored in the field named in the field_name field and that matches the value stored in the parmvalue field of the paramtrs table. d. shortdesc a short description that gives meaning to the value in the parmvalue field. To continue our example, the name of the county, Sanders, would be stored in the shortdesc field because it is the readable value that matches the parmvalue of 089. e. longdesc this field can store a longer description of the parameter value if desired, but is usually just left blank which is signified by the value -1. In our example, Sanders gives complete meaning to the county name so there is no need to give a long description. f. misvalflg this field is used to deal with missing values. This field can be just stored as "_" g. helpid stores a link to a help file. This is really only used in previous versions of Pontis and should be just -1. 8. To add county names to the PDI file, simply copy the sections beginning with TABLE PARAMTRS, making sure you get all the text up to the next TABLE PARAMTRS heading. Edit the values of the parmvalue and shortdesc entries (the table_name and field_name values will stay the same in this example since all your county names will reference the same table and field name). You will need one TABLE PARAMTRS entry for every county in your state. To import parameter values: 1. Get into Pontis and select the Gateway tab. 2. Click on the Import task. The Import Data screen will appear. 3. Select Pontis Data Interchange File (PDI) from the Import What? Drop-down list. 4. Use the Browse button to navigate to the path and file name for the PDI file you created above. 5. Click Import. 6. At the end of the import you will be informed whether the import succeeded or not. 7. Go to the Admin tab and the Parameters task and check the values of the appropriate field name for the parameter just imported to verify the new values imported correctly.
1-23
G E T T I N G
S T A R T E D
W I T H
P O N T I S
For Information On
Minimum System Requirements
See
Pontis_Installation_Guide.chm User Manual Chapter 1 Technical Manual Chapter 1
Installation: Basic
Installation: Advanced
Database Migration from Prior Version of Pontis Database administration/security Establishing an Integrated BRIDGEWare Database Integration with other applications and data Customizing pick lists User Interface Login Procedure Toolbars and Menus Finding and Selecting Structures Viewing and Printing Reports Inventory/ Inspection Inventory/Inspection Data Input Calculating NBI and Sufficiency Ratings
Pontis_Installation_Guide.chm
User Manual Chapter 1 User Manual Chapter 2 User Manual Chapter 2 User Manual Chapter 2 User Manual Chapter 2 User Manual Chapter 3 User Manual Chapter 3
1-24
G E T T I N G
S T A R T E D
W I T H
P O N T I S
Topic
For Information On
Performing Data Validation Preparing NBI Files
See
User Manual Chapter 3 User Manual Chapter 3 Technical Manual Chapter 4
Pontis Models Theory and Algorithms Preservation Cost and Deterioration Models Health Index Targeting Improvement Standards, Costs and Benefits Running a Needs Analysis Entering Rules Governing Pontis Work Recommendations Defining Flexible Actions
Entering Inspector Work Recommendations Creating and Updating Projects Simulating Project Impacts Ranking/Prioritizing Projects
User Manual Chapter 6 User Manual Chapter 6 User Manual Chapter 6 User Manual Chapter 7
Customization
Customizing Structure Elements and Actions Adding new data items to Pontis Developing custom structure lists, data entry screens and reports Customizing database management parameters Customizing user interface labeling / localization Customizing user interface parameters Customizing simulation and modeling parameters
1-25
2 System Basics
Pontis has been installed successfully. Now some of our staff need a basic tutorial on how to log in and operate the system. How do we navigate to different modules? How do we find information for a particular group of structures? How do we print reports? How do we get on-line help?
his chapter covers logging on to Pontis, and provides an introduction to the Pontis Desktop. It describes how to use the basic menu options and tools available from the Pontis Desktop for selecting modules, finding and viewing bridge information and viewing/printing reports. Separate sections have been provided for Pontis 4.5 and Pontis 5.1.2 as indicated in the section headings below.
2-1
S Y S T E M
B A S I C S
3. From the Database drop-down list, select the database that you will be using if different from the one already displayed. 4. Enter your user name and password. (The checkboxes 'Default structure list' and 'Default project list' are for use in special cases. Ignore them during normal logons.) 5. Click OK.
If you get a database error at this point, first try re-typing your user name and password. If that doesnt work and you are certain that these are correct, it means that the ODBC profile for the database you have selected was not properly set up, or the Pontis name for the database you have selected does not match with the proper ODBC profile. Call your system administrator for assistance.
2-2
S Y S T E M
B A S I C S
Structure List
2-3
S Y S T E M
B A S I C S
The menu bar contains five main items: File, View, Tools, Window and Help. Available choices under each of these items vary depending on which module you are in, and what activity you are performing. See the screen reference documentation available in the online help system, and in Appendix B for complete information on menu options. The most important options are as follows: Use File-Close to close the current window. Use File-Save to save data in the data entry screens to the database. Use File-Exit to quit Pontis. Use File-Print Screen to print an image of the current Pontis screen. Use File-Print to print or export the contents of the Structure List to a file. Use View-Retrieve All to retrieve all structures from the database that meet the current selection criteria. Use View-Reports to select, view and print Pontis reports. Use the Windows menu to select windows that may be hidden or minimized behind the current window. Use the Help-Reference menu to view context-sensitive reference help for the current screen. Use the Help Tutorial option to see tutorial style help for the current module. Use the Help-Glossary option to see a glossary of Pontis terms. Use the Help-About option to see your Pontis serial number and information on the software build you have installed. Click the SysInfo in the About Pontis window button for detailed information about your database profiles, and drivers installed.
You may invoke the menus by the following three methods (all standard to Windows): Click a menu item to display the drop-down list of submenu items, and then click on your desired menu selection. Press <Alt> together with the underlined letter (appears after you press <Alt>) in the toplevel menu to display the drop-down list of submenu items. Then select a submenu item. Use short-cut keystrokes as indicated on the menu to reach your desired choice, e.g., press F1 for screen help.
2-4
S Y S T E M
B A S I C S
The Toolbar
The Toolbar down the left side of the screen contains buttons for commonly performed functions, which change as you select different modules. For example, in the Inspection module there are buttons for creating structures and inspections; in the Project Planning module there are buttons for creating and deleting projects. The Reports button on the Toolbar is present in all modules (with the exception of Configuration), and has the same function as the View-Reports menu option it allows you to select, view and print Pontis reports. The Toolbar also contains some items that operate in conjunction with the Structure List: The Retrieve Icon allows you to refresh the structure list by retrieving all structures meeting the current selection criteria from the database. If you have a large database, and only want to retrieve a limited number of structures, you can enter this number into the Limit To field underneath the Retrieve Icon (all structures are retrieved if the limit is set to 0). The set of five buttons directly below the Limit To field is called the scroller widget. These buttons operate as follows when you click on them with the left mouse button: ? ||< |< >| >|| Display info about the number of rows in the Structure List Scroll to the first line in the list of data set the current row to that first line Scroll up a page Scroll down a page Scroll to the last line in the list of data
Two of these keys can also be used to control the amount of zoom when you hold the <Alt>, <Ctrl>+<Alt>, or <Shift>+<Alt> key(s) down, and click with the right mouse button3: ||< >|| Zoom smaller (the default is 5% smaller) Zoom larger
The amount of zoom done by the [ ||< ] and [ >|| ] keys is modified as follows. If you hold down both the control <Ctrl> and <Alt> keys while right mouse-clicking one of the zoom buttons, then the zoom amount is reduced by half, e.g. 2.5% instead of 5%. This gives you finer control over the zoom amount. Still finer control is provided if you hold down both the <Shift> and <Alt> keys; in that case, the zoom changes just one percent. This lets you size the display precisely.
2-5
S Y S T E M
B A S I C S
The Status Bar across the bottom of the screen includes (from left to right): System Status Database Status Edit Status Block DateTime
The System Status Block, which shows various messages generated by Pontis. When the system is waiting for you to do something, this block will say Ready. When the system is busy, this block will contain an indication of what is being done. If you click once on this block the Message History List will be displayed. This list shows the latest messages that were displayed in the system status block. The Database Status Block, which indicates which database you are using. For example, if you are using the sample database, this block will say Pontis 44 ASA Sample DB. If you click this block, the Login to Pontis window will appear, allowing you to login to a different Pontis database without quitting the system. The Edit Status Block, which will say N/A (for Not Applicable) on the main desktop. This block is used when Pontis data entry screens are active, and allows you to toggle between Edit On and Edit Off modes to allow/disallow data edits. The Date-Time Block, which indicates the current system date and time. This can be turned off by de-selecting the Date and Time option on the View menu. You can also toggle among different date-time formats by clicking on this block.
The Structure List is available in the Inspection, Gateway, and Project Planning modules. The
Structure List, along with its seven control buttons across the top allows you to:
Browse through the different structures in the inventory; Define a subset of structures to work with; Find a particular structure; and Select structures for various operations available from the Toolbar (e.g. editing, exporting data, calculating sufficiency ratings, etc.).
When Pontis is first installed, the default Structure List is shown. This list shows all structures sorted by Bridge ID, and includes basic information about each structure, including Bridge ID, feature intersected, district, county, owner, maintenance responsibility, area, length in meters, year built, structure name, and facility carried.
2-6
S Y S T E M
B A S I C S
Alternative layouts for the Structure List can be defined and made available for selection. These layouts can include a different set of data items, different fonts, a different sort order, and a filter criteria (e.g. restrict list to structures in a single district). Several example layouts are included with the Pontis product. See Chapter 3 of the Pontis Technical Manual for information on how to create new layouts. The following table summarizes how to use the various controls for the Structure List.
Do this
Click4 on a structure <Shift>-click5 a structure
In order to
Select the structure, and de-select all other structures Select the structure, and any structures between it and the closest selected structure above it (or below, if no structures above were selected) Select the structure without changing the selection of any existing structures on the list. (Inspection module only) Opens the Inspection tab cards for that structure for data review and modification Sort structures by the value of that column. If you click again, the sort will toggle between ascending and descending order. Change column widths
<Ctrl>-click6 a structure
Double-click7 a structure
<Alt>-click8 on the border between two columns and drag Click Layout
Select from a list of alternative layouts for the structure list by clicking on the down arrow beside the drop-down list that is displayed and selecting the desired layout. Then click again on Layout to toggle the drop-down list off and redisplay the other control buttons. Display a message box with the total number of structures on the structure list. Locate a structure based on its ID, name, facility carried, feature intersected, and/or route/km-post by setting criteria within the Find Structure window. (See Finding a Structure below for more detailed instructions.) Restrict the structure list to a selected group of structures based on structure location, route system, ownership, inspection schedule/status, or ID by setting criteria within the Select Structures window. (See Looking at a Subset of Structures below for more detailed instructions.) Save your current structure list layout under a new name by setting up a new entry within the Structure List window..
Click Select
Click Save
4 5 6 7 8
Click refers to one click of your left mouse button (assuming you have a right-handed mouse). <Shift>-Click means holding down the <Shift> key and then clicking with your left mouse button. <Ctrl>-Click means holding down the <Ctrl> key and then clicking with your left mouse button. Double-click means two quick clicks of your left mouse button. <Alt>-click means holding down the <Alt> key and then clicking with your left mouse button.
2-7
S Y S T E M
B A S I C S
Do this
Click Select All/De-select All Click Just Selected/ All Rows
In order to
Select (highlight) all rows/ De-select (remove highlight) all rows
Right-clicking on the Structure List displays a pop-up menu of options. These options are as follows:
Selecting this option allows you to enable the flexible relabeling functionality. Once the flexible relabeling is enabled, you can right-mouse click on buttons or labels to bring up the Edit Object Localization Attribute Values window. Please refer to the Technical Manual for more detail.
FIELD DEFINITION
If you have right-clicked on a data item, the Field Definition option will appear. Selecting this option brings up a help screen with documentation for the particular database column that you clicked on.
SORT
Selecting this option allows you to define (and optionally, save) complex sort orders for the list. 1. Specify the sort order by clicking the Sort Order column: the first row you click will be the primary sort column, the second click identifies the secondary sort column, and so on. Numbers (1, 2, ...) are placed in the columns to show the sequence by which they are to be sorted. You can de-select a row by clicking the Sort Order column again; all the other selected rows (if any) will be renumbered to reflect the new sort order. Or, you can click Clear to remove all the selections
2-8
S Y S T E M
B A S I C S
2. Specify whether a particular column sorts in ascending or descending order by clicking the Direction column. By default, it comes up "Ascending", but you can click the column to toggle between "Ascending" and "Descending." If you click a row's Direction column before its Sort Order column, then the direction will be set to the default ascending order, and the order column will be set to the next number in the sequence. 3. Click the Apply Sort Automatically checkbox if you want to save the sort order you specify. If this option is checked, then the sort order is saved in a file on your hard-disk, and will be restored as the default when you next open the sort window. Each time the data is retrieved, it will automatically be sorted according to your specification. 4. When you have specified at least one sort column, click the Sort button to perform the sort and close the window.
FILTER
The Filter window can be used when you want to select structures based on criteria other than those provided via the Find and Select buttons on the Structure List. Note that any filter that you define here will be applied on top of the current selection criteria that have been set via the Select Structures screen. 1. For each item youd like to include in your filter condition, select an option from the Relation column, and enter or select filter values. To see and select from a list of possible values for the item the database, either right-click on the row or left-click on the row and select the Filter Values button. This brings up a window with a list of the different values that are present for the current Structure List. You can select one or more of these values for your filter criteria. To select multiple values, select the Multiple Selection option. To filter based on whether values are NULL, enter IsNull in the value column. 2. If you are filtering based on more than one criteria, select an option from the And/Or column AND if you want all of the filter criteria to be met; OR if you want at least one of the criteria to be met. 3. If you would like only the structures that are currently selected on the list to be included, click the Selected option. If you would like the structures that are currently selected on the list to be excluded, click the UNSelected option. 4. Click the Apply Filter button to apply the filter and close the window. 5. To eliminate the filter click on the Retrieve Icon, or re-open the filter window and click Cancel.
SPLIT
This option will split the Structure List window vertically in the location that you right mouse clicked. To remove the split, right-mouse click in the same location and select Split again.
2-9
S Y S T E M
B A S I C S
EXPORT DATA
This option will export the rows in the Structure List to a range of file formats (DBF, XLS, SQL, HTML, Text, etc.)
PRINT DATA
This option shows a window with information about the number of rows in the Structure List.
SQL SYNTAX
This option shows a window with the SQL that was used to retrieve the current set of rows in the
Structure List.
PRINT DESKTOP
This option is the same as the menu option File-Print Screen. It sends an image of the desktop to the printer.
ZOOM
This option allows you to set a zoom factor for the Structure List so that it appears larger or smaller.
CUSTOMIZE COLUMN POSITIONS
This option allows you to select from a set of tools for changing the order of the columns in the Structure List and for hiding certain columns. To move a column: 1. Right-mouse click on the Structure List, select Customize Column Positions from the popup menu and then select Turn on Column Move from the submenu. 2. Hold down the <Alt> key, and drag the column you wish to move to its new position: click the label at the top, and hold down the left mouse-button as you move the mouse left or right to reposition the column. A ghost will indicate where the column will be placed, as you drag it around. 3. To save your current column positions to the current Structure List layout, right-mouse click on the Structure List, select Customize Column Positions from the popup menu and then select Save Column Positions As Default. (This customization is stored on your personal computer and will not effect users on other machines.) To revert to the default column order, select Restore Default Column Positions from the Customize Column Positions submenu. To revert to the original column order (prior to customization), select Restore
Original Column Positions.
To hide a column: 1. Right-mouse click on the column you wish to hide (but not in the headings row), select Customize Column Positions from the popup menu and then select Hide Column from the submenu.
2-10
S Y S T E M
B A S I C S
2.
To save the current Structure List layout to maintain the hidden column(s), select
Save
Column Positions As Default. To show the columns, select Restore Default Column Positions from the Customize Column Positions submenu.b.
To un-hide a column: 1. If you have saved the column positions as the default since you hid the column, you must select Restore Original Column Positions from the Customize Column Positions submenu.. Otherwise, you can select Restore Default Column Positions.
2-11
S Y S T E M
B A S I C S
Finding a Structure
To find a particular structure:
1. Click the Find button above the Structure List. Enter search criteria into one or more of the fields at the top of the screen.
2. Click the Find Records Based on Current Criteria button, and a list of structures meeting the current criteria will appear. 3. Click on the structure(s) you are trying to find. Different buttons will appear, depending on which module you are using: In the Inspection module, click on the Open Past button to open the existing inspections for the first selected structure on the list. Click on the Open New button to create a new inspection for the structure.
2-12
S Y S T E M
B A S I C S
In the Project Planning module, clicking the Apply Selected Bridge button will select it on the Structure List and add it to the Tree View. In the Gateway module, clicking the Export or Check Out buttons will allow you to export or check out information on the selected structures to a PDI or NBI file.
2. When you are finished making your selections, click OK. The subset will appear on the Structure List.
2-13
S Y S T E M
B A S I C S
If you want to create a subset based on items that are not on the Select Structures screen, you can right-mouse click on the Structure List, and select Filter from the popup menu. Instructions on using the Filter menu option are provided above in Section 2.2.
2-14
S Y S T E M
B A S I C S
1. If the Structure List is visible in the module you are in (Inspection, Gateway, or Project Planning), and you want your report to be based on a subset of structures, either select these structures by hand using mouse clicks combined with <Ctrl> or <Shift> if necessary, or use the Select button to set criteria for the list within the Select Structures window.
2.
Select View-Reports from the Menu Bar, or click on the Reports button on the Pontis Desktop Toolbar. The report selection window will appear. Options will reflect the current module. However, all Pontis reports are accessible from all modules. To generate a standard Pontis report,
select View <module-name> Results (e.g. in the Inspection module, you would select View Inspection Results). For custom reports, select View User Reports.
3.
4. The Report Viewer will open. A default report will be selected based on the module you are in. (Default reports for each module can be customized in the Configuration module see Chapter 7). To select a different report, click on the name of the currently selected report in the Selected Report drop down list to expand the list, and then click on the one you want.
2-15
S Y S T E M
B A S I C S
5. Click in the field next to the report name to view comments about the report. Or, click Describe Report if you want to see detailed information about the selected report (including the SQL statement that is used to retrieve the data). 6. Click Generate Report to run the report. 7. For reports that present information on individual structures (e.g. SI&A reports, inspection schedules, lists of needs for each structure), the Select Bridges for Report screen will appear. Options are: Bridges Selected on Desktop: include bridges you have selected (highlighted) on the Structure List.
List.
Bridges Listed on Desktop: include bridges that have been loaded into the Structure (The number of bridges that have been loaded appears on the top of the structure list. For example, Rows 1-18 of 528 indicates that 528 bridges have been loaded and the first 18 are currently visible on the list.)
All Bridges Meeting Select Criteria: include bridges which meet the current criteria as specified in the Select Structures screen. All Bridges in Database: include all bridges Bridges Specified by Report Definition: include bridges meeting criteria specified in the (later) report Specify Retrieval Criteria screen. This option ignores any selections or filters on the Structure List.
8. For many reports, the Specify Retrieval Criteria screen will appear. (For example, summaries of element condition [insp005 and insp009] allow you to select which elements to include; reports listing projects or work candidates allow you to specify project IDs, year(s) in which the work is scheduled, status, etc.) You may enter one or more criteria for each column. Multiple criteria for a single column are joined by a logical OR. Criteria for different columns are joined by a logical AND. You can leave this screen blank to retrieve all records. Click OK to apply your criteria and close the screen. 9. When your report appears, you can use the First Page, Prior Page, Next Page, and Last Page buttons (or their shortcut keys) to scroll through the different pages. Or, you can use the scrollbar on the right side of the screen. 10. For certain simple list-style reports, you can modify the sort order and filter criteria by using the Filter and Sort tools at the top of the Report Viewer If you are familiar with Infomaker, you can experiment with these features to customize the report. 11. To print the report, click the Print button. You can also export the information in reports to external files using the Rows-Save As menu item. 12. Click the Close button to close the Report Viewer window.
2-16
S Y S T E M
B A S I C S
3. The Database drop down list, which displays when you have more than one database defined in Pontis, displays the name of the most recently used database profile automatically. Select the database that you will be using if different from the one already displayed. 4. Enter your user name and password. 5. Click Login.
If you get a database error at this point, first try re-typing your user name and password. If that doesnt work and you are certain that these are correct, it means that the ODBC profile for the database you have selected was not properly set up, or the Pontis name for the database you have selected does not match with the proper ODBC profile. Call your system administrator for assistance.
2-17
S Y S T E M
B A S I C S
2-18
S Y S T E M
B A S I C S
Pontis Header
The Pontis Header contains three buttons: Help?, Account, and Logout. The buttons are as follows: Use Help? to view the Pontis help screen for the current screen. Use Account to view account information of the user. Use Logout to quit Pontis.
The Pontis Header also shows the current user you are logged in as and the database that is currently being used.
Tab Bar
The Tab Bar contains five items: Bridge, Reports, Admin, Inspection and Gateway. The options are as follows: Use Bridges to view the Bridge List. Use Reports allows you to select, view and print Pontis DataWindow.NET and/or Crystal Reports based reports for selected bridges or all bridges in the list. Use Admin to access the administration functions of Pontis, e.g. Security-Users-Add New User. Use Inspection to access the inspection information about a selected bridge. Use Gateway export, import, check out or check in the contents of the Bridge List .
2-19
S Y S T E M
B A S I C S
Task List
The Task List is located on the left side of the screen and contains commonly used tasks, which change as you select different tabs. For example, selecting the Bridges tab displays the Task List shown above. The tasks that belong to the Bridges tab includes the Manage Layouts task which has options to change what columns the bridge list displays. Any given task can also include sub-tasks. For example, the View List task, which is the default task for the Bridges tab, contains some sub-tasks that operate in conjunction with the Bridge List: Select All will select all the bridges on the Bridge List. Unselect All will unselect all the bridges that are currently selected from the Bridge List. Select Page will select all the bridges on the current page. Unselect Page will unselect all the bridges on the current page. Just Selected will only show those bridges that are currently selected
2-20
S Y S T E M
B A S I C S
All Rows will make available all the bridges in the Bridge List; this sub-task will only show if the Just Selected option was selected previously selected. Apply Grid Settings will save the current settings of the Bridge List (e.g. changing column width or sorting columns) for the current layout of the current user. Reset Grid Settings will reset the Bridge List settings to the default settings. Printable View will open a new window with a screen that will give the option to print the rows in the Bridge List.
The Pontis Footer across the bottom of the screen includes (from left to right): Pontis Version Build Date
The Pontis Version will show the current version for Pontis. The Build Date will show the build date and time for the latest version of Pontis.
2-21
S Y S T E M
B A S I C S
Bridge List
The Bridge List, along with its several control buttons across the top allows you to: Choose a different layout; Choose a different filter; Find a particular structure; and Select structures for various operations available from the Task Bar
The Bridge List has another control on the bottom of the page that will allow the user to switch between pages if there is more than one page listed on the bottom. There is also information that states the how many total bridges there are in the database; how many bridges match the current filter; and how many bridges are selected. When Pontis is first installed, the default Bridge List is shown. This list shows all structures sorted by Bridge ID, and includes basic information about each structure, including Bridge ID, district, county, facility carried, feature intersected, owner, maintenance responsibility, and the year built.
AASHTO Pontis Users Manual 2-22
S Y S T E M
B A S I C S
Alternative layouts for the Bridge List can be defined and made available for selection. These layouts can include a different set of data items, a different sort order, and a filter criteria (e.g. restrict list to structures in a single district). Several example layouts are included with the Pontis product. See Chapter 3 of the Pontis Technical Manual for information on how to create new layouts. The following table summarizes how to use the various controls for the Bridge List.
Do this
Click9 on a structure Click Apply
In order to
Selects the structure After picking bridges by putting check marks next to them, click Apply and the bridges will be selected. The number of bridges selected will show next to Selected in the lower right hand corner. Sort structures by the value in that column. If you click again, the sort will toggle between ascending and descending order. Change column widths
Click on the border between two columns and drag Click, hold and drag a column name Click on the drop-down list next to Layout Click on the drop-down list next to Filter
Select from a list of alternative layouts for the bridge list by clicking on the down arrow beside the drop-down list that is displayed and selecting the desired layout. Select from a list of alternative filters for the bridge list by clicking on the down arrow beside the drop-down list that is displayed and selecting the desired filter. The total amount of bridges that match the filter will show next to Matching Filter in the middle of the screen located at the bottom. Locate a structure based on its Bridge ID.
You can also sort the bridge list by using the following steps: 1. Specify the sort order by clicking the column header. Initially the row will be sorted in ascending order. This column will be the primary sort column. Hold the shift key and click on another column header along the top of the Bridge List. This one will be the secondary column. Do this for every column you want to sort by and will be sorted in the order you select the columns. You can click Reset Grid Settings to remove all the sorts. 2. By default, columns sort in "Ascending" order, but you can click the column heading to toggle between "Ascending" and "Descending." If you click a row's column a second time, it
9
Click refers to one click of your left mouse button (assuming you have a right-handed mouse).
2-23
S Y S T E M
B A S I C S
will be sorted Descending. The sort status is shown by small white arrows pointing up or down in the column header. 3. Click Apply Grid Settings if you want to save the sort order you specified. If this option is clicked, then the sort order is saved, and will be restored as the default when you next open Pontis with the same login and layout. Each time the data is retrieved, it will automatically be sorted according to your specification. 4. To clear out any sort, click Reset Grid Settings.
2-24
S Y S T E M
B A S I C S
Edit Filter
2. Select ad hoc from the drop down menu labeled Select existing filter.
2-25
S Y S T E M
B A S I C S
3. Enter the search criteria into one or more of the fields at the top of the screen which can be selected by the Bridge ID, Structure Name, Facility Carried, Feature Intersected, Route, and Km. Post. 4. Filter criteria can also be entered into one or more fields located in the middle section of the screen. This area allows you to set selection criteria based on district, county, ownership, bridge status, custodian, functional class, administrative area, bridge life cycle phase, inspector(s), bridge groups, NHS status, on/off system, inspection due date, or type of inspection. To select structures based on one of these criteria, make sure the All checkbox for the criterion is unchecked, and then click on the values that you wish to include. 5. Click the Apply button located at the bottom of the screen, and a list of structures meeting the current criteria will appear on the bridge list. No other bridges will appear except those meeting the criteria.
To create a new filter and save it, use the following steps: 1. Click the Manage Filters task in the task list to the left of the Bridge List. This will open the Manage Filter sub-task page. 2. Click the Create New sub-task under Manage Filters task.
2-26
S Y S T E M
B A S I C S
4. Enter the search criteria into one or more of the fields at the top of the screen which can be selected by the Bridge ID, Structure Name, Facility Carried, Feature Intersected, Route, and Km. Post. 5. The information can also be entered into one or more fields located in the middle section of the screen. This allows you to set selection criteria based on district, county, ownership, bridge status, custodian, functional class, administrative area, bridge life cycle phase, inspector(s), bridge groups, NHS status, on/off system, inspection due date, or type of inspection. To select structures based on one of these criteria, make sure the All checkbox for the criterion is blank, and then click on the values that you wish to include. 6. Enter a description and whether you want the filter to be shared (usable by other users) and have group access. The description is a required field.
2-27
S Y S T E M
B A S I C S
Additional Information
8. Click the Apply button located at the bottom of the screen, and a list of structures meeting the current criteria will appear on the bridge list.
Edit Filters
1. Click the Manage Filters task in the task list to the left of the Bridge List. This will open the Manage Filter page. 2. Select Edit Filter if not already chosen. 3. Select which filter to edit by choosing from the drop-down menu next to Select existing filter. 4. Edit the filter by entering the values in the fields that you would want to filter. 5. Once you complete the editing, click the Save button located at the bottom of the screen. 6. Click the Apply button located at the bottom of the screen, and a list of structures meeting the current criteria will appear on the bridge list.
2-28
S Y S T E M
B A S I C S
2. Select which filter to edit by choosing from the drop-down menu next to Select existing filter. 3. Click on the Edit SQL sub-task in the task bar if not already selected.
4. The Edit SQL screen will open up, allowing the SQL to be edited directly. 5. Click on Evaluate to verify the SQL query.
6. Once you complete the editing, Click the Save button located at the bottom of the screen. 7. Click the Apply button located at the bottom of the screen, and a list of structures meeting the current criteria will appear on the bridge list.
Important Note:
If you edit a filter using SQL, you will no longer be able to edit the filter by using graphical interface of the Edit Filter sub-task since the filter will be considered a custom filter.
2-29
S Y S T E M
B A S I C S
Delete Filters
1. Click the Manage Filters task in the task list to the left of the Bridge List. This will open the Manage Filter page. 2. Select which filter to edit by choosing from the drop-down menu next to Select existing filter. 3. Click on Delete Filter located at the bottom of the screen.
2-30
S Y S T E M
B A S I C S
2. Select ad hoc from the drop down menu Select existing layout. This takes you to the Edit Layout screen.
3. Enter the search criteria into the fields by clicking on the columns. You can select more than one column or unselect in each table by holding down the Ctrl key.
2-31
S Y S T E M
B A S I C S
5. Enter custom names for the columns in the Edit Column Headings list.
6. Click on Apply. This will take you to the Bridge List with the new layout and the columns that were selected. Based upon what was chosen for the columns, this could also filter out those bridges that do not have the necessary information for the columns.
2-32
S Y S T E M
B A S I C S
To create a new layout and save it, use the following steps: 1. Click the Manage Layout task in the task list to the left of the Bridge List. This will open the Manage Layout page. 2. Click the Create New sub-task under Manage Layout task.
2-33
S Y S T E M
B A S I C S
4. Enter the search criteria into the fields by clicking on the columns. You can select more than one column or unselect in each table by holding down the Ctrl key. 5. Click Add To Layout. 6. Enter custom names for the columns in the Edit Column Headings list.
7. Enter a description and whether you want the filter to be shared. 8. Click the Save button located at the bottom of the screen.
2-34
S Y S T E M
B A S I C S
9. To view the layout, click on the View List then select the new layout you created.
Edit Layout
1. Click the Manage Layouts task in the task list to the left of the Bridge List. This will open the Manage Filter page. 2. Select which layout to edit by choosing from the drop-down menu next to Select existing layout. 3. Click the Edit Layout sub-task.
4. Edit the layout by changing the values in the fields that you want to change. 5. Once you complete the editing, click the Save button located at the bottom of the screen. 6. Click the Apply button located at the bottom of the screen, and a list of structures meeting the current criteria will appear on the bridge list.
2-35
S Y S T E M
B A S I C S
Evaluate Button
6. Once you complete editing, click the Save button located at the bottom of the screen. 7. Click the Apply button located at the bottom of the screen, and a list of structures meeting the current criteria will appear on the bridge list.
Important Note:
If you edit a layout using SQL, you will no longer be able to edit the layout by using the graphical interface of the Edit Layout option since the layout will be considered a custom layout.
Delete Filters
1. Click the Manage Layout task in the task list to the left of the Bridge List. This will open the Manage Layout page. 2. Select which filter to edit by choosing from the drop-down menu next to Select existing layout. 3. Click on Delete Layout located at the bottom of the screen.
2-36
S Y S T E M
B A S I C S
1. If you are in the Bridge List and you want your report to be based on a subset of bridges, select several bridges by checking the box next to the desired Bridge IDs and then click the Apply button. 2. Select the Reports tab from the Tab Bar. 3. The report generation window will appear. To generate a standard Pontis report, select name of the report you wish to generate by selecting from the drop-down list next to Report. 4. Choose the desired format (e.g. PDF, Text, Excel, RTF, Word, HTML for Crystal, and PDF, Text, CSV, XML, and HTML). 5. Many reports have the option to choose from various parameters. For example, summaries of element condition [insp006 and insp009] allow you to select which elements to include. You may enter one or more criteria for each column by clicking on multiple elements while holding down the CTRL key on the keyboard. You can also leave this screen blank to retrieve all records. Click OK to apply your criteria and close the screen. 6. For reports that present information on individual structures (e.g. SI&A reports, inspection schedules, lists of needs for each structure), the following options will appear: All Structures: include all bridges
2-37
S Y S T E M
B A S I C S
xx structure(s) in the list: include bridges that have been loaded into the Bridge List. (The number of bridges that have been loaded appears on the bottom of the bridge list. For example, Total Bridges:55 indicates that 55 bridges have been loaded.) x selected structures: include bridges you have selected (highlighted) on the Bridge List. Specific bridge (please enter its Bridge ID): includes only the bridge entered in manually in the space provided.
7. Click Generate Report to run the report. 8. When your report appears, you can use the Next Page and Previous Page buttons to scroll through the different pages. You can also use the scrollbar on the right side of the screen. 9. To print the report, click the Print button. You can also export the information in reports to external files using the Save button. 10. Click the Back to Report Generation button to close the Report window.
2-38
S Y S T E M
B A S I C S
Manage Layouts
Edit Layout Edit SQL Create New
Manage Filters
Edit Filter Edit SQL Create New
New Inspection
Suff Rate
Validate
Create Structure
Copy Structure
Remove Structure
Reports
Generate
2-39
S Y S T E M
B A S I C S
Admin
Security
Users Groups Roles Permissions Databases
Parameters
Element Spec
Definitions
Actions
Action Type Defs Flex Actions
Options
Export Options
Data Dictionary
Renumber BrKey
Inspection
Condition Appraisal Inventory
Admin Design Roads Agency Items
Schedule
Work
Work Candidates Project Information
Multimedia
Gateway
Export Import Check Out Check In Override
2-40
We have loaded our existing structure inventory into Pontis, and need to know how to keep this information up-to-date to reflect changes in our inventory. We are also ready to collect element-level inspection data on our structures, and want to know how Pontis can help us to plan and prepare data for these inspections. When the inspections are completed, how do we get the data into Pontis? After we get the inspection data in, what reports are available and how do we export data for NBI reporting and other purposes?
his chapter covers maintaining inventory and inspection information in Pontis, and using this information to create reports, NBI files, and other export files for use in other systems. It begins with an introduction to how Pontis inventory and inspection data is structured. Instructions are provided for adding and removing structures from the inventory, viewing and updating structure information, planning and conducting inspections, and recording inspection information. The chapter concludes with sections on common data export procedures (such as producing an NBI file) and available inspection reports. Section 3.1 of this chapter covers concepts about structures that are common to users working with either Pontis 4.5 or 5.1.2. Sections 3.2 thru 3.14 are specific to Pontis 4.5 and sections 3.15 thru 3.27 are specific to Pontis 5.1.2.
3-1
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
3.1
Important Concepts
The Pontis database stores all of the NBI-required structure inventory and condition data, and the system can be used for handling the standard NBI reporting requirements. In order to take advantage of the modeling and optimization features of Pontis, you will need to expand your inventory information to include identification of the major types of elements on each structure, and the quantity of each element. When inspections are done, you will need to assess and record the condition of each element. In order to prepare for this approach to structure inspection, it is important to understand some key concepts and definitions related to how structures are represented in Pontis, and how element conditions are determined.
Representation of Structures
A structure is a bridge, culvert, tunnel or any other structure for which data are required for the analysis. Structures can be divided into one or more smaller units, called structure units. A structure unit is any logical grouping of structure components usually having the same structural design and material. Although a structure unit can be an individual span, structure units can be used to represent groups of spans having the same structural design and material, or portions of the structure that might be rehabilitated separately (e.g. approach spans might be one unit; the main span another). In order to keep data collection manageable, it is best to define the smallest possible set of structure units that adequately captures the major structural components. To keep inspections as simple as possible, a structure need not be divided into multiple structure units the entire structure can be identified as a single structure unit. An element is an individual component type that together with other elements constitutes the structure. Pontis uses the Commonly Recognized (CoRe) structural elements which were developed by a task group of bridge engineers from six state highway agencies and the Federal Highway Administration (FHWA)10. The purpose of the CoRe elements is to provide a uniform basis for data collection for bridge management systems and to facilitate sharing of information across agencies. A guide to CoRe elements is published by the American Association of State Highway and Transportation Officials (AASHTO)11. As stated in the introduction to this guide: In general, all girders, trusses, arches, cables, floor beams, stringers, abutments, piers, pin and hangers, culverts, joints, bearings, railings, decks and slabs are included as CoRe elements. The CoRe element guide defines the measurement units for each element. When elements are first set up in Pontis, the total quantity of the structure must be supplied . If a structure has been divided into structure units, the quantity of each element on each structure unit is required.
10
While the CoRe elements are built into the standard Pontis database, agencies also have the capability to define their own unique types of elements. See Section 7.4 for further information. AASHTO Guide for Commonly Recognized Structural Elements, 1997.
11
3-2
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
Environments
The deterioration of a structure is partially determined by its environment and operating practices (e.g. weather conditions or use of road salt). To capture these effects, four standard environmental classifications have been defined: Benign - No environmental conditions affecting deterioration. Low - Environmental conditions create no adverse impacts, or are mitigated by past nonmaintenance actions or highly effective protective systems. Moderate - Typical level of environmental influence on deterioration. Severe - Environmental factors contribute to rapid deterioration. Protective systems are not in place or are ineffective.
Each element on a structure can belong to one or more of these environment classifications. While the full quantity of an element on a structure is typically in a single environment, there may be cases where an element should be split into more than one environment for example, if one portion of a structure is subject to salt spray. If an element is in more than one environment, the total quantity of the element in each environment must be determined.
Condition Measurement
During a Pontis inspection, each combination of structure unit, element, and environment is assigned one of up to five condition states. A condition state categorizes the nature and extent of damage or deterioration on a bridge element. Traditionally, each bridge element can have up to five condition states (some have less); however, starting with Pontis 5.1.2 there will only be 4 condition states available to the inspector. Condition state one is always defined as no damage. The higher the condition state, the more damage there is on the element. Condition states for each element have been precisely defined in terms of the specific types of distresses that the elements can develop.
3-3
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
Pontis stores an unlimited number of inspections for each structure in the database. Some of the information on the tab cards (e.g. condition and appraisal ratings) pertains to particular inspections, while other information pertains to the bridge (e.g. classification, identification, structural characteristics). The Inspections selection list at the top center of the screen (next to the Find button) allows you to view data from previous inspections. (When the tab cards are
3-4
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
opened, the most recent inspection is shown by default.) The number next to this list (e.g. 2 Inspections) indicates how many inspections are in the database for the current structure.
Selecting Measurement Units
There are radio buttons for selection of English or metric measurement units at the top of the screen to the right of the Inspections selection list. Pontis stores data in metric units, but you can enter or view information in English units by selecting the English radio button.
Finding NBI and Other Information on the Tab Cards
Different cards and their contents are as follows. This card shows both NBI and element condition information for the inspection date indicated in the Inspections selection list at the top of the screen. NBI condition ratings are shown for the structure at the top of the card, followed by elementlevel condition information. You can add and remove elements, and enter condition information from this card. You can also calculate the sufficiency and NBI ratings and perform data validation. (See Sections Error! Reference source not found., Error! Reference source not found. and Error! Reference source not found..)
1 Condition:
This card contains free-form notes about the structure, and about findings of the current inspection.
3 Work:
2 Notes:
This card consists of a list of work candidates identified by the inspector and a record detail for the work candidate selected from the list. Note that all work candidates for a structure are displayed on this card from the both the current and all previous inspections. Work candidates that are added here may be viewed in the Project Planning module, and used to create projects. You may use the Show Projects button to display projects that are associated with the work candidate.
4 Appraisal: This card has two tab cards of information. The first, 1 Other Ratings, shows NBI structure appraisal information, including the sufficiency rating, clearances, and navigation data. The second, 2 Load Ratings, shows operating and inventory ratings, and the posting status of the structure.
This card has five tab cards of information. 1 ID/Admin contains structure identification, location, age and service, and management information. 2 Design has information on the structural and geometric characteristics of the deck and spans. 3 Roads has data on roadways on or under the structure including traffic, clearance and classification data. 4 Structure Units contains descriptive information about structure units. 5 Classification has miscellaneous administrative and descriptive classificatory values on the structure, including a set of open 30-character width fields that your agency can use for any purpose it chooses. This card will only appear if your system administrator has set the option to turn it on in the Configuration module. It includes up to four screens which can be set up to contain information from the four special user-defined tables in Pontis which can supplement
6 Agency:
5 Inventory:
3-5
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
information provided in the standard Pontis tables. User tables are provided for bridge, inspection, roadway and structure unit information. See the Pontis Technical Manual for information on how to make use of custom user tables in Pontis.
7 Schedule:
This card contains the date and type(s) of the selected inspection, as well as information about the scheduling of subsequent inspections, and inspection resource requirements. (See Section 3.4 Reviewing and Updating Inspection Schedules for a more detailed explanation of the contents of this card.)
8 - Media: This card lets you associate multimedia documents with bridges and bridge inspections. You can also view these multimedia documents by double-clicking on the entries or using Open.
Tip:
Right-clicking on any field in Pontis, and then selecting Field Definition from the popup menu will bring up a screen documenting the item. Clicking Details in the Field Definition window will bring you to the Pontis help system topic for that field. If the field is an NBI item, the text from the NBI guide is included in the help.
The table in Appendix B provides a guide to the location of the NBI items in the Inspection Tab Cards12.
12
Items 75, 76, and 94-97 pertain to project information for the structure, and are therefore located in the Project Planning module instead of in the Inspection tab cards.
3-6
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
6. Make your desired changes, and then either select File-Save or click the Save button to save them. 7. To return to the desktop, select File-Close.
Caution: Important Note on Adding New Inspections vs. Editing Old Inspections: When you double-click on a structure in the Structure List, or select it and click Open Past, you will be viewing and changing information for a previous inspection. If you want to add information on a new inspection, select the structure, and click the New button on the desktop. For information about adding inspections, see Section 3.5.
3-7
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
3.3
Prior to adding a new structure into Pontis, you will need to assign an ID for the structure, identify its structure units, elements and environments, and assemble available data.
By default, when bridge data is imported from an NBI file, all three of these IDs are set to be the value of NBI Item 8 structure number. Similarly, when a new structure is created and a value for Item 8 is entered, the other two IDs are automatically set to this value. For agencies that will be using Pontis to import and export NBI files, the bridge key must match the structure number. Agencies can use a bridge ID that differs from the structure number.
3-8
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
3. Enter data into the fields on the screen. In the screen item names, the numbers in parentheses represent the NBI Item Number. Note that if you enter the first item, NBI Structure, and then press the <Tab> key, the other two Structure Identification items are automatically filled in to match the NBI Structure Number. 4. You have the option to create several structures in a row and then add inspection data for the structures after they are all added. If you wish to add several structures in a row, select the Build Several Structures At Once checkbox in the bottom left corner of the window. If you are only adding a single structure, de-select this checkbox. 5. If you are adding several structures at once, click OK to create the new structure and return to the desktop. A new Build A New Structure Record screen will appear for you to enter data for the next structure in your batch. When you have entered information for the last structure, click OK. A new screen ready for data entry will appear. Click Cancel to return to the desktop.
Note: When a new structure is created, records are also created for: a roadway on the structure, a structure unit, and an inspection with the current system date. This default data should be reviewed and revised on the Condition, Appraisal and Inventory tabs in the initial inspection as described below.
6. If you are not using the option to build several structures at once, you can now create an initial inspection for the new structure. To do this, click the Initial Inspection button (instead of the OK button) to create the new structure and open the Inspection tab cards
3-9
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
to enter and edit the information. Follow the procedures described in the remainder of this section to add/modify inventory information for the structure. If you have already completed an element inspection for the structure, follow the procedures in Section 3.5 Entering Inspection Information to enter the new condition data and inspector work recommendations.
2. Edit the Unit ID, Type, and Description for the structure unit. You may enter longer notes about the structure in the notes block at the bottom of the screen. (The key is assigned automatically and may not be changed). The Default Bridge Unit item is covered in the following step. 3. To add a new structure unit, click the Create button, and then enter information for the new unit. Note that only one structure unit may be designated as the default structure unit. Any new elements that are created are assigned to this structure unit. To modify the default structure unit, select the structure unit that you want to be the default from the grid-style list
3-10
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
at the top of the card, and then check the Default Bridge Unit item. The default designation is automatically removed from the previous default structure unit. 4. To remove a structure unit, first make sure that it has not been designated as the default unit. (If it has, you will need to designate another unit as the default). Then, click the Remove button. You will be asked to confirm the deletion. 5. Click the Save button to save your changes to the database.
2. Enter/update the items on the card (these are primarily NBI items). Only one roadway may be designated as a route ON the structure (by selecting Route on Structure from the Position/Prefix (5a) Item), but you can have an unlimited number of UNDER records. To designate a roadway as the ON roadway, first make sure that an ON roadway does not already exist (if so, remove it, or designate it as an under-route.) To exclude the roadway from NBI reporting, de-select the NBI Roadway item. There are five free-form fields at the bottom that can be used to store additional items about the roadway.
3-11
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
3. To add a new roadway, click the Create button, and then enter information for the roadway. If a roadway ON the structure already exists, you will need to designate the new roadway as a roadway UNDER the structure. 4. To remove a roadway, first make sure that it has not been designated as the ON-route (If it has, you will need to designate another roadway as the ON route). Then, click the Remove button. You will be asked to confirm the deletion. 5. Click the Save button to save your changes to the database.
3-12
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
5. Select the Element ID. By default, this list includes all of the CoRe elements (See Section 3.1 for a discussion of the CoRe elements). If your agency has defined your own custom elements in the Configuration module, these will also appear on the pick list. 6. Select the Structure Unit for the element. 7. Select the Environment. 8. Enter the total Quantity of the element on the selected structure unit. The measurement units are automatically determined by the specification for the element in the Configuration module. 9. (Optional) Enter the Scale Factor for this element. This has a default value of 1 (and must be greater than 0). This can be used to specify an additional measurement for the element that can be used to adjust project-level cost calculations. The type of scale factor is part of the element specification. For example, most deck elements have an overlay depth scale factor; girders and stringers which are measured in lineal feet or meters have a depth scale factor; cables which are measured in eaches have a length scale factor. (See the Technical Manual for further information.) 10. (Optional) Set the Element Record Trigger for this element. This item is used in conjunction with the Pontis Formula facility in the Configuration module, which allows you to define formulas for modifying data. (For example, a formula could be run to set initial values for the condition distribution for a given type of element, or a default value for the scale factor for an element when this value is set to 1) When the Element Record Trigger is set to ON, formulas can change the information related to the element. When it is set to OFF, formulas will not be able to update the information. (See the Technical Manual for further information.) 11. (Optional) Enter a detailed description of the element. 12. Click OK to save the information.
3-13
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
3-14
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
4. Check that the system is in edit mode. If the Edit Status Block on the bottom of the screen says EDIT OFF, click the block to toggle to EDIT ON. 5. Click on the Inspections pick list at the top of the screen to make sure that you are looking at the most recent inspection for the structure (this is displayed by default). 6. If you have not yet entered any actual inspections into Pontis for this structure (in this case there will be an empty inspection record corresponding to when you added the structure), modify the Inspection Date, Inspector (if available), and Primary Type to reflect the last inspection. (Most typical element inspections have a Primary Type of Regular NBI). While each inspection has a primary type for reporting purposes, it is common practice for more than one type of inspection to be done at the same time (e.g. a regular condition inspection and an underwater or fracture critical inspection). It is important to check off what types of inspections were actually performed this information is used to determine the next inspection dates for each required type. 7. Verify the accuracy of the information on required inspection types and frequencies in the Schedule section of the card. Most of this information is required for NBI reporting purposes. 8. If you want Pontis to re-calculate the last actual inspection dates for each type of inspection (based on the inspections in the database), click on the icon next to Last Date. Note that Last Date refers to the last date prior to the inspection currently being edited. Pontis will search for an inspection of each type prior to the currently selected inspection. If there are no inspections of a particular type in the Pontis database, a missing value for the date will be
3-15
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
shown (01/01/1901). You may enter the actual dates in place of the missing values (to reflect inspections that were done before you started entering data into Pontis), with one important exception. Pontis will issue a warning if you attempt to enter a last inspection date that is BEFORE an existing inspection of the relevant type that is in the Pontis database (and prior to the currently selected inspection.) For example, if you are looking at an NBI inspection on 1/1/2000, and the Pontis database also has an NBI inspection on 1/1/1998, you will receive a warning from Pontis if you attempt to enter 1/1/1997 for Last NBI inspection date (since Pontis knows there was actually one later than that, on 1/1/1998). 9. You can manually enter next inspection dates for the structure, or you can have Pontis calculate them. If you want Pontis to calculate the next inspection dates for each type of inspection (based on the inspections in the database and the intervals), click on the icon next to Next Date. (The update to the next inspection date does not occur automatically when you change the inspection frequency or last date you must click the inspection icon to calculate next inspection dates.) For the inspection types performed as part of the inspection, the calculations of next inspection dates are performed relative to the date of the currently selected inspection shown in the Inspections drop-down list at the top of the screen (e.g. Inspections: 10/25/2001). That is, the frequency is added to the CURRENT inspection date, not the Last Inspection date. For the inspection types not performed as part of the inspection, calculations are performed relative to the Last Inspection date. 10. If you want to see the next scheduled inspection dates of ALL types for a bridge, considering data in all of the Pontis inspection records, select Tools-Next Inspection Dates from the menu.
Example: There have been 2 inspections for the current bridge, one for 2/5/1995, and another on 2/5/1997. Both of these inspections have element and Regular NBI checked under type of inspections performed. If you select the 2/5/1995 inspection, enter a frequency of 24 months for NBI and Element inspections, and then click on the check mark above the Next Date column, you will get a 2/5/1997 for these types of inspections. Clicking on the check mark above the Last Date column will result in the missing value data for all types of inspections, since there were no inspections prior to 2/5/1995. If you select the 2/5/1997 inspection, with the same frequency of 24 months, and then click on the check mark above the Next Inspection column, you will get 2/5/1999. Clicking on the check mark above the Last Date column will result in the 2/5/1995 for NBI and Element inspections (and a missing value date for the other types of inspections).
3-16
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
11. In the Bridge Inspection Resources portion of the Schedule tab card, select the inspector to whom the next inspection is assigned from the list of inspectors. This defaults to the inspector for the current inspection. You can also assign the structure to an inspection group. Enter the group designation into the field, and it will be added to the pick list for subsequent inspections (on this and other structures). 12. You may enter the number of hours for personnel and equipment for the inspection under the Inspection Resources section. This information may be helpful for scheduling available inspection resources. 13. Select File-Save or click the Save button to commit your changes to the database.
3-17
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
Note: If you are creating a duplicate inspection, Pontis copies information from the latest inspection to the new one. If the new inspection is an element inspection, but the prior one was not, Pontis copies element condition information from the most recent element inspection in the database.13 5. The Verify Inspection Schedule screen will appear. Edit information on the inspection schedule and resources, and click OK to create the inspection. If you do not want to create the inspection, click Cancel, and then File-Close from the menu. When prompted to save changes to bridge inspection, click No.
13
If the Configuration Module Option called COPYNBIONLY is set to YES, the latest NBI inspection will be copied. Otherwise (the default), information from the latest inspection of any type will be copied.
3-18
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
6. The Inspection Condition card will be active, with edit mode set on. You can proceed to enter inspection information (see below). If you wish to enter the data later, click File-Close from the menu, and when prompted to save changes to bridge inspection, click Yes.
3-19
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
3-20
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
2. When you have finished your edits, choose File-Save or click the Save button to commit your changes to the database.
14
You can customize the options for the Status field on the Parameters card in the Configuration module the table and column name are insp_wcand.agency_status.
3-21
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
To add a new work candidate: 1. Select the Work card, and check that the system is in edit mode. If the Edit Status Block on the bottom of the screen says EDIT OFF, click the block to toggle to EDIT ON. 2. To add a work candidate, click the Create button. A detail screen for the new inspector work candidate will appear. 3. Use the pick list to select the Type of Work (Bridge, Element, or Flexible). Select Bridge if you want to recommend structure replacement or improvement actions. Select Element to recommend a preservation action on a particular element. Select Flexible if your agency has set up flexible actions in Pontis and want to recommend one of them. (Flexible actions are defined on the Actions card of the Configuration module. They can be used to define packages of element work (e.g. replace the deck and joints, all superstructure elements). They also contain rules which tell the Pontis simulation what impacts they will have on element conditions (e.g. when flexible action Replace Deck is done, all deck and joint elements will move to condition state 1)
3-22
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
For Bridge work candidates: a. Enter an ID for your work candidate. This ID can be anything you choose (e.g. a sequential number, inspector initials plus the month and year, etc.) b. Select the Action you want to recommend from the dropdown list. This list includes actions in the Structure Replacement or Improvement categories on the Action card in the Configuration module. c. Set a Priority for your work candidate. This appears on the standard Pontis report plan002_projects_candidates which shows work candidates and scheduled projects for a set of selected structures.) d. The Date Recommended will by default be set to the inspection date. You can modify this if you wish. e. Enter the Target Year for the work this is the year that you recommend the work be completed. f. For Work Assignment, , select whether the work is likely to be done by contractor or inhouse agency forces. g. Select a Status for the work candidate. This item can be used for management of the work candidate review process. h. Enter the Estimated Cost for the work candidate. i. j. Enter free-form notes about the work candidate click on the pencil icon to expand the Notes field. Choose File-Save from the menu or click the Save button to save your entries
For Element work candidates: a. Enter an ID for your work candidate. This ID can be anything you choose (e.g. a sequential number, inspector initials plus the month and year, etc.). b. If the structure has more than one structure unit, you can either specify the structure unit on which the work is recommended, or you can select All Units from the Structure Unit dropdown list. c. Select the Element you want to recommend the work for. The dropdown list will contain all the elements that belong to the specified structure unit. d. Select the Action you want to recommend from the dropdown list. This list will include the action types that have been defined for the selected element (in any condition state) on the Element Specifications card in the Configuration module.
3-23
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
e. Set a Priority for your work candidate. This appears on the standard Pontis report plan002_projects_candidates which shows work candidates and scheduled projects for a set of selected structures.) f. The Date Recommended will by default be set to the inspection date. You can modify this if you wish. g. Enter the Target Year for the work this is the year that you recommend the work be completed. h. For Work Assignment, select whether the work is likely to be done by contractor or inhouse agency forces. i. j. Select a Status for the work candidate. This item can be used for management of the work candidate review process. Enter the quantity of the element needing work. The Estimate! button sets the Estimated Quantity to the quantity of the element in each of the applicable condition states selected by the user. Please note that the calculation will be done for the selected structure unit(s) as recorded on the Condition card. For example, if a bridge had a 3,000 SF deck, with 1000 SF in structure unit 0 and 2000 SF in structure unit 1 and a work candidate was set up to include only structure unit 1, the Estimate! button would calculate a quantity of 1000 SF.
k. Enter the Estimated Cost for the work candidate. The Estimate! button calculates the Estimated Cost by multiplying the quantity of the selected element in each applicable state by the cost for the action stored in the ACTMODLS table multiplied by the scale factor for the element. If the action of the specified type is not specified for a given state, a cost of 0 will be used for that state. l. If you want to simulate the impacts of a work candidate in the Project Planning module, select which condition states you would like the action to be applied (if feasible). Click on the applicable condition states or click on the Select All button to apply the action to all condition states. It is recommended that you select all condition states here only actions which have been defined as feasible for a given condition state (on the Element Specifications card of the Configuration module) will be applied.
m. Enter free-form notes about the work candidate click on the pencil icon to expand the Notes field. n. Choose File-Save from the menu or click the Save button to save your entries For Flexible work candidates: a. Enter an ID for your work candidate. This ID can be anything you choose (e.g. a sequential number, inspector initials plus the month and year, etc.).
3-24
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
b. If the structure has more than one structure unit, you can either specify the structure unit on which the work is recommended, or you can select All Units from the Structure Unit dropdown list. c. Select the Action you want to recommend from the dropdown list. This will include all of the flexible actions that have been set up on the Actions card of the Configuration module. d. Set a Priority for your work candidate. This appears on the standard Pontis report plan002_projects_candidates which shows work candidates and scheduled projects for a set of selected structures.) e. The Date Recommended will by default be set to the inspection date. You can modify this if you wish. f. Enter the Target Year for the work this is the year that you recommend the work be completed. g. For Work Assignment, , select whether the work is likely to be done by contractor or inhouse agency forces. h. Select a Status for the work candidate. This item can be used for management of the work candidate review process. i. j. Enter the Estimated Cost for the work candidate. Enter free-form notes about the work candidate click on the pencil icon to expand the Notes field.
k. Choose File-Save from the menu or click the Save button to save your entries
3-25
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
To associate a multimedia document with a bridge or bridge inspection: 1. Select the Media card in the Inspection tab cards. 2. Press the Link button. Pontis displays a window for you to use to browse for the multimedia document that you want to associate with the bridge or inspection. 3. If desired, enter a descriptive note for the document, and/or select an agency type for the document. Once you have associated a multimedia document with a selected bridge or inspection, you can display the thumbnail image at full-size. When you select Open or click on the thumbnail image displayed with the file information, the associated Windows application for viewing the document will be launched, retrieving the document and allowing you to view it at full size. You can display any of the following standard Windows file types and others, provided you have loaded an application that can interpret them: BMP, GIF, JPG, PDF, PCX, TXT, HTML, XLS, PPT, and DOC.
To remove the association of a multimedia document with a bridge or bridge inspection: 1. Select the multimedia document you want to unlink. 2. Press the Unlink button. Pontis deletes the reference link from the database. The actual document file is not affected and must be removed externally.
3-26
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
3-27
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
3.6 Using Paper Forms for Inspection Data Entry (Version 4.5)
1. (Optional) Develop an inspection data entry form. Pontis comes with standard structure information and SI&A reports (insp007_inspection_sia_english or insp008_inspect_report_english or insp002_inspect_report_metric or insp001_inspection_sia_metric) which can be used to record inspection information (or to attach to a standard blank paper form). Alternatively, a customized form may be developed within InfoMaker using this report as a starting point. See the Technical Manual for procedures on creating custom forms and reports. 2. Select the structures to be inspected from the Structure List on the Desktop. 3. Click on the Reports button on the Inspection desktop. 4. If you are using one of the standard Pontis inspection reports for your data collection, click on View Inspection Results. If you are using a custom form, click on View User Reports. 5. Select your custom inspection report, or the standard Pontis report you are using from the selection list. 6. Click on the Print button. 7. The Datawindow Print Option window will appear. You may select a printer, specify the number of copies to be printed, select a subset of pages for printing, or have the report printed to a file. After selecting the desired options, click OK to send the report to the printer/file. 8. Once the forms are filled-in, use the procedures described in Section 3.5 to enter the data into Pontis.
3-28
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
4. The color of the Accept column indicates whether there were notices, errors or warnings for the particular structure. Red indicates an error, which means that the calculated ratings for the structure may not be accepted. Yellow indicates a warning, blue indicates a notice, and green indicates success. The first 32 K bytes of the NBI Translator log file are shown in the window at the bottom of the screen. You can click on a row, and then click on the Find button to move to the error, warning or notice associated with the selected structure. If necessary, correct problems indicated by the errors, warnings and notices and re-run the translator to obtain acceptable results.
3-29
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
5. To accept all of the calculated ratings and save them to the database, click on the Accept All button. To accept only some of the ratings, click an X into the Accept column, then click on the Accept button. This will save the selected ratings to the database. Those ratings that were not accepted will be discarded, and the previously existing ratings for those structures will be kept. Click on the Cancel button to close the screen.
3-30
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
3-31
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
3-32
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
5. To accept all of the calculated ratings and save them to the database, click on the Accept All button. To accept only some of the ratings, click an X into the Accept column, then click on the Accept button. This will save the selected ratings to the database. Ratings that are not accepted will be discarded, and the previously existing ratings will remain unchanged in the database. Click on the Cancel button to close the screen.
3-33
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
3.9
Pontis can perform data validation checks such as the Federal Highway Administration (FHWA) Edit/Update check for the selected bridges. 1. Prior to performing data validation, make sure the inspection data are up-to-date. 2. If you are in the Inspection tab cards, perform data validation for the current structure by clicking on the Validate button on the Condition card. 3. You can perform data validation for a group of structures from the Inspection desktop. To do this, click on the Layout button, and select a layout. You will normally want to select all of the structures on this list, using the Select All button. If you prefer, you can select smaller groups of structures from the list by clicking on them. 4. Click the Validate button on the desktop toolbar. The data validation will be performed for your selected structure(s), and the Validation Results screen will appear. The top pane of the screen displays the selected structure(s). The bottom pane shows warnings and fatal errors generated by the data validation routine. 5. To display the validation result for all selected structures, check the Show All Results checkbox. To view the result for one structure at a time, uncheck the checkbox. You must close the screen to edit the data.
3-34
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
1. Check with the system administrator to make sure that you have the necessary privileges to delete an inspection. 2. Get into the Pontis Inspection module. 3. Use the Find button OR double-click on the structure in the structure list OR single-click on the structure and then click on the Open Past button to open the Inspection tab cards for the structure. 4. If more than one inspection exists for the structure, use the Inspections selection list at the top of your screen to select the date of the inspection you wish to delete. The inspection information will be displayed. 5. Check that the system is in edit mode. If the Edit Status Block on the bottom of the screen says EDIT OFF, click the block to toggle to EDIT ON. 6. From the menu bar at the top of your screen, select Tools Delete Inspection. If this option is grayed out, either you do not have permission to delete inspections or the edit status block is showing EDIT OFF. 7. A confirmation message will appear at the bottom of screen. Click Yes to complete the deletion. All data associated with the inspection will be deleted permanently.
3-35
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
1. Check with the system administrator to make sure that you have the necessary privileges to delete a structure. 2. Get into the Inspection module. 3. Select the structure(s) you wish to delete. It is good practice to click the Only Selected button to clearly view the set of structures you have selected before performing a delete. 4. Click the Remove button. You will be given a second chance to verify that you really want to delete the structure. If you click OK, the structure will be permanently removed from the database, and all associated data will be lost.
3-36
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
Note: Data from any report can be exported to common text, spreadsheet or database formats by using the Save Rows As menu item in the Report Viewer. Data from the current structure list can also be exported to a variety of file formats by right-clicking on the Structure List and selecting Export Data from the popup menu.
Tip: You may wish to save a layout with this filter condition so that you dont have to set it each time you export NBI files. To do this, click the Save button above the Structure List. When the Save Structure List screen appears, enter a name for the layout. It must begin with XL_ and have no embedded spaces, e.g. XL_NBI. Enter a comment to describe the list, e.g. Bridges for NBI Export. Then click OK to save the new layout.
4. Click on the Export button. The Export Data window will appear. 5. Select Metric NBI File or English NBI File from the Export What? selection list. 6. Enter the name of the output file you wish to produce. Use the Browse button to navigate to the desired location for the output file. 7. Select which structures to include in the NBI file. Select the All Bridges Meeting Select Criteria option if you want to select all bridges which meet the current criteria as specified in the Select Structures screen. 8. Click Export. See the Technical Manual for details on how Pontis data fields are converted to NBI fields.
3-37
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
3-38
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
15
The Pontis Lite installation option includes only the Inspection and Gateway modules, and is designed to support the field inspection process.
3-39
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
Note: only structures that have been checked out using the Check-Out feature, can be checked in. For other structures, use Import instead of Check-In.. 1. Prior to checking in a PDI file, review the status of checked-out structures, and see if any have had data changed since the check-out. To do this, click on the Layout button on the Structure List, and select the layout called Checked-out bridges (xl_checked_out). Structures that have had information modified since being checked out will show a Yes in the Changed Since Check-Out column. 2. Click on the Check-In button on the Inspection or Gateway desktop. The Check-In Data window will appear. 3. Select Pontis Data Interchange from the Import What? list. 4. Use the Browse button to navigate to the path and file name for the PDI file you wish to check back in. 5. Click the Check-In button. 6. The system will check the structures in the PDI file against the database, and make sure that they exist, and that they have not already been checked-in. If a structure does not exist in the database, or if it has already been checked back in, an exception will be recorded. If data for the structure have been changed in the master database after the structure was checked-out, an exception will also be recorded. To review exceptions, click Accept Exceptions. Click an X into the Accept column for those structures you wish to accept into the database, and then click on the Accept button. To accept all exceptions, click on the Accept All button. Then click on the Re-Check-In button. If you dont wish to accept any of the exceptions, click Finished, and then Cancel.
Note: Overriding exceptions is a privileged function and appropriate security must be granted by the system administrator.
3-40
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
3-41
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
In addition, the Tabcard Inspection Report is a special report which sends images of all of the Inspection tab card screens directly to the printer. (This report is not available from the Report Viewer.) To print this report: 1 2 3 4 Make sure your printer is on and ready. Select a structure on the list with the mouse. Click on the Reports button. Click on the Run Tabcard Inspection Report button. This report will be automatically sent to the printer.
3-42
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
Inspection Tab
If you select a bridge in the Bridge List by clicking anywhere on its row, the bridge will be highlighted and more information about the bridge will display below the bridge list. In the figure below, a user clicked on bridge 04 09175, which highlighted the information on its row and displayed bridge photos and inspection information in the panels below the list. To access the specific and editable inspection information, click on the Inspection tab at the top of the page. Doing so will take you to the inspection pages for the highlighted bridge.
3-43
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
The following figure shows the initial page of the Inspection task. The Condition task is the first task you will see unless your agency has changed the task list on the left.
Pontis stores an unlimited number of inspections for each structure in the database. Some of the information on the task screen (e.g. condition and appraisal ratings) pertains to particular inspections, while other information pertains to the bridge (e.g. classification, identification, structural characteristics). The Inspection drop down list at the top center of the screen allows you to view data from previous inspections. (When the task is opened, the most recent inspection is shown by default.)
Selecting Measurement Units
There are radio buttons for selection of English or metric measurement units at the top of the screen to the right of the Inspections drop down list. Pontis stores data in metric units, but you can enter or view information in English units by selecting the English radio button.
Finding NBI and Other Information on the Inspection Task Screens
This task screen shows both NBI and element condition information for the inspection date indicated in the Inspections selection list at the top of the screen. NBI condition ratings are shown for the structure at the top of the card, followed by element-level condition information. You can add and remove elements, and enter condition information from this card. You can also calculate the sufficiency and NBI ratings and perform data validation. (See Sections Error! Reference source not found., 3.20 and 3.21.)
This task screen shows NBI structure appraisal information, including the sufficiency rating, clearances, and navigation data. This task screen also shows operating and inventory ratings, and the posting status of the structure.
Appraisal:
3-44
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
This task screen has four sub-tasks. Admin contains structure identification, location, age and service, management information and miscellaneous administrative data, and descriptive classificatory values on the structure. Design has information on the structural and geometric characteristics of the deck and spans, plus descriptive information about structure units. Roads has data on roadways on or under the structure including traffic, clearance and classification data. Agency Items has a set of open 30-character width fields that your agency can use for any purpose it chooses.
Schedule: This task screen contains the date and type(s) of the selected inspection, as well as information about the scheduling of subsequent inspections, and inspection resource requirements. (See Section 0 Reviewing and Updating Inspection Schedules for a more detailed explanation of the contents of this task.)
Inventory:
This task screen has two sub-tasks. Work Candidates consists of a list of work candidates identified by the inspector and a record detail for the work candidate selected from the list. Note that all work candidates for a structure are displayed on this task screen from both the current and all previous inspections. Work candidates that are added here may be viewed in the Project Planning module of Pontis 4.5, and used to create projects. Project Information shows projects that are associated with the bridge. This task screen lets you associate multimedia documents with bridges and bridge inspections. You can also view these multimedia documents by clicking on the entries or using Open.
Agency: This task will only appear if your system administrator has set the option to turn it on in the Navigation and Field Level Security task under the Admin tab. It may or may not include sub-tasks which can be set up to contain information from the four special userdefined tables in Pontis which can supplement information provided in the standard Pontis tables. User tables are provided for bridge, inspection, roadway and structure unit information. See the Pontis Technical Manual for information on how to make use of custom user tables in Pontis. Multimedia:
Work:
Tip:
Place your mouse over any field in Pontis to bring up a screen documenting the item. Hover over labels for drop-down lists or over the field directly for other control types to see the documentation.
The table in Appendix B provides a guide to the location of the NBI items in the Inspection Tab16.
16
Items 75, 76, and 94-97 pertain to project information for the structure, and are therefore located in the Project Planning module of Pontis 4.4 instead of in the Inspection tab of Pontis 5.x.
3-45
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
1. From the View List of the Bridges tab, click on a structure to highlight it and then click on the Inspection tab OR click in the checkbox to the left of a structures Bridge ID, click the Apply button and then click the Inspection tab. 2. The Condition task of the Inspection tab for the most recent inspection of the selected structure will appear. 3. Select the inspection you wish to view/edit from the Inspection selection list at the top of the screen. 4. Select the task with information you wish to edit. Note that the Inventory and Work tasks have sub-tasks as well. 5. Depending on your privileges, you may not be able to edit certain items. 6. Make your desired changes, and then the Save button to save them. 7. To return to the View List, click on the Bridges tab.
Caution: Important Note on Adding New Inspections vs. Editing Old Inspections: When you highlight a structure in the View List and then click on the Inspection tab, or select it and click on the Inspection tab, you will be viewing and changing information for a previous inspection. If you want to add information on a new inspection, highlight or select the structure, and click the New Inspection task in the task menu on the left. For information about adding inspections, see Section 3.5.
3-46
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
By default, when bridge data is imported from an NBI file, all three of these IDs are set to be the value of NBI Item 8 structure number. Similarly, when a new structure is created and a value for Item 8 is entered, the other two IDs are automatically set to this value. For agencies that will be using Pontis to import and export NBI files, the bridge key must match the structure number. Agencies can use a bridge ID that differs from the structure number.
2. Enter data into the fields on this screen. On this page the item names, which are given as numbers in parentheses, represent the NBE Item Number. Note that if you enter the first item, NBE Structure No, and then press the <TAB> key, the other two Structure Identification items are automatically filled in to match the NBE Structure Number.
3-47
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
3. You have the option to create several structures in a row and then add inspection data for the structures after they are all added. If you wish to add several structures at one time, click the Build Several Structures At Once checkbox in the bottom middle of the window. If you are only adding a single structure, make sure this box is not checked (default setting).
Note: When a new structure is created, records are also created for: a roadway on the structure, a structure unit, and an inspection with the current system date. This default data should be reviewed and revised on the Condition, Appraisal and Inventory tabs in the initial inspection as described below.
4. If you are adding several structures at once, click Save to create the new structure. A new Create New Structure screen will appear for you to enter data for the next structure in your batch. When you have entered information for the last structure, click Save. A new screen ready for data entry will appear. Click Cancel to return to the View List. If you are not using the option to build several structures at once, you can now create an initial inspection for the new structure. To do this, click the Initial Inspection button (instead of the OK button) to create the new structure and open the Condition task of the Inspection tab to enter and edit the information. Follow the procedures described in the remainder of this section to add/modify inventory information for the structure. If you have already completed an element inspection for the structure, follow the procedures in Section 3.18 Entering Inspection Information (Version 5.1.2) to enter the new condition data and inspector work recommendations.
3-48
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
2. Edit the Unit, Type, and Description for the structure unit. You may enter longer notes about the structure by clicking on the in the following step. symbol in the Notes column. The Default item is covered
3. To add a new structure unit, click the Add New button, and then enter information for the new unit. Note that only one structure unit may be designated as the default structure unit. Any new elements that are created are assigned to this structure unit. To modify the default structure unit, select the structure unit that you want to be the default from the grid-style list, and then check the Default item. The default designation is automatically removed from the previous default structure unit. 4. To remove a structure unit, first make sure that it has not been designated as the default unit. (If it has, you will need to designate another unit as the default before you may delete the unit). Then, click the Delete button, which looks like a garbage can. confirm the deletion. 5. Click the Save button to save your changes to the database. You will be asked to
3-49
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
2. Enter/update the items on the screen (these are primarily NBI items). Only one roadway may be designated as a route ON the structure (by selecting Route on Structure from the Roadway (005A) item), but you can have an unlimited number of UNDER records. To designate a roadway as the ON roadway, first make sure that an ON roadway does not already exist (if so, remove it, or designate it as an under-route.) To exclude the roadway from NBI reporting, de-select the NBI Rte item in the Alternate Classifications group. There are five free-form fields at the bottom that can be used to store additional items about the roadway. 3. To add a new roadway, click the Create button, and then enter information for the roadway. If a roadway ON the structure already exists, you will need to designate the new roadway as a roadway UNDER the structure. 4. To remove a roadway, first make sure that it has not been designated as the ON-route (If it has, you will need to designate another roadway as the ON route). Then, click the Remove button. You will be asked to confirm the deletion. 5. Click the Save button to save your changes to the database.
3-50
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
the Pontis elements match the AASHTO NBE/BME elements, though new elements may be added. For each of these element/structure unit combinations, you must decide whether a single environment classification is appropriate, or if youd like to split the element into two or more environments. You will end up with a set of unique structure unit/element/environment combinations, each of which must have a quantity. To set up elements for a new structure: 1. For your selected bridge, click the Schedule task in the Inspection tab. Make sure that the Element Condition checkbox is selected under Types of Inspections Performed. If it is not, select it and click the Save button. 2. Select the Condition task in the Inspection tab. 3. Make sure that the Metric /English radio button is set to the measurement units that you would like to use for specifying the element quantity. 4. Click on the Add New Element button. The Add Element screen will appear.
5. Select the Element ID. By default, this list includes all of the NBE/BME elements. If your agency has defined your own custom elements in the Configuration module, these will also appear on the pick list. 6. Select the Parent Element: 7. Select the Structure Unit for the element.
3-51
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
8. Select the Environment. 9. Enter the total Quantity of the element on the selected structure unit. The measurement units are automatically determined by the specification for the element in the Configuration module. 10. (Optional) Enter the Scale Factor for this element. This has a default value of 1 (and must be greater than 0). This can be used to specify an additional measurement for the element that can be used to adjust project-level cost calculations. The type of scale factor is part of the element specification. For example, most deck elements have an overlay depth scale factor; girders and stringers which are measured in lineal feet or meters have a depth scale factor; cables which are measured in eaches have a length scale factor. (See the Technical Manual for further information.) 11. (Optional) Enter a detailed description of the element. 12. Click OK to save the information.
3-52
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
3. The items on the screen will be affected by your level of privileges. If you dont have the correct privileges, much of this screen wont be editable.
3-53
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
4. Click on the Inspection pick list at the top of the screen to make sure that you are looking at the most recent inspection for the structure (this is displayed by default). 5. If you have not yet entered any actual inspections into Pontis for this structure (in this case there will be an empty inspection record corresponding to when you added the structure), modify the Inspection Date, Inspector (if available), and Primary Type to reflect the last inspection. (Most typical element inspections have a Primary Type of Regular NBI). While each inspection has a primary type for reporting purposes, it is common practice for more than one type of inspection to be done at the same time (e.g. a regular condition inspection and an underwater or fracture critical inspection). It is important to check off what types of inspections were actually performed this information is used to determine the next inspection dates for each required type. 6. Verify the accuracy of the information on required inspection types and frequencies in the Schedule section of the screen. Most of this information is required for NBI reporting purposes. 7. If you want Pontis to re-calculate the last actual inspection dates for each type of inspection (based on the inspections in the database), click on the Calculate Last button. Note that the dates in the Last Date column refer to the last date prior to the inspection currently being edited. Pontis will search for an inspection of each type prior to the currently selected inspection. If there are no inspections of a particular type in the Pontis database, a missing value for the date will be shown (01/01/1901). You may enter the actual dates in place of the missing values (to reflect inspections that were done before you started entering data into Pontis), with one important exception. Pontis will issue a warning if you attempt to enter a last inspection date that is BEFORE an existing inspection of the relevant type that is in the Pontis database (and prior to the currently selected inspection.) For example, if you are looking at an NBI inspection on 1/1/2009, and the Pontis database also has an NBI inspection on 1/1/2007, you will receive a warning from Pontis if you attempt to enter 1/1/2006 for Last NBI inspection date (since Pontis knows there was actually one later than that, on 1/1/2007). 8. You can manually enter next inspection dates for the structure, or you can have Pontis calculate them. If you want Pontis to calculate the next inspection dates for each type of inspection (based on the inspections in the database and the intervals), click on the Calculate Next button. (The update to the next inspection date does not occur automatically when you change the inspection frequency or last date you must click the inspection icon to calculate next inspection dates.) For the inspection types performed as part of the inspection, the calculations of next inspection dates are performed relative to the date of the currently selected inspection shown in the Inspections drop-down list at the top of the screen (e.g. Inspections: 10/25/2001). That is, the frequency is added to the CURRENT inspection date, not the Last Inspection date. For the inspection types not performed as part of the inspection, calculations are performed relative to the Last Inspection date.
3-54
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
Example: There have been 2 inspections for the current bridge, one for 2/5/1995, and another on 2/5/1997. Both of these inspections have element and Regular NBI checked under type of inspections performed. If you select the 2/5/1995 inspection, enter a frequency of 24 months for NBI and Element inspections, and then click on the Calculate Next button, you will get a 2/5/1997 for these types of inspections. Clicking on the Calculate Next button will result in the missing value data for all types of inspections, since there were no inspections prior to 2/5/1995. If you select the 2/5/1997 inspection, with the same frequency of 24 months, and then click on the Calculate Next button, you will get 2/5/1999. Clicking on the Calculate Last button will result in the 2/5/1995 for NBI and Element inspections (and a missing value date for the other types of inspections).
9. In the Inspection Resources group of the Schedule task screen, select the inspector to whom the next inspection is assigned from the list of inspectors. This defaults to the inspector for the current inspection. You can also assign the structure to an inspection group. Enter new group designations to this field through the Parameters task on the Admin tab. Once added, a parameter will be available on the pick list for subsequent inspections (on this and other structures). 10. You may enter the number of hours for personnel and equipment for the inspection under the Inspection Resources section. This information may be helpful for scheduling available inspection resources. 11. Click the Save button to commit your changes to the database.
3-55
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
3. If you want the new inspection to be created with the same information as the last inspection, select the Duplicate Previous checkbox. If you want the new inspection to be blank, with elements initialized to the best condition state, de-select the Duplicate Previous checkbox.
3-56
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
4. If the new inspection is an element-level inspection, select the Element Inspection checkbox. Otherwise, make sure this box is empty. 5. Click the Create button. The Schedule screen will appear. Enter the date that the new inspection was done, the name of the Inspector, and the primary type for the inspection. Check off the specific types of inspections to be done. Note that all of this information can be modified later. However, if you will be entering element inspection data, be sure that the Element checkbox is selected. Be sure to edit information on the inspection schedule and resources.
Note: If you are creating a duplicate inspection, Pontis copies information from the latest inspection to the new one. If the new inspection is an element inspection, but the prior one was not, Pontis copies element condition information from the most recent element inspection in the database.17
6. To retain your inspection, click Save. If you want to retain your inspection and come back later to change or add data, click Save & Close. If you do not want to create the inspection, click Cancel. When prompted to navigate away from the page, click OK. 7. If you clicked Save, you will be transferred to the Condition task of the Inspection tab. You can proceed to enter inspection information (see below). If you wish to enter the data later click Save & Close.
17
If the Configuration Module Option called COPYNBIONLY is set to YES, the latest NBI inspection will be copied. Otherwise (the default), information from the latest inspection of any type will be copied.
3-57
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
2. If you do not see any element information or buttons for adding or removing elements, this means that the inspection you are editing was not designated as an Element inspection. Select the Schedule task, and select the Element Condition checkbox under Types of Inspections Performed. Click the Save button. Select the Condition task again, and you should see the element-related buttons, and whatever elements were set up on the previous element inspection. 3. To change the quantity of an element on the structure, edit the quantity directly in the Condition task. You will be asked to confirm that you want to change this quantity for this and any later inspections. 4. To change the structure unit or environment for an element, make the changes directly on the screen. Click Save. 5. To replace an element on the structure, you will need to add a new element (using the Add ). When you remove an element, you will need to confirm that you want to remove the element from this and any existing later inspections. If you want to remove any work recommendations and project work items for the element, click the checkbox in the Delete WCand column before clicking the Delete button.
New Element button), and then delete the old one (using the Delete button
3-58
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
100 percent), a message will be displayed and you will need to modify your entries before moving to a new element. For elements which have the Inspect as Each option selected on the Element Spec task screen in the Admin task, you must enter 100 percent in a single condition state. (By default, all deck elements are designated as Inspect as Each, shown with (ea) after the element description.) 4. Enter NBI condition ratings at the top of the screen. If you have entered element condition distributions, you have the option of using the NBI Translator button to calculate the NBI ratings. To enter notes: 1. Pontis is designed to store notes about the bridge as a whole, about each structure unit and roadway on/under the bridge, about the overall inspection, and about each element inspected. The notes for the bridge, structure unit and roadways are part of the inventory, and do not change when you switch inspections or enter a new inspection. Notes about the inspection and the elements change with each inspection. Notes about the bridge can be entered in the Bridge Notes item on the Admin sub-task under the Inventory task on the Inspection tab. Notes about the inspection can be entered by clicking on the notes icon near the top of the Condition task screen under the Inspection tab. Notes about structure units and roadways are entered on the Inventory task screen (Design and Roads sub-tasks). To enter notes about a particular element, select the Condition task, select the element by clicking on the select triangle ( ), and then click on the notes icon bottom of the screen. in the area that opens at the
2. When you have finished your edits, click the Save button to commit your changes to the database.
3-59
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
Status field18 to keep track of which work candidates have already been addressed, and should no longer be examined in the project planning process.
To add a new work candidate: 1. Select the Work Candidate sub-task screen. 2. To add a work candidate, click the Add New button. A new row in the grid for the new inspector work candidate will appear. The new row will be selected and the area at the bottom of the screen, which corresponds to the new row, will be available for editing. a. Enter a Candidate ID for your work candidate. This ID can be anything you choose (e.g. a sequential number, inspector initials plus the month and year, etc.). b. If the structure has more than one structure unit, you can either specify the structure unit on which the work is recommended, or you can select 9999 - All StrUnits from the Structure Unit dropdown list. c. Select the Action you want to recommend from the dropdown list. This will include all of the flexible actions that have been set up in the Flex Actions sub-task of the Actions task on the Admin tab. d. Set a Priority for your work candidate. This appears on the standard Pontis report plan002_projects_candidates which shows work candidates and scheduled projects for a set of selected structures. e. The Date Recommended will by default be set to the inspection date. You can modify this if you wish.
18
You can customize the options for the Status field on the Parameters task screen of the Admin tab the table and column name are insp_wcand.agency_status.
3-60
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
f. Enter the Target Year for the work this is the year that you recommend the work be completed. g. For Work Assignment, select whether the work is likely to be done by contractor or inhouse agency forces. h. Select a Status for the work candidate. This item can be used for management of the work candidate review process. i. j. Enter the Estimated Cost for the work candidate. Enter free-form notes about the work candidate click on the notes icon to expand the Notes field.
3-61
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
If your agency has added a customized inspection information table and form containing special data elements that are not in the standard Pontis database, select the Agency tab, and enter the required information. This card can contain additional information about bridges, structure units, roadways, and inspections. To use the Agency tab, your system administrator must create the new data items in the Pontis database, create the tab using the Navigation and Field Security task, and set the necessary security options to make the tab active. The Technical Manual provides detailed instructions on setting up custom forms in Pontis.
3-62
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
3-63
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
To remove the association of a multimedia document with a bridge or bridge inspection: 1. Select the multimedia document you want to unlink by clicking on the select triangle. 2. Press the Unlink button. Pontis deletes the reference link from the database. The actual document file is not affected and must be removed externally.
3-64
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
3.19 Using Paper Forms for Inspection Data Entry (Version 5.1.2)
(Optional) Develop an inspection data entry form. Please see the Pontis Technical Manual for instructions on how to create, register and use custom agency data forms.
3-65
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
5. To accept all of the calculated ratings and save them to the database, click on the Accept All button. To accept only some of the ratings, click the Accept column for the bridge(s) you want, and then click on the Accept button. This will save the selected ratings to the database. Ratings that are not accepted will be discarded, and the previously existing ratings will remain unchanged in the database. Click on the Cancel button to close the screen.
3-66
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
3-67
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
3-68
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
to delete an inspection. 2. Select or highlight a structure and click on the Inspection tab. 3. If more than one inspection exists for the structure, use the Inspections selection list at the top of your screen to select the date of the inspection you wish to delete. The inspection information will be displayed. 4. Click the Delete Inspection button. If this option is grayed out, then you do not have permission to delete inspections. 5. A confirmation message will appear; click OK to complete the deletion. All data associated with the inspection will be deleted permanently.
3-69
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
1. Check with the system administrator to make sure that you have the necessary privileges to delete a structure. 2. Select or highlight a structure and click on the Inspection tab. 3. Select the structure(s) you wish to delete. It is good practice to click the Just Selected sub-task on the View List to clearly view the set of structures you have selected before performing a delete. 4. Click the Remove Struct task in the menu on the left. You will see a list of the selected bridges. Click the Remove button. You will be given a second chance to verify that you really want to delete the structure. If you click OK, the structure will be permanently removed from the database, and all associated data will be lost.
3-70
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
Note: Data from any report can be exported to common text, spreadsheet or database formats by selecting the desired format in the Reports tab. Data from the current structure list can also be exported to a variety of file formats by selecting the structure(s) you wish to export and clicking on the Gateway tab.
Tip: You may wish to use a combination of the Manage Layouts and Manage Filters tasks to retain your customized list of structures for NBI export.
5. The default option is XML, therefore, you will have to manually select Metric NBI File or English NBI File from the Export What? selection list. 6. Click on the Export button. A dialog will appear telling you that the export is in process. 7. When complete, you will see a message to that effect in the box at the bottom of the screen, and you will be prompted to save the export file to a location of your choice.
3-71
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
8. Click the Save button and enter the name of the output file you wish to produce. Use the Save As dialog to navigate to the desired location for the output file. 9. Click Save to save the file. See the Technical Manual for details on how Pontis data fields are converted to NBI fields.
3-72
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
10. Click on the Gateway tab and you will see a list of the bridges you selected. The screen defaults to the Export task. IF you wish to export to PDI, stay on this task. If you wish to check out structures, click on the Check Out task. 11. Select Pontis Data Interchange File or Pontis Data Interchange Custom Export File from the Export What? selection list. If you are checking out data, this list will be labeled Check-Out What? 12. If exporting to a non-custom PDI formant, the Include list is set to <01> Bridge Data by default, although several other options are available. Select the data you wish to include in your export. If you selected the custom PDI option, the Include list is not available. 13. Select what data are to be included in the PDI export file. Options are to export bridge data only (use this option for field inspections) non bridge data, all data, data from a single selected table, data from a custom list of tables, scenario summary data, or scenario detail data. If you are checking out data, only two options, bridge data only and non bridge data, are available. If you wish to use the custom list of tables option, use the Export Options task on the Admin tab to define the list. See the Technical Manual for more information. 14. Click Export or Check-Out. A dialog will appear telling you that the export is in process. 15. When complete, you will see a message to that effect in the box at the bottom of the screen, and you will be prompted to save the export file to a location of your choice. 16. Click the Save button and enter the name of the output file you wish to produce. Use the Save As dialog to navigate to the desired location for the output file. 17. Click Save to save the file.
3-73
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
2. Install Pontis onto the field computer using the Workstation installation option on the Pontis Installation CD. You will need to install an empty database that matches the structure of the master database (the working database is fine assuming no customizations have been made) and set up an ODBC data source on the field computer for this database using the ODBC tool in your Windows control panel. See the Pontis Installation Guide for more details. 3. Copy the PDI file onto your field computer, or attach your field computer to the network. 4. Import the PDI file into the database on your field computer, following the procedure described in Section 1.3. 5. Add inspections and enter inspection data for each of the structures in the field computer database. 6. In the field computer, check out completed inspections to a PDI file using the procedure described in Section 3.24. 7. Copy the PDI file with the completed inspections onto your office computer hard disk or network drive, or attach your field computer to the network. 8. Check in the PDI file with completed inspections into the master database, following the procedure described below.
Checking in a PDI File
Note: only structures that have been checked out using the Check-Out feature can be checked in. For other structures, use Import instead of Check-In. 1. Prior to checking in a PDI file, review the status of checked-out structures, and see if any have had data changed since the check-out. To do this, go to the Bridges tab and select the layout called Checked-out bridges. Structures that have had information modified since being checked out will show a Yes in the Changed Since Check-Out column. 2. Click on the Gateway tab and click on the Check-In task. 3. Select Pontis Data Interchange from the Import What? list. 4. Use the Browse button to navigate to the path and file name for the PDI file you wish to check back in. 5. Click the Check-In button. You will be prompted to continue. Click OK. 6. The system will check the structures in the PDI file against the database, and make sure that they exist, and that they have not already been checked-in. If a structure does not exist in the database, or if it has already been checked back in, an exception will be recorded. If data for the structure have been changed in the master database after the structure was checked-out, an exception will also be recorded. To review exceptions, click Accept Exceptions. Click an X into the Accept column for those structures you wish to accept into the database, and then click on the Accept button. To accept all exceptions, click on the Accept All button.
3-74
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
Note: Overriding exceptions is a privileged function and appropriate security must be granted by the system administrator.
3-75
I N V E N T O R Y
A N D
I N S P E C T I O N
D A T A
M A N A G E M E N T
3-76
his chapter describes how an optimal preservation policy can be developed, which takes into account the costs and effectiveness of different types of preservation actions when applied to structure elements in different stages of deterioration. It covers procedures for model development and estimation, using information from agency experts as well as historical data on costs and facility deterioration. It concludes with a description of the model results and how to interpret them. It is important to note that Pontis 5.1.2 does not contain the modeling capabilities that are included in Pontis 4.5, as the primary direction of 5.1.2 was to The optimal preservation policy developed using the procedures in this chapter is used during the program simulation (covered in Chapter 5) to generate recommended preservation work on structures in the inventory. A mathematically-derived preservation policy can provide useful insights into the least long term cost investment strategy. However, the results of this policy cannot be applied to produce a realistic set of projects without significant modification to reflect practical considerations of work mobilization and scheduling. Therefore, powerful and flexible capabilities to define decision rules for the simulation are provided in Pontis. While the simulation uses the optimal preservation policy as a base, the user-defined rules can ensure that the simulation produces work candidates that reflect agency-specific preservation policies and work scheduling practices. Further information about simulation rules is provided in Chapter 5, and in the Technical Manual.
4-1
D E V E L O P I N G
A N
O P T I M A L
P R E S E R V A T I O N
P O L I C Y
Chapter 4 pertains specifically to Pontis Version 4.5 only and will be updated with future versions of Pontis.
4-2
D E V E L O P I N G
A N
O P T I M A L
P R E S E R V A T I O N
P O L I C Y
4-3
D E V E L O P I N G
A N
O P T I M A L
P R E S E R V A T I O N
P O L I C Y
With a particular action applied during the following year (e.g., do nothing or spot blast, clean and paint) will: Improve to condition state 1 (no corrosion, paint system sound); Improve to condition state 2 (early distress of paint system); Stay in condition state 3; Change to condition state 4 (failure of paint system, surface pitting); or Change to condition state 5 (section loss, structural analysis required).
Transition probabilities are stored in the Pontis database for every combination of element, environment, condition state, and action.
4-4
D E V E L O P I N G
A N
O P T I M A L
P R E S E R V A T I O N
P O L I C Y
2. Historical inspection data on actual changes in element condition distributions over time. A deterioration model update procedure is available to take information from both of these sources and generate a model to represent how the condition of different elements changes over time.
Conducting a Deterioration Elicitation
While Pontis comes with some default deterioration models, it is recommended that these be closely examined and customized to local conditions. This is done initially through the deterioration elicitation process, in which expert judgment is used to predict the behavior of different types of structure elements. Several different experts may complete a deterioration elicitation. The results from each of the experts are combined to make a composite deterioration model. You may choose to have individual experts focus only on portions of the elements (for example, one person handles concrete elements, another handles steel elements). Alternatively, you can have several different experts go through the entire set of elements. In this latter case, results from the different experts are averaged together (using weights as appropriate). In general, it is a good idea to have at least two different experts complete an elicitation for each element. To conduct a deterioration elicitation: 1. Each user who will be conducting an elicitation should have their own set of elicitation records. If records have not yet been added for you, or if any new elements have been added into the element specifications card in the Configuration module since elicitation records were last created, you will need to tell the system to add new elicitation records for you and/or for the new elements. To do this, get into the Configuration module and click on the User Administration card. Click on your user name, and then click on the Add Deterioration Elicitations button. Elicitation records for the selected user will be added. Select File-Close. 2. To add elicitation records for all users, get into the Configuration module and click on the Element Specifications card. Click on the Add Deterioration Elicitations button. The system will ask you if you want to add elicitation records for each user on the User Administration card. Elicitation records for the selected users will be added. Select FileClose. 3. Get into the Preservation module by clicking on the Preservation icon on the Pontis desktop. 4. Click on the Elicit Deter. button. The Expert Transition Probability Model Elicitation screen will appear.
4-5
D E V E L O P I N G
A N
O P T I M A L
P R E S E R V A T I O N
P O L I C Y
5. Get into edit mode by clicking on the Edit Status Block at the bottom of the screen so that it reads EDIT ON. There is one elicitation for each combination of the following: A user (the person doing the elicitation); An element; An environment; A condition state; and An action.
6. Initially, elicitations for the current user (as determined at login) and the element and environment that were selected on the desktop will be shown. To switch to a new user, element or environment, use the selection lists on the top portion of the screen. The elicitation information at the bottom of the screen will change based on your selections. 7. Enter a weight for the elicitation on the top portion of the screen. You must set the weight to a number >= 10. This weight should reflect the importance of your elicitation relative to other experts that will be completing an elicitation for the current element. For example, if three different inspectors with all roughly the same amount of experience will be conducting an elicitation for the same element, each of them should enter the same weight (weights are normalized automatically, and need not add up to 100).
4-6
D E V E L O P I N G
A N
O P T I M A L
P R E S E R V A T I O N
P O L I C Y
Weights are expressed in terms of numbers of bridges. This is because expert elicitation information is combined with historical inspection information to derive the Pontis deterioration models. Thus, setting the weight of your expert elicitation to a low number compared to the number of bridges with at least two annual condition inspections would mean that actual historical data would be weighted much higher than the judgments for expert elicitation. Conversely, setting the weight of your elicitation to a high number compared to the number of bridges for which historical data exists would give your elicitation much more influence in establishing the deterioration models than the historical data. 8. For each condition state, there will be a row for each of the feasible actions that have been defined in the Element Specification card. Action 0 is Do Nothing, and is always present. For each of the condition states and their associated feasible actions, complete the information in the columns to the right. The P.St.1 through P.St.5 columns are Transition Probabilities for condition states 1 through 5. These probabilities are interpreted as follows: If 100 units of this element are in the indicated condition, how many units will be in each condition state next year if the current action (which is do nothing, where action = 0) is taken? The Med Years column represents the answer to the question: If 100 units of this element are currently in the indicated condition state, after how many years will 50 of them have deteriorated to at least the next state, while 50 remain in the current state, if no action is taken? For the Do Nothing action, you may enter the median years for the current condition state, or transition probabilities for remaining in the current state or deteriorating to the next (worse) condition state. If you enter median years a set of transition probabilities consistent with the median years you have entered will be calculated for you. You should be aware, however, that for a given value of median years, there will exist may sets of transition probabilities that would produce that value. (Note: median years may only be specified for the Do Nothing action. Other cells are labeled with a -2 value, which is a missing value code in Pontis, and may not be edited.) For other actions, you must enter transition probabilities for all possible condition states. These probabilities are automatically adjusted to sum to 100.
9. Complete the previous two steps for each of the element/environment combinations.
Updating Deterioration Models
The Pontis deterioration models can be updated based on new inspection data to reflect new information about actual changes in condition states over time. A regression approach is used, with each new data point used to improve the model. Because the preservation optimization models (which specify the optimal condition state distribution for each element) depend on the deterioration models, these models must be updated as well. Finally, because budget scenarios make use of the optimization model results, you may wish to update those that are currently active.
4-7
D E V E L O P I N G
A N
O P T I M A L
P R E S E R V A T I O N
P O L I C Y
To update the models: 1. Get into the Configuration module. 2. Click on the Formulas card. Select a formula set containing formulas that update missing data related to inventory and inspections. Click on Run Formulas. This will update any database fields that have formulas that would be triggered by a change in the inspection data. 3. Get into the Preservation module. 4. Click on the Update button at the left of the screen. Check the Update Probability Model option to update the deterioration (probability) models. If the Use Experts option is selected, the expert elicitations will be used to update the models. If the Use History option is selected, historical inspection information will be used to update the models. Experts, history, or both, are needed to perform an update. If the Keep Existing History option is selected, historic information will be used without being rebuilt. If the Rebuild History Using option is selected, historic data will be rebuilt for the bridge set selected in the dropdown list. The dropdown list contains the following values: selected bridges, bridges listed on the desktop, bridges meeting select criteria, and all bridges in the database. If the Update Only option is selected, the existing model information will be updated; otherwise, the expert elicitation and/or history data will be used to create new model information for each element. If you have conducted a new elicitation and want the models to be based only on the new elicitation, this option should be de-selected. If the Update Just This Elm option is selected, model information for the currently selected element will be updated. This option should be used when new elements are added, or changes to element characteristics are made on the Element Specifications card in the Configuration module. If the Update Cost Model option is selected, the cost models will be updated as well. See the next section for more details. If the Backup Before Update option is selected, the probability and cost models will be backed up before the update is performed. Clicking the Restore button on the Preservation desktop will restore the most recently backed-up models. If the Optimize After Update option is selected, a preservation optimization will be performed following the update.
4-8
D E V E L O P I N G
A N
O P T I M A L
P R E S E R V A T I O N
P O L I C Y
5. Click on the OK button. The deterioration model update procedure will be run. If you have specified that the cost models should be updated or an optimization should be performed, these processes will follow the update. 6. You may wish to update the budget scenarios so that they make use of the new Preservation Optimization results. Note that re-running a scenario will remove all of the existing Pontis work candidates associated with the scenario. If these work candidates are still being reviewed by users of the Project Planning module, you may want to create a new copy of the scenario and re-run that instead. You may also wish to back up your database prior to rerunning scenarios. To update a scenario, get into the Programming module, and select the scenario you wish to update from the selection list at the top of the screen, and click on the Run button. This update procedure is very time-consuming, so you will need to schedule a long-enough block of time to run it.19
19
The time required to run a scenario is dependent on many factors, including the number of bridges, the number of years, the selection of various scenario parameters, the type of computer hardware used, whether the database is local or on a network, etc. As an example, a 20 year scenario run for a 15,000 bridge network can take between 6 and 24 hours to run.
4-9
D E V E L O P I N G
A N
O P T I M A L
P R E S E R V A T I O N
P O L I C Y
While Pontis comes with some default cost models, most users will want to customize them to local conditions. This is done initially through the cost elicitation process, in which existing
20
Cost updating based on action costs is not supported in version 4.0 of Pontis. This feature will be restored in a future version.
4-10
D E V E L O P I N G
A N
O P T I M A L
P R E S E R V A T I O N
P O L I C Y
historical information together with expert judgment is used to develop a reasonable set of unit cost estimates. Several different experts may complete a cost elicitation. The results from each of the experts are combined to make a composite cost model. You may choose to have individual experts focus only on portions of the elements or certain types of actions. Alternatively, you can have several different experts go through the entire set of elements and actions. In this latter case, results from the different experts are averaged together (using weights as appropriate). In general, it is a good idea to have at least two different experts complete an elicitation for each element and action. To conduct a cost elicitation: 1. If you have not yet entered any cost elicitation information, or if you have entered any new elements into the element specifications card in the Configuration module, (you will need to tell the system to add new elicitation records for you and/or for the new elements. To do this, get into the Configuration module and click on the User Administration card. Click on your user name, and the click on the Add Cost Elicitations button. Elicitation records for the selected user will be added. Select File-Close. 2. To add elicitation records for all users, get into the Configuration module and click on the Element Specifications card. Click on the Add Cost Elicitations button. The system will ask you if you want to add elicitation records for each user on the User Administration card. Elicitation records for the selected users will be added. Select File-Close. 3. Get into the Preservation module. 4. Click on the Elicit Cost button. The Expert Transition Probability Cost Elicitation screen will appear. Elicitation records are stored for all of the combinations of elements, environments, condition states and actions. If other experts have already entered cost elicitation information for an element, there may be several entries for a given elementenvironment-condition state-action combination one for each expert. 5. Initially, elicitation records for the current user (as determined at login) and the element and environment that were selected on the desktop will be shown on the screen. To switch to a new user, element or environment, use the selection lists on the top portion of the screen. The elicitation information at the bottom of the screen will change based on your selections. For each possible condition state, there will be a row for each of the feasible actions defined on the Element Specifications card in the Configuration module. Action 0 is Do Nothing, and is always present. For each of the condition states and their associated feasible actions, fill in the unit cost. (The cost for the Do Nothing action is typically 0.)
4-11
D E V E L O P I N G
A N
O P T I M A L
P R E S E R V A T I O N
P O L I C Y
6. At the top of the screen, enter a weight for the elicitation. You must set the weight to a number >= 10. This weight should reflect the importance of your elicitation relative to other experts that will be completing an elicitation for the current element. For example, if three different inspectors with all roughly the same amount of experience will be conducting an elicitation for the same element, each of them should enter the same weight (weights are normalized automatically, and need not add up to 100). Note that weights are expressed in terms of numbers of bridges, as described above in Section 4.3. Weights on the individual cost elicitations determine the relative importance of the different expert judgments in developing unit costs that are used in the optimization and project cost estimation procedures. 7. At the top of the screen, enter the theoretical agency and user costs of element failure21. The failure cost represents the "penalty" the public will incur should the element fail (including the cost of restoring the structure to serviceable condition, the costs of possible damages caused by the failure, the costs of user delays, etc.). Failure cost is used in the optimization model to determine whether it is less expensive to take an action on the element or to let the element fail. If the failure cost is set too low, there will be no economic reason to prevent the element from failing. Thus, for every element in every environment the minimum value of the failure cost is determined by the value that forces an action in an earlier condition state. Failure costs
21
An alternative method of failure cost calculation can be used by selecting the Calculate Failure Costs button on the Element Specifications card of the Configuration module. This method calculates failure costs as the product of an element weighting factor (reflecting its relative importance) and the cost of the most expensive action that can be taken for the element (typically replacement). Note that if this alternative method is used, the resultant costs may not be sufficiently high to ensure that the models produce reasonable results.
4-12
D E V E L O P I N G
A N
O P T I M A L
P R E S E R V A T I O N
P O L I C Y
may also be used by Pontis to calculate an overall Health Index for a structure22. Though the concept of the failure cost may be easy to understand, an objective procedure to calculate a failure cost above the absolute minimum is not currently available. Periodically an agency must review its element actions to insure that the failure costs are appropriately set. If optimal actions are not generated for an element then most likely the failure cost is set too low. As a rule of thumb, failure costs would typically be 3-10 times the repair costs for elements in the worst condition state. 8. At the top of the screen select metric or English units for data entry. 9. At the top of the screen, enter the average value of the scale field associated with the current element. This value is used to adjust project-level cost estimates based on actual values of the scale field for particular structure elements. The name of the scale field can be found on the Element Specifications card in the Configuration module. 10. Complete Steps 6-9 for each of the element/environment combinations. Note that you can use the Copy... button on the elicitation screen to copy the unit costs for the current user and element to all other environments for that user and element.
Note: If you do not want an elicitation to be used to adjust the master preservation model, simply set its weight to 0.
When new cost elicitations are added, or existing elicitations are modified, the Pontis cost models should be updated to reflect the changes that have been made23. To update cost models: 1. Get into the Preservation module. 2. Click on the Update button at the left of the screen. If the Update Probability Model option is selected, the probability models will be updated. See the preceding section for details. Check the Update Cost Model option to update the cost models.
22
The Health Index is a single number (from 0-100) which reflects the condition distribution for the different elements on a structure. The Advanced Scenario parameter EW can be set in the Programming module so that Failure costs are used in the Health Index formula to assign weights to the different elements (instead of the element weighting factors in the Configuration module). See the Technical Manual for a description of the Health Index calculation. Cost updating based on action costs is not supported in version 4.0 of Pontis. This feature will be restored in a future version.
23
4-13
D E V E L O P I N G
A N
O P T I M A L
P R E S E R V A T I O N
P O L I C Y
If the Backup Before Update option is selected, the probability and cost models will be backed up before the update is performed. Clicking the Restore button on the Preservation desktop will restore the most recently backed-up models. If the Optimize After Update option is selected, a preservation optimization will be performed following the update.
3. You may wish to update the budget scenarios so that they make use of the new Preservation Optimization results, Note that re-running a scenario will remove all of the existing Pontis work candidates associated with the scenario. If these work candidates are still being reviewed by users of the Project Planning module, you may want to create a new copy of the scenario and re-run that instead. You may also wish to back up your database prior to rerunning scenarios. To update a scenario, get into the Programming module, and select the scenario you wish to update from the selection list at the top of the screen, and click on the Run button.
Adjusting Cost Models
The unit costs within Preservation Models can be adjusted for inflation. In addition, any arbitrary cost factor may be applied in order to conduct a sensitivity analysis. To make adjustments to the costs used in the MR&R Optimization model: 1. Click on the Cost radio button on the Preservation desktop, and then click on the Adjust Costs button. The MR&R Model Information screen will appear. 2. To inflate all costs in the model to a current index (which you must have already entered within the Configuration module), press the Inflate button. This will multiply all unit costs by the ratio of the current cost index divided by the cost index last used. The MR&R Optimization model will also be updated to reflect the adjusted costs. 3. To conduct an analysis of the models sensitivity to user and agency cost assumptions, click on the Adjust Costs button at the bottom of the screen. The Adjust MR&R Model Costs screen will appear. 4. To apply a multiplier to all costs calculated by the model, enter a percentage next to Adjust Agency Costs by. For example, to increase all agency costs by 20 percent, enter 120. To decrease all agency costs by 20 percent, enter 80. 5. To apply a multiplier to all user costs calculated by the model, enter a percentage next to Adjust User Costs by:. 6. Click OK to have the system update the costs and rerun the MR&R Optimization model to reflect the adjusted costs. 7. You may enter a comment about the model in the space provided for Notes. 8. Click OK to close the MR&R Model Information screen.
4-14
D E V E L O P I N G
A N
O P T I M A L
P R E S E R V A T I O N
P O L I C Y
4-15
D E V E L O P I N G
A N
O P T I M A L
P R E S E R V A T I O N
P O L I C Y
To run the Health Index Target Analysis: 1. Click on the HI Target button on the Preservation desktop. The Optimal Health Index Target Analysis screen will appear. 2. Enter a name for the analysis run. Enter any notes if desired. 3. Select the structures to be included in the analysis run bridges selected on Inspection Desktop, all bridges listed on Inspection Desktop, all bridges in the database, bridges listed in the structure list, or selected bridges 4. Specify the health index constraint type. Selecting Minimum causes the optimization to use a specified health index as a minimum value. Selecting Equality forces the optimization to find a solution with the health index values equal to the constraint, even if it would be more cost effective to have a greater value. 5. Check the Launch Viewer After Optimization checkbox. The Long-Term Performance Targeting screen will be automatically opened after the optimization is complete. 6. Click the Optimize button
4-16
D E V E L O P I N G
A N
O P T I M A L
P R E S E R V A T I O N
P O L I C Y
To view the performance targeting results: The Long-Term Performance Targeting screen displays the predicted long-term annual cost by element category of achieving the specified performance targets. The results can be viewed in either Graphs or Targets mode. The Graphs view shows a line graph of how annual long-term cost and achieved health index change as the health index target changes for the specified element category. You can modify the graph by specifying whether the target applies to each element (condition unit) in the category, or to the category as a whole, and by selecting different categories of elements. The Targets view is an interactive view which allows you to see how changes in the health index target affect the annual long-term cost and the actually achieved health index of various element categories. You can specify whether the target applies to each element (condition unit) in the category, or to the category as a whole. The graphical sliders and the spin control support dynamic adjustment of targets. The spin control can be used to either increment or decrement the health index target by decimal points. As you move the slider or click on the spin control, the annual long-term cost and the actually achieved health index values will change. You may use the slider to roughly set up the target value, then use the spin control to set a more precise number.
4-17
D E V E L O P I N G
A N
O P T I M A L
P R E S E R V A T I O N
P O L I C Y
Preservation Desktop
The screen contains the following information: All possible condition states and associated feasible actions, with the recommended action for each condition state. (as shown by >>) The transition probabilities for the element, representing the percent of element quantity predicted to change from the state on the left to each of the other possible states if a particular action is taken. The cost units the type of units on which the unit costs are based. The direct unit costs of taking each action. The long-term costs of each action, which are the discounted sum of the action cost and all future costs that will be incurred after taking the action. The recommended action will have the lowest long-term cost.
4-18
D E V E L O P I N G
A N
O P T I M A L
P R E S E R V A T I O N
P O L I C Y
Agency and user costs of element failure these represent the costs to restore the element to serviceable condition after failure, potentially including the cost of restoring any other elements that may be affected by the failure, the penalty the public will incur should the element fail, the costs of motorist delays caused by the need to close the bridge or restrict its use during repairs, and other such costs. The probability of failure from the worst condition state defined for the element. The optimal percent of the element in each of the condition states that would achieve the least long-term preservation cost. Typically, this distribution would be achieved if the model recommendations were consistently followed over a number of years.
4-19
D E V E L O P I N G
A N
O P T I M A L
P R E S E R V A T I O N
P O L I C Y
24
There may be some cases where the simulation recommends structure replacement based on specified thresholds. The cost of these replacements is not included in this report. The costs shown exclude needs that were suppressed by the simulation based on user-specified thresholds (e.g. for minimum project cost). The report includes needs that were generated based on user-specified rules for up-scoping projects (e.g. if you replace the deck, replace the joints).
4-20
We have a good understanding of the current bridge network condition, and have run the preservation optimization model. Now we would like to understand what level of investment would be necessary to move towards the least long term cost preservation strategy recommended by the model. We also want to analyze our improvement needs given a set of minimum standards for width, clearances, and load ratings, and see the total preservation and improvement needs. In addition to understanding the needs, we would like to predict the costs and performance impacts of specific projects we have defined, and generate candidate work based on our preservation model, policies and standards, and rules for applying these at the bridge level.
his chapter covers the Pontis simulation model. It describes how to specify each of the required inputs for the model, including parameters used to determine structure improvement needs. It covers the procedure for running a program simulation, and describes how to use the Pontis Results module and the programming reports to review the results of the simulation. Chapter 5 pertains specifically to Pontis Version 4.5 only and will be updated with future versions of Pontis.
5-1
B R I D G E
P R O G R A M
S I M U L A T I O N
Developing a Program
Several different program scenarios with different budgets, improvement standards, and improvement costs can be defined and run. After you have defined and run different scenarios, and reviewed their results, a working program scenario can be established as the starting point for the project development process. Steps in developing a program are as follows: 1. Develop one or more sets of functional improvement policy standards and costs (see Sections 5.2 and 5.3); 2. Develop one or more sets of improvement modeling assumptions (Section 5.4);
AASHTO Pontis Users Manual 5-2
B R I D G E
P R O G R A M
S I M U L A T I O N
3. Develop one or more sets of rules for how you would like the simulation to select and package work. (Section 5.5); 4. Develop one or more budgets (Section 5.6); and 5. Define and run one or more program scenarios (Section 5.7). Section 5.8 covers the review of scenario results. Default values have been established and reviewed by the Pontis Task Force for functional improvement policy standards and costs, improvement modeling assumptions, simulation rules, and other simulation parameters. These default values provide a reasonable starting point for defining and running program scenario, but you should carefully review these and substitute the default values with values appropriate for your agency.
5-3
B R I D G E
P R O G R A M
S I M U L A T I O N
5-4
B R I D G E
P R O G R A M
S I M U L A T I O N
3. To define a new Policy Matrix containing a new set of standards without over-writing the current ones, click on the Model Info button. The Existing Policy Sets screen will appear. Click on the New Copy button at the bottom of the screen. Enter a name for your new Policy Matrix, and record some descriptive information about the set of standards you will be entering. Click on the Save button, and then click on the Close button. 4. To modify a previously defined set of standards, click on the Model Info button, and then click on the policy set you wish to edit. Then click on the Close button. 5. Get into edit mode by clicking on the Edit Status Block at the bottom of the screen so that it reads EDIT ON. 6. At the top of the screen click the Metric or English radio button to specify whether you will enter policy data in metric or English units. 7. You may now enter a set of standards for any combination of ADT class, functional class, funding responsibility, and NHS status. It is a good idea to make some notes in advance consisting of a table of standards for each of the different combinations you wish to enter. When you are ready to enter the information, simply type in new values for the different standards. The first row contains default standards that will be applied to any structure that has missing data for ADT, functional class, funding responsibility or NHS status. 8. You can also use the Copy... button to copy the standards for the current row to all other rows on the current tab card. This provides a shortcut for data entry you need only go and edit the values that will be different. a. Click OK to save your standards.
Tip: To restrict the matrix entries based on ADT class, functional class or other items, right click on the matrix, and select Filter from the popup menu. Right-click on one or more Filter Value cells and select which values you wish to include. Then click on the Apply Filter button.
The entries in the Policy Matrix are divided into two categories: Legal and Design.
LEGAL
This category includes level-of-service standards and load ratings. Level-of-service standards are used to determine whether improvements are needed. Minimum level-of-service standards for lane width, shoulder width, load capacity and vertical clearance may be specified. Three different policy load ratings are included the operating rating, the inventory rating, and another type of rating which may be in use by your agency. Note that only the operating rating is used by the Pontis simulation to determine improvement needs. The inventory and other ratings are included for agencies wishing to enter them here for reference purposes.
5-5
B R I D G E
P R O G R A M
S I M U L A T I O N
DESIGN
Design standards are used to determine the extent of improvement needed when the structure characteristics do not meet the level-of-service standards. Design standards may be specified for lane width, shoulder width, vertical clearance, and replacement swell factor. The replacement swell factor is the average increase in deck area to be assumed for a replacement bridge.
5-6
B R I D G E
P R O G R A M
S I M U L A T I O N
3. To define a new Cost Matrix containing a new set of costs and benefit assumptions without over-writing the current ones, click on the Model Info button. The Existing Cost Sets screen will appear. Click on the New Copy button at the bottom of the screen. Enter a name for your new Cost Matrix, and record some descriptive information about the set of costs and benefit assumptions you will be entering. Click on the Save button, and then click on the Close button.
5-7
B R I D G E
P R O G R A M
S I M U L A T I O N
4. To modify a previously defined set of costs and benefit assumptions, click on the Model Info button, and then click on the cost set you wish to edit. Then click on the Close button. 5. Get into edit mode by clicking on the Edit Status Block at the bottom of the screen so that it reads EDIT ON. 6. At the top of the screen click the Metric or English radio button to specify whether you will enter policy data in metric or English units. 7. You may now enter a set of costs and benefit assumptions for any combination of district, functional class, funding responsibility, and NHS status. It is a good idea to make some notes in advance consisting of a table of assumptions for each of the different combinations you wish to enter. When you are ready to enter the information, simply type in new values for the different assumptions. The first row contains default standards that will be applied to any structure that has missing data for ADT, functional class, funding responsibility or NHS status. 8. You can also use the Copy... button to copy the costs for the current row to all other rows on the current tab card. This provides a shortcut for data entry--you need only go and edit the values that will be different. 9. Click OK to save your costs and benefit assumptions.
Cost Matrix Data Items
Cost matrix items include agency functional improvement unit costs, and factors used to calculate user detour and accident costs which may be reduced by making functional improvements to structures.
UNIT COSTS
Replace Cost per square meter of structure replacement. Widening (variable) Direct (or variable) cost per square meter of structure widening. This is the portion of the cost that varies based on the number of new square meters added. Raise Cost per square meter of raising the structure. Strengthen Cost per square meter of structure strengthening.
USER COSTS
Detour per Hour User cost per hour of additional travel time incurred by vehicles that would normally use a structure but cannot due to clearance or load restrictions. This is used to calculate user cost reductions associated with raising or strengthening a structure. Detour per Km User cost per kilometer of additional travel distance incurred by vehicles that would normally use a structure but cannot due to clearance or load restrictions. This is used to calculate user cost reductions associated with raising or strengthening a structure. Avg. per Accident The user cost per accident. This is used to calculate the accident reduction benefits of widening or replacing a deficient structure.
AASHTO Pontis Users Manual 5-8
B R I D G E
P R O G R A M
S I M U L A T I O N
Weight The user cost weight determines the weight of user costs relative to actual dollar costs in the benefit-cost calculations. If the user cost weight is 100, user costs are treated on par with agency costs. If the user cost weight is 50, user costs would be cut in half. This data item has been provided because user cost estimates do not often have the same level of confidence as agency cost estimates. Therefore, the ability to conduct sensitivity analysis using the weighting factor may be helpful. You may set the user cost weight to 0. However, be aware that this will result in your improvement projects showing up as having no benefit.
5-9
B R I D G E
P R O G R A M
S I M U L A T I O N
See the Technical Manual for information on improvement benefit modeling and the precise use of the customizable parameters. Multiple sets of alternative improvement modeling assumptions can be established and assigned different names (each one is called a Improvement Set). This allows you to conduct what-if analyses. Each set of assumptions that you establish should be associated with a particular analysis scenario.
5-10
B R I D G E
P R O G R A M
S I M U L A T I O N
3. To define a new Improvement Set containing a new set of assumptions without over-writing the current ones, click on the Model Info button. The Existing Improvement Sets screen will appear. Click on the New Copy button at the bottom of the screen. Enter a name for your new Improvement Set, and record some descriptive information about the set of assumptions you will be entering. Click on the Save button, and then click on the Close button. 4. To modify a previously defined set of assumptions, click on the Model Info button, and then click on the improvement set you wish to edit. Then click on the Close button. 5. Get into edit mode by clicking on the Edit Status Block at the bottom of the screen so that it reads EDIT ON. 6. You may now enter a set of assumptions. Click OK to save your standards.
5-11
B R I D G E
P R O G R A M
S I M U L A T I O N
Note that using these rules is entirely optional effectively you can run a simulation with no rules specified to see the pure preservation and improvement model results. You may wish to do
5-12
B R I D G E
P R O G R A M
S I M U L A T I O N
this to gauge the impact of the rules on network-level results, to better understand the results generated by different rules, or to compare the results with those generated in previous versions of Pontis that did not have these rules. You can define multiple Rule Sets for each type of rule (except Paint Rules, which are defined at the scenario level and described in Section 5.7). When you run a scenario, you select the Rule Set you want to use for that particular scenario run.
Application of Rules
The rules are applied as part of the program simulation. Before you can see the effect of the rules you must define your elements, actions and flex actions in the Configuration module, as described above. Also, you must develop a preservation model in the Preservation module. The preservation model establishes the costs of the element-level actions, deterioration rates, and the network-level policy that should be followed (which may be tuned at the bridge-level based on the simulation rules). Once you have defined elements, actions and flex actions, and have developed a preservation model, you can proceed with developing simulation rules. In developing the simulation rules you
AASHTO Pontis Users Manual 5-13
B R I D G E
P R O G R A M
S I M U L A T I O N
should carefully consider what rules you wish to define, as well as how each individual rule will interact with each other rule of the same type, and rules of other types. Each rule in a set of Scoping, Major Rehab, or Agency Policy rules has a Priority number, which determines the order in which it is considered by the simulation. If more than one rule applies to a particular object, then the lower numbered rule will take precedence. However, if the first rule is defined for a specific element number and the second is defined for an element category including that element number, the first rule will be applied for the selected element number, and the second rule will be applied to all other elements in the selected element category. Rules can have cumulative effects. For example, if rule #1 says If you overlay the deck replace the joints, and rule #2 says If you replace the joints, then replace the deck, the simulation would schedule a deck replacement whenever a deck overlay was recommended by the preservation model. Different types of rules can also interact with each other, and therefore the order in which they are applied is important to note: a. Painting rules specified on the Programming desktop; b. Agency Policy rules; c. Scoping rules; d. Major rehab rules; and e. Look Ahead rules. Rules that are applied later can change the results of rules that are applied earlier.
5-14
B R I D G E
P R O G R A M
S I M U L A T I O N
5. The top portion of the screen contains a list of rules in the current Scoping Set. If the list is large, you can use the arrow keys at the top of the screen to scroll up and down the list. If you select a rule from the list, the lower, Build a Rule portion of the screen shows the selections that make up that rule. You can edit an existing rule by selecting it from the list, and then choosing different options from the selection lists below. The English version of the rule will automatically change based on your selections. Scoping rules are of the form: IF action A is done to object B, then do action C to object D. Select the action A and the object B under the section titled If this action is done to this object. Select the action C and the object D under the section titled then (also) do this action to this object. To select an object, first pick whether you want the object to be the entire bridge, an element category, an element type, or a specific element number. If the object is an element number, element type or category, select the number, type or category from the list below. To select an action, first pick whether you want to use an action category, action type, or flex action. Depending on which of these you select, the picklist below will present you with a list of appropriate selections. Select the specific action category, type or flex action. 6. To add a new rule, click on the Add Rule button. A copy of the currently selected rule will be created. You can then modify it. 7. To delete a rule, select it and click on the Delete Rule button.
5-15
B R I D G E
P R O G R A M
S I M U L A T I O N
8. To change the order in which the rules are applied in the simulation, edit the Priority column enter any numbers; they need not be sequential. You can then click on the Renumber button to put the rules in priority order and assign sequential numbers.
5. The top portion of the screen contains a list of rules in the current Look Ahead Set. If the list is large, you can use the arrow keys at the top of the screen to scroll up and down the list. If you select a rule from the list, the lower, Build a Rule portion of the screen shows the selections that make up that rule. You can edit an existing rule by selecting it from the list, and then choosing different options from the selection lists below. The English version of the rule will automatically change based on your selections.
5-16
B R I D G E
P R O G R A M
S I M U L A T I O N
Look Ahead rules are of the form: IF action A is done to object B within n years, then do NOT do action C to object D. Select the action A and the object B under the section titled If this action is done to this object within <n> years. Select the action C and the object D under the section titled then do NOT do this action to this object. Select the number of years n to the right of this section. To select an object, first pick whether you want the object to be the entire bridge, an element category, an element type, or a specific element number. If the object is an element number, element type or category, select the number, type or category from the list below. To select an action, first pick whether you want to use an action category, action type, or flex action. Depending on which of these you select, the picklist below will present you with a list of appropriate selections. Select the specific action category, type or flex action. 6. To add a new rule, click on the Add Rule button. A copy of the currently selected rule will be created. You can then modify it. 7. To delete a rule, select it and click on the Delete Rule button.
5-17
B R I D G E
P R O G R A M
S I M U L A T I O N
5. The top portion of the screen contains a list of rules in the current Major Rehab Set. If the list is large, you can use the arrow keys at the top of the screen to scroll up and down the list. If you select a rule from the list, the lower, Build a Rule portion of the screen shows the selections that make up that rule. You can edit an existing rule by selecting it from the list, and then choosing different options from the selection lists below. The English version of the rule will automatically change based on your selections. Major Rehab rules are of the form: IF threshold type X (> or ) value, then for object A action B. The threshold type can be: The health index for the entire bridge, or for an element category; The cost in dollars of recommended work; The cost of recommended work as a percentage of the structure replacement cost; or The cost of recommended work for a given element category as a percentage of the replacement cost for all elements of that category.
Select the indicator under If this threshold type, and then enter a value. Under then for this object type do this action, select the object A and the action B. To select an object, first pick whether you want the object to be the entire bridge or an element category. If the object is an element category, select the category from the list below.
5-18
B R I D G E
P R O G R A M
S I M U L A T I O N
To select an action, first pick whether you want to use an action type or flex action. Depending on which of these you select, the picklist below will present you with a list of appropriate selections. Select the specific action type or flex action. 6. To add a new rule, click on the Add Rule button. A copy of the currently selected rule will be created. You can then modify it. 7. To delete a rule, select it and click on the Delete Rule button. To change the order in which the rules are applied in the simulation, edit the Priority column enter any numbers; they need not be sequential. You can then click on the Renumber button to put the rules in priority order and assign sequential numbers.
3. To define a new Agency Policy Set, click on the Edit button next to the Agency Policy Set selection list. When the Existing Agency Policy Sets screen appears, select the existing set that you would like to use as a base for your new set of rules, and click on the New Copy button. Enter a name for the Agency Policy set (and detailed comments if you wish). Click Save to save your new set, and then Close. 4. To modify an existing Agency Policy Set, select the one you wish to edit from the Agency Policy Set selection list at the top of the screen.
5-19
B R I D G E
P R O G R A M
S I M U L A T I O N
5. The top portion of the screen contains a list of rules in the current Agency Policy set. If the list is large, you can use the arrow keys at the top of the screen to scroll up and down the list. If you select a rule from the list, the lower Build a Rule portion of the screen shows the selections that make up that rule. You can edit an existing rule by selecting it from the list, and then choosing different options from the selection lists below. The English version of the rule will automatically change based on your selections. Agency Policy rules are of the form: IF object A has > x % of its quantity in condition state n or worse, then for object B, take action C1 for the portion in condition state 1, C2 for the portion in condition state 2, C3 for the portion in condition state 3, C4 for the portion in condition state 4, and C5 for the portion in condition state 5. Select the object A under the section titled If this is object, and enter the quantity x and the condition state n. Under the section titled: Then for this is object select object B. Finally, under the section titled Take these actions enter actions C1 - C5 (one action for each condition state). To select an object, first pick whether you want the object to be an element category, an element type, or a specific element number. Then select the number, type, or category from the list below. To select an action, first pick whether you want to use an action category, action type, or flex action. Depending on which of these you select, the picklist to the right will present you with a list of appropriate selections. Select the specific action category, type or flex action.
5-20
B R I D G E
P R O G R A M
S I M U L A T I O N
6. To add a new rule, click on the Add Rule button. A copy of the currently selected rule will be created. You can then modify it. 7. To delete a rule, select it and click on the Delete Rule button. 8. To change the order in which the rules are applied in the simulation, edit the Priority column enter any numbers; they need not be sequential. You can then click on the Renumber button to put the rules in priority order and assign sequential numbers.
5-21
B R I D G E
P R O G R A M
S I M U L A T I O N
3. To modify an existing budget set, click on the row for that set. Use the arrow buttons below the grid to navigate up and down the list. 4. To define a new Budget Set containing a new set of budget constraints without over-writing the current ones, click on the New Copy button. 5. A new row will be added to the grid. Enter a name for your new Budget Set, and (optionally) some descriptive information. Click on the Save button, and then click on the Close button. 6. Enter a set of budget limits in the detail panel below the grid. For each year of your program, enter the amount of funding (from all sources) available.
5-22
B R I D G E
P R O G R A M
S I M U L A T I O N
7. If you want to change the number of years in the budget set, or set all of the budgets to a specified amount, click on the Initialize button. The Initialize Budget Set screen will appear. Enter the starting year for your budget set, the number of years, and the annual budget. If you want to replace the existing rows in your budget set, click on the Clear existing records for this budget set option. If this option is not selected, then only the rows for years that do not already exist in the budget set will be added. Click OK to apply your selections. 8. Select the Save button to save your Budget Set. 9. Select File-Close to exit the Annual Funding Levels screen.
5-23
B R I D G E
P R O G R A M
S I M U L A T I O N
Tip: The total number of scenarios may be restricted by the value of the MAXNUMSCENARIOS option variable on the Options card within the Configuration module
Each scenario has the following associated with it: An ID and name; A timeframe for the scenario (start year, number of years, first year to begin recommending projects); A Policy Set (containing improvement level-of-service and design standards); An Improvement Set (containing parameters for the model which estimates benefits of improvements); A Cost Set (containing unit costs of different types of improvements, and user cost factors which are used to estimate improvement benefits); A Budget Set name (containing annual budget limits for the scenario period); Simulation Rule Sets (for scoping, look-ahead, major rehab, and agency policy rules); A set of painting rules based on condition thresholds for when painting is to be done; A set of thresholds governing minimum project and action cost, the minimum number of years between projects on a structure; Rules for when structure replacements should be recommended; Selection of structure elements to be included in the simulation; and A variety of other technical parameters governing the simulation behavior.
5-24
B R I D G E
P R O G R A M
S I M U L A T I O N
Programming Desktop
5-25
B R I D G E
P R O G R A M
S I M U L A T I O N
Rules, select your rule set. Otherwise, select the Default Agency Policy (this set will have no effect on the simulation). 5. Set Thresholds for the simulation, as follows: Minimum Project Cost ($) The minimum cost of a project structures with needs in a given year totaling less than this minimum will not be included in the program for that year Minimum Action Cost ($) The minimum cost for an action to be included in a recommended project. Paint Rule There are four options here: No painting rule for the scenario in this case, select Do Not Use Thresholds from the dropdown. A painting rule of the form: paint all of the paintable elements when the condition index (for paintable elements) is <=X %. For this option, select Use Threshold 1 Only, and enter a number for the first threshold (to replace X in the formula above). A painting rule of the form: paint all of the paintable elements that are in condition state 2 or worse when the condition index (for paintable elements) is <=X %. For this option, select Use Threshold 2 Only, and enter a number for the second threshold (to replace X in the formula above). A painting rule combining the two thresholds: paint all of the paintable elements when the condition index (for paintable elements) is <=X% AND paint all of the paintable elements in condition states 2 or worse when the condition index (for paintable elements) is < Y%. For this option, select Use Both Thresholds, and enter numbers for both thresholds (to replace X and Y in the above formulas). Note that it is possible to modify the paint rule logic by changing the value of the advanced parameter HC from the default of 0 to 1 by clicking on the Set Advanced Parameters button. This affects the cost and impact of applying the paint rule. See Step 11 for instructions on modifying advanced parameters, and the Technical Manual for details on paint rule logic. Deferment (Yrs) The minimum number of years between projects on a bridge.
6. Enter the criterion for when replacement should be considered by the simulation. If the cost of needed actions on a structure exceeds the given criterion percentage of the cost of replacing the structure, then the system will consider replacement as an alternative. You can also select the option to prohibit all replacements. 7. Select which types of projects to include: Optimal and User Projects - include both optimal projects and user-defined projects. Optimal Projects Only - include only optimal projects, and ignore any sub-optimal projects, including those that were user-generated.
5-26
B R I D G E
P R O G R A M
S I M U L A T I O N
8. Select which types of needs to include: MRR Needs Only - include only preservation projects. Functional Needs Only - include only functional improvement projects. MRR and Functional Needs - include both preservation (MR&R) and functional improvement projects in the program.
9. Select a Needs Growth option for how changes in preservation and improvement needs over time should be modeled: Grow All Needs select if you want the simulation to project new preservation and functional needs, based on element deterioration and traffic growth. Use All Current Needs select if you do not want the simulation to project any new preservation or functional needs. Current MRR Needs Only select if you do not want the simulation to project new preservation needs, but you do want it to project new functional needs. Current Functional Needs select if you do not want the simulation to simulate new functional needs, but you do want it to project new preservation needs.
10. If you would like to restrict your scenario to include only selected structure elements, click on the Set Scenario Elements button, and de-select the elements you do not wish to include. The default is to include all elements. To select or de-select all elements for the scenario, make sure the Element Category is set to All, and click on the Select All or Select None button. To select or de-select all elements in a particular element category, select the category and then click on the Select All or Select None button. Your selections will apply to the current scenario only. Click OK to apply your selections to the currently selected scenario. 11. Additional scenario parameters can be set by clicking on the Set Advanced Parameters button. See the Technical Manual for information on how these parameters affect the simulation. Of the advanced parameters, the three that may have the greatest impact on the results of a scenario include: EW (health index weighting method) determines how total element value is calculated, used for weighting elements in calculation of the health index. The default value for this parameter is RELWEIGHT, indicating that the total element value for a particular element per unit of the element is calculated as the cost of the most expensive action for the element (typically replacement) multiplied by the elements weight, as specified in the Configuration module (see Section 7). In calculating the health index for a structure, each elements contribution to the health index is weighted by total element value. MB (MR&R benefit calculation method) determines how preservation benefits are calculated. The default value is HIXTEV. When the default is specified, the benefits of performing preservation work on a structure are calculated as the
5-27
B R I D G E
P R O G R A M
S I M U L A T I O N
improvement in health index resulting from the work, multiplied by the Total Element Value for the elements on the structure. PP (allow Pontis projects) determines whether Pontis is allowed to recommend additional work, besides work already specified in the Project Planning module. This parameter should be set to YES for every scenario except the Programmed Work scenario. For the Programmed Work scenario, this parameter should be set to NO because this scenario is used to summarize the impact of programmed work without recommending additional work.
12. If you are running a scenario involving a relatively small set of bridges, and would like to store projected annual performance indicators for each bridge, select the Store bridge-level results option. Note that this option slows down the simulation and consumes considerable disk space. 13. If you like, you can enter notes describing the scenario for the benefit of other users, or for your future reference. 14. Click Save to save your changes and close the screen.
Running a Scenario
Note that running a scenario is a time consuming process. The time is dependent on the number of years specified for simulation duration, the number of structures, your database configuration, and your computer hardware configuration. As an example, running a 20-year scenario for a database with 15,000 bridges may be expected to take between 6 and 24 hours. To run a scenario: 1. If you would like your scenario to include a subset of structures, go to the Inspection module and select the structures to be included from the Structure List (either by clicking on individual structures or by using the Select button.) 2. Get into the Programming module, and select the scenario you wish to run from the selection list at the top of the screen. 3. Click on the Run button. 4. The Select Bridges screen will appear. To run the scenario for all bridges in the database, select the All Bridges in DataBase option. If you have selected a subset of structures on the Structure List, select the Bridges Selected on Inspection Desktop option. Click OK. 5. You will get a message which tells you which scenario you are about to run, with the number of structures to be included. Click OK to proceed. 6. A window will appear while the simulation is running, providing status and progress indicators. When the simulation is finished, you will get a message about whether the simulation succeeded or not. Click OK to close this message.
7.
You will get a final message saying that you are about to update project work item costs and benefits. Confirm that you would like to do this by clicking OK.
5-28
B R I D G E
P R O G R A M
S I M U L A T I O N
Log Files
Pontis generates several log files which provide diagnostic information about the modeling process. These files are placed in the UserFiles directory (typically Pontis44\USR). The most useful file is named PR + <scenario key> + SIM.LOG. For example, for scenario key XB, this file would be named PRXBSIM.LOG. This file contains a record of the input parameters, and the major steps and calculations of the simulation.
Scenario Specification Report
Report prog012_scenario_report provides a useful record of the various parameters that were used for a particular scenario. This report can be viewed and printed following the procedure in section 2.4.
Deleting a Scenario
Note that deleting a scenario will remove all Pontis scenario work recommendations associated with that scenario from the database. This is a privileged operation, and access must be granted via the Configuration module. 1. Select the scenario you wish to delete from the selection list at the top of the screen. 2. Click on the Delete button. 3. You will be asked to confirm that you want to delete the scenario. Click OK to proceed.
5-29
B R I D G E
P R O G R A M
S I M U L A T I O N
5-30
B R I D G E
P R O G R A M
S I M U L A T I O N
There is a specially designated scenario called the Programmed Work scenario. This scenario is used to simulate results of the programs that have been developed in the Project Planning module in order to allow for estimates of performance measures over time associated with implementation of the projects in the programs. In a Programmed Work simulation, needs are estimated but no new projects are generated; only those projects that have been created in the Project Programming module are assumed. Only projects with a status of 1-Initiated, 2Programmed, and 4-In Progress are scheduled (projects with a status of 0-Proposed, 3-Deferred or 5-Completed are not included). To run a Programmed Work simulation, click on the Summarize button on the Results desktop.
Viewing Scenario Results
To see the results of a scenario that you have run in the Programming module: 1. Get into the Results module. 2. Select Scenario from the radio buttons at the top of the screen. 3. Select a scenario for the report from the selection list. You can click on the Show Only Scenarios With Work checkbox to restrict the list to scenarios with at least one programmed work item. If you have just run a scenario, and do not see it on the selection list, click on the Refresh button. 4. (Optional) Enter a note about your report.
5-31
B R I D G E
P R O G R A M
S I M U L A T I O N
5. Select the type of report you would like. Options are: Work and Needs report shows the cost and benefit of preservation and improvement needs and programmed work over a selected time period. Preservation Work and Needs report shows the cost and benefit of preservation needs and programmed work over a selected time period. Performance Measures report shows the value of a selected performance measure for a selected time period. Summary report a tabular report showing the scenario budget, needs, work, and benefits of doing the scheduled work. The entire scenario period is shown on the report.
6. For all but the Summary report, you can set a filter condition by selecting a filter criteria and the a value (e.g. District = 3). The available filter criteria vary based on the report. If you do not want to apply a filter, select the No Filter option. 7. For the Performance Measures report, select which measure you would like to include on the report. 8. For all but the Summary report, select a start and end year for the report. 9. Click the Generate button. A new tab will be created for the report (and assigned a sequential number). 10. You can now use the Print button to get a hard copy of the report. 11. Click Close to close the tab, or leave the tab open and click on the Specifications tab to run additional .
Viewing Program Results
To see the results of one or more programs of projects that you have set up in the Project
Planning module:
1. Select Program from the radio buttons at the top of the screen. 2. Select one or more programs for the report from the selection list. You can click on the Show Only Programs With Work checkbox to restrict the list to programs with at least one work item. To include all programs in the report, you can click the All checkbox. 3. (Optional) Enter a note about your report. 4. Select the type of report you would like. Options are: Work and Needs report shows the cost and benefit of preservation and improvement programmed work over a selected time period. If the All checkbox was selected, it includes needs for the Programmed Work scenario.
5-32
B R I D G E
P R O G R A M
S I M U L A T I O N
Preservation Work and Needs report shows the cost and benefit of preservation needs and programmed work over a selected time period. If the All checkbox was selected, it includes needs for the Programmed Work scenario. Summary report a tabular report showing the budget, work, benefits, and number of projects scheduled for each program. All programs are always included in this report.
5. For all but the Summary report, you can set a filter condition by selecting a filter criteria and the a value (e.g. District = 3). The available filter criteria vary based on the report. If you do not want to apply a filter, select the No Filter option. 6. For all but the Summary report, select a start and end year for the report. 7. Click the Generate button. A new tab will be created for the report (and assigned a sequential number). 8. You can now use the Print button to get a hard copy of the report. 9. Click Close to close the tab, or leave the tab open and click on the Specifications tab to run additional reports.
5-33
B R I D G E
P R O G R A M
S I M U L A T I O N
Reports on needed and programmed work for individual structures are included in the Project Planning module, and are described in Chapter 6.
5-34
6 Project Planning
Inspectors have identified a group of bridges which need repair or rehabilitation, and have entered these needs into the Inspection module. We now want to sort through the needs that were identified, and develop a set of projectsWe want to do an analysis of how different types of work would affect the performance of a particular structure in order to decide what work to schedule and whenThe Pontis simulation has been run for a five year scenario period, which has yielded a list of preservation and improvement needs. We want to compare these needs to what our inspectors identified, and decide what makes the most sense to doThere are currently a number of programmed bridge projects in various stages of planning, design and construction. In addition, several projects have been completed over the past year. We want to update the status of the projects in our database so that we can maintain an accurate history and see how much capacity we have for additional work
he Project Planning module provides a flexible set of tools for planning and scheduling project work. It is designed to help you select bridge work to be done based on inspector work candidates and results of the Pontis simulation. However, you can set up projects without either running the simulation or entering inspector work candidates. To assist with project development, a Bridge Analysis tool is included which produces graphical displays of structure performance over time given implementation of different project options. For agencies wishing to use Pontis for development of budgetconstrained programs, capabilities are provided to group projects by program category and identify project funding sources. The Project Planning module can also be used to track the status of projects throughout planning and implementation phases. When projects are completed, the actual work done and costs can be recorded to maintain a convenient history of work for each structure. This information can be used to provide improved cost estimates for future planning, and to track the effectiveness of different types of work over time. Chapter 6 pertains specifically to Pontis Version 4.5 only and will be updated with future versions of Pontis.
6-1
P R O J E C T
P L A N N I N G
6-2
P R O J E C T
P L A N N I N G
the Programming module produces a set of Pontis-generated work candidates. These work candidates are programmed in the scenario for particular years based on the scenario budget constraint. The term programmed here means that the work is scheduled only in the context of a particular scenario, which is a hypothetical rather than an actual program. Running a scenario does not automatically create actual projects. It is up to the Pontis user to review the scenario work candidates together with inspector work candidates and create projects. The system was designed this way in order to make a clear distinction between an actual program of projects that an agency is planning to do versus a set of possible futures that an agency wishes to analyze. The Project Planning module on the other hand helps you to develop actual projects. These projects are organized into Programs, which are intended to correspond to categories reflecting how bridge work is actually programmed in an agency. While both Programs and Scenarios have annual budgets and scheduled work in each year, there is not necessarily any relationship between the budgets and work for a scenario and the budgets and work in a program. Pontis was designed to support integration between program simulation and actual project and program development. Work recommended in a scenario can be used to develop a program of projects, and conversely, scenario runs can incorporate assumptions about projects that are created in the Project Planning module. Specifically: In the Project Planning module, you can view work candidates that were produced by one or more scenarios. You can also choose to automatically create projects in a batch fashion from all (or selected) work candidates from a scenario. When conducting a scenario analysis, it is often desirable to reflect actual planned or proposed projects. The program simulation has this capability when a scenario is run in the Programming module, it looks at all of the projects that have been set up in the Project Planning module. You can designate how youd like each project to be handled in the simulation for example, you can tell the simulation to automatically schedule the work in the project, ignore the project completely, or have the project compete with work candidates that are generated based on application of the preservation policy. If you have created a set of projects in the Project Planning module and youd like to analyze their likely impacts, and see performance results analogous to those that are available for scenario results, you can run a simulation for this purpose by selecting the Summarize button in the Results module. This simulation creates a special scenario called the Programmed Work scenario. Reports on this scenario can be viewed in the Results module.
6-3
P R O J E C T
P L A N N I N G
Project List
Toolbar
Work Candidates Panel Tree Project Planning Desktop Project View Parts of the Desktop
There are three data panels on the desktop: the main Project List at the top (containing either structures or projects), the Tree (lower left), and the Work Candidates Panel (lower right). The left portion of the screen contains a Toolbar, with buttons to perform various common operations, and radio buttons to control the contents and display of the data panels The main Project or Structure List is used to set the scope for your work in the Project Planning module. Selecting an item on one of these lists adds it to the tree; clicking on an already selected item de-selects it and removes it from the tree. Double-clicking on a project will open the project data entry forms. (Bridge data may only be edited from the Inspection module). The most recently selected item is shown in bold (indicating that it has focus, in software lingo). When you use a button that operates on a single bridge or project (such as Open Project), this is the bridge or project used. The Tree provides an Explorer-like interface, and shows a hierarchical view of programs, projects, bridges, and work items. Clicking on a + will expand the branches; clicking on a will collapse branches. Right-clicking on an item will show basic information about that item (e.g. for a bridge: feature intersected, facility carried, and notes).
6-4
P R O J E C T
P L A N N I N G
The Work Candidates Panel has two tabs one shows detailed information about the currently selected work item on the list, and the other shows a list of inspector and Pontis-generated work
Note: Resizing Windows: Note that you can resize each of the windows on the Project Planning Desktop by positioning your mouse on the border between windows until your cursor changes to a double arrow, and then dragging with the mouse.
candidates. This panel also has controls for selecting which work candidates are shown, and for synchronizing the work candidates with the main structure or project list. The radio buttons labeled Desktop on the lower left side of the screen control which of the three panels are shown. Select Three panels to see all of the panels: the Structure List on the top, the tree view on the lower left, and the work candidate list on the lower right. Select Explorer to see the tree view on the left and the work candidates list on the right. Select Project List or Bridge List to see only the list of projects or bridges. Select Candidates to see only the list of work candidates.
There are radio buttons in the upper left corner of the screen which control whether you see Projects or Bridges on the main list at the top of the screen. These also affect the tree view and the buttons on the Toolbar. In the Project view, you will see a list of projects (if any have been defined) in place of the Structure List. When you click on a project, it will be added to the tree view. Bridges included in that project will be shown as branches below the project, and work items appear as branches below each bridge. In the Bridge view, you will see the familiar Structure List at the top of the screen. When you click on a structure, that structure will be added to the tree view. If any projects have been defined including the structure, they will be shown as branches below the bridge. Work items for each project (for the parent bridge) are shown as branches below the project.
6-5
P R O J E C T
P L A N N I N G
The toolbar buttons (along the left side of the screen) change, depending on whether you are in Bridge view or Project view. The following provides a brief overview of the different buttons. See later sections for more details. Buttons available in both Project and Bridge views: Sync Lists: Synchronizes information in project and bridge views. If you are in Bridge view, clicking this button will switch you to Project view and show you a list of projects that include work on the structures on the Structure List you were viewing. If you are in Project view, clicking this button will switch you to Bridge view and show you a list of structures that were covered by the projects on your Project List. Note: there is also a Sync Lists button on the Work Candidates panel, which has a different function and is discussed below. Programs: Brings up a screen which allows you to define and modify information about multi-year bridge programs. Funding: Opens a screen which allows you to define and modify information about different available funding sources for projects.
Buttons available in Project view: New Project: Creates a new empty project, and opens the project tab cards where you can enter information about the project and define work items.
6-6
P R O J E C T
P L A N N I N G
Open Project Opens the project tab cards for the currently selected project on the Project
List, and allows you to view and edit the information.
Split Project Opens a screen which allows you to split the currently selected project on the Project List into multiple projects. Rank Projects Opens a screen which allows you to rank projects in a particular work program for one or all program years. Shift Projects Opens a screen which allows you to modify information about a group of projects at once. For example, you can use this feature to change the status of a set of projects when they are completed. Combine Projs Opens a screen which allows you to make a single project out of a selected group of projects. You can designate one of the projects as the master project. Work items from the other projects in the group are moved to the master project. Delete Project This removes the projects selected on the Project List from the database. All work items associated with the projects are removed as well.
Buttons available in Bridge view: NBI Project Info This opens the NBI Project Data screen with all of the required NBI project-related information (items 75A, 75B, 76, and 94-97). Analysis This opens the Bridge Analysis screen, which allows you to simulate performance of individual structures under different assumptions about what work will be done. You can also modify work item information and create and modify projects for the selected structure.
When you use the radio buttons to switch between Bridge and Project views, the views are by design NOT automatically coordinated the bridges on the Structure List are not necessarily those which have projects on the Project List. However, you can use the Sync Lists button on the Toolbar to see which bridges are associated with one or more projects, or to see what projects have been set up for a set of bridges. To see projects for bridges on the structure list:
Example:
Select the Bridges radio button to get into Bridge view. 1. (Optional) Use the Select button on the Structure List if youd like to only see certain structures on the list (for example, to restrict the list to bridges in District 1).
6-7
P R O J E C T
P L A N N I N G
2. Click on the Sync Lists button on the Toolbar. This will automatically switch the desktop to Project view, and display a list of projects that include work on bridges on the Structure List. 3. To see any of these projects on the tree, click on them individually, or use the Select All button. (Caution: since it is time consuming and memory-intensive to populate the tree view with large numbers of items, it is usually better to select only the projects of interest when there is more than 30 projects on the list.) 4. To reset the criteria for the Structure List so that it is no longer synchronized with the Project List, click on the Select button above the Structure List. Adjust the criteria (if
desired), and then click OK.
To see what bridges are included in a set of projects: 1. Select the Projects radio button to get into Project view. 2. (Optional) Use the Select button on the top of the Project List to restrict the list to only certain projects (e.g. projects in District 1). 3. Click on the Sync Lists button on the Toolbar. This will automatically switch the desktop to Bridge view, and display a list of bridges included in projects that were listed on the Project List. 4. To see these bridges on the tree view, click on the bridges individually, or use the Select All button. 5. To reset the criteria for the Project List so that it is no longer synchronized with the Structure List, click on the Select button above the Project List. Adjust the criteria
(if desired), and then click OK.
The work candidates list and the structure/project lists are not automatically coordinated. You can use the From List and Sync List buttons on the top of the Work Candidates tab to see the work candidates associated with bridges on the Structure List, and to see bridges associated with the work candidates shown on the work candidates list. To see work candidates for bridges on the structure list:
Example: You want to see which Interstate bridges in District 1 need replacement.
1. 2.
Select the Bridges radio button to get into Bridge view. Use the Select button on top of the Structure List to narrow the scope of the list (in this example, select Rural Interstate and Urban Interstate under Functional Class, and District 1 under District).
6-8
P R O J E C T
P L A N N I N G
3.
Click on the Select button at the top of the Work Candidates tab, and choose Clear Selection to remove any previously set criteria. If you only want to see certain types of work candidates on the list you can set criteria on this screen (for this example, select Replace Structure under Action Types), and click OK to close the Select Work Candidates screen.
Selected button and de-select the bridges by clicking on them.
4.
Make sure there are no structures selected on the Structure List. You can click the Just Then click on the From List button at the top of the work candidates list. All work candidates for the bridges on the Structure List which meet the work candidate criteria you established will be shown in the work candidates list.
1. Select the Bridges radio button to get into Bridge view. 2. On the work candidates list, click on the Select button, and choose Clear Selection to remove any previously set criteria. Now set the criteria for the work candidates you want to see (in this example, you would select Replace Paint System under Action Type). Click OK to close the Select Work Candidates screen. 3. Click on the Sync List button at the top of the Work Candidates tab. The Structure List will now be restricted to the bridges which have work candidates meeting your selected criteria (in this example, bridges needing painting).
6-9
P R O J E C T
P L A N N I N G
2. Select the Add button. The Adding Funding Source screen will appear.
25
Note: Annual budgets for programs in the Project Planning module are completely independent from the budgets set in the Programming module. The Programming module budgets are used in the simulation to constrain the total cost of work candidates produced by a scenario run. The Project Planning module Program budgets are used to assist with tracking of committed vs. budgeted funds from different sources.
6-10
P R O J E C T
P L A N N I N G
3. In the Funding Source field, enter the name of the funding source, as youd like it to appear in the pick lists. 4. Select the type of funding source. 5. (Optional) Enter a description of the funding source. 6. (Optional) Enter longer notes about the funding source (e.g. restrictions, authorizing legislation, etc.). 7. Click OK to save your changes. 8. Pontis requires that one funding source be designated as the default funding source. When new programs are set up, the default funding source is used to initialize the funding information for the program. If you would like this new funding source to be the default funding source, click on the Set As Default Funding Source button. To see what the current default funding source is, click on the Show Default Funding Source button. The default funding source will be shown on the status bar at the bottom of the screen. 9. Click Close to close the Funding Source Setup screen.
6-11
P R O J E C T
P L A N N I N G
3. In the Program ID field, enter a short name for the program, as youd like it to appear in the pick lists and reports. 4. Select the type of program. This is an optional item that can be used if you want to develop custom reports or queries based on a category of program rather than a specific program. For example, you may want to maintain separate programs for structure replacement, seismic
6-12
P R O J E C T
P L A N N I N G
retrofit, and structure widening along a specific corridor, and classify all of these programs as Improvement. Options for this field can be modified on the Parameters card in the Configuration module. 5. Enter a longer name for the program (This longer name is used on some pick lists where space allows). 6. (Optional) Enter the objective for the program. 7. Enter the Start Year and End Year for the program. Rows are added for annual program budgets based on the values that you enter. These values are also used when creating new projects. When a particular program is selected for a new project, the program start and end dates are displayed, and you are given the option of automatically scheduling the project for the first or last program year. Note that you are not prevented from assigning a project to a program if the project start date is not consistent with the program start and end year. 8. Enter the program Status. When setting up a new program, you will generally want to select Active, unless you are entering test data. Inactive programs are excluded from reports plan005 and plan006 which present information on program funding and budgets. Other reports include information on projects from inactive programs 9. (Optional) Enter longer notes about the program. 10. (Optional) For each year of the program, select a funding source and enter a budget amount. This allows you to track the costs of projects assigned to the program against the established annual budgets for the program. This is an optional feature for those users wishing to use Pontis for program balancing purposes. Note that the system does not automatically ensure that programs are balanced it simply provides the necessary information. You may add and edit funding sources from the current screen by clicking on the Fund Sources button. 11. Click OK to save your changes. 12. Pontis requires that one program be designated as the default program. When new programs are set up, the default program is used to initialize the Start and End years. Newly created projects are automatically assigned to the default program. If you would like this new program to be the default program, click on the Set As Default Program button. To see what the current default program is, click on the Show Default Program button. The default program will be shown on the status bar at the bottom of the screen. 13. Click Close to close the Program Setup screen.
6-13
P R O J E C T
P L A N N I N G
Select the Programs button on the left side of the screen. The Program Setup screen will appear. Select the program you wish to modify or delete by clicking on it. To edit information about the program, click on the Open button, edit any of the program information, and then click OK to save the changes. To remove the program, first check to make sure that it is not the default program, since the default program may not be deleted. To assign a different program as the default, click on the new program, and click on the Set As Default Program button. Now select the program you wish to delete again. Click on the Delete button. If any projects have been assigned to the selected program, a message will notify you of this, and you will be given the option of canceling your action. IMPORTANT: If you go ahead with the delete, the program AND all of the projects (and work items) assigned to this program will be deleted. Note that the work candidates associated with any work items that are deleted will be retained, and their status will be changed from assigned to unassigned. Click Close to close the Program Setup screen.
2. 3.
4.
5.
6.
6-14
P R O J E C T
P L A N N I N G
The column labeled A indicates the assignment status of the work candidate. If the work candidate has been assigned to a project and is now a work item, there will be a in the column. Unassigned work candidates will have a in this column. The column labeled S indicates the source of the work candidate. Inspector work candidates are indicated with a . Pontis-generated work candidates are indicated with a . If several different scenarios have been run, there may be duplicate work candidates in the list (since each scenario generates its own set of work candidates).
The column labeled Object contains either 0-Bridge for bridge-level work candidates (e.g. replace bridge or flex actions) or the number and name of the element for which work is recommended.
6-15
P R O J E C T
P L A N N I N G
The column labeled Work ID/Explication will include the inspector work candidate ID if the work candidate was entered manually in the Inspection module. If the work candidate was generated by the Pontis simulation, this column contains a brief explanation of why the work was selected. Note: if the window isnt wide enough to read the entire explication, you can resize it with your mouse, or click on the Description tab to see the full text. The SC column shows the scenario key for Pontis-generated work candidates. The other columns are self-explanatory.
The Select Work Candidates screen allows you to set criteria for which types of work candidates appear on the list. Its function is similar to the Select Structures screen.
Example: You want to see major projects recommended by inspectors, and by the Pontis simulation.
To set selection criteria: 1. Click on the Select... button at the top of the Work Candidates tab. The Select Work Candidates screen will appear.
6-16
P R O J E C T
P L A N N I N G
2. The previously set criteria will be shown in the Current Selection field. It is good practice to begin by clicking on the Clear Selection button before modifying the selection criteria. 3. Set your criteria by clearing the All Checkbox next to the item(s) that you would like to select. Then, select or enter your criteria. (In this example, you would clear the check box marked All next to Action Types, and select Replace Structure, Replace Superstructure, Widen Structure, Raise Structure, and Strengthen Structure.)
Tip: If you are reviewing Pontis-generated work candidates, and have run several scenarios with similar specifications, you should select a single scenario in order to avoid viewing duplicate work candidates.
4. Once you have set the criteria, you can use the English or Where buttons to verify your choices (English will display your choices in plain English; Where will display the SQL statement corresponding to your choices). You can also use the Count button to see how many work candidates meet the criteria. 5. Click OK to close the screen and apply the selection criteria.
Using the From List Button
In Bridge view, the From List button will restrict the list of work candidates to those bridges currently selected on the Structure List. If there are no bridges selected, the list of work
6-17
P R O J E C T
P L A N N I N G
candidates will be restricted based on the full set of bridges on the Structure List. In Project view, this button works in an analogous fashion, except that the list of work candidates is restricted to the set of bridges covered by projects selected on the Project List. (If no projects are selected, then the selection criteria is based on the full list.) Any existing criteria that have been set on the Work Candidate Select Screen will remain in effect.
Using the Scope, Status and Source Selection Lists
The three selection lists directly above the work candidates grid provide a convenient way to apply additional restrictions to the work candidates list. Note that these restrictions do not replace those already set with the Select Work Candidates screen rather they are used to provide additional filter criteria on top of those which already exist. For example, if you had set a selection criteria that restricted the list to Inspector work candidates only, and then you used the Source dropdown to view All candidates, you would still not see any Pontis-generated candidates on the list. The Scope selection list allows you to dynamically restrict the work candidate list based on the selected bridge or project on the tree. This allows you to quickly view the work candidates associated with a particular bridge, or those associated with any of the bridges in an already existing project. To see work candidates for a bridge, select the bridge on the tree, and then select Bridge from the Scope selection list. As you click on other bridges in the tree, the work candidates will automatically change to reflect the selected bridge. To see work candidates for the bridges in a project, select the project on the tree, and then select Project from the Scope selection list. As you click on other projects in the tree, the work candidates will change automatically. To stop applying the restrictions, select All from the Scope selection list If there are no work candidates for the selected bridge or project, you will get a message to that effect, and the Scope selection list will be reset to All. The Status selection list allows you to restrict the work candidate list based on whether or not the work candidate has been assigned to a project. The Source selection list allows you to restrict the work candidate list based on whether the work candidate was generated by running a Pontis scenario (Generated) or was entered into the Work tab of the Inspection module (Inspector).
Refreshing and Removing Work Candidate Selection Criteria
The Refresh button at the bottom of the Work Candidates panel will reapply the last set of criteria that you applied in the Work Candidate Selection Screen. You should use this button after making changes to data (e.g. adding work candidates in the Inspection module) to ensure that the list reflects the modifications. You should also use it after you have modified the contents of the list with the From List button, and want to return to your previous selections.
6-18
P R O J E C T
P L A N N I N G
Status.
The Go button works in conjunction with the three dropdown lists for Scope, Source, and If you edit information after you have set criteria with the dropdowns, the Go button reapplies the dropdown selection criteria. For example, if you use the Status dropdown to view only unassigned work items, and then you subsequently assign one of the work items on the list to a project, that work item will remain on the work candidates list until you click on the Go button. When you use the dropdown lists to set criteria, a Remove Filter button appears next to the Go button. This button can be used to remove the criteria established by the dropdown lists. It does not affect the filter established by the Select Work Candidates screen.
6-19
P R O J E C T
P L A N N I N G
Get into Bridge view by clicking on the Bridges radio button. Use the Find button above the Structure List to select the bridge youd like to work with. In the Work Candidates panel, click on the From List button to see work candidates for the selected bridge on the Structure List.
Create Projects button at the bottom of the Work Candidates panel.
4.
To create a project for a bridge, select the work candidates youd like to include, and click the The Create Projects screen will appear.
5. Under Which Work Candidates?, click on the Selected Work Candidates radio button. 6. Select the Program for the project.
6-20
P R O J E C T
P L A N N I N G
7. Select a Status. The status of a project is used to determine which projects are considered when the Summarize button is used in the Results module to create the Programmed Work scenario. Only projects with a status of 1-Initiated, 2-Programmed and 4-In Progress are included in this scenario. (Status 0Proposed, 3Deferred, and 5-Completed are excluded.) 8. Select a Scenario Treatment if you want to specify how youd like this project to be handled the next time a program simulation is run: Schedule the simulation will schedule the project and deduct its costs from available budget. Assume Done the simulation will assume the project was done and account for its impacts, but wont deduct its cost from the available budget. Ignore the simulation will ignore the project. Compete the simulation will consider the project as an alternative to the Pontisgenerated projects in the same year (if any), and schedule the project that has the highest benefit-cost ratio. See the Technical Manual for a detailed discussion of how the simulation schedules work.
9. (Optional) Select the primary funding source for the project. This funding source will be associated with each work item included in the project. (Association between work items and funding sources is not a requirement in many agencies, and therefore this is an optional item and can be ignored in most cases.) 10. Select the Program Year for the project, either by typing a specific year, or setting it based on the work item or program years. It is good practice to schedule the project within the Program time limits, but this is not enforced by the system. 11. Under Number of Projects to Create, click the radio button marked ID, and enter a Project ID for the new project. It is recommended that a consistent project identification convention be followed. You may want to assign an ID that is consistent with the project IDs that can be automatically generated when multiple projects are created at once. See step 12 under the section below on Batch Mode: Automatically Generating Projects from Work Candidates for further information. Note that the project ID can be easily edited at a later time. 12. Click the Apply Specifications button. Information about the project to be created will appear for your review on tab 2 on the right side of the window. You may edit any of this information. 13. Click the Create Projects button. A message will appear confirming the creation of the new project. Click OK to close the message window, and then Close to close the Create Projects window.
6-21
P R O J E C T
P L A N N I N G
1. Get into Bridge view by selecting the Bridges radio button at the top left corner of the screen. 2. (Optional) Use the Select button on the top of the Structure List to select the bridges that youd like to work with. (In this example, you would select District 1 under Districts and Rural Interstate, Urban Interstate under Functional.) 3. Set the work candidate selection criteria by clicking on the Select... button at the top of the Work Candidates panel. Use the Select Work Candidates screen to filter the work candidate list to include the types of work youd like to group. (See the subsection in Section 6.4 titled Using the Select Work Candidates Screen for step-by-step instructions.) In this example you would select Replace Paint System under Action Type. Click OK to close the Select Work Candidates screen and apply your selection criteria. The Work Candidates panel will now include all work candidates with actions that have been assigned this action type on the Element Specifications card in the Configuration module. Note that the Action Type selection list cannot be used to query for flexible actions that include particular action type(s). You must use the Flex Actions selection list instead. 4. If you have set selection criteria for bridges, make sure that none of the bridges are selected, and then use the From List button to restrict the work candidates to those for bridges on the Structure List. 5. Select the work candidates that youd like to group into a single project. 6. Click on the Create Projects button. The Create Projects screen will appear. 7. Under Which Work Candidates?, click on the Selected Work Candidates radio button. 8. Select the Program, Status, Scenario Treatment, Funding Source, and Program Year for the project (see Creating Projects for Individual Bridges From Work Candidates for details). 9. Under Number of Projects to Create, click the radio button marked ID, and enter a Project ID for the new project. This can be easily changed later. 10. Click the Apply Specifications button. Information about the project to be created will appear for your review on Tab 2 on the right side of the window. You may edit any of this information. 11. Click the Create Projects button. A message will appear confirming the creation of the new project. Click OK to close the message window, and then Close to close the Create Projects window.
6-22
P R O J E C T
P L A N N I N G
1. Get into Bridge view by selecting the Bridges radio button at the top left corner of the screen. 2. Decide which work candidates that youd like to make into projects. You can select a set of work candidates based both on characteristics of the affected bridges (e.g. district, ownership), and characteristics of the work candidates. 3. Set the work candidate selection criteria in the Select Work Candidates screen by clicking on the Select... button at the top of the Work Candidates panel. (In this example, you would select Pontis Generated under Source, and the name of your scenario under Scenarios.)
Caution: Use care when selecting work candidates to avoid duplication in your projects it is possible that there will be duplicate work candidates in different scenarios, or that a work candidate duplicates work that has already been included in an existing project.
4. If you want to create projects for all bridges, skip this step. Otherwise, set the bridge selection criteria by clicking on the Select... button at the top of the Structure List. Follow the same procedure as in the previous step to select which bridges to include. The Structure List should now include only those bridges meeting your selection criteria. Make sure that none of the structures are selected. 5. In the Work Candidates panel, click on the From List button. The list of work candidates will now reflect both the work and bridge-related selection criteria. 6. Click the Create Projects button at the bottom of the Work Candidates panel. The Create Projects window will appear, with the list of work candidates shown on the right. 7. If you want to make projects for all of the work candidates, under Which Work Candidates?, click on the All Candidates Shown on List radio button. Otherwise, select a set of candidates by clicking on them, and then click on the Selected Work Candidates radio button. 8. Select the Program, Status and Scenario Treatment for the projects. Since you are creating several projects at once, these values may vary across the different projects. For now, select options that best describe the majority of projects. After the projects are created, you either edit this
6-23
P R O J E C T
P L A N N I N G
information for individual projects, or use the Shift button to change these items for a group of projects at once. (See the subsection in Section 6.9 titled Using the Shift Button to Change Information for Groups of Projects.) 9. (Optional) Select the primary Funding Source for the projects. If there is variation across the projects, you can edit this for individual projects after they are created. 10. Set the Program Year for the projects. When creating a batch of projects, you can use the option to schedule projects for the year of their earliest (or latest) work item instead of selecting a particular year for all of the projects to be programmed. 11. Under Number of Projects to Create, select either One Project for each Structure or One Project for each Work Item. In most cases, you will want to create a project for each structure, including all of the work items for that structure. However, you may want to create a project for each work item if you expect that different types of work on a structure will be scheduled or programmed separately. 12. Since you will be creating multiple projects, you need to decide on a convention for assigning project IDs. Standard project reports include both project IDs and names. It is a good idea to keep project IDs relatively short to make them easy to enter for query purposes (in the Project List Find and Select screens, and report selection criteria screens.) One option is to use a common prefix which reflects the type of project (e.g. major work in District 1 could be assigned a prefix of D1-MAJ. If you specify a prefix, and leave the other options blank, the project IDs will consist of the prefix plus a sequential number (e.g. D1-MAJ 1, D1-MAJ 2) If you specify a prefix and select Include Bridge ID in Project ID, the project ID will consist of the prefix plus the bridge ID. (If you choose to include the bridge ID, you can also select the BID option, which prefaces the bridge ID with the label BID:). If you are creating a project for each work item, the option to Include Work ID in Project ID can be used. You can also choose to add a date or date-time stamp to the project ID by selecting the Append date-time or Append time options. If you leave all of the numbering options blank, your project IDs will consist of the word Pontis plus a sequential number. 13. Click the Apply Specifications button. Information about the projects to be created will appear for your review on Tab 2 on the right side of the window. You may edit any of this information. You can also choose different options on the left side (e.g. for project IDs), and re-apply the specifications. 14. Click the Create Projects button. A message will appear confirming the creation of the new projects. Click OK to close the message window. 15. You can edit the individual projects from here, by selecting them in the Project IDs tab, and then clicking the Open Project button. 16. Click the Close button to close the Create Projects window.
6-24
P R O J E C T
P L A N N I N G
1. Get into Projects view by clicking the Projects radio button . 2. Click the New Project button on the left side of the Project Planning desktop. 3. Complete items on the Overview tab. At a minimum, enter a meaningful Project ID (this is what will appear on the tree), a Project Name, and select a Program and Program Year. In addition, if you will be running Pontis simulations, you will want to select values for Status and Scenario Treatment:
The Status of a project is used to determine which projects are considered when the Summarize button is used in the Results module to create the Programmed Work scenario. Only projects with a status of 1-Initiated, 2-Programmed and 4-In Progress are included in this scenario.
6-25
P R O J E C T
P L A N N I N G
The Scenario Treatment is used to determine which projects to schedule when a scenario is run in the Programming module (see step 8 of the section on Creating Projects for Individual Bridges From Work Candidates). 4. If you want to add work items to your project at this point, proceed to step 5. (Work items can also be added to a project once it is created by dragging Pontis or inspector-generated work candidates from the Work Candidates list to the project on the tree.) Otherwise, skip to step 6. A project does not need to have any work items it is possible to define a project as a placeholder for a general type of work to be determined later. However, work items provide the linkage to specific bridges and elements. Work items must exist for the project to be considered in scenario simulations. You can add as many work items as you like. 5. Select the Work Items tab, and click the Add Work Item button. Use the Find Bridge button to select the bridge for the work item. Then, enter an ID for the work item as youd like it to appear on the tree, and complete the other items:
Select the Type of Work: Bridge work includes replacement or improvement actions, Element work includes maintenance and rehabilitation actions applied to a single element on a selected structure unit (or all units) on the bridge.
6-26
P R O J E C T
P L A N N I N G
Flexible (bridge) work allows you to choose a FLEX action26 to apply to all elements on the bridge that were included in the definition of the FLEX action. Flexible (element) work allows you to choose a FLEX action to apply to a single selected element on a selected structure unit (or all units) on the bridge. You would choose Flexible (element) work if you wanted to have the simulation model the impact of this work item based on rules that you define along with the flex action specification (e.g. set all condition states back to 1). For element-level work, select an element. You can also select a particular structure unit, or all structure units. The total quantity of the element on the bridge will appear. You can edit this quantity to reflect the quantity of work to be done. If you will be running the Pontis simulation to incorporate this project, you should select the condition states to which the selected action should be applied. If all of the condition states are selected (recommended), the action will be applied to those condition states for which the action is feasible (as determined by the information on the Element Specifications card in the Configuration module). If none of the condition states are selected, then the action will be ignored by the simulation. Enter a Cost for the work item. This cost is used to calculate the overall project cost, and is displayed in project reports. If you will be running the Pontis program simulation (or using the Bridge Analysis feature to analyze this item), and you do not want this cost recalculated by the model, select the Lock checkbox. If the cost is locked, then the cost that you have entered will be used in the simulation model to calculate the benefit-cost ratio. Otherwise, the simulation model will calculate its own cost. (Optional) Enter a Benefit for the work item. This is used to calculate the overall project benefit, and appears on project reports. If you will be running the Pontis program simulation (or using the Bridge Analysis feature to analyze this item), and you do not want this benefit to be recalculated by the model, select the Lock checkbox. If the benefit is locked, then the benefit that you have entered will be used in the simulation model to calculate the benefit-cost ratio. Otherwise, the simulation model will calculate its own benefit. (Optional) Select a Priority for the work item. For work items that were derived from inspector work candidates, this shows the priority that was set by the inspector. It is for reference only, and is not included in any standard Pontis analysis or report. (Optional) Select a Status for the work item. For work items that were derived from inspector work candidates, this shows the last status that was established for the work candidate. It is for reference only, and is not included in any standard Pontis analysis or report. (Optional) Enter Notes about the work item. This is for reference only and may be left blank.
26
FLEX actions consist of a group of element-level actions that are commonly done at the same time. They are defined on the Action card of the Configuration module
6-27
P R O J E C T
P L A N N I N G
Select a Contractor for the project (the pick list of contractors can be customized in the Configuration module.) Enter the Contract ID, Estimated Cost (typically the engineers estimate), Contract Cost (typically the accepted bid price), and the Final Cost (including change orders) as they become available. In general, the total contract costs should be approximately equal to the project costs (which are calculated by summing work item costs and adding indirect costs from the Overview tab). However, it is up to the user to manually ensure that the numbers are consistent. The contract costs are for reference only and are only displayed on standard report plan004_project_details. You can enter funding sources to be used for this project, by clicking on the Add button. Then select a Funding Source, and enter an Amount. You may also enter any Notes about use of this funding source for the project. Note that Funding Sources are defined on the Funding Source Setup screen, which can be reached by clicking the Maintain Funding Sources button.
6-28
P R O J E C T
P L A N N I N G
Get into Bridge view by selecting the Bridges radio button in the upper left corner of the Project Planning desktop. Select the bridge you wish to analyze from the desktop. You can use the Find button at the top to quickly move to a bridge based on its ID, Name, Facility Carried, Feature Intersected, or Route/KM post. Click on the Analysis button. The Bridge Analysis screen will open.
2.
3.
If you want to see needs for this bridge that were generated by a Pontis scenario run, select the scenario from the pick list. Otherwise, select the Bridge Analysis scenario.
6-29
P R O J E C T
P L A N N I N G
5.
Click the Get Work Items button. This will retrieve all of the work items in projects that have been set up for the bridge. It will also retrieve all of the inspector work candidates, and Pontis work candidates from the selected scenario. If there are no work candidates and no work items for the bridge, you will get a message to try another bridge/scenario combination.
6. To view and edit information about the parent project for a work item, select the work item, and click on the Open Project button.
3. Click the Generate button to run the simulation. When the simulation is completed, there will be six tabs in the Bridge Analysis screen: The first tab will contain the specifications for the simulation (selected work items/candidates). The second tab is the Performance Summary. It shows the cost of work done each year, as well as the cumulative and discounted cumulative costs. The first year in which work was scheduled is used as the base for calculating the cumulative discounted cost. This report also shows key performance measures for the bridge
6-30
P R O J E C T
P L A N N I N G
for the different years in which work was scheduled: the health index, the sufficiency rating, and NBI ratings. The third tab is a graphical presentation of the costs by year. The fourth tab shows a graph of health index and sufficiency rating by year. The fifth tab shows the projected NBI ratings by year The sixth tab shows the projected condition distribution for each element on the bridge.
4. Once you have reviewed the results, you may print them using the Print (current screen only) or Print All buttons. 5. You can now return to the first tab, and run additional analyses. (You can switch to a different bridge by typing its ID into the Bridge entry field, or by using the Find button.) If you have not closed the first set of analysis tabs, they will remain open for comparison purposes. When a new analysis is run, new results tabs will be created, and numbered sequentially to follow the currently highest numbered tab.
6-31
P R O J E C T
P L A N N I N G
Finding a Project
In Project view, you can use the Find button to find a project based on characteristics of the project: ID, Name, or Status, or based on characteristics of the bridges included in the project: Feature Intersected, Route/KM-Post.
Example: You want to see if any new projects have been defined for structures on Route 50.
1. Select the Projects radio button to get into Project view. 2. Click on the Find button. 3. Click the Clear Criteria button to remove any previously set criteria. 4. Enter criteria for the project. You can click on the buttons next to Project ID, Project Name, Feature Intersected and Route to toggle them among Contains, Equals, Begins With, and Ends With. For this example, you would enter a 50 into the Route field, and set the button next to the field to Equals. You would enter a KM Post range from 0 to 1,000. 5. Click on the Find Records Based on Current Criteria button. A list of projects meeting your criteria will appear. 6. Select the project of interest, and click the Select Project and Close button. The project will be selected on the Project list, and added to the tree. 7. To view/modify information about this project, double-click on it, or click the Open Project button.
6-32
P R O J E C T
P L A N N I N G
2. Click on the Select button at the top of the Project List. The Select Projects screen will appear.
3. Click on the Clear Selection button to remove any previously set selection criteria. 4. Set your criteria by clearing the All Checkbox next to the item(s) that you would like to select. Then, select or enter your criteria. (In this example, you would clear the check box marked All next to Program, and select Improvements Program, clear the checkbox marked All next to Action Type, and select Replace Structure, and clear the checkbox marked All next to Program Year, and enter From 2002 To 2002. 5. Once you have set the criteria, you can use the English or Where buttons to verify your choices. (English will display your choices in plain English; Where will display the SQL statement corresponding to your choices.) You can also use the Count button to see how many work candidates meet the criteria. 6. Click OK to close the screen and apply the selection criteria. The Project list will show projects meeting your criteria.
6-33
P R O J E C T
P L A N N I N G
1. Get into Projects view by clicking the Projects radio button . 2. Click on the Rank Projects button on the left side of the desktop. The Rank Projects screen will open.
3. Select a Program. (You can only rank projects within a particular program; not across programs.) The projects assigned to the selected program will be displayed.
27
Agency ranks which are typically calculated by external systems - can be entered in the Overview tab of the Project tab cards.
6-34
P R O J E C T
P L A N N I N G
4. If youd like to rank projects within a particular year, select the Filter on Year checkbox, and select a year. The list of projects will be restricted to the selected year. 5. Sort the project list according to the criteria on which you want to base your ranking, by clicking on the column heading. (Clicking more than once on a column will change the sort from ascending to descending order). 6. Click on the Rank in Sorted Order button. This will assign a sequential number, starting with 1 in the Program Rank column, based on the current sort order of the list. 7. You can manually adjust the Program Ranks by typing numbers in that column (they need not be sequential; order is all that matters). Then, click on the Re-Rank button to assign sequential numbers from 1 to n= the number of projects, based on the Program Ranks that you have entered. 8. The Program Rank for individual projects can be viewed for individual projects on the Overview tab of the Project data entry screens. The report plan003_project_priority _list shows projects sorted by program, year, and Program Rank.
6-35
P R O J E C T
P L A N N I N G
To update project information: 1. Get into Projects view by clicking the Projects radio button. 2. Select the project you wish to update on the Project List. (You can use the Find or Select buttons at the top of the Project List to help you locate the project.) 3. Click the Open Project button on the left side of the Project Planning desktop. 4. Update items on the different tabs of the Project data entry screens. See Creating Projects Without Using Work Candidates or the screen reference help for information on the different screen items. (In this example, you would go to the Contract & Funding tab, select a Contractor, enter the Contract ID and Contract Cost.) 5. Click Close. Your changes are automatically saved.
Adding, Removing, and Moving Project Work Items Using the Tree
You can easily add or remove work items to/from a project, or move work items from one project to another: 1. Get into Project view by selecting the Projects radio button. 2. Make sure that the Three Panels radio button is selected from the Desktop options on the lower left side of the desktop. 3. Select the project(s) you wish to modify on the Project list so that they are added to the Tree. 4. To remove a work item from a project, select the work item on the Tree, and drag it onto the Work Candidates panel. If the work item was originally created based on a work candidate, (and if that work candidate still exists28), the work candidates status will change from Assigned to Unassigned. If the work item was created from scratch on the Project
28
Inspector work candidates may be deleted on the Inspection module Work card. Pontis-generated work candidates from a particular scenario will all be deleted and replaced with a new set of candidates when the scenario is re-run. If work candidates are used to create work items, and then these work candidates are subsequently deleted, there will be no impact on the associated work items.
6-36
P R O J E C T
P L A N N I N G
Work Items tab, it will be removed from the database (a new work candidate is never created when a work item is removed from a project). 5. To assign a work candidate to a project (thereby creating a work item), select the work candidate in the Work Candidates panel, and drag it onto the project. The work candidates status will change from Unassigned to Assigned. 6. To move a work item from one project to another, select the work item on the tree, and drag it to the other project.
Deleting Projects
Deleting a project will remove it and its work items from the database. If the work items were created from work candidates (and these work candidates still exist), the source work candidates will NOT be deleted; their status will simply be changed from Assigned to Unassigned. To delete projects, select them on the Project list and click the Delete Projects button. You will get a message telling you the number of projects and work items you are about to delete, and you will be asked to confirm that you want to delete them.
1. Get into Projects view by clicking the Projects radio button. 2. Select the projects you wish to update on the Project List. (You can use the Find or Select buttons at the top of the Project List to help you locate the project). 3. Click the Just Selected button on the top of the Project List. This will restrict the list to show only the selected projects 4. Click the Shift Projects button on the left side of the Project Planning desktop. The Shift Projects screen will open, and show your selected projects in the list.
6-37
P R O J E C T
P L A N N I N G
5. Select values for Status, Program Year, Completion Date, Program, and Treatment at the top of the screen. You only need to set values for those items that you would like to change leave the others blank. At the bottom of the screen, you can also lock or unlock work item costs and benefits for the selected projects (costs and benefits that are locked will not be over-written by running a scenario). 6. Click on the Shift button. This will change the items that you have set for all of the selected projects. (In this example, you would select 5-Completed under Status, and enter a project End Date.) 7. Click Close to close the Shift Projects screen.
Combining Projects
The Combine Projs button allows you to combine two or more projects into a single project.
Example: You used the batch approach to automatically create a set of projects based on a group of work candidates. Four of the projects involve deck overlays on bridges on the same route, and youd like to package these into a single project.
1. Get into Projects view by clicking the Projects radio button . 2. Decide which of the projects is to be the Master Project. When projects are combined, work items from the selected projects are added to the Master Project.
6-38
P R O J E C T
P L A N N I N G
3. Select the projects you wish to combine with the Master Project on the Project List you do not need to select the Master Project here. (You can use the Find or Select buttons at the top of the Project List to help you locate the project). 4. Click the Just Selected button on the top of the Project list. This will restrict the list to show only the selected projects. 5. Click the Combine Projs button on the left side of the Project Planning desktop. The Combine Selected Projects into Master Project screen will open, and show your selected projects in the list.
6. Select the Master Project. 7. If you would like to delete the projects that you are combining, select the Delete projects being combined checkbox. If this checkbox is NOT selected, the work items of the selected projects will be moved to the designated Master Project. The old projects will still exist, but wont have any work items in them. The old project costs will be set to equal the indirect costs that were entered the costs of the eliminated work items will not be included. 8. Click the Apply button to combine the projects. 9. Click the Close button to close the window.
6-39
P R O J E C T
P L A N N I N G
Splitting Projects
The Split Project button allows you to create several projects from a single project.
Example:
You want to split a 50 bridge painting project into two projects with 25 bridges each, to be scheduled in two different years.
1. Get into Projects view by clicking the Projects radio button. 2. Select the project you wish to split on the Project List. (You can use the Find or Select buttons at the top of the Project List to help you locate the project). 3. Click the Split Project button on the left side of the Project Planning desktop. The Split Project screen will open. All of the work items for the selected project will be shown on the Work Items tab list.
4. You can now do one of three things: a. Create one new project with a selected set of work items. In this case, select the work items to be included in the new project, and click the Just selected work items radio button. Under Number of Projects to Create, select the ID radio button, and enter the ID for the new project. (In the above example, you would select the painting work items for the
6-40
P R O J E C T
P L A N N I N G
25 bridges to be included in the new project, and enter a new Project ID: Painting FY 2003.) b. Create a set of new projects from the work items in the project one for each bridge. In this case, click the All work items shown on the list radio button. Under Number of Projects to Create, select the One Project for Each Structure radio button. Decide how youd like the new projects to be identified. One common method for this case is to enter a prefix for the set of projects, and append the Bridge ID onto that prefix. To do this, enter a prefix for the projects to be created, and click the Include Bridge ID in Project ID option. c. Create a set of new projects one for each work item in the original project. In this case, click the All work items shown on the list radio button. Under Number of Projects to Create, select the One Project for Each Work Item radio button. Decide how youd like the new projects to be identified. One common method for this case is to enter a prefix for the set of projects, and append the Work Item ID onto that prefix. To do this, enter a prefix for the projects to be created, and click the Include Work Item ID in Project ID option. 5. Select the Program, Status and Scenario Treatment for the new project(s). If you are creating several projects at once, these values may vary across the different projects. For now, select options that best describe the majority of projects. After the projects are created, you can use the Shift button to easily modify this information for individual projects. See the section above titled Using the Shift Button to Change Information for Groups of Projects) 6. (Optional) Select the primary Funding Source for the project(s). If there is variation across the projects, you can edit this for individual projects after they are created. 7. Set the Program Year for the project(s). When creating several projects at once, it is recommended that you use the option to schedule projects for the year of the earliest (or latest) work item.
6-41
P R O J E C T
P L A N N I N G
29
Agencies can create custom reports using Infomaker, and make them available from within Pontis. See the Technical Manual for instructions on creating custom reports.
6-42
P R O J E C T
P L A N N I N G
plan008_pontis_candidate_list: This report shows Pontis-generated needs or work candidates for a selected set of bridges. You can select which types of work to include based on year, costs and benefits, whether the work was programmed in the scenario (pontwcstatus = 0 for programmed work), whether the work was assigned to a project (pont_work_assigned=1 for work assigned to projects) and a variety of other items in the pont_work table.
6-43
Wed like to know how can Pontis be customized for our particular needs. Can we define our own elements? Can we change the picklists that appear in the data entry screens? What other customization is possible?
ontis was designed to be used by a wide range of agencies. Therefore, the software is highly customizable, providing each agency with powerful capabilities to add new data items, create custom screens and reports, and configure the modeling and analysis routines to meet their needs. When an agency first implements Pontis, it is recommended that they experiment with sample data to understand the systems features, and then develop a plan for the type of customization to be done. It is much easier to customize the system at the start. Once data have been loaded, models have been run, projects developed, etc., customization must be done with a greater degree of care. The Technical Manual provides detailed coverage of how to customize Pontis, including instructions for customizing the user interface. Some Pontis customization for version 4.5, such as development of new screens, structure lists, and reports must be done through the InfoMaker tools (which is packaged with the Pontis license). Other types of customization are done through the Configuration module. This chapter provides an overview of each of the cards in this module. Separate sections have been provided for Pontis 4.5 and Pontis 5.1.2 as indicated in the section headings below.
7-1
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
Caution: Before undertaking any customization, see the Technical Manual for an in-depth discussion of customization and configuration procedures, and how different options affect the database, the application, and the models. Most of the procedures described in this chapter should only be performed by a system administrator who understands what the impacts of the changes they are making will be, and can take steps to recover from unintended loss or modification to information.
7-2
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
Note that the System Administrator will need to assign each user a password and grant them access to the Pontis database before they will be able to use Pontis. To set up new users or change information for existing users: 1. Click on the User Administration card in the Configuration module.
2. To enter a new user, select File-New from the menu. A blank row will appear. To modify information for an existing user, click on the appropriate row. 3. Enter or edit information about the user. The only required item is the User ID. All other items may be left blank.
7-3
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
4. Check off user permissions at the bottom of the form. Users will have access to the checked items. Access to any Pontis module can be restricted by un-checking the box next to the module name. Access to the entire system can be cut off by un-checking the box marked PONTIS. Other types of privileges can be granted, such as the ability to delete bridges or inspections, and the ability to modify simulation rules. See the application help (F1) for this screen for further information. 5. If desired, set bridge access privileges for the user for use in the Inspection and Gateway modules by clicking the Set Bridge Access button. See the application help (F1) for this screen for further information. 6. If the user will be entering deterioration and/or cost elicitation information, click on the Add Deterioration Elicitation Records and/or Add Cost Elicitation Records buttons to add blank elicitation records for the user to the database. 7. Click the Save button to save your changes.
7-4
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
Parameters Card
5. On the left side of the card, scroll down to the table/field name combination for the parameter you wish to edit, and click on it. The coding for the selected field will appear on
7-5
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
the right side of the card. If the field is not there, it generally means that there is no picklist for it, or the picklist cannot be customized. 6. To edit the descriptions for the different codes, click on the one you wish to edit, and modify the information. The Short Label is the item that typically appears on picklists and reports. To edit the Detailed Description, click on the Edit Description button. 7. To add a new value for the parameter, click the Add Value button. A blank row will appear. 8. Enter the Value and Short Label. Other items are optional. Make sure that the Value you enter is not already listed for this parameter it must be unique. 9. To remove a value from the list, select its row, and click the Delete Value button. 10. Click the Save button to save your changes. To add a new parameter: 1. Click on the Parameters card in the Configuration module. 2. Click on the Add New Parameter button. The Add Parameter screen will appear. 3. Enter the table and field name for your parameter. 4. Click OK. A new row for this table and field will be added to the parameter list. 5. Use the Add Value button (described above) to add a set of values for the new parameter. 6. Click the Save button to save your changes. If you want to delete a parameter, it is strongly recommended that you backup the parameters table first. To delete a parameter, click on the Delete Parameter button. You will be asked to confirm the deletion. If you confirm by clicking OK, the parameter and all of its values will be removed from the database. Note that this only affects the picklists and display of information it does not affect the actual values stored for the field that the parameter was for.
7-6
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
The standard set of elements in Pontis consists of the Commonly Recognized (CoRe) bridge elements and smart flags. Use of CoRe elements provides a standard for bridge condition tracking which enables data sharing among states, and provides a basis for a conversion of detailed bridge condition data to NBI condition ratings. Smart flags are also included in the element specifications list. Smart flags allow tracking of distress conditions such as pack rust and deck cracking which are not included in the standard condition state language for CoRe elements because they follow different patterns of deterioration and are measured in a different way. In Pontis, smart flags operate as if they are elements (i.e., they each have a distinct element number and are described by a conditions state language). However, they do not have feasible actions and costs associated with them, and are therefore excluded from the preservation modeling. Pontis also supports the concept of sub-elements, which are elements that correspond to a specific CoRe element, sharing the same units, condition state language and feasible actions. Subelements are intended to be used where deterioration patterns or repair costs may vary based on factors such as the type of paint systems in place, element location (e.g., internal vs. external girders), or other characteristics (e.g., the degree of deck/slab substrate repair). Each agency must add and maintain sub-elements as they decide is necessary.
7-7
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
To modify element specifications: 1. Click on the Element Specifications card in the Configuration module.
2. Use the scrollbar at the top right side of the screen to scroll down to the element you wish to edit, and then click on it. Notice that the condition state descriptions for the element will appear in the lower left corner of the card. If you click on one of the condition states, and then use the arrow keys to move among different condition states, the possible actions for the selected condition state will be shown in the lower right corner of the card. 3. Click the Save button to save your changes. To add a new element: 1. To add a new element, click on the Create button. The Create New Element Specification screen will appear. 2. To create a new element not associated with a CoRe element, click on the Create a New Element radio button 3. If you want to create a sub-element associated with an existing CoRe element, select the Inherit from Core Element radio button, and then select the CoRe element from the list. Check off which types of element-level information you want to use for the new element:
7-8
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
The Inherit State Definitions option will copy the condition state definitions from the current CoRe element. The Inherit MR&R Action Definitions option will copy the feasible actions for each condition state from the current CoRe element. The Inherit Elicitation Records option will copy cost and deterioration elicitation records from the current CoRe element. The Inherit Model Records option will copy the preservation deterioration and cost model information and the optimization model results from the current CoRe element.. Click More to enter a custom element number and element key value.
4 5
Click OK to create the new element. Edit information in the element, condition state, and action sections of the card. See the reference help for this screen in the application help (F1) for an explanation of each of the items. If you have added a sub-element, then you need only edit the names, and skip to step 11. To add new condition states for the currently selected element, click on the condition states list, and then click on the Add State button. To view the long description of the currently selected condition state, click on the pencil icon next to the condition state. To add new actions for the currently selected element and condition state, click on the actions list, and then click on the Add Action button. Click the Save button to save your changes.
6 7 8 9
10 To add new cost and deterioration elicitation records for any new elements that you have added (not necessary if you have added a sub-element), select the Add Deterioration Elicitation Records and/or Add Cost Elicitation Records buttons. You will be given the option of adding elicitation records for each user in the system.
7-9
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
11 The Calculate Failure Costs button provides an optional method for specifying the failure costs of the current element. Selecting this button calculates failure costs as the product of the element Weighting Factor (reflecting its relative importance) and the cost of the most expensive action that can be taken for the element (typically replacement). 12 If you are using the NBI Translator to calculate NBI ratings from Pontis element conditions ratings, and you would like the new element that you have added to be reflected in this procedure, see the Technical Manual for information about the files used by the NBI Translator, and what modifications to these files may be required. To delete an element: 1. Make sure that you have the necessary privileges to remove an element, and be aware that this will have far-reaching effects throughout the Pontis database. 2. Click on the Element Specifications card in the Configuration module. 3. Click on an element on the top of the screen, and use the arrow keys to scroll down to the one you wish to delete. 4. Click on the Delete button. This deletes all information related to the current element (including elicitation records, inspection information, action information, etc.) To track down missing or invalid element data: 1. Click on the Element Specifications card in the Configuration module. 2. Click on the Verify button or select Tools-Element Diagnostics from the menu. A detailed file listing all elements, condition states, actions, and MR&R model information will be produced and stored in USR\ELEMDIAG.LOG. This file will contain messages about missing or invalid data. 3. Using any text editor (such as Notepad), review the element diagnostics report.
Important Note: Note that adding a new element in the Configuration module does not update the ELEMENTS.PRN file, which is used by the NBI Translator to generate NBI condition ratings from element condition ratings. You will need to manually edit this file to synchronize with the Pontis element definitions.
7-10
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
7.5 Viewing and Modifying Environment, Materials and Element Classification Definitions (Version 4.5)
The Definitions card of the Configuration module maintains the codes and associated meanings of the following: Environments; Element Types; Element Materials; and Element Categories.
Caution: These definitions are used throughout the system, and should only be modified with extreme care. It is strongly advised that a backup of the database be performed prior to making any changes.
To view or modify the definitions of environments, element types, materials and categories: 1. Click on the Definitions card in the Configuration module. There are separate sections for environments, element types, element materials and element categories. Each section includes codes, names, and positions (which can be used in user-defined reports for special sort orders). The element type section also designates which element category each type belongs to.
7-11
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
Definitions Card
2. In the appropriate section of the card, click on the name or category (for element types) column. 3. Enter your edits. 4. Click the Save button to save your changes.
7-12
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
considered for each element condition state. On that card, each action is assigned an Action Type. The Action card is used to view and modify the list of Action Types in Pontis, and to group Action Types according to more general Action Categories. (Action Categories are defined on the Parameters card, for the database column actypdfs.atypcat.) Modifications to action types should only be made with caution. They are used as building blocks of Flexible Actions (see the next section on Modifying Flexible Action Definitions), and for development of scenario rules in the Programming module. Therefore, any changes to action types will require that any dependent Flexible Actions or rules be modified. To view and modify Pontis Action Types: 1. Click on the Actions card in the Configuration module. You will see a list of the different Action Types in the system. 2. Select the Action Type you wish to edit, and then modify the entries for that row. See the reference help for this screen for descriptions of the different items. 3. Click the Save button to save your changes.
7-13
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
To add a new flexible action, click on the Add Flex Action button, and then follow the instructions below to enter information for it. To modify a Flexible Action: 1. Select the Flexible Action you wish to modify on the list on the top half of the screen. The rules associated with that Flexible Action will be listed on the bottom half of the screen. 2. Edit the Name, Description, Impact and Affected States for the Flexible Action. The Name is what appears on the picklists in the Inspection and Project Planning modules. For Impact, you can select: As Is, which means that the action will maintain the elements in their existing state; Use Transition Probabilities, which uses the deterioration models which are set up for the individual elements included in the Flexible Action, or a particular condition state that you want the Affected States to move into as a result of the Flexible Action.
For Affected States, you can select: An individual condition state (From_State 5 means that only condition state 5 is affected for the elements included in the Flexible Action.) The worst set of 1, 2, 3, 4, or 5 states (Last_State 2 means that only the two worst condition states are affected for the elements included in the Flexible Action.) A specific range of condition states (Range: 2-5 means that only conditions states 2-5 are affected for the elements included in the Flexible Action.)
7-14
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
To modify the rules for a selected Flexible Action: 1. To eliminate a rule, select it and click the Delete Rule button.
2. To add a new rule, click the Add Rule button, or select a rule similar to the one youd like to add, and click the Copy Rule button to duplicate it. 3. For each rule, you must select an Element and an Action Type. You can enter notes about the rule by clicking on the pencil icon on the left side of the row. To delete a Flexible Action, click on the Delete Flex Action button. Use caution in deleting Flexible Actions, since this will affect any inspector work candidates or project work items which were based on that action. When you have completed your modifications, click the OK button to save your changes, and then click the Close button to close the Maintain Flexible Actions window.
7-15
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
Options Card
2. Use the arrow keys to navigate to the appropriate Option Name. 3. Edit the Option Value. 4. Click the Save button to save your changes. To restore all configuration options to their default values, click on the Restore Defaults button. The different configuration options are described in the Technical Manual.
7-16
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
2. To enter a new cost index, click on the Add Index button. A blank row will appear. 3. To modify information for an existing entry, click on it. 4. Enter/update the Effective Date and Value.
7-17
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
5. Click on the Save button to save your changes. To delete a row from the cost index table, click on it, and then click on the Delete Index button. This will remove the current row only.
7-18
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
Trigger Fields
Trigger fields allow users to control the execution of formulas at the level of individual bridges or projects. Normally, they are turned on, which causes the formulas to be calculated whenever Run Formulas is selected. However, if you want to freeze the data in a record so that the formulas cannot modify valid data, the trigger field should be turned off. In this case, the formula is triggered only if the field has a missing (unknown) value.
Inspection module.
The trigger field for the bridge table is located on the Inventory - Classification card within the It is a checkbox labeled Formulas Trigger.
Example: missing roadway speed. Since speed is not an NBI data item, many states will not have data for it. There is a formula in the system to estimate roadway speed from the functional class. If the roadway trigger field is turned on, this formula is re-calculated when Run Formulas is selected to reflect changes in either the speed formula, or in the functional class. If the user has field-checked the speed, then he should click off the roadway trigger field. In this case, the speed remains as-is even if the speed formula or functional class are later modified.
7-19
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
Formulas Card
To add new formulas to a formula set, or edit existing formulas: 1. Select a formula set from the Formula Set picklist at the top of the screen. 2. Click on the New button if you are adding a new formula. To edit an existing formula, select it with the mouse, and then click on the Edit button. 3. The Formula Maintenance window will appear. Position the cursor in the formula area to revise the text as required.
Note: It is a good practice to comment formulas using the ! comment convention from release 2 or the new comment convention of /* comment */. Comments will make debugging problems easier and ensure good communication between different Pontis users sharing the formula table. Use CTRL-ENTER to go to a new line and add blank lines for clarity in the formula text area.
4. To select a field to use in your formula, click on the Fields button. The Select Formula Fields screen will open, listing all of the tables and fields which can be used within formulas. Formulas utilize Pontis unique field names (so there is no need for both a table and column name). Both the unique field name and the actual column name are shown. To transfer a unique field name to the current cursor location in the formula text or to the result or trigger fields, select a table on the left, and click on the field on the right. Click on the Paste button. The selected field will be inserted into the formula. Click the Close button to close the window.
AASHTO Pontis Users Manual 7-20
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
5. When you have finished entering your formula, click the OK button on the Formula Maintenance window. 6. Click the Verify Formula button to check the syntax of the formula. If the message The Formula Verification run was cancelled appears, errors were found in the formula. Any errors will be displayed in the text box at the bottom of the Formulas tab. If errors were found, repeat the previous steps to correct the formula and verify it again. To delete a formula, select it and click on the Delete button. Choose the Run Formulas button to execute the formulas in the currently selected set.
7-21
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
Administrative pages can be accessed from the task bar menu under Admin tab. The task bar menu has links to the pages as tasks and some tasks may have sub-tasks under it. You should use the tab and task bar menu to navigate to the required page. The following is an outline of the Admin tab:
7-22
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
The Admin tab has fourteen tasks. The Security task allows you to register Pontis users and establish privileges for different operations, as well as restrict the bridges with which each user can work. It also lets you administer database connections. The Parameters task allows you to customize picklists of values for different data items. The Element Spec task allows you to define new structure elements, or edit information about existing elements. The Definitions task allows you to view and edit information about the definition of environments, element materials, element categories, and element types. The Actions task allows you to view and edit information about different types of work. It allows you to supplement the standard set of actions with additional actions (which are necessary to support the new Scoping and Painting simulation rules). It also lets you define Flexible Actions, which are sets of action/element combinations along with rules for how the Pontis simulation should model resultant changes in conditions (Flexible Actions should be set up to support the new Major Rehabilitation simulation rules). The Options task allows you to set values for a wide range of parameters which control how the application and database operate. The Cost Index task allows you to enter new values for the Construction cost index, which is used to inflate unit costs for actions to the current year. The Formulas task allows you to create formulas for modifying data in your Pontis database in order to fill in missing values. The Export Options task allows you to configure the options available on the Export task under the Gateway tab. The Data Dict task allows you to edit the entries in the Pontis data dictionary table. The Checked Out Bridges task allows you to remove the checked out status of bridges. The Renumber Brkey task allows you to renumber the brkey of the existing bridges in the database. The Logging task allows you to configure application logger settings and also lets you download and view current application log file. The Navigation & Field Security task allows you to set the role based field level security for the bridge inspection. You can also use this task to apply navigational security independent of the user roles. It also lets you create custom agency inspection and noninspection pages.
7-23
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
Caution: Before undertaking any customization, see the Technical Manual for an in-depth discussion of customization and configuration procedures, and how different options affect the database, the application, and the models. Most of the procedures described in this chapter should only be performed by a system administrator who understands what the impacts of the changes they are making will be, and can take steps to recover from unintended loss or modification to information. In an enterprise environment, you should make sure that the Pontis 5.1.2 web server is shut down and that no users are connected while you are performing the operations described in this chapter. You should inform users well in advance regarding your Pontis 5.1.2 maintenance schedule.
7-24
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
Note that the System Administrator will need to assign each user a password and user id, set up the authentication and set up the Pontis database connection profile before they will be able to use Pontis. To set up the new users or change information for existing users: 1. Click on the Users sub-task under Admin\Security task. 2. To enter a new user, click Add New User link on the Users task screen. A new user screen will be presented with some blank fields. You must enter a new unique User ID on the new user screen. 3. The new user screen will set a default password to be password. You can assign a different password by entering the password of your choice. You can also use the Reset Password button to reset the password back to password. 4. The create new user screen has following required fields: a. First Name b. Last Name c. Agency You may leave the other fields empty. When you save a new user to the database Pontis will warn you about fields that you left empty. 5. You can the select appropriate groups for your new user. Pontis is shipped with one group named Default. You can create new groups from the groups task screen as described later in the section. This feature allows you to organize your users in to the different groups so that
7-25
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
they can be assigned different group filters to each user. This enables you to enforce different bridge access policies for your users.
6. You can select appropriate application role for your new user. Pontis 5.1.2 is shipped with four roles in the sample database. a. Default b. Basic c. Advance d. Admin Pontis will automatically assign the Default role to each new user. This is a very important aspect of new role based security implemented in Pontis 5.1.2. You can modify the role membership by clicking Edit under the User Roles header. 7. To modify the information for an existing user, select the appropriate user from the Select Existing Users dropdown list. 8. Enter or edit information about the user. The User ID of the existing user is not editable once the user is created. 9. You can click the Delete User button to delete a user from the Pontis 5.1.2 system. Deleting a user will not remove the user from the system but it will mark it inactive.
7-26
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
10. You can use the Groups task to create a new group or modify the existing groups. You can assign Access Filters for each group. The filters assigned to the selected group are listed under Group Bridge Access Filters. This list can be modified by clicking the Edit button. The edit filters form lists all the shared user filters that have a group access attribute. 11. You can use the user list boxes to move users in and out of the different groups.. The user must be a member of at least one group, and there is no maximum. In other words, you will not be able to remove a user from a group if he is not a member of any other groups.
12. The Roles task allows you to add new roles, add users to the role, delete a role, and edit existing roles.
7-27
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
13. You can use the arrows between the list boxes to move users in and out of a role. Users must be a member of at least one role and there is no maximum.
7-28
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
14. The Permissions Task Screen lists all of the permissions used by Pontis along with the roles that have the given permission granted. To modify the permission, click the Modify Role Permissions button.
15. You can assign the Inspector check box to grant a user Inspector rights. Granting this permission will cause that user to be displayed in the Inspector and Next Inspector pick lists on the inspection schedule page. 16. You can assign the Modify CoRe Element check box to grant a user the privilege to modify coRe elements on the Element Specification task screen. If the user does not have this permission then the Element Specification task screen will display element definitions as read only if the element is a coRe element. 17. Click the Save button to save your changes and remain on the page, or Save & Close to save your changes and return the the Permissions Task Screen. 18. Click the Cancel button to revert your changes to the default values and return to the Permisions Task Screen.
7-29
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
Pontis 5.1.2 is developed to support three different types of databases: Microsoft SQL Server 2005 and 2008, including the Express version Oracle 10g and 11g, including the Express version
The Databases task under the Admin tab can be used to set up the database connection profile for Pontis. It also allows you to configure authentication mode for your Pontis implementation. Before using this screen, you have to make sure that ODBC connection profile is created on your machine for your database. Please refer to the Pontis Installation Guide and the Pontis Technical Manual for detailed discussion on database profiles and authentication methods. This section explains the features available on this task screen.
7-30
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
Important Note: The database configuration can also be accessed without logging in to Pontis 5.1.2. This can be done by using a special login account that Pontis 5.1.2 will honor and it will bring up the Database task screen. Please use the login: .dbadmin and the password: password in order to launch the database screen directly. See the Technical Manual for an in-depth discussion of customization and configuration procedures, and how different options affect the database and the application. Most of the procedures described in this chapter should only be performed by the system administrator who understands what the impacts of the changes they are making will be, and can take steps to recover from unintended loss or modification to the information.
1. You can click the Add new database link to create new database profile. When you select the appropriate vendor, the ODBC Data Source pick list will be populated with profiles specific to that vendor. You can pick an appropriate ODBC profile by pointing to the Pontis 5.1.2 database that you created. 2. Type in a description for your database profile. 3. Select the appropriate authentication method for your application. 4. Pontis will generate a connection string automatically based on your earlier input. You can also use the Edit connection string button to enable the connection string text box and edit it manually. 5.
The Verify Connection button allows you to make sure the connection string is valid and that
the database connection can be established without any errors. 6. You can save your database profile by entering a name in the Save As text box. This name will be available in the Select existing Database pick list once you save your new profile. 7. Click the Apply button to save your changes. 8. Click the Revert button to revert your changes to the default values. 9. You can use the Select existing database pick list to edit the existing database profiles.
Caution: Database configuration should only be performed by a system administrator. It is strongly recommended that agencies should add only one database profile for Pontis 5.1.2 in a production environment. It is also recommended that the database configuration should be done only by logging in to Pontis using the special credentials mentioned earlier. If you make changes to your database profile from Admin\Security\Databases then you must log out of Pontis and restart the web server. As a rule of thumb, if you switch the database for your Pontis system, you should shut down and restart the Pontis 5.1.2 web server. However, it is not recommended to switch the databases in a production environment.
7-31
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
Parameters Screen
5. On the left side of the screen, scroll down to the table/field name combination for the parameter you wish to edit, and click blue triangle for that row. The coding for the selected field will appear on the right side of the screen. If the field is not there, it generally means that there is no picklist for it, or the picklist cannot be customized.
7-32
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
6. To edit the descriptions for the different codes, you can directly enter the text for all the fields. The Short Label is the item that typically appears on pick lists and reports. To edit the Description, either directly edit the text or click on the notes image . 7. To add a new value for the parameter, click the Add New Value button. A blank row will appear. 8. Enter the Value and Short Label. Other items are optional. Make sure that the Value you enter is not already listed for this parameter it must be unique. 9. To remove a value from the list, click the trashcan image 10. Click the Save button to save your changes. To add a new parameter: 1. Click on the Parameters task on the menu under Admin tab. 2. Enter the table and field name for your parameter and click on the Add New Parameter button. 3. A new row for this table and field will be added to the parameter list. 4. Use the Add Value button (described above) to add a set of values for the new parameter. 5. Click the Save button to save your changes. If you want to delete a parameter, it is strongly recommended that you backup the parameters table first. To delete a parameter, click the trashcan image for that row. You will be asked to confirm the deletion. If you confirm by clicking OK, the parameter and all of its values will be removed from the database. Note that this only affects the picklists and display of information it does not affect the actual values stored in the field that the parameter was for. for that row.
7-33
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
The standard set of elements in Pontis consists of the National Bridge Elements (NBEs) and smart flags. Use of these elements provides a standard for bridge condition tracking which enables data sharing among states, and provides a basis for a conversion of detailed bridge condition data to NBI condition ratings. Smart flags are also included in the element specifications list. Smart flags allow tracking of distress conditions such as pack rust and deck cracking which are not included in the standard condition state language for national bridge elements because they follow different patterns of deterioration and are measured in a different way. In Pontis, smart flags operate as if they are elements (i.e., they each have a distinct element number and are described by a conditions state language). However, they do not have feasible actions and costs associated with them, and are therefore excluded from the preservation modeling. Pontis also supports the concept of sub-elements, which are elements that correspond to a specific NBE, sharing the same units, condition state language and feasible actions. Sub-elements are intended to be used where deterioration patterns or repair costs may vary based on factors such as the type of paint systems in place, element location (e.g., internal vs. external girders), or other characteristics (e.g., the degree of deck/slab substrate repair). Each agency must add and maintain sub-elements as they deem necessary.
7-34
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
To modify element specifications: 1. Click on the Element Specifications task under the Admin tab.
2. Use the scrollbar at the top right side of the screen to scroll down to the element you wish to edit, and then click on it. Notice that the condition state descriptions for the element will appear in the lower left corner of the screen. If you click on for one of the condition states, then the possible actions for the selected condition state will be shown in the lower right corner of the screen. 3. Click the Save button to save your changes. To add a new element: 1. To add a new element, click on the Create Element button. The Create New Element Specification screen will appear.
7-35
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
2. To create a new element click on the Create a New Element radio button Click More to enter a custom element number and element key value.
To delete an element: 1. Make sure that you have the necessary privileges to remove an element, and be aware that this will have far-reaching effects throughout the Pontis database. 2. Click on the Element Specifications task under the Admin tab. 3. Click on an element on the top of the screen, and use the arrow keys to scroll down to the one you wish to delete. 4. Click on the trashcan image . This deletes all information related to the current element (including elicitation records, inspection information, action information, etc.) To track down missing or invalid element data: 1. Click on the Element Specifications task under the Admin tab. 2. Click on the Verify button.
7-36
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
A detailed file listing all elements, condition states, actions, and MR&R model information will be produced and presented to the user to download. The user can either open or save the diagnostic report file on their computer. This file will contain messages about missing or invalid data. 3. Using any text editor (such as Notepad), review the element diagnostics report.
Important Note: The old ELEMENTS.PRN file is now represented by a new PON_CTRL_ELEMENTS database table in Pontis 5.1.2. Note that adding a new element from the Element Specification task under the Admin tab does not update the PON_CTRL_ELEMENTS database table, which is used by the NBI Translator to generate NBI condition ratings from element condition ratings. You will need to perform the database update operation to edit this table outside Pontis 5.1.2 and synchronize it with the Pontis element definitions.
7.15 Viewing and Modifying Environment, Materials and Element Classification Definitions (Version 5.1.2)
The Definitions task of the Admin tab maintains the codes and associated meanings of the following: Environments; Element Types; Element Materials; and
7-37
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
Element Categories.
Caution: These definitions are used throughout the system, and should only be modified with extreme care. It is strongly advised that a backup of the database be performed prior to making any changes.
To view or modify the definitions of environments, element types, materials and categories: 1. Click on the Definitions task under the Admin tab. There are separate sections for environments, element types, element materials and element categories. Each section includes codes, names, and positions (which can be used in user-defined reports for special sort orders). The element type section also designates which element category each type belongs to.
Definitions Screen
2. In the appropriate section of the screen, click on the name or category (for element types) column. 3. Enter your changes. 4. Click the Save button to save your changes.
7-38
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
To view and modify Pontis Action Types: 1. Click on the Actions task under the Admin tab. You will see a list of the different Action Types in the system. 2. Select the Action Type you wish to edit, and then modify the entries for that row. See the reference help for this screen for descriptions of the different items. 3. Click the Save button to save your changes.
7-39
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
To add a new flexible action, click on the Add button. Follow the instructions below to enter information for it. To modify a Flexible Action: 1. Select the Flexible Action you wish to modify on the list on the top half of the screen. Edit the Name and Description, for the Flexible Action. The Name is what appears on the pick lists in the Inspection and Project Planning modules. To Modify a Flexible Action: To delete a Flexible Action, click on the trashcan image for that row. Use caution in deleting Flexible Actions, since this will affect any inspector work candidates or project work items which were based on that action. When you have completed your modifications, click the Save button to save your changes.
7-40
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
Options Screen
4. Click the Save button to save your changes. To restore all configuration options to their default values, click on the Restore Defaults button. The different configuration options are described in the Technical Manual.
7-41
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
2. To enter a new cost index, type in an Effective Date or select it from calendar popup window by clicking image. Enter the cost Value in the text box. Click on the Add New button to add the new cost index. 3. You can directly modify information for an existing entry. 4. Click on the Save button to save your changes.
7-42
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
To delete a row from the cost index table, click on the trashcan
7-43
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
Trigger Fields
Trigger fields allow users to control the execution of formulas at the level of individual bridges or projects. Normally, they are turned on, which causes the formulas to be calculated whenever Run Formulas is selected. However, if you want to freeze the data in a record so that the formulas cannot modify valid data, the trigger field should be turned off. In this case, the formula is triggered only if the field has a missing (unknown) value. The trigger field for the bridge table is located on the Inventory - Admin sub-task within the Inspection tab. It is a checkbox labeled Formulas Trigger.
Example: missing roadway speed. Since speed is not an NBI data item, many states will not have data for it. There is a formula in the system to estimate roadway speed from the functional class. If the roadway trigger field is turned on, this formula is re-calculated when Run Formulas is selected to reflect changes in either the speed formula, or in the functional class. If the user has field-checked the speed, then he should click off the roadway trigger field. In this case, the speed remains as-is even if the speed formula or the functional class is later modified.
7-44
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
To add new formulas to a formula set, or edit existing formulas: 1. Select a formula set from the Formula Set picklist at the top of the screen. 2. Click on the New Formula button if you are adding a new formula. To edit an existing formula, click image to select the row.
7-45
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
3. The Formula Maintenance window will appear. Position the cursor in the formula area to revise the text as required. 4. To select a field to use in your formula, click on the Fields button. The Select Formula Fields screen will open, listing all of the tables and fields which can be used within formulas. Formulas utilize Pontis unique field names (so there is no need for both a table and column name). Both the unique field name and the actual column name are shown. Select a row by clicking image for the required DB Column Name and hit OK button. A unique field name will be now available to paste and Fields window will be closed. Use right button click with cursor being in the formula text or trigger field or results field at desired location and click Paste. Alternatively, use CTRL+V keyboard keys to paste the unique name at desired location. Click the Cancel button to close the window. 5. When you have finished entering your formula, click the OK button on the Formula Maintenance window. 6. Click the Verify Formula button to check the syntax of the formula. If the message The Formula Verification run was cancelled appears, errors were found in the formula. Any errors will be displayed in the text box at the bottom of the Formulas box on the screen. If errors were found, repeat the previous steps to correct the formula and verify it again. 7. Click Save button to save changes. To delete a formula, click the trashcan image on the formula row.
Choose the Run Formulas button to execute the formulas in the currently selected set.
7-46
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
There are six standard export options listed with name starting with <01> - <06> in the Export Data picklist. Each standard export option has pre-defined tables pertaining to that option. You can customize these options by adding the new tables to their lists. You can not delete the table names that are part of the standard list, however, you can use the check box for each standard Table Name row to include or exclude that table from that standard option. You can delete the new tables that you may have added to the standard options. This screen also enables you to create a completely customized export option by selecting <07>
Custom Table List, which can contain only the tables of your choice.
7-47
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
The options beginning with <99> Just Table are single table options; they are dedicated to a predefined single table. You can neither delete the table from these options nor add a new table to them. To customize the export options: 1. Use Export Data pick list to select the option. 2. To add a new table to the option, select a new table from the picklist on the right of the Add Table button and click the Add Table button. 3. You can uncheck or check the check box under the Include column, to include or exclude a table from that option. 4. The grayed trashcan image 5. Click trashcan image indicates that you are not allowed to delete that row.
if you want to remove the table you have added to the option.
7-48
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
Caution: The data dictionary data is used throughout the system, and should only be modified with extreme care. It is strongly advised that a backup of the database be performed prior to making any changes.
The Select Table Name group box on the left of this task screen provides the list of table names. When you select an item in the table name group box, the right side of the screen will display data pertaining to that table name. The Select a Column Name pick list on the top right of the screen is populated with the column names of the table name that you selected on the left. The Edit Details group box displays the data from the record in the DATADICT database table that you can modify.
To Modify Data Dictionary Data: 1. Select a table name from the left Select Table Name list box. 2. Select a column name from the Select a Column Name pick list located on the top-right of the screen. 3. Edit the data under Edit Details group box. 4. Click the Save button to save your changes.
7-49
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
Caution: It is recommended that only the person who has appropriate privileges as well as the functional knowledge of how the CICOCNTL table is used should perform this operation. Inappropriate modifications made to the CICOCNTL table can have a system wide adverse effect, such as the data exchange operations under the Gateway module not functioning correctly, which could result in loss of data or unwanted modifications to your database.
1. Navigate to the Admin\Checked Out Bridge task screen. 2. Check the check boxes for the rows you want to delete. 3. Check the check box in the first column of the grid header to select all the rows. 4. Click the Remove button to remove the selected rows. 5. Click the Close button to return to the bridge list.
7-50
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
Caution: This operation should be performed with extreme care. This is a far reaching database operation since it could affect numerous tables in the database. You may have to perform additional steps if your database contains unregistered custom tables with a dependency on the Bridge Brkey. Please consult with your database administrator before performing this operation. This operation could result in unwanted modifications to your database and make your system unstable.
To renumber a Brkey: 1. Navigate to the Admin\Renumber Brkey task screen. 2. Select the Brkey you want to change from the Change Brkey From pick list 3. Enter a new Brkey in the To New Brkey text box. 4. Click the Renumber Brkey button to perform the operation.
7-51
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
To modify the logger settings: 1. Navigate to the Admin\Logging task screen. 2. Check the Turn Logging ON check box to turn on or off the logging. 3. Click the appropriate logging level check box under Logging Levels group box. The level of verbosity increases from Fatal to Debug. If you select the Warn level then Pontis will also log all the messages up to that level. In other words, Error and Fatal messages will also be logged. However, Debug and Information message will not be logged. If you select the Debug level, then Pontis will log the message from all the lower levels as well. 4. Enter desired number to control the count of archived log files. 5. Click View Log File button to download and view the current log file. 6. Click Apply to apply your changes.
7-52
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
To modify Standard/Agency Navigational Object Properties: 1. Navigate to the Admin\Navigation & Field Security\Standard task screen.
7-53
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
3. Select the appropriate navigational object from Object Group Box. 4. Select the appropriate Parent item from the pick list under Select Group Box.
5. Select an object item from the selection list box on the left. This selection box will list the items pertaining to the parent object selected under Select Group Box. 6. Edit the data in the Properties group box on the right. 7. Click the Save button to save your changes. 8. Click the Admin\Navigation & Field Security\Agency sub-task and follow steps 2 through 6 to modify Agency Navigational Object Properties.
To apply Standard/Agency Role-Based Security 1. Navigate to the Admin\Navigation & Field Security\Standard task screen.
7-54
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
2. Select the appropriate Object type and select the parent object. 3. Select a role from the list box on the left of the screen. 4. The security Group Box on the right of the screen will show the object items of the parent object that you selected in step 2. 5. Check or Uncheck Visible and/or Read Only check boxes for all the objects for that role. 6. You can click different roles and check or uncheck the Visible and Read Only check boxes to configure the security for that role for each object. 7. Navigate to the Admin\Navigation & Field Security\Agency sub-task screen to apply the role-based security to agency items by following steps 2 through 6.
7-55
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
To Add New Navigational Objects The following section describes how you can add a new task to Pontis 5.1.2.
1. Navigate to the Admin\Navigation & Field Security\Agency task screen 2. Select the Navigation radio button under the Type group box.
Adding Custom Navigational Object Task Screen 3. Select the type of object you want to add by clicking the corresponding radio button under
Object group box.
4. From Add New group box, you should enter the name for your object and optionally select a
you just added in the selection list on the left. The corresponding properties will be displayed under the group box on the right of the screen.
6. Edit the object properties under the group box on the right of the screen. 7. Click the Save button to save your changes to the database. 8. You can follow steps 1 through 7 to create any of the four objects. Group and Control objects
may offer more properties to edit compared to the Tab and Task objects.
7-56
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
Note:
Please refer to the Pontis 5.1.2 Technical Manual for in-depth discussions on how to apply navigational security and role-based security and for information on creating the basic agency task screens and complex agency task screens.
7-57
C O N F I G U R I N G
A N D
C U S T O M I Z I N G
P O N T I S
config001_elem_states_actions shows the specifications for a selected set of elements. Options are provided for printing this report for all elements or for selected element numbers, types, or categories. For each element, all of the information on the Element Specifications card is shown, including all of the possible condition states (and the associated condition state language), and the actions for each condition state. config002_config_options_list is an alphabetical listing of all of the configurable options, from the Options card. Default values, current values and descriptions are shown for each option.
Parameters card in order to customize picklists.
config003_parameter_report is a list of all of the parameters that can be modified on the It is organized by table and field name.
config004_data_dictionary is a data dictionary for the Pontis database, providing information for each column including names, widths, types and descriptions. It can be printed for all tables, or a selected set of tables. config005_ini_file_report allows you to view the contents of the Pontis INI file, as well as other INI files that are examined by the Pontis software. config006_user_list displays information about each user on the User Administration card. config007_misc_sys_param includes information from the Definitions and Actions cards lists of environments, element materials, element categories, and action types config008_flex_actions displays information on flexible actions defined on the Actions card. It shows each flexible action that has been created, along with the associated impacts and included element actions.
Version 5.1.2 only
config009_ui_navigation displays information about navigational security defined on the Navigation and Field Security task screen. It shows tab, task, group and controls properties for selected tab. Object properties also display navigational security settings. config010_app_security displays information about Pontis 5.1.2 role-based security defined on the Navigation & Field Security task.. It shows visible and read only settings for all the tabs, tasks, groups and controls for selected role. You can generate this report to audit Pontis 5.1.2 application wide security for each role.
7-58
Wed like to know how Pontis can be customized for our particular needs. Can we add our own inspection screens? Can we add our own non-inspection screens? Can we configure the inspection module so that users can only perform the operations they are authorized to perform?
ontis release 5.1.2 enables agencies to create new custom screens and integrate them with the standard Pontis screens. Agencies can add their own inspection screens by simply using the Pontis 5.1.2 user interface. The Pontis 5.1.2 system also allows you to add new agency tabs to host non-inspection task screens, configure role based security for standard and agency task screens, configure navigational security for standard and agency task screens, and to customize standard Pontis 5.1.2 inspection screens. Before you perform the operations described in this chapter, you should coordinate with your database administrator to find out how you can prepare the database before you add new screens to the Pontis 5.1.2 system. You should also coordinate with your system administrator to plan the security implementation for the Pontis system. It is important to back up your production database before you carry out the operations described herein. After carefully planning your customization and security implementation, you should implement it on the standalone Pontis 5.1.2 system before applying your changes to the production server. The Pontis Technical Manual provides detailed information on how to create basic and complex agency task screens. This chapter provides an overview of the operations that can be performed using Navigation and Field Security pages that are accessible under the Pontis 5.1.2 Admin Tab.
8-1
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
8.1
The standard inspection task screens in Pontis 5.1.2 can be customized through the Navigation & Field Security task under the Admin tab. These operations require administrative privileges since the changes have system-wide impact. Pontis 5.1.2 allows the following customizations on standard screens: Modify the captions of the Tab, Task, Group and Control items Modify the Tab and Task tooltips. Make the Tab, Task, Group and Controls visible or invisible. Make the Tab, Task, Groups and Controls editable or read only.
To modify Standard Tab properties: 1. 2. Navigate to Admin\Navigation & Field Security\Standard task screen. Select the Navigation radio button in the Type group box.
8-2
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
3.
4. 5. 6. 7.
Select the Tab from the Tab Name list box on the left of the screen. Modify the Label text box to update the Tab caption. Check or uncheck the Visible check box to make the selected Tab Visible or Invisible respectively. Check or uncheck the Read Only check box to make the selected Tab editable or read only.
Important Note: When a Tab is marked read only, all the tasks under it will be automatically marked read only. When the Task is read only, all the Groups under that task will automatically become read only. Similarly, if the Group is read only then all the controls under that group will automatically become read only. Hence, if you make a Tab read only then it will have a hierarchical effect on the entire module.
8. 9.
Modify the ToolTip text box to update the tab tooltips. Click the Save button to update your changes in to the database.
To modify Standard Task properties: 1. 2. 3. 4. 5. Navigate to Admin\Navigation & Field Security\Standard task screen. Select the Navigation radio button in the Type group box. Select the Tasks radio button from Object group box. The Select group box will display the available tabs in the drop down list. You can pick the desired tab under Select group box to retrieve the corresponding Tasks. Select the Task from the list box on the left of the screen.
8-3
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
6. 7. 8.
Modify the Label text box to update the Task caption. Check or uncheck the Visible check box to make the selected Task Visible or Invisible respectively. Check or uncheck the Read Only check box to make the selected Task editable or read only.
Important Note: When the Task is made read only, all the Groups under that task will be automatically made read only. When the Group is read only, all the controls under that group will be automatically made read only. Hence, if you make a Task read only then it will have hierarchical effect and will make the entire task screen read only. Read only tasks may still allow you to browse the data but you will not be able to edit the data or perform any operations.
9. 10.
Modify the ToolTip text box to update the Task tooltip. Click the Save to update your changes in to the database.
To modify Standard Group properties: 1. 2. 3. 4. Navigate to the Admin\Navigation & Field Security\Standard task screen. Select the Navigation radio button in the Type group box. Select the Groups radio button from Object group box. The Select group box will display the available Tabs and Tasks drop down list. You can pick the desired tab and then desired task under Select group box to retrieve the corresponding Groups. Select the Group from the Group Name list box on the left of the screen. Modify the Label text box to update the Group caption. Check or uncheck the Visible check box to make the selected Group Visible or Invisible respectively. Check or uncheck the Read Only check box to make the selected Group editable or read only.
Important Note: When the Group is marked read only, all the controls under that group will be automatically marked read only. The Standard Pontis 5.1.2 inspection screens also have several complex controls that represent data from the multiple rows in the database. These complex controls also have their own groups. The complex control will be read only when the group representing such composite control is marked read only.
5. 6. 7. 8.
8-4
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
9.
To modify Standard Inspection Control properties: 1. 2. 3. Navigate to the Admin\Navigation & Field Security\Standard task screen. Select the Navigation radio button in the Type group box. Select the Controls radio button from the Object group box.
4.
The Select group box will display the available Tab, Task and Group drop down list. You can pick the desired tab and task and then desired group under the Select group box to retrieve the associated Controls. Select the Control from the Control Name list box on the left of the screen. Modify the Label text box to update the Control caption. Check or uncheck the Visible check box to make the selected Control Visible or Invisible respectively. Check or uncheck the Read Only check box to make the selected Control editable or read only. Click the Save to update your changes in to the database.
5. 6. 7. 8. 9.
Important Note:
The Tooltips on the standard inspection controls are generated automatically by the Pontis 5.1.2 system. The tooltip on the inspection task screen controls represent the field descriptions from DATADICT table. Hence, these tooltips are not editable by the user.
8-5
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
8.2
Pontis 5.1.2 enables users to create custom data entry Task screens. Agencies can also develop complex controls that manipulate multiple rows of data from the database. Developing the agency inspection screens may require you to perform certain database operations as a prerequisite.
Important Note: Please refer to Pontis 5.1.2 Technical Manual for in-depth discussion on how to create basic as well as complex agency task screens that represent inspection or non inspection data.
This section covers the following basic steps involved in creating agency inspection screens: Create a new agency task under the Inspection tab. Create a new group under the agency inspection task screen. Add controls to the agency groups.
To create a new agency task under Standard Inspection Tab: The Pontis 5.1.2 system offers two ways to represent the agency inspections task screens as shown in the following two screen captures:
8-6
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
A.
To add an Agency inspection task as a Root inspection task: 1. Navigate to the Admin\Navigation & Field Security\Agency task screen. 2. Select the Navigation radio button in the Type group box. 3. Select the Tasks radio button from Object group box. 4. Select Inspection on the Tab dropdown list under Select group box. 5. Select None on the Parent Task dropdown list under Add New Task group box. 6. Enter a name for your task in the Task Name text box. 7. Click the Add New button.
8-7
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
8. Click the Save button to store the new task into the database.
B.
To add an Agency inspection task as a Sibling of the existing standard inspection sub- tasks: 1. Navigate to the Admin\Navigation & Field Security\Agency task screen. 2. Select the Navigation radio button in the Type group box. 3. Select the Tasks radio button from the Object group box. 4. Select Inspection from the Tab dropdown list under the Select group box 5. Select Inventory or Work from the Parent Task dropdown list under the Add New Task group box. 6. Enter a name for your task in the Task Name text box. 7. Click the Add New button.
8-8
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
8. Click the Save button to store the new task in the database.
To create a new group on the agency task screen: 1. Navigate to the Admin\Navigation & Field Security\Agency task screen. 2. Select the Navigation radio button in the Type group box. 3. Select the Groups radio button from the Object group box. 4. Select the agency task to which you want to add your group from the Task dropdown list under the Select group box. 5. Set the Parent Group to be None on the Parent Group dropdown list (under the Add New Group box) if you want your group to be the root group. If you already have groups added then you could select any of them to be the parent of your new group. If you select the parent for your new group then the new group would be displayed within the parent group box on your new agency task screen.
6. Enter the name for your new group in the Add New Group box.
8-9
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
7. Select an appropriate Group Type for your group. Pontis 5.1.2 will automatically organize the task screen content based three group types as follows: a.
Inspection Header Group: Select this group type if you have controls that you would like to be on top of the task screen. The following image illustrates the inspection header on the standard Appraisal task screen:
b.
Content Group: Select this group type if you want to add controls to the center of the
task screen. In other words, below the inspection header and above the inspection footer (see below). The following image illustrates the inspection content groups on the standard Appraisal task screen.
8-10
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
c.
Inspection Footer Group: Select this group type if you have controls that you would like
to be on the bottom of the task screen. The following image illustrates the inspection footer group on the standard Appraisal task screen.
d.
Eng_Metric Selection Group: Select this group if you would like to place a English-
8-11
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
1. Select None in the DeskTop Url dropdown list under the Add New Group box. Please refer to Pontis 5.1.2 Technical Manual for in-depth discussion on when to select the option other than None. 2. Click the Add New button. 3. Click the Save button to update the database. 4. Select your newly created group from the list box in the Group Name group box on the left of the screen. 5. On the right side of the screen you will see the Group Properties box for your selected group on the left. You can modify your group properties and click the Save button to store the changes to the database.
Important Note: You can select the SkinID dropdown list to be None if you want the transparent background for your group box. You can edit the Label text box entry to the name of your choice. If you want your group box to have no grouping text with the border then you should clear the Label text box entry. Please note that your group box will not be displayed on the task screens until you add controls to it. Please refer to Pontis 5.1.2 Technical Manual for in-depth discussion on how to set the group properties for agency task screens.
To add new controls on the agency task screen: 1. Navigate to the Admin\Navigation & Field Security\Agency task screen. 2. Select the Navigation radio button in the Type group box. 3. Select the Controls radio button from the Object group box. 4. Select your agency task on the Task dropdown list under the Select group box. 5. Select your agency group in the Group dropdown list under the Select group box. 6. In the Add New Control group box, enter a name for your control.
8-12
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
7. In the Add New Control group box, select the appropriate Control Type that you are creating. Please refer to the Pontis 5.1.2 Technical Manual for further details about each type of predefined control types.
8. In the Add New Control group box, select the bridge or inspection table name. 9. In the Add New Control group box, select the appropriate column name of the table name that you selected. 10. Click the Add New button. 11. Click the Save button to store changes to the database. 12. Select the control name from the Control Name list box on the left of the screen
8-13
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
13. Update the control properties on the left of the screen. Please refer to the Pontis 5.1.2 Technical Manual for more in-depth details on how to set the control properties. 14. Click the Save button to store the changes to the database.
To delete Tabs, Tasks, Groups and Controls on an agency task screen: 1. Navigate to the Admin\Navigation & Field Security\Agency task screen. 2. Select the Navigation radio button in the Type group box. 3. Select the appropriate radio button from the Object group box. 4. Select the appropriate parent task on the dropdown list under Select group box. 5. Select the Tab, Task, Group or Control on the list box displayed on the left of the screen based on your selections in step 3 and step 4. 6. Click the Delete button to delete the selected item. 7. Click the Delete All button to delete all the items in the list box on the left of the screen. 8. Click the Save button to store the changes to the database.
Important Note:
Tabs , Tasks , Group and Controls are the building blocks of the Pontis 5.1.2 application. The Delete operation effect propagates in a Top-Down hierarchical manner with Tabs at the top level to Controls at the bottom. In other words, if the Tab is deleted then all the Tasks, Groups and Controls under it are automatically deleted. Similarly, if the Group is deleted then all the Sub-Groups and Controls under it are automatically deleted.
8-14
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
8.3
Pontis 5.1.2 enables you to create your own Tabs in addition to the standard Pontis Tabs. This allows agencies to group their new custom Task screens under a separate Tab . These custom task screens may not be inspection related. Pontis 5.1.2 comes with the five standard tabs. NonInspection task screens are those that will reside under the agency tabs. This section describes how to add a new Tab and how to create a new Non-Inspection Task screen under the agency Tab. Non-inspection screens do not require the bridge to be selected before screen can be displayed. Non-inspection task screens will require a new agency tab as their parent. Creating NonInspection screens requires database preparation before the screens are developed and added to Pontis 5.1.2. To create a new agency Tab: 1. Navigate to the Admin\Navigation & Field Security\Agency task screen.
2. Select the Navigation radio button in the Type group box. 3. Select the Tabs radio button from the Object group box. 4. Enter a name for your tab in the Task Name text box in the Add New Tab group box. 5. Click the Add New button.
8-15
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
6. Click the Save button to store the new tab in the database.
7. Modify the properties under the Tab Properties group box on the right side of the screen. 8. Click the Save button to store the changes in the database. To create a new agency Task under an agency Tab:
9. Select the Tasks radio button from Object group box. 10. Select the Task in the Task Name list box on the left of the screen. Please note that a new Task is automatically created when you create a new Tab.
8-16
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
11. Modify the properties of your newly added task. 12. Click the Save button to store the changes in the database.
Important Note:
Please refer to the Pontis 5.1.2 Technical Manual for an in-depth discussion on how to create basic and complex agency task screens that represent the inspection or non inspection data. Also, refer to Section 8.2 of this chapter for details on how to create sub-tasks under a root task and how to add groups and controls on the task screens.
To delete Tabs, Tasks, Groups and Controls on the agency task screen: 1. 2. 3. 4. 5. 6. 7. 8. Navigate to the Admin\Navigation & Field Security\Agency task screen. Select the Navigation radio button in the Type group box. Select the appropriate radio button from the Object group box. Select the appropriate parent from the dropdown list under Select group box. Select a Tab, Task, Group or Control on the list box displayed on the left of the screen based on your selections in step 3 and step 4. Click the Delete button to delete the selected item. Click the Delete All button to delete all the items in the list box on the left of the screen. Click the Save button to store the changes to the database.
Important Note:
The Tabs , Tasks , Group and Controls are the building blocks of the Pontis 5.1.2 application. The Delete operation effect propagates in a Top-Down hierarchical manner from Tabs being at the top level to Controls at the bottom. In other words, if the Tab is deleted then all the Tasks, Groups and Controls under it are automatically deleted. Similarly, if the Group is deleted then all the Sub-Groups and Controls under it are automatically deleted.
8.4
Pontis 5.1.2 allows an agency to enforce the application security depending upon the role of the logged in user. This means that if you have fifty Pontis users in your agency then you do not need
8-17
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
to create set of security settings for each of the fifty Pontis users. You can create logical roles that reflect the business practices and responsibilities of the Pontis users in your agency. Once you create the roles you need, you can create a set of security settings for each role such that the settings will restrict the use of Pontis 5.1.2 for that role. The set of security settings for each role can be called a security profile for that role. You can assign each user an appropriate role so that user will be able to use the Pontis based on the security profile associated with his/her role.
Important Note:
Please refer to the Pontis 5.1.2 User Manual - Chapter 7 and the Pontis 5.1.2 Technical Manual for detail information on how to create Pontis users, how to create user roles, and how to associate users with roles.
This section describes the main steps involved in creating security profiles for your user roles. You should plan your security profiles before you create them. You can represent these security profiles in a spreadsheet that you can maintain and use to track the settings on the production server. The planning typically involves following steps: Identify the Operations that are not allowed for each role. Identify the Controls to edit the data that are not supposed to be visible or supposed to be read-only for each role. Identify the Tabs that are not supposed to be visible or supposed to be read-only for each role. Identify the Task screens under tabs that are not supposed to be visible or supposed to be read-only for each role. Identify the Groups on the task screens that are not supposed to be visible or supposed to be read-only for each role.
Important Note: The Tabs , Tasks , Group and Controls are the building blocks of The Pontis 5.1.2 application. The security settings propagate in Top-Down hierarchical manner from Tabs being at the top level to Controls at the bottom. In other words, if the Tab is marked read only then all the Tasks, Groups and Controls under it are automatically marked read only. Similarly, if the Group is marked read only then all the Controls under it are automatically marked read only.
Pontis 5.1.2 comes with a sample database that has four basic roles and corresponding security profiles that can be used as an example. The following list enumerates the four sample roles in the out of the box sample database: Default
8-18
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
Important Note:
Role Based Security settings override the Navigational Security settings with restrictive rights only when Navigation Security settings are non-restrictive. In other words, if role based security is restrictive and if navigation security is not restrictive then role based security will govern.
To configure role based security for the Standard Tabs: The following steps can also be use for Agency tabs by selecting Agency instead of the Standard sub-task on the task bar menu.
1. Navigate to the Admin\Navigation & Field Security\Standard task screen. 2. Select the Security radio button in the Type group box. 3. Select the Tabs radio button from the Object group box. 4. Select the Role from the Roles list box on the left of the screen. 5. Check or uncheck the Visible check boxes for each tab listed under the Name column in Tab Security group box on the right of the screen.
8-19
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
6. Check or uncheck the Read Only check boxes for each tab listed under the Name column in Tab Security group box on the right of the screen. 7. Click the Save button update your changes in to the database.
To configure role based security for the Standard Tasks: The following steps can also be used for Agency tabs by selecting the Agency instead of the Standard sub-task on the task bar menu. 1. Navigate to the Admin\Navigation & Field Security\Standard task screen. 2. Select the Navigation radio button in the Type group box. 3. Select the Tasks radio button from the Object group box. 4. Select the parent tab on the Tab dropdown list in the Select group box. 5. Select the Role from the Roles list box on the left of the screen. 6. Check or uncheck the Visible check boxes for each task listed under the Name column in the Task Security group box on the right of the screen. 7. Check or uncheck the Read Only check boxes for each task listed under the Name column in the Task Security group box on the right of the screen. 8. Click the Save button update your changes in to the database.
To configure role based security for the Standard Groups: The following steps can also be used for Agency tabs by selecting the Agency instead of the Standard sub-task on the task bar menu.
8-20
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
1. Navigate to the Admin\Navigation & Field Security\Standard task screen. 2. Select the Security radio button in the Type group box. 3. Select the Groups radio button from Object group box. 4. Select the parent tab on the Tab dropdown list in the Select group box. 5. Select the parent task on the Task dropdown list in the Select group box. 6. Select the Role from the Roles list box on the left of the screen. 7. Check or uncheck the Visible check boxes for each group listed under the Name column in the Group Security group box on the right of the screen. 8. Check or uncheck the Read Only check boxes for each group listed under the Name column in the Group Security group box on the right of the screen. 9. Click the Save button update your changes in to the database.
To configure role based security for the Standard Tabs: The following steps can also be use for Agency tabs by selecting the Agency instead of the
Standard sub-task on the task bar menu.
8-21
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
1. Navigate to the Admin\Navigation & Field Security\Standard task screen. 2. Select the Security radio button in the Type group box. 3. Select the Controls radio button from Object group box. 4. Select the parent tab on the Tab dropdown list in the Select group box. 5. Select the parent task on the Task dropdown list in the Select group box. 6. Select the parent group on the Group dropdown list in the Select group box. 7. Select the Role from the Roles list box on the left of the screen. 8. Check or uncheck the Visible check boxes for each group listed under the Name column in Control Security group box on the right of the screen. 9. Check or uncheck the Read Only check boxes for each group listed under the Name column in Control Security group box on the right of the screen. 10. Click the Save button update your changes in to the database.
8.5
Navigational security can be applied to either agency or standard screens. This mainly includes setting the visibility and read only properties of Tabs, Tasks, Groups, and Controls from the Navigation context. These settings enable you to secure the Pontis 5.1.2 user interface from all the Pontis users regardless of their application role.
8-22
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
Navigation security also allows you to globally customize Pontis 5.1.2 as per your agency needs. For example, if your agency does not use one of the standard Pontis 5.1.2 inspection fields then you could mark that particular field invisible. Furthermore, if your agency does not need a certain standard task screen then you could make that task screen invisible.
Important Note: Navigational Security settings override the role based security with restrictive rights. In other words, if role base security is not restrictive and if navigation security is restrictive then navigational security will govern. If navigational security is non-restrictive then role based security will govern.
While applying navigational security settings, you should plan the granularity at which you need to apply the agency wide restrictions on the use of Pontis 5.1.2. The following are some examples of the typical questions you should consider while planning navigational security settings: Do I need to restrict the use of one control on certain inspection task screen or several controls? In my agency, we do not need Snooper hours, Special Crew Hours, Special Equip. Hours fields displayed on Inspection\Schedule task screen. Can I just make the whole group read only instead of making all three controls read only within that sub-group one by one? In my agency, we do not need all the controls on the Inspection\Work\Project Information editable. Can I just make the whole Inspection\Work\Project Information task screen read only instead of making all Groups or all the Controls under it read only?
Caution:
Modification to Navigation Security settings have a system wide impact and can affect the whole Pontis System as well as users. This operation requires administrative privileges. These settings should only be performed by an individual who has functional knowledge of Pontis 5.1.2 security architecture and the related database structure. You should back up your database and try different settings in conjunction with the role based security profiles that you may have on your Pontis 5.1.2 system before applying them to the production server.
To make a Standard Tab Invisible or Read Only: The following steps can also be use for Agency tabs by selecting the Agency instead of the Standard sub-task on the task bar menu.
8-23
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
1. Navigate to the Admin\Navigation & Field Security\Standard task screen. 2. Select the Navigation radio button in the Type group box. 3. Select the Tabs radio button from Object group box. 4. Select the Tab from the Tab Name list box on the left of the screen. 5. Check or uncheck the Visible check box to make the selected Tab Visible or Invisible respectively. 6. Check or uncheck the Read Only check box to make the selected Tab editable or read only. 7. Click the Save button update your changes in to the database.
Important Note:
When a Tab is made read only, all the tasks under it will be automatically made read only. When the Task is read only, all the Groups under that task will be automatically become read only. If the Group is read only then all the controls under that group will be automatically become read only. Hence, if you make a Tab read only then it will have hierarchical effect and it will make the entire module read only.
8-24
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
To make a Standard Task Invisible or Read Only: The following steps can also be followed for Agency tasks by selecting the Agency instead of the
Standard sub-task on the task bar menu.
1. Navigate to the Admin\Navigation & Field Security\Standard task screen. 2. Select the Navigation radio button in the Type group box. 3. Select the Tasks radio button from Object group box. 4. Select the parent tab on the Tab dropdown list in the Select group box. 5. Select the Task from the Task Name list box on the left of the screen. 6. Check or uncheck the Visible check box to make the selected Task Visible or Invisible respectively. 7. Check or uncheck the Read Only check box to make the selected Task editable or read only. 8. Click the Save button update your changes in to the database.
Important Note: When the Task is made read only, all the Groups under that tasks will be automatically made read only. When the Group is read only, all the controls under that group will be automatically made read only. Hence, if you make a Task read only then it will have hierarchical effect and it will make the entire task screen read only. Read only tasks may still allow you to browse the data but you will not be able to edit the data or perform any operations.
8-25
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
To make a Standard Group Invisible or Read Only: The following steps can also be followed for Agency groups by selecting the Agency instead of the Standard sub-task on the task bar menu.
1. Navigate to the Admin\Navigation & Field Security\Standard task screen. 2. Select the Navigation radio button in the Type group box. 3. Select the Groups radio button from Object group box. 4. Select the parent tab on the Tab dropdown list in the Select group box. 5. Select the parent task on the Task dropdown list in the Select group box. 6. Select the Group from the Group Name list box on the left of the screen. 7. Check or uncheck the Visible check box to make the selected Group Visible or Invisible respectively. 8. Check or uncheck the Read Only check box to make the selected Group editable or read only.
Important Note:
When the Group is marked read only, all the controls under that group will be automatically marked read only. The Standard Pontis 5.1.2 inspection screens also have several complex controls that represent data from the multiple rows in the database. These complex controls also have their own groups. The complex control will be read only, when the group representing such composite control is marked read only. For example, Element Condition group under condition task.
8-26
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
To make a Standard Control Invisible or Read Only: The following steps can also be followed for Agency controls by selecting the Agency instead of the Standard sub-task on the task bar menu.
1. Navigate to the Admin\Navigation & Field Security\Standard task screen. 2. Select the Navigation radio button in the Type group box. 3. Select the Controls radio button from Object group box. 4. Select the parent tab on the Tab dropdown list in the Select group box. 5. Select the parent task on the Task dropdown list in the Select group box. 6. Select the parent group on the Group dropdown list in the Select group box. 7. Select the Control from the Control Name list box on the left of the screen. 8. Check or uncheck the Visible check box to make the selected Control Visible or Invisible respectively. 9. Check or uncheck the Read Only check box to make the selected Control editable or read only. 10. Click the Save button to update your changes in to the database.
8-27
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
9 Index
A
Action defined, 6-2 type, 7-13, 7-42 viewing and editing, 7-2, 7-23 Agency bridge ID, 3-8, 3-46 Agency policy rules, 5-12, 5-19, 5-21 navigational security, 8-23 role-based security profiles, 8-18 stamdard inspection control properties, 8-5 standard group properties, 8-4 standard tab properties, 8-2 standard task properties, 8-3 Customizing elements, 7-11, 7-40 overview, 7-2, 7-23 pick lists, 1-14, 1-20
B D
Benefit, 5-2, 5-7 Bridge. See structure Bridge analysis, 6-29 Bridge key, 3-8, 3-46 Budget program, 5-22 scenario, 4-8, 4-13 Data dictionary, 1-16, 7-5, 7-32 DataWindow .NET, 1-9, 3-56, 3-81 DataWindow.NET, 2-19, 39 Design standards, 5-6 Desktop, 2-18 Deterioration models definition, 4-3 deterioration elicitation, 4-4 developing, 4-3 results, 4-17 updating, 4-6 Direct cost, 4-9
C
Cassini, 1-2, 1-9 Check-in/check-out, 3-38, 3-39, 3-79, 3-80 Condition ratings calculating, 3-29, 3-69 entering, 3-20, 3-60 Condition state, 3-3, 4-6, 4-10 Configuration options, 7-16, 7-45 overview, 7-2 CoRe elements, 3-2, 7-7, 7-34 Cost adjusting for inflation, 4-13 agency, 4-9 elicitation, 4-9 failure, 4-9 improvment, 5-7 index, 4-9, 7-2, 7-17, 7-18, 7-23, 7-46, 7-47 user, 4-9 Cost matrix, 5-7, 5-8 Cost models adjusting for inflation, 4-13 developing, 4-9 introduction, 4-9 updating, 4-12 County labels, 1-14, 1-20 Crystal Reports, 1-3, 1-9, 2-19, 39, 3-56, 3-81 Custimizing Agency inspection screens, 8-6 Agency non-inspection screen, 8-15 inspection task screens, 8-2
E
Element adding to a structure, 3-8, 3-46 changing types, structure units or environments, 3-19, 3-59 creating, 3-12, 3-50 definition of, 3-2 deleting, 7-10, 7-39 environment, 3-13, 3-51 ID, 3-13, 3-51 inspect as each option, 3-20, 3-60 invalid or missing data, 7-10 modifying specifications, 7-8, 7-35 quantity, 3-13, 3-51 record trigger, 3-13, 3-51 scale factor, 3-13, 3-51 selecting for inclusion in simulation, 5-27 structure unit, 3-13, 3-51 viewing and modifying definitions, 7-11, 7-40 Elicitation adding records for new elements, 7-4, 7-9, 7-29, 737 cost, 4-9, 4-12 deterioration, 4-2, 4-3 English units, 3-5, 3-43 Environment
I-2
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
definition of, 3-3 viewing and modifying definitions, 7-11, 7-40 Exceptions overriding, 3-39, 3-80 Exporting data NBI, 2-13, 3-36 PDI, 2-13
F
Failure cost, 4-11, 7-10, 7-38 Flexible actions creating, 7-13, 7-43 definition of, 5-13, 6-2, 7-2, 7-23 deleting, 7-15, 7-44 modifying rules, 7-15, 7-44 using, 3-22, 5-15, 5-19, 6-27 Formulas creating, 7-20, 7-49 running, 7-21, 7-51 syntax check, 7-21, 7-51 trigger field, 3-13, 3-51, 7-19, 7-48 Funding source default, 6-11 defining, 6-10
appraisal, 3-5, 3-44 condition, 3-5, 3-44 inventory, 3-5, 3-6, 3-44 notes, 3-5 schedule, 3-6, 3-44 work, 3-5, 3-44 type, 3-14, 3-18, 3-53, 3-59 Installation procedure, 1-10, 1-17 system requirements, 1-10
L
Level of service standards, 5-5 Load ratings, 5-5 Log files, 5-29 Logging on, 2-2, 2-17 Look ahead rules, 5-12, 5-16
M
Major rehab rules, 5-12, 5-17 Master database, 3-38, 3-79 Materials, 7-11, 7-40 Measurement units, 3-5, 3-43 Menus, 2-4 Metric units, 3-5, 3-43 Missing values representation in Pontis, 1-14, 1-19 using formulas to fill in, 7-2, 7-19, 7-23, 7-48 Models cost, 4-12 deterioration, 4-6 preservation optimization, 4-6 Modules selecting, 2-18
H
Health index, 4-12, 5-18, 5-30, 6-31 Highway Construction Cost Index, 7-17, 7-46
I
Importing data NBI, 1-12, 1-18, 3-9, 3-20, 3-47, 3-60 PDI, 1-13, 1-19 Improvement costs and benefits, 5-7 determination of needs, 5-6 model parameter, 5-10 Indirect cost, 4-9 Inflation, 4-9, 4-13, 7-2, 7-17, 7-23, 7-46 Inspection data importing and exporting, 3-36, 3-77 dates, 3-14, 3-53 deleting, 3-34, 3-75 due dates, 3-16 duplicate, 3-18, 3-58 element, 3-18, 3-58 entering, 3-18, 3-57 initial, 3-18, 3-57 intervals, 3-16, 3-55 NBI, 3-5, 3-44 notes, 3-20, 3-61 planning, 3-16 resources, 3-14, 3-17, 3-40, 3-53, 3-56, 3-81 scheduling, 3-17, 3-40, 3-56, 3-81 tab card, 3-4, 3-41 agency, 3-5, 3-44, 5-19
N
NBI files exporting, 3-8, 3-36, 3-46, 3-77 files importing, 1-12, 1-18, 3-8, 3-46 item 8, 3-8, 3-46 ratings, 3-5, 3-29, 3-44, 3-69, 5-30 reporting, 3-11, 3-50 structure number, 3-8, 3-46 sufficiency ratings, 3-31, 3-71 NBI translator, 3-20, 3-29, 3-60, 3-69, 7-10, 7-38 Network improvement strategy developing, 5-2
O
Optimization, 4-2, 4-14, 4-15 Options parameter values, 7-2, 7-23
I-3
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
P
Paint rules, 5-12, 5-26 Parameters importing, 1-15 modifying, 1-14, 1-20, 7-6, 7-33 PDI exporting/checking out, 3-37, 3-38, 3-78, 3-79 importing, 1-13, 1-19 Performance measures, 5-30, 5-32, 5-34 Policy matrix, 5-4 Pontis customizing, 7-16, 7-45 databases supported, 1-3 development tools, 1-3 workflow, 1-7 Pontis Lite, 1-11, 3-18 Preservation module overview, 4-2 optimization model, 5-2 results, 4-19 Privileges, 7-3, 7-25 Probabilities failure, 4-18 transition, 4-17 Programs active/inactive, 6-13 defining, 6-2 vs. scenarios, 6-2 Project planning desktop, 6-4, 6-5 bridge view, 6-5 project view, 6-5 project/structure list, 6-4 tree, 6-4 work candidates panel, 6-5 Projects assigning ID, 6-24 automatically generating projects (Batch mode), 623 changing information for groups of, 6-37 combining, 6-38 creating for individual bridges, 6-20 creating multi bridge projects, 6-22 creating without using work candidates, 6-25 definition of, 6-2 deleting, 6-37 finding, 6-32, 6-36, 6-37 fund tracking, 6-10 funding source, 6-28 master, 6-38 ranking, 6-34, 6-35 reports, 6-42 reviewing information, 6-32 splitting, 6-40 status, 6-21, 6-42 updating, 6-36
R
Reports configuration, 7-64 customizing, 2-15, 2-16, 6-12 default, 2-15 filtering, 5-30 inspection, 3-28, 3-40, 3-81 preservation, 4-19 programming, 6-3 project planning, 6-42 selecting bridges to include, 2-16 specify retrieval criteria screen, 2-16, 2-37 viewing and printing, 2-15 Results module, 5-30 Roadway information entering, 3-11, 3-49 on/under, 3-11, 3-50
S
Scale field, 4-12 Scenarios advanced parameters, 5-26, 5-27 analyzing results, 5-30 bridge analysis, 6-30 defining and running, 5-24, 5-28 deleting, 5-29 limiting number of, 5-24 programmed work, 5-31 specification report, 5-29 storing indicators for each bridge, 5-28 treatment of projects in, 6-3, 6-21 viewing results, 5-31 Scoping rules, 5-12, 5-15 security, 8-1 Security, 7-4 SI&A report, 3-40, 3-81 Simulation budgets, 5-2 improvement standards, 5-2 improvment, 5-7 interaction of rules, 5-14 overview, 5-2 parameters, 5-26, 5-27 rules overview, 5-12 thresholds, 5-26 Smart flags, 7-7, 7-34 Standards service and design, 5-4 Status bar database status block, 2-6, 2-21 date-time block, 2-6 edit status block, 2-6 message history list, 2-6 system status block, 2-6, 2-21 Structure adding a new, 3-8, 3-46
I-4
N A V I G A T I O N
A N D
F I E L D
L E V E L
S E C U R I T Y
elements, 7-2, 7-23 finding, 2-12 ID, 3-8, 3-46 inventory and condition information, 3-5, 3-44 ratings, 3-5, 3-44 removing, 3-35, 3-76 replacement criteria, 5-26 representation, 3-2 reviewing needs and work for, 6-29 updating information for, 3-6, 3-45 Structure list controls, 2-7, 2-22 customizing columns, 2-10 default, 2-6, 2-22 exporting, 2-10 field definition, 2-8 filtering, 2-9, 2-13, 2-24, 2-30 find button, 2-7, 2-12, 2-23, 2-24, 2-25, 2-27, 2-28, 2-29, 2-30, 2-33, 2-35, 2-36 layouts, 2-7, 2-22 making larger or smaller, 2-10 printing, 2-10 right mouse click on, 2-8 sorting, 2-7, 2-8, 2-22 splitting, 2-9 SQL syntax, 2-10 Structure unit default, 3-10, 3-49 definition of, 3-2 entering information for, 3-10, 3-48 identifying for a structure, 3-8, 3-46 selecting for an element, 3-13, 3-51 Structure, Inventory and Appraisal (SIA) sheet, 3-40, 3-81 Subelements, 7-7, 7-8, 7-34, 7-36
T
Tab card condition, 7-9, 7-13, 7-37, 7-42 inventory, 7-19 Toolbar, 2-5 Transition probabilities, 4-3, 4-6
U
User administration, 7-3, 7-25 User cost, 5-2
W
Work candidates definition of, 6-2 entering, 3-21, 3-61 filtering, 6-16 finding and selecting, 6-16, 6-17 inspector generated, 6-15 Pontis generated, 6-15 resize window, 6-16 reviewing, 6-15 Work items adding to a project, 6-20, 6-22, 6-23, 6-26 definition of, 6-2 using the tree to add, move and remove, 6-36
Z
Zooming, 2-5
I-5
Appendix
A
Glossary of Terms
Action
A work activity at the bridge or element level. Bridge-level actions include four standard types of improvements that are modeled in the Pontis simulation (replacement, widening, raising, and strengthening). Additional bridge-level actions (such as seismic retrofit) are available for project planning. Element-level actions are defined for each condition state. Each element-level action belongs to one action type.
Agency Need
Agency cost of meeting a need of any type for a structure. Any structure may have one or more agency needs. Agency needs can be input by users in the form of Inspector Work Candidates (which in turn may become Work Items). Alternatively, agency needs may be directly input by users as project Work Items. The Scenario Treatment attribute of the project determines how these needs will be recognized in the simulation once defined as work items.
Benefit
Benefits are the value of taking actions to address preservation or functional improvement needs. The benefit of addressing preservation needs is defined in Pontis as the cost savings resulting from performing all recommended MR&R work on a bridge in the current year, versus postponing it for one period and then following the recommended actions for the condition that the bridge would be in at that time. The benefits of addressing functional improvement needs are calculated by user-modifiable formulas which are based on user cost (travel time, accident) reductions gained from eliminating detours and improving safety.
A-1
G L O S S A R Y
O F
T E R M S
Bridge ID
Agency defined identifier for a bridge. This value is used for identifying bridges on Pontis screens and reports. It may differ from the NBI structure number and bridge key used internally by Pontis.
BME
See Bridge Management Element.
Budget Matrix
A budget matrix contains budget limits by year used when performing a program simulation. Several different budget matrices can be defined and used within different scenarios in order to develop and save multiple programs.
Condition State
A condition state categorizes the nature and extent of damage or deterioration a bridge element. Starting with Pontis 5.1.2 release, each bridge element will have four condition states. Condition state one is always defined as no damage. The higher the condition state, the more damage there is on the element. Condition states for each element have been precisely defined in terms of the specific types of distresses that the elements can develop.
Condition Unit
A condition unit is a combination of an element and an environment.
Control
A control in Pontis 5.1.2 refers to any of the basic programming items that make up a Pontis screen. For example, buttons, text boxes, labels, pick-lists (or drop-down boxes) are all controls.
A-2
G L O S S A R Y
O F
T E R M S
CoRe (legacy)
Commonly Recognized Element. AASHTO has defined a set of CoRe elements definitions. These definitions are used as defaults in Pontis, and are described in the AASHTO Guide For Commonly Recognized (CoRe) Structural Elements.
Cost Matrix
A table containing unit costs and benefits for improvement actions. These costs and benefits can vary for different combinations of ADT class, functional class, funding responsibility, and NHS status. They are used to estimate improvement costs when performing a program simulation.
Crystal Reports
Crystal Reports is a report generation tool delivered with Pontis 5.1.2. Crystal Reports allows users to create custom reports that can be registered with and displayed by Pontis 5.1.2.
Deterioration
The process by which the physical condition of structure elements declines over time due to traffic loadings, weather, or any chemical or physical processes.
Determinate
Non-probabilistic outcome. For example, an action taken may have a determinate or probabilistic upgrading effect on an element condition distribution.
Direct Cost
The portion of a project cost which varies with the particular characteristics of the actions applied and the elements to which they are applied. These are distinguished in Pontis from indirect costs, which include costs for mobilization, traffic control, and engineering which apply at the structure level rather than the level of individual elements and/or actions taken. (Note: direct costs are synonymous with variable costs.)
Design Standard
Level to which an operating deficiency will be corrected when an improvement need is generated.
A-3
G L O S S A R Y
O F
T E R M S
Element
A fundamental part of a bridge for which condition is assessed and work is recommended. Elements are distinguished from Smart Flags by their condition distribution/extent within a structure and the ability to take corrective actions on them.
Element Category
An overarching categorization of a Pontis element, usually by a gross bridge division such as superstructure, substructure. There are one or more Element Types per Element Category.
Element Distribution
A graphical or tabular view of how element condition is distributed across different condition states.
Element Materials
The standard version of Pontis has categories of element materials, although these may be customized. The standard categories are: Unpainted Steel, Painted Steel, Prestressed Concrete, Reinforced Concrete, Timber, Decks, Slabs, and Smart Flags.
Element Types
An aggregation/shorthand grouping of similar/interrelated bridge elements. There may be one or more specific elements per element type. Element type does not have to consider element material as a grouping criteria. Default element types (and their associated element categories) are:
A-4
Superstructure Unspecified (Superstructure) Railings/Barriers (Superstructure) Girders/Stringers/Beams (Superstructure) Pin and Hangers (Superstructure) Truss Components (Superstructure) Arches (Superstructure)
AASHTO Pontis Users Manual
G L O S S A R Y
O F
T E R M S
Piers/Columns (Substructure) Footings and Pilings (Substructure) Caps (Substructure) Wingwalls/Abutments (Substructure) Deck/Slab (Deck/Slab) Bearings (Bearings) Joints (Joints) Smart Flags (Smart Flags)
Elicitations
Process in which expert judgment is used to predict the behavior of different types of structure elements. The results from each of the experts are combined to make a composite deterioration model.
Environment
The deterioration of a structure is partially determined by its environment and operating practices (e.g. use of road salt). To capture these effects, each element of a structure is identified by the following standard environmental classifications: Benign No environmental conditions affecting deterioration. Low Environmental conditions create no adverse impacts, or are mitigated by past nonmaintenance actions or highly effective protective systems. Moderate Typical level of environmental influence on deterioration. Severe Environmental factors contribute to rapid deterioration. Protective systems are not in place or are ineffective.
Failure Cost
Represents the penalty the public will incur should the element fail. It includes all costs (agency and public, direct and indirect) and is used by Pontis in the optimization model to determine optimal actions.
A-5
G L O S S A R Y
O F
T E R M S
Feasible Needs
Subset of unconstrained needs recognizing policy constraints e.g., ability to widen.
Field
A field in Pontis 5.1.2 refers to either a database field that holds Pontis data, or a control on a screen that accepts data. For example, a text box that accepts a minimum vertical clearance measurement is a field.
Fixed Cost
See Indirect Cost.
Flexible Action
Sets of action/element combinations along with rules for how the Pontis simulation should model resultant changes in conditions.
Functional Need
See Improvement Need.
Funding Sources
Explicitly defined funding authorizations which are available for bridge work. Funding sources are associated with programs, projects and/or work items.
Group
A group in Pontis 5.1.2 refers to the areas on a given screen that contain controls and fields. Usually, a group has a title, like the Condition Ratings group on the Inspection/Condition task, coupled with a thin lined box surrounding the controls and fields.
Improvement Matrix
An improvement matrix defines assumptions which are used to estimate the benefits of structure improvements. Such assumptions include accident probabilities as a function of deck width, and the percent of vehicles that must detour based on load restrictions. The Improvement Matrix is used during a program simulation.
A-6
G L O S S A R Y
O F
T E R M S
Improvement Need
Cost to improve deficiencies for a structure to meet agency design standards, recognized when the structure configuration is compared with minimum operating standards (width, strength, under/over clearances, etc.). This need may be defined by the agency or Pontis models.
Indirect Cost
Indirect costs are those which are associated with a structure project as a whole such as costs for mobilization, traffic control, and administration. Indirect costs are distinguished in Pontis from direct costs, which depend on the specific actions taken on individual bridge elements. (Note: indirect costs are synonymous with the term "fixed costs".)
Length mm, m, km, in, ft, yd, mi Area sqmm, sqm, sqkm, sqin, sqft, sqyd, sqmi Speed mph, kph, fps, mps (these stand for miles/hour, kilometers/hour, feet/sec, meters/sec) Mass/Weight ton, mton, kg, lb Volumetric cm/s, cf/s, cy/s (these stand for cubic meters/sec, cubic feet/sec, cubic yards/sec) Number ea Volume cum, cuft, cuyd (these stand for cubic meters, cubic feet, cubic yards)
Supported Metric to English Conversions:
Millimeters to Inches Millimeters to Feet Millimeters to Yards Millimeters to Miles Meters to Inches Meters to Feet Meters to Yards Meters to Miles Kilometers to Inches Kilometers to Feet Kilometers to Yards Kilometers to Miles
A-7
G L O S S A R Y
O F
T E R M S
SqMillimeters to SqInches SqMillimeters to SqFeet SqMillimeters to SqYards SqMillimeters to SqMiles SqMeters to SqInches SqMeters to SqFeet SqMeters to SqYards SqMeters to SqMiles SqKilometers to SqInches SqKilometers to SqFeet SqKilometers to SqYards SqKilometers to SqMiles KPH to MPH KPH to FPS MPS to MPH MPS to FPS Kilograms to Pounds Kilograms to Tons MetricTons to Pounds MetricTons to Tons CubicMeters to CubicFeet CubicMeters to CubicYards CubicMetersPS to CubicFeetPS CubicMetersPS to CubicYardsPS
Supported English to Metric Conversions:
Inches to Millimeters Inches to Meters Inches to Kilometers Feet to Millimeters Feet to Meters Feet to Kilometers Yards to Millimeters Yards to Meters Yards to Kilometers Miles to Millimeters Miles to Meters Miles to Kilometers
A-8
G L O S S A R Y
O F
T E R M S
SqInches to SqMillimeters SqInches to SqMeters SqInches to SqKilometers SqFeet to SqMillimeters SqFeet to SqMeters SqFeet to SqKilometers SqYards to SqMillimeters SqYards to SqMeters SqYards to SqKilometers SqMiles to SqMillimeters SqMiles to SqMeters SqMiles to SqKilometers MPH to KPH MPH to MPS FPS to KPH FPS to MPS Pounds to Kilograms Pounds to Metric Tons Tons to Kilograms Tons to Metric Tons Cubic Feet to CubicMeters Cubic Yards to CubicMeters Cubic FeetPS to CubicMetersPS Cubic YardsPS to CubicMetersPS
Other Supported Conversions:
Each to Each
MR&R
Maintenance, Repair, and Rehabilitation. This term is used interchangeably with "preservation".
MR&R Model
See preservation model.
A-9
G L O S S A R Y
O F
T E R M S
MR&R Need
These are the costs of a preservation action (taken to offset the effects of deterioration) to be taken on an element in a given condition state. Pontis defines this based upon lowest long-term steady-state cost. By definition, any other action costs more over the long term and is an agencydefined MR&R need. May become a Work Candidate, and then a Work Item in project planning process.
NBE
See National Bridge Elements.
NBI
See National Bridge Inventory.
Need
Within Pontis, a need is defined as the cost of performing preservation and implement work recommended for a structure.
Network-Level
An analysis or policy which applies to a group of bridges (e.g. all bridges in a state, district or county) and does not distinguish among individual bridges.
A-10
G L O S S A R Y
O F
T E R M S
Operating Standard
Threshold to identify an operating deficiency that will generate a bridge improvement need.
PDI
See Pontis Data Interchange File.
Policy Constraint
Factor limiting feasibility of a project in non-economic terms such as accepted practices (no truss widening), minimum project size, deferment period, minimum size of need, and others.
Policy Matrix
A table containing standards for when different types of improvement actions should be applied. These standards can vary for different combinations of ADT class, functional class, structure funding responsibility, and NHS status. The Policy Matrix is used when performing a program simulation.
Pontis
Pontis is a Bridge Management System (BMS) which incorporates dynamic, probabilistic models, and a detailed bridge database to predict maintenance and improvement needs, recommend optimal policies, and plan projects within budget and policy constraints. Its name derives from the Latin word for "bridge".
Pontis Need
Cost of an improvement or MR&R need generated from Pontis models. May become a Work Item in project planning process.
Prioritization Method
By default, during a program simulation, Pontis prioritizes projects based on incremental benefit/cost ratios in order to maximize the benefits obtained from a fixed maximum budget.. Benefits and costs are calculated differently for functional improvement actions and preservation actions. For functional improvement actions, benefits are calculated based on the expected
A-11
G L O S S A R Y
O F
T E R M S
reductions in bridge user accidents and delay related to detours. These benefits can be adjusted in the programming module.
Preservation Model
A preservation model (also referred to as an MR&R Model) in Pontis consists of: Deterioration Models which define how and when elements change condition when different actions (or no action) are taken Cost Models which specify the unit costs of MR&R actions Results of an optimization procedure using the deterioration and cost models: an optimal long term strategy for preservation of structures which defines what action should be taken for any given element in a particular environment and condition state.
Program
A set of one or more projects which are grouped together for planning or budgeting purposes. Programs in Pontis are typically defined based on established agency capital and maintenance programming practices. Each program has a budget, which in turn may be derived from multiple funding sources. Some agencies will want to set up programs based on type of work: for example: Work Force Maintenance, Major Maintenance, Rehabilitation, Replacement. Others may want to align programs closely with federal and state funding programs.
Program-Level
An analysis concerned with prioritizing and scheduling a set of structure projects given constraints on funding.
Program Work
The collection of all Project Work Items.
Project
A set of one or more actions on one or more bridges with associated costs, benefits, and expenditures of other resources. Projects may be proposed, initiated, programmed, deferred, in progress or completed. Projects are funded by a single or multiple sources. Every project belongs to a Program.
A-12
G L O S S A R Y
O F
T E R M S
Project Status
Current stage of the project. Project status classifications for Pontis are: Initiated Formal process has been initiated within the agency for inclusion in a program. Programmed Project has been formally included in a program, and/or funding is committed. Deferred Project has been deferred to an unknown date. In Progress Contract for the project has been awarded, and/or work is underway. Completed All project work has been completed.
Protective Systems
Protective systems influence the deterioration and condition of the underlying structural element.
Recommended Needs
Subset of feasible needs meeting budget and model constraints. These needs generate Work Candidates.
Scenario
A set of various parameters, control tables, and bridges controlling a simulation of future bridge needs and work, and the outcome/results of the simulation. Both network-level and bridge-level results are stored. Bridge-level results are Pontis Work Candidates.
A-13
G L O S S A R Y
O F
T E R M S
Scenario Work
Work candidates generated from running a scenario simulation.
Scoping Rule
A user specified rule considered in project simulation that looks at combinations of needs in order to make algorithmic decisions on up scoping recommended work.
SDF
See System Data Format File.
Simulation Rules
Rules that can be established to control the manner in which the Pontis program simulates, selects and schedules work.
Structure
Structure is the generic term used within Pontis to refer to a bridge, culvert or tunnel.
Structure Unit
Any logical grouping of structure components usually having the same structural design and material. Although a structure unit can be an individual span, structure units can be used to represent groups of spans having the same structural design and material, or portions of the structure that might be rehabilitated separately (e.g. approach spans might be one unit; the main span another).
Sub-Task
(See also: Task) Sub-tasks are similar to tasks. Sub-tasks do not exist on their own under a tab; they are always a child to another task.
A-14
G L O S S A R Y
O F
T E R M S
Tab
A tab in Pontis 5.1.2 refers to the items across the top of the Pontis interface that users click on to get into the major functional areas of Pontis.
Task
A task in Pontis 5.1.2 refers to the menu items that appear on the left side of the interface. Tasks are associated with a tab and will change depending on the tab.
Unconstrained Needs
Needs generated during program simulation without regard to specific budget or policy constraints.
Variable Cost
The portion of a project cost which varies with the particular characteristics of the actions applied and the number of elements to which they are applied. These are distinguished in Pontis from fixed or indirect costs, which include costs for mobilization, traffic control, and engineering which apply at the structure level rather than the level of individual elements and/or actions taken. (Note: Variable Costs are generally referred to as "Direct Costs" within the system.)
Work Candidates
Work which is available for inclusion in projects. Candidate work items are generated by 1) inspectors, and 2) running Pontis program simulation scenarios.
Work Item
An individual project work line item with bridge identifier if appropriate, cost, element type if appropriate, work type, year, and other attributes. Work Items may be manually entered into Pontis, or may be derived from inspector recommendations or Pontis work candidates. There are one or more work items per project.
XML
See Extensible Markup Language.
A-15
Appendix
B
NBI Data Items
his appendix provides a table showing the locations of all standard NBI items on the Pontis data entry Tab Cards. The column positions for each item in the standard NBI file format1 which is required for submittal to FHWA are also shown here for convenience.
Item Name Pontis Tab and Task Location NBI File Column Positions
1-3 28-29 30-32 33-37 19 20 21 22-26 27 Inventory ID/Admin Inventory - Roads Inventory ID/Admin 38-61 62 63-80
T
1 2 3 4 5a 5b 5c 5d 5e 6a 6b 7
NBI Item #
State Code Highway Agency District County(Parish)Code Place Code Record Type Route Signing Prefix Designated Level of Service Route Number Directional Suffix Features Intersected Critical Facility Facility Carried by Structure
Inventory ID/Admin Inventory ID/Admin Inventory ID/Admin Inventory ID/Admin Inventory - Roads
FHWA, Recording and Coding Guide for the Structure Inventory and Appraisal of the Nations Bridges, Bridge Division, Office of Engineering, December, 1995.
B-1
N B A
D A T A
I T E M S
NBI Item #
Item Name
8 9 10
Structure Number Location Inventory Route, Minimum Vertical Clearance Kilometer Point Base Highway Network LRS Inventory Route Subroute Number Latitude Longitude Bypass ,Detour Length Toll Maintenance Responsibility Owner Functional Classification of Inventory Route Year Built Sum of lanes under Lanes on the structure Lanes under the structure Average Daily Traffic Year of Average Daily Traffic Design Load Approach Roadway Width Bridge Median Skew Structure Flared
11 12 13a 13b 16 17 19 20 21 22 26
Inventory ID/Admin Inventory ID/Admin Inventory Roads Inventory Roads Inventory ID/Admin Inventory ID/Admin Inventory Roads
27 28 28a 28b 29 30 31 32 33 34 35
Inventory ID/Admin Inventory ID/Admin Inventory Roads Inventory Roads Inventory Roads Inventory Roads Appraisal Load Ratings Inventory Roads Inventory Design Inventory Design Inventory Design
157-160
B-2
N B A
D A T A
I T E M S
NBI Item #
Item Name
Traffic Safety Features Bridge Railings Transitions Approach Guardrail Approach Guardrail Ends Historical Significance Navigation Control Navigation Vertical Clearance Navigation Horizontal Clearance Structure Open, Posted, or Closed to Traffic Type of Service On Type of Service - Under Main Span Material/Design Main Span Design/Construction Approach Span Material/Design Approach Span Design/Construction
Inventory Classification Appraisal Other Ratings Appraisal Other Ratings Appraisal Other Ratings
41
199
Inventory ID/Admin
200 201
Inventory - Design
202 203-204
44a 44b
Inventory - Design
205 206-207
45
Number of Spans in Main Unit Number of Approach Spans Inventory Route, Total Horizontal Clearance Length of Maximum Span Structure Length Left Curb/Sidewalk Width Right Curb/Sidewalk Width Bridge Roadway Width, Curbto-Curb Deck Width, Out-to-Out
Inventory - Design
208-210
46 47
211-214 215-217
48 49 50a 50b 51
Inventory Roads
235-238
52
Inventory - Design
239-242
B-3
N B A
D A T A
I T E M S
NBI Item #
Item Name
53
Minimum Vertical Clearance Over Bridge Roadway Reference Feature Minimum Vertical Underclearance Reference Feature Minimum Lateral Underclearance on Right Minimum Lateral Underclearance on Left Deck Superstructure Substructure Channel and Channel Protection Culverts Method Used to Determine Operating Rating Operating Rating Method Used to Determine Inventory Rating Inventory/Appraisal Rating Structural Evaluation
54a 54b
247 248-251
55a 55b
252 253-255
56
256-258
58 59 60 61
62 63
263 264
64 65
265-267 268
66 67
Appraisal Load Ratings Appraisal Other Ratings (calculate with Sufficiency Rating button on Condition Card)
269-271 272
68
Deck Geometry
Appraisal Other Ratings (calculate with Sufficiency Rating button on Condition Card)
273
69
Appraisal Other Ratings (calculate with Sufficiency Rating button on Condition Card) Appraisal Load Ratings Condition
274
70 71
275 276
B-4
N B A
D A T A
I T E M S
NBI Item #
Item Name
72
Approach Roadway Alignment Type of Work Proposed Work Done By Length of Structure Improvement Inspection Date Designated Inspection Frequency Critical Feature Inspection Underwater Inspection Other Special Inspection Fracture Critical Details Date Underwater Inspection Date Other Special Inspection Date Bridge Improvement Cost
75a 75b 76
Project Planning Module Bridge View, NBI Project Info Project Planning Module Bridge View, NBI Project Info Schedule Schedule
90 91
287-290 291-292
Schedule
Schedule
Project Planning Module Bridge View, NBI Project Info Project Planning Module Bridge View, NBI Project Info Project Planning Module Bridge View, NBI Project Info Project Planning Module Bridge View, NBI Project Info Inventory ID/Admin
314-319
95
320-325
96
326-331
97
Year of Improvement Cost Estimate Neighboring State Code Percent Responsibility Border Bridge Structure Number STRAHNET Highway Designation Parallel Structure Designation Direction of Traffic Temporary Structure Designation
332-335
98A 98B 99
336-338 339-340
Inventory ID/Admin
341-355
100
Inventory Roads
356
B-5
N B A
D A T A
I T E M S
NBI Item #
Item Name
104
Highway System of the Inventory Route Federal Lands Highways Year Reconstructed Deck Structure Type Type of Wearing Surface Type of Membrane Deck Protection Average Daily Truck Traffic Designated National Network Pier or Abutment Protection (for Navigation) NBIS Bridge Length Scour Critical Bridges Future Average Daily Traffic Year of Future Average Daily Traffic Minimum Navigation Vertical Clearance, Vertical Lift Bridge Sufficiency Rating
Inventory Roads
116
386-389
SR
Appraisal Other Ratings (calculate with Sufficiency Rating button on Condition Card)
429-432
B-6
Appendix
C
Entity Relationship Diagram
his appendix provides a diagram of the database tables organized by their category (colorcoded). When printed in color on 8.5 x 11 paper, the colored legend will aid in locating groups of information. Specific table details can then be viewed and printed by zooming in and then using the print option. The following indicates the breakdown between the two versions of Pontis: Physical Inventory Used in version 4.5 and 5.x Program Simulation Present in version 4.5 and 5.x; only used in 4.5 Project Planning - Present in version 4.5 and 5.x; only used in 4.5 Definition Tables - Used in version 4.5 and 5.x System Tables - Used in version 4.5 and 5.x Pontis 5.0 Tables Version 5.x only Navigation and Security - Version 5.x only
C-1
Appendix
D
Report Reference
T
D.1 D.2 D.3 D.4 D.5 D.6 D.7 D.8 D.9 D.10 D.11 D.12 D.13 D.14 D.15
his appendix provides a reference for each of the Pontis reports. The reports are listed in alphabetical order by report name. All reports are available in DataWindow .NET and Crystal Reports formats unless otherwise indicated.
A list of the reports is included below. CONFIG001: Elements, States and Actions CONFIG002: User Configurable Options List CONFIG003: Parameter Report CONFIG004: Data Dictionary CONFIG005: INI File Report CONFIG006: User List CONFIG007: Miscellaneous System Parameters CONFIG008: Flexible Actions CONFIG009: UI Navigation CONFIG010: Application Security INSP001: Inspection SI&A (Metric) INSP002: Bridge Inspection Report (Metric) INSP003: Inspection Scheduling Information INSP004: Inspection Resource Requirements INSP005: Bridge Health Index Detail
D-1
R E P O R T
R E F E R E N C E
D.16 D.17 D.18 D.19 D.20 D.21 D.22 D.23 D.24 D.25 D.26 D.27 D.28 D.29 D.30 D.31 D.32 D.33 D.34 D.35 D.36 D.37 D.38 D.39 D.40 D.41 D.42 D.43
INSP006: Network Element Summary Distribution (Metric) INSP007: Inspection SI&A (English) INSP008: Bridge Inspection Report (English) INSP009: Network Element Summary Distribution (English) INSP010: Bridge Condition Summary MODELS001: Total Unconstrained Needs MODELS002: Preservation Model Details PLAN001: Pontis-Generated Preservation Needs PLAN002: Projects and Work Candidates by Bridge PLAN003: Project Priority List PLAN004: Project Details Sheet PLAN005: Actual versus Budgeted Work PLAN006: Program Funding PLAN007: Pontis Priority List PLAN008: Pontis Work Candidate List PROG001: Bridge Management Network Summary PROG002: Backlog Summary Report PROG003: Total Needs vs. Programmed Work Over Time PROG004: Annual Allocation of Needs and Work PROG005: Bridge Performance Measure Summary PROG006: Network Performance Measure Summary PROG007: Element Condition Over Time PROG008: Annual Needs and Programmed Work by Element and Category PROG009: Total Needs by Element Category and Material PROG010: Preservation Work Programmed by District PROG011: Total Preservation Needs and Programmed Work Over Time PROG012: Scenario Specification Report Sample Report Printouts
D-2
R E P O R T
R E F E R E N C E
Retrieval Criteria
elemnum (element number) ecatkey (element category) etypkey (element type)
Report Definitions
SELECT elemdefs.elemkey, elemdefs.elemnum, elemdefs.coreflag, elemdefs.smartflag, elemdefs.parent, elemdefs.matlkey, elemdefs.ecatkey, elemdefs.etypkey, elemdefs.elemshort, elemdefs.elemlong, elemdefs.statecnt, elemdefs.eachflag, elemdefs.paircode, elemdefs.scaleshort, elemdefs.scaleunit, elemdefs.scalemet, elemdefs.elemweight, elemdefs.useparmdls, elemdefs.paintflag, elemdefs.notes FROM elemdefs ORDER BY elemdefs.elemnum ASC
D-3
R E P O R T
R E F E R E N C E
Action Definitions
SELECT mrractdf.elemkey, mrractdf.skey, mrractdf.akey, mrractdf.actnum, mrractdf.actshort, mrractdf.actlong, mrractdf.wholeflag, mrractdf.tkey, mrractdf.modelflag, mrractdf.paintflag, mrractdf.notes FROM mrractdf WHERE ( mrractdf.elemkey = :elemkey ) AND ( mrractdf.skey = :skey )
State Definitions
SELECT statedfs.elemkey, statedfs.skey, statedfs.statenum, statedfs.stateshort, statedfs.statedesc FROM statedfs WHERE ( statedfs.elemkey = :elemkey ) ORDER BY statedfs.statenum ASC
Computed Fields
ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') ProfileString ("PONTIS44.INI", "Site", "Office", ' ') ProfileString ("PONTIS44.INI", "Site", "Department", ' ') Describe ("DataWindow.Print.DocumentName") "Page" + page() + " of " + pagecount () left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]") trim (upper (stateshort)) + "..." + trim (statedesc)
D-4
R E P O R T
R E F E R E N C E
Report Definitions
SELECT coptions.optionname, coptions.optionval, coptions.defaultval, coptions.description, coptions.helpid FROM coptions ORDER BY coptions.optionname ASC
Computed Fields
ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') ProfileString ("PONTIS44.INI", "Site", "Department", ' ') ProfileString ("PONTIS44.INI", "Site", "Office", ' ') if (len (descrption) <= 255, descrption, left (descrption, 252) + '') Describe ("DataWindow.Print.DocumentName") "Page" + page() + " of " + pagecount () left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]")
D-5
R E P O R T
R E F E R E N C E
Report Definitions
SELECT paramtrs.table_name, paramtrs.field_name, paramtrs.parmvalue, paramtrs.shortdesc, paramtrs.longdesc, paramtrs.misvalflg FROM paramtrs ORDER BY paramtrs.table_name ASC, paramtrs.field_name ASC, paramtrs.misvalflg ASC, paramtrs.parmvalue ASC
Computed Fields
ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') ProfileString ("PONTIS44.INI", "Site", "Department", ' ') ProfileString ("PONTIS44.INI", "Site", "Office", ' ') Describe ("DataWindow.Print.DocumentName") "Page" + page() + " of " + pagecount () left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]")
D-6
R E P O R T
R E F E R E N C E
Retrieval Criteria
table_name (table name)
Report Definitions
SELECT datadict.table_name, datadict.col_name, datadict.col_alias, datadict.v2convert, datadict.datatype, datadict.width, datadict.dec_plcs, datadict.null_allow, datadict.uniquekey, datadict.position, datadict.nbi_cd, datadict.helpid, metric_english.metricunit, metric_english.englishunit, datadict.snotes, datadict.conversionrules, datadict.sysdefault, datadict.sysfield, datadict.unique_fld FROM datadict, metric_english WHERE ( datadict.paircode = metric_english.paircode )
D-7
R E P O R T
R E F E R E N C E
Computed Fields
ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') ProfileString ("PONTIS44.INI", "Site", "Department", ' ') ProfileString ("PONTIS44.INI", "Site", "Office", ' ') sum (width for group 1) count (position for group 1) String (width, "###,###') + "(" + string (dec_plcs) + ")" col_name + " (" + datadict_unique_fld + ")" Describe ("DataWindow.Print.DocumentName") "Page" + page() + " of " + pagecount () left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]")
D-8
R E P O R T
R E F E R E N C E
Retrieval Criteria
INI file
Computed Fields
ProfileString ("PONTIS44.INI", "Site", "Department", ' ') ProfileString ("PONTIS44.INI", "Site", "Office", ' ') ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') Describe ("DataWindow.Print.DocumentName") "Page" + page() + " of " + pagecount () left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]")
D-9
R E P O R T
R E F E R E N C E
Report Definitions
SELECT users.userkey, users.userid, users.last_name, users.first_name, users.middle, users.district, users.title, users.agency, users.address1, users.address2, users.city, users.state, users.zip, users.phone, users.fax, users.email, users.superuser, users.initials FROM users
Computed Fields
ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') ProfileString ("PONTIS44.INI", "Site", "Department", ' ') ProfileString ("PONTIS44.INI", "Site", "Office", ' ') Describe ("DataWindow.Print.DocumentName") "Page" + page() + " of " + pagecount () left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]")
D-10
R E P O R T
R E F E R E N C E
Report Definitions
Environments
SELECT envtdefs.envkey, envtdefs.envtnum, envtdefs.envtshort, envtdefs.notes FROM envtdefs ORDER BY envtdefs.envtnum ASC
Element Materials
SELECT elcatdfs.ecatkey, elcatdfs.ecatcode, elcatdfs.ecatname, elcatdfs.ecatpos FROM elcatdfs ORDER BY elcatdfs.ecatcode ASC
Element Types
D-11
R E P O R T
R E F E R E N C E
Action Types
SELECT actypdfs.tkey, actypdfs.atypenum, actypdfs.atypeshort, actypdfs.atypelong, actypdfs.atypcat, actypdfs.atypeelig, metric_english.metricunit, metric_english.englishunit FROM actypdfs, metric_english WHERE ( actypdfs.paircode = metric_english.paircode ) ORDER BY actypdfs.atypenum ASC
Computed Fields
ProfileString("PONTIS44.INI","Site","Agency",'') ProfileString("PONTIS44.INI","Site","Office",'') ProfileString("PONTIS44.INI","Site","Department",'') left(dayname(today()),3) + " " + string(today(), "[shortdate] [time]") "Page " + page() + " of " + pageCount() Describe("DataWindow.Print.DocumentName")
D-12
R E P O R T
R E F E R E N C E
Report Definitions
SELECT flexactions.fxactkey, flexactions.fxname, flexactions.impact, flexactions.states, flexrules.seqnumber, elemdefs.elemnum, elemdefs.elemshort, actypdfs.atypenum, actypdfs.atypeshort FROM flexactions, flexrules, elemdefs, actypdfs WHERE flexactions.fxsetkey = '00' and flexactions.fxactkey = flexrules.fxactkey and flexrules.elemkey = elemdefs.elemkey and flexrules.feastkey = actypdfs.tkey ORDER BY flexactions.fxactkey ASC, elemdefs.elemnum ASC, flexrules.seqnumber ASC, actypdfs.atypenum ASC
Computed Fields
ProfileString("PONTIS44.INI","Site","Agency",'') ProfileString("PONTIS44.INI","Site","Office",'') ProfileString("PONTIS44.INI","Site","Department",'') "Page " + page() + " of " + pageCount() left(dayname(today()),3) + " " + string(today(), "[shortdate] [time]") Describe("DataWindow.Print.DocumentName")
D-13
R E P O R T
R E F E R E N C E
This report details the user interface (UI) items in the current installation of Pontis. For each tab, any tasks, groups and controls are listed as a hierarchy. Also shown are the attributes of each UI element, such as the order number, the enabled status, etc.
Report Definitions
SELECT PON_NAV_TAB.order_num, PON_NAV_TAB.enabled_ind, PON_NAV_TAB.visible_ind, PON_NAV_TAB.read_only_ind, PON_NAV_TAB.navigate_url, PON_NAV_TAB.pontis_standard_ind, PON_NAV_TASK.order_num, PON_NAV_TASK.visible_ind, PON_NAV_TASK.read_only_ind, PON_NAV_TASK.navigate_url, PON_NAV_TASK.image_url, PON_NAV_TASK.pontis_standard_ind, PON_NAV_CONTROL_GROUP.order_num, PON_NAV_CONTROL_GROUP.visible_ind, PON_NAV_CONTROL_GROUP.read_only_ind, PON_NAV_CONTROL_GROUP.control_group_type, PON_NAV_CONTROL_GROUP.pontis_standard_ind, PON_NAV_CONTROL.order_num, PON_NAV_CONTROL.visible_ind, PON_NAV_CONTROL.read_only_ind, PON_NAV_CONTROL.control_type, PON_NAV_CONTROL.pontis_standard_ind, PON_NAV_CONTROL.table_name, PON_NAV_CONTROL.column_name, PON_NAV_CONTROL.control_id, PON_NAV_TAB.tab_id, PON_NAV_TASK.task_id, PON_NAV_CONTROL_GROUP.control_group_id, PON_NAV_CONTROL.name, PON_NAV_TAB.name, PON_NAV_TASK.name, PON_NAV_CONTROL_GROUP.name, PON_NAV_TASK.parent_task_id, PON_NAV_CONTROL_GROUP.parent_control_group_id FROM ((PON_NAV_TAB LEFT OUTER JOIN PON_NAV_TASK ON PON_NAV_TAB.tab_id=PON_NAV_TASK.tab_id)
D-14
R E P O R T
R E F E R E N C E
LEFT OUTER JOIN PONTIS.PON_NAV_CONTROL_GROUP PON_NAV_CONTROL_GROUP ON (PON_NAV_TASK.tab_id=PON_NAV_CONTROL_GROUP.tab_id) AND (PON_NAV_TASK.task_id=PON_NAV_CONTROL_GROUP.task_id)) LEFT OUTER JOIN PONTIS.PON_NAV_CONTROL PON_NAV_CONTROL ON ((PON_NAV_CONTROL_GROUP.tab_id=PON_NAV_CONTROL.tab_id) AND (PON_NAV_CONTROL_GROUP.task_id=PON_NAV_CONTROL.task_id)) AND (PON_NAV_CONTROL_GROUP.control_group_id=PON_NAV_CONTROL. control_group_id) ORDER BY PON_NAV_TAB.tab_id ASC, PON_NAV_TASK.task_id ASC, PON_NAV_CONTROL_GROUP.control_group_id ASC, PON_NAV_CONTROL.control_id ASC
D-15
R E P O R T
R E F E R E N C E
This report details the application security items in the current installation of Pontis. For each security role, all tabs, tasks, groups and controls are listed in a security hierarchy showing the visibility, read-only status, mobile visibility and mobile read-only status.
Report Definitions
SELECT PON_APP_ROLES.ROLEKEY, PON_APP_ROLES.ROLENAME, PON_APP_TAB_SECURITY.tab_id, PON_NAV_TAB.name, PON_APP_TASK_SECURITY.task_id, PON_NAV_TASK.name, PON_APP_CONTROL_GROUP_SECURITY.control_group_id, PON_NAV_CONTROL_GROUP.name, PON_APP_CONTROL_SECURITY.control_id, PON_NAV_CONTROL.name, PON_APP_TAB_SECURITY.visible_ind, PON_APP_TAB_SECURITY.read_only_ind, PON_APP_TAB_SECURITY.mobile_visible_ind, PON_APP_TAB_SECURITY.mobile_read_only_ind, PON_APP_TASK_SECURITY.visible_ind, PON_APP_TASK_SECURITY.read_only_ind, PON_APP_TASK_SECURITY.mobile_visible_ind, PON_APP_TASK_SECURITY.mobile_read_only_ind, PON_APP_CONTROL_GROUP_SECURITY.visible_ind, PON_APP_CONTROL_GROUP_SECURITY.read_only_ind, PON_APP_CONTROL_GROUP_SECURITY.mobile_visible_ind, PON_APP_CONTROL_GROUP_SECURITY.mobile_read_only_ind, PON_APP_CONTROL_SECURITY.visible_ind, PON_APP_CONTROL_SECURITY.read_only_ind, PON_APP_CONTROL_SECURITY.mobile_visible_ind, PON_APP_CONTROL_SECURITY.mobile_read_only_ind, PON_APP_TAB_SECURITY.ROLEKEY FROM (((((((PONTIS.PON_APP_ROLES PON_APP_ROLES LEFT OUTER JOIN PONTIS.PON_APP_TAB_SECURITY PON_APP_TAB_SECURITY ON PON_APP_ROLES.ROLEKEY=PON_APP_TAB_SECURITY.ROLEKEY) LEFT OUTER JOIN PONTIS.PON_APP_TASK_SECURITY PON_APP_TASK_SECURITY ON (PON_APP_TAB_SECURITY.ROLEKEY=PON_APP_TASK_SECURITY.RO LEKEY) AND (PON_APP_TAB_SECURITY.tab_id=PON_APP_TASK_SECURITY.tab_id))
D-16
R E P O R T
R E F E R E N C E
LEFT OUTER JOIN PONTIS.PON_NAV_TAB PON_NAV_TAB ON PON_APP_TAB_SECURITY.tab_id=PON_NAV_TAB.tab_id) LEFT OUTER JOIN PONTIS.PON_APP_CONTROL_GROUP_SECURITY PON_APP_CONTROL_GROUP_SECURITY ON ((PON_APP_TASK_SECURITY.ROLEKEY= PON_APP_CONTROL_GROUP_SECURITY.ROLEKEY) AND (PON_APP_TASK_SECURITY.tab_id= PON_APP_CONTROL_GROUP_SECURITY.tab_id)) AND (PON_APP_TASK_SECURITY.task_id= PON_APP_CONTROL_GROUP_SECURITY.task_id)) LEFT OUTER JOIN PONTIS.PON_NAV_TASK PON_NAV_TASK ON (PON_APP_TASK_SECURITY.tab_id=PON_NAV_TASK.tab_id) AND (PON_APP_TASK_SECURITY.task_id=PON_NAV_TASK.task_id)) LEFT OUTER JOIN PONTIS. PON_APP_CONTROL_SECURITY PON_APP_CONTROL_SECURITY ON ((PON_APP_CONTROL_GROUP_SECURITY.ROLEKEY= PON_APP_CONTROL_SECURITY.ROLEKEY) AND (PON_APP_CONTROL_GROUP_SECURITY.tab_id= PON_APP_CONTROL_SECURITY.tab_id)) AND (PON_APP_CONTROL_GROUP_SECURITY.task_id= PON_APP_CONTROL_SECURITY.task_id)) LEFT OUTER JOIN PONTIS.PON_NAV_CONTROL_GROUP PON_NAV_CONTROL_GROUP ON ((PON_APP_CONTROL_GROUP_SECURITY.tab_id= PON_NAV_CONTROL_GROUP.tab_id) AND (PON_APP_CONTROL_GROUP_SECURITY.task_id= PON_NAV_CONTROL_GROUP.task_id)) AND (PON_APP_CONTROL_GROUP_SECURITY.control_group_id= PON_NAV_CONTROL_GROUP.control_group_id)) LEFT OUTER JOIN PONTIS.PON_NAV_CONTROL PON_NAV_CONTROL ON (((PON_APP_CONTROL_SECURITY.tab_id=PON_NAV_CONTROL.tab_id) AND (PON_APP_CONTROL_SECURITY.task_id=PON_NAV_CONTROL.task_id) ) AND (PON_APP_CONTROL_SECURITY.control_group_id= PON_NAV_CONTROL.control_group_id)) AND (PON_APP_CONTROL_SECURITY.control_id= PON_NAV_CONTROL.control_id) ORDER BY PON_APP_ROLES.ROLEKEY ASC, PON_APP_TAB_SECURITY.tab_id ASC, PON_APP_TASK_SECURITY.task_id ASC, PON_APP_CONTROL_GROUP_SECURITY.control_group_id ASC, PON_APP_CONTROL_SECURITY.control_id
R E P O R T
R E F E R E N C E
D-18
R E P O R T
R E F E R E N C E
Retrieval Criteria
brkey (bridge key)
Report Definitions
SELECT bridge.brkey, bridge.bridge_id, bridge.struct_num, inspevnt.suff_rate, bridge.fips_state, bridge.facility, bridge.location, roadway.on_under, roadway.kind_hwy, roadway.levl_srvc, roadway.routenum, roadway.dirsuffix, bridge.bb_pct, bridge.district, bridge.county, bridge.placecode, roadway.kmpost, bridge.featint, bridge.latitude, bridge.longitude, bridge.nstatecode, bridge.bb_brdgeid, bridge.appspans, bridge.mainspans, bridge.materialmain, bridge.designmain, bridge.materialappr, bridge.designappr, bridge.dkstructyp, bridge.dksurftype, bridge.dkmembtype, bridge.dkprotect, bridge.yearbuilt,
D-19
R E P O R T
R E F E R E N C E
bridge.yearrecon, bridge.servtypon, bridge.servtypund, roadway.lanes, bridge.sumlanes, roadway.bypasslen, roadway.adttotal, roadway.truckpct, roadway.adtyear, bridge.maxspan, bridge.length, bridge.lftcurbsw, bridge.rtcurbsw, roadway.roadwidth, bridge.deckwidth, roadway.aroadwidth, bridge.bridgemed, bridge.deck_area, bridge.skew, bridge.strflared, bridge.vclrover, bridge.refvuc, bridge.vclrunder, bridge.refhuc, bridge.hclrurt, bridge.hclrult, inspevnt.inspkey, inspevnt.inspdate, inspevnt.nbinspdone, inspevnt.brinspfreq, inspevnt.lastinsp, inspevnt.nextinsp, inspevnt.fcinspdone, inspevnt.fcinspreq, inspevnt.fcinspfreq, inspevnt.fclastinsp, inspevnt.fcnextdate, inspevnt.uwinspdone, inspevnt.uwinspreq, inspevnt.uwinspfreq, inspevnt.uwlastinsp, inspevnt.uwnextdate, inspevnt.osinspdone, inspevnt.osinspreq, inspevnt.osinspfreq, inspevnt.oslastinsp, inspevnt.osnextdate, inspevnt.elinspdone,
D-20 AASHTO Pontis Users Manual
R E P O R T
R E F E R E N C E
inspevnt.elinspfreq, inspevnt.elinspdate, inspevnt.elnextdate, roadway.defhwy, bridge.paralstruc, roadway.trafficdir, bridge.tempstruc, roadway.nhs_ind, bridge.nbislen, roadway.tollfac, roadway.funcclass, bridge.histsign, bridge.owner, bridge.custodian, inspevnt.dkrating, inspevnt.suprating, inspevnt.subrating, inspevnt.culvrating, inspevnt.chanrating, bridge.irtype, bridge.ortype, bridge.irload, bridge.orload, bridge.designload, bridge.posting, inspevnt.oppostcl, inspevnt.railrating, inspevnt.arailratin, inspevnt.transratin, inspevnt.aendrating, inspevnt.strrating, inspevnt.deckgeom, inspevnt.underclr, inspevnt.wateradeq, inspevnt.appralign, inspevnt.scourcrit, bridge.nbiimpcost, bridge.propwork, bridge.nbirwcost, bridge.implen, bridge.nbitotcost, roadway.adtfuture, bridge.nbiyrcost, roadway.adtfutyear, bridge.navcntrol, bridge.navvc, bridge.navhc, inspevnt.pierprot,
AASHTO Pontis Users Manual D-21
R E P O R T
R E F E R E N C E
bridge.lftbrnavcl FROM bridge, roadway, inspevnt WHERE ( roadway.brkey = bridge.brkey ) and ( inspevnt.brkey = bridge.brkey ) and ( inspevnt.inspkey = (select max(inspkey) from inspevnt i where i.brkey = bridge.brkey and i.inspdate = (select max(inspdate) from inspevnt j where j.brkey = bridge.brkey))) and ( roadway.on_under = (select min(on_under) from roadway r where roadway.brkey = r.brkey ))
Headquarter Element Report
SELECT structure_unit.strunitlabel, elemdefs.elemnum, envtdefs.envtnum, elemdefs.elemkey, eleminsp.pctstate2, eleminsp.qtystate2, eleminsp.pctstate3, eleminsp.qtystate3, eleminsp.pctstate4, eleminsp.qtystate4, eleminsp.pctstate5, eleminsp.qtystate5, eleminsp.pctstate1, eleminsp.qtystate1, elemdefs.paircode as unitsmet FROM eleminsp, elemdefs, envtdefs, structure_unit WHERE ( elemdefs.elemkey = eleminsp.elemkey )and ( envtdefs.envkey = eleminsp.envkey) and ( structure_unit.brkey = eleminsp.brkey) and ( structure_unit.strunitkey = eleminsp.strunitkey) and ( ( eleminsp.brkey = :bridgenumb ) AND ( eleminsp.inspkey = :as_inspkey ) )
D-22
R E P O R T
R E F E R E N C E
Computed Fields
ProfileString ("PONTIS44.INI", "Site", "Department", ' ') ProfileString ("PONTIS44.INI", "Site", "Office", ' ') ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') if(inspevnt_nbinspdone = "1", string(inspevnt_inspdate) , string(inspevnt_lastinsp)) if(inspevnt_fcinspreq = "Y", string(inspevnt_fcinspfreq, "### months") , "NA") if(inspevnt_fcinspdone = "1", string(inspevnt_inspdate), if(inspevnt_fcinspreq = "Y", string(inspevnt_fclastinsp), "NA")) if(inspevnt_fcinspreq = "Y", string(inspevnt_fcnextdate), "NA") if(inspevnt_uwinspreq = "Y", string(inspevnt_uwinspfreq, "## months"), "NA") if(inspevnt_uwinspdone = '1', string(inspevnt_inspdate), if(inspevnt_uwinspreq = "Y", string( inspevnt_uwlastinsp), "NA")) if(inspevnt_uwinspreq = "Y", string(inspevnt_uwnextdate), "NA") if(inspevnt_osinspreq = "Y", string(inspevnt_osinspfreq, "## months"), "NA") if(inspevnt_osinspdone = "1", string(inspevnt_inspdate) , if(inspevnt_osinspreq = "Y", string(inspevnt_oslastinsp) , "NA")) if(inspevnt_osinspreq = "Y", string(inspevnt_osnextdate) , "NA") if( roadway_on_under = "1", string( roadway_lanes , "0#"), "Unknown") bridge_irload/1.8 bridge_orload/1.8 Describe ("DataWindow.Print.DocumentName") "Page" + page() + " of " + pagecount () left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]") string( elemdefs_elemnum ,"")+"/"+string( envtdefs_envtnum ,"")
D-23
R E P O R T
R E F E R E N C E
Retrieval Criteria
brkey (bridge key)
Report Definitions
SELECT bridge.brkey, bridge.bridge_id, bridge.struct_num, inspevnt.suff_rate, bridge.fips_state, bridge.facility, bridge.location, roadway.on_under, roadway.kind_hwy, roadway.levl_srvc, roadway.routenum, roadway.dirsuffix, bridge.bb_pct, bridge.district, bridge.county, bridge.placecode, roadway.kmpost, bridge.featint, bridge.latitude, bridge.longitude, bridge.nstatecode, bridge.bb_brdgeid, bridge.appspans, bridge.mainspans, bridge.materialmain, bridge.designmain, bridge.materialappr, bridge.designappr, bridge.dkstructyp, bridge.dksurftype, bridge.dkmembtype, bridge.dkprotect, bridge.yearbuilt,
D-24
R E P O R T
R E F E R E N C E
bridge.yearrecon, bridge.servtypon, bridge.servtypund, roadway.lanes, bridge.sumlanes, roadway.bypasslen, roadway.adttotal, roadway.truckpct, roadway.adtyear, bridge.maxspan, bridge.length, bridge.lftcurbsw, bridge.rtcurbsw, roadway.roadwidth, bridge.deckwidth, roadway.aroadwidth, bridge.bridgemed, bridge.deck_area, bridge.skew, bridge.strflared, bridge.vclrover, bridge.refvuc, bridge.vclrunder, bridge.refhuc, bridge.hclrurt, bridge.hclrult, inspevnt.inspkey, inspevnt.inspdate, inspevnt.nbinspdone, inspevnt.brinspfreq, inspevnt.lastinsp, inspevnt.nextinsp, inspevnt.fcinspdone, inspevnt.fcinspreq, inspevnt.fcinspfreq, inspevnt.fclastinsp, inspevnt.fcnextdate, inspevnt.uwinspdone, inspevnt.uwinspreq, inspevnt.uwinspfreq, inspevnt.uwlastinsp, inspevnt.uwnextdate, inspevnt.osinspdone, inspevnt.osinspreq, inspevnt.osinspfreq, inspevnt.oslastinsp, inspevnt.osnextdate, inspevnt.elinspdone,
AASHTO Pontis Users Manual D-25
R E P O R T
R E F E R E N C E
inspevnt.elinspfreq, inspevnt.elinspdate, inspevnt.elnextdate, roadway.defhwy, bridge.paralstruc, roadway.trafficdir, bridge.tempstruc, roadway.nhs_ind, bridge.nbislen, roadway.tollfac, roadway.funcclass, bridge.histsign, bridge.owner, bridge.custodian, inspevnt.dkrating, inspevnt.suprating, inspevnt.subrating, inspevnt.culvrating, inspevnt.chanrating, bridge.irtype, bridge.ortype, bridge.irload, bridge.orload, bridge.designload, bridge.posting, inspevnt.oppostcl, inspevnt.railrating, inspevnt.arailratin, inspevnt.transratin, inspevnt.aendrating, inspevnt.strrating, inspevnt.deckgeom, inspevnt.underclr, inspevnt.wateradeq, inspevnt.appralign, inspevnt.scourcrit, bridge.nbiimpcost, bridge.propwork, bridge.nbirwcost, bridge.implen, bridge.nbitotcost, roadway.adtfuture, bridge.nbiyrcost, roadway.adtfutyear, bridge.navcntrol, bridge.navvc, bridge.navhc, inspevnt.pierprot,
D-26 AASHTO Pontis Users Manual
R E P O R T
R E F E R E N C E
bridge.lftbrnavcl FROM bridge, roadway, inspevnt WHERE ( roadway.brkey = bridge.brkey ) and ( inspevnt.brkey = bridge.brkey ) and ( inspevnt.inspkey = (select max(inspkey) from inspevnt i where i.brkey = bridge.brkey and i.inspdate = (select max(inspdate) from inspevnt j where j.brkey = bridge.brkey))) and ( roadway.on_under = (select min(on_under) from roadway r where roadway.brkey = r.brkey ))
Element Inspection Information
SELECT structure_unit.strunitlabel, elemdefs.elemnum, eleminsp.elemkey, envtdefs.envtnum, eleminsp.notes FROM eleminsp, structure_unit, elemdefs, envtdefs WHERE (eleminsp.brkey = :bridgenumb ) and ( eleminsp.inspkey = :as_inspkey ) and ( structure_unit.brkey = eleminsp.brkey) and ( structure_unit.strunitkey = eleminsp.strunitkey) and ( elemdefs.elemkey = eleminsp.elemkey) and ( envtdefs.envkey = eleminsp.envkey)
Headquarters Element Report
SELECT structure_unit.strunitlabel, elemdefs.elemnum, envtdefs.envtnum, elemdefs.elemkey, eleminsp.pctstate2, eleminsp.qtystate2, eleminsp.pctstate3, eleminsp.qtystate3, eleminsp.pctstate4, eleminsp.qtystate4, eleminsp.pctstate5, eleminsp.qtystate5, eleminsp.pctstate1, eleminsp.qtystate1, elemdefs.paircode as unitsmet FROM eleminsp, elemdefs,
D-27
R E P O R T
R E F E R E N C E
envtdefs, structure_unit WHERE ( elemdefs.elemkey = eleminsp.elemkey )and ( envtdefs.envkey = eleminsp.envkey) and ( structure_unit.brkey = eleminsp.brkey) and ( structure_unit.strunitkey = eleminsp.strunitkey) and ( ( eleminsp.brkey = :bridgenumb ) AND ( eleminsp.inspkey = :as_inspkey ) )
Bridge Notes
SELECT inspevnt.inspdate, inspevnt.inspname, inspevnt.inspusrkey, inspevnt.notes, bridge.bridge_id, inspevnt.insptype, inspevnt.nbinspdone, inspevnt.elinspdone, inspevnt.uwinspdone, inspevnt.fcinspdone, inspevnt.osinspdone FROM inspevnt, bridge WHERE ( bridge.brkey = inspevnt.brkey ) and ( ( bridge.brkey = :bridgenumb ) ) ORDER BY inspevnt.inspdate DESC, inspevnt.insptype ASC
Work Candidates Report
D-28
R E P O R T
R E F E R E N C E
FROM insp_wcand, kind_code_labels kcl1, kind_code_labels kcl2 WHERE ( (kcl1.label_type = 'OB') and (kcl1.kind = insp_wcand.objkind ) and ( kcl1.code = insp_wcand.objcode ) ) and ( (kcl2.label_type = 'AC') and (kcl2.kind = insp_wcand.actkind) and ( kcl2.code = insp_wcand.actcode ) ) and ( insp_wcand.brkey = :bridgenumb )
Computed Fields
ProfileString ("PONTIS44.INI", "Site", "Department", ' ') ProfileString ("PONTIS44.INI", "Site", "Office", ' ') ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') if(inspevnt_nbinspdone = "1", string(inspevnt_inspdate) , string(inspevnt_lastinsp)) if(inspevnt_fcinspreq = "Y", string(inspevnt_fcinspfreq, "### months") , "NA") if(inspevnt_fcinspdone = "1", string(inspevnt_inspdate), if(inspevnt_fcinspreq = "Y", string(inspevnt_fclastinsp), "NA")) if(inspevnt_fcinspreq = "Y", string(inspevnt_fcnextdate), "NA") if(inspevnt_uwinspreq = "Y", string(inspevnt_uwinspfreq, "## months"), "NA") if(inspevnt_uwinspdone = '1', string(inspevnt_inspdate), if(inspevnt_uwinspreq = "Y", string( inspevnt_uwlastinsp), "NA")) if(inspevnt_uwinspreq = "Y", string(inspevnt_uwnextdate), "NA") if(inspevnt_osinspreq = "Y", string(inspevnt_osinspfreq, "## months"), "NA") if(inspevnt_osinspdone = "1", string(inspevnt_inspdate) , if(inspevnt_osinspreq = "Y", string(inspevnt_oslastinsp) , "NA")) if(inspevnt_osinspreq = "Y", string(inspevnt_osnextdate) , "NA") if( roadway_on_under = "1", string( roadway_lanes , "0#"), "Unknown") bridge_irload/1.8 bridge_orload/1.8 if( insp_wcand_assigned = 1, 'Yes', 'No') Describe ("DataWindow.Print.DocumentName") "Page" + page() + " of " + pagecount () left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]") string( elemdefs_elemnum ,"")+"/"+string( envtdefs_envtnum ,"")
D-29
R E P O R T
R E F E R E N C E
Retrieval Criteria
brkey (bridge key)
Report Definitions
SELECT inspevnt.inspkey, inspevnt.inspdate, bridge.brkey, inspevnt.inspname, inspevnt.nbinspdone, inspevnt.lastinsp, inspevnt.brinspfreq, inspevnt.nextinsp, inspevnt.uwinspdone, inspevnt.uwlastinsp, inspevnt.uwinspreq, inspevnt.uwinspfreq, inspevnt.uwnextdate, inspevnt.fcinspdone, inspevnt.fclastinsp, inspevnt.fcinspreq, inspevnt.fcinspfreq, inspevnt.fcnextdate, inspevnt.osinspdone, inspevnt.oslastinsp, inspevnt.osinspreq, inspevnt.osinspfreq, inspevnt.osnextdate, bridge.district, bridge.bridge_id, bridge.owner, bridge.custodian, bridge.adminarea, bridge.facility FROM inspevnt, bridge
D-30
R E P O R T
R E F E R E N C E
WHERE ( inspevnt.brkey = bridge.brkey ) and ( inspevnt.inspkey = (select max(inspkey) from inspevnt i where i.brkey = bridge.brkey and i.inspdate = (select max(inspdate) from inspevnt j where j.brkey = bridge.brkey))) ORDER BY bridge.bridge_id ASC
Computed Fields
ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') ProfileString ("PONTIS44.INI", "Site", "Office", ' ') ProfileString ("PONTIS44.INI", "Site", "Department", ' ') if( inspevnt_nbinspdone = '1', inspdate , inspevnt_lastinsp ) if( inspevnt_brinspfreq <> -1, string(inspevnt_brinspfreq,"###"), "NA") if( inspevnt_uwinspdone = '1', inspdate , inspevnt_uwlastinsp ) if(inspevnt_uwinspfreq > -1, string(inspevnt_uwinspfreq, '##'), 'NA') if(inspevnt_fcinspdone = '1', inspdate, inspevnt_fclastinsp) if(inspevnt_fcinspfreq > -1, string(inspevnt_fcinspfreq, '##'), 'NA') if(inspevnt_osinspdone = '1', inspdate, inspevnt_oslastinsp) if(inspevnt_osinspfreq > -1, string(inspevnt_osinspfreq, '##'), 'NA') count (bridge_id for all) left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]") "Page" + page() + " of " + pagecount () Describe ("DataWindow.Print.DocumentName")
D-31
R E P O R T
R E F E R E N C E
Retrieval Criteria
brkey (bridge key)
Report Definitions
SELECT bridge.brkey, inspevnt.inspdate, inspevnt.nbinspdone, inspevnt.lastinsp, inspevnt.brinspfreq, inspevnt.nextinsp, bridge.crewhrs, bridge.flaggerhrs, bridge.helperhrs, bridge.snooperhrs, bridge.spcrewhrs, bridge.spequiphrs, bridge.bridge_id, bridge.facility FROM bridge, inspevnt WHERE (( bridge.crewhrs > -1 ) OR ( bridge.flaggerhrs > -1 ) OR ( bridge.helperhrs > -1 ) OR ( bridge.snooperhrs > -1 ) OR ( bridge.spcrewhrs > -1 ) OR ( bridge.spequiphrs > -1 )) AND ( inspevnt.brkey = bridge.brkey ) AND ( inspevnt.inspkey = (select max(inspkey) from inspevnt i where i.brkey = bridge.brkey and i.inspdate = (select max(inspdate) from inspevnt j where j.brkey = bridge.brkey))) ORDER BY bridge.bridge_id ASC
Computed Fields
ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') ProfileString ("PONTIS44.INI", "Site", "Department", ' ') ProfileString ("PONTIS44.INI", "Site", "Office", ' ')
D-32 AASHTO Pontis Users Manual
R E P O R T
R E F E R E N C E
if( inspevnt_nbinspdone = '1', inspevnt_inspdate , inspevnt_lastinsp ) count (bridge_bridge_id for all) Describe ("DataWindow.Print.DocumentName") left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]") "Page" + page() + " of " + pagecount ()
D-33
R E P O R T
R E F E R E N C E
The health index is calculated as the sum of the current value of all condition units divided by the sum of total value of all condition units. A health index of 100% indicates that all of the condition units of the structure are in the best possible condition state. A health index of 0% indicates that all of the condition units are in the worst possible condition state.
Retrieval Criteria
brkey (bridge key)
Report Definitions
SELECT bridge.bridge_id, eleminsp.strunitkey, eleminsp.elemkey, eleminsp.envkey, eleminsp.quantity, inspevnt.inspdate, inspevnt.inspkey, eleminsp.qtystate1,
D-34
R E P O R T
R E F E R E N C E
eleminsp.qtystate2, eleminsp.qtystate3, eleminsp.qtystate4, eleminsp.qtystate5, elemdefs.statecnt, elemdefs.elemnum, condumdl.failagcyco, elemdefs.elemweight * max(statmdls.varunitco) as unitvalue, scenparam.scparamvalue, bridge.brkey FROM bridge, condumdl, elemdefs, eleminsp, inspevnt, coptions, scenparam, statmdls WHERE ( bridge.brkey = inspevnt.brkey ) and ( bridge.brkey = eleminsp.brkey ) and ( inspevnt.inspkey = (select max(inspkey) from inspevnt i where i.brkey = bridge.brkey and i.inspdate = (select max(inspdate) from inspevnt j where j.brkey=bridge.brkey and j.elinspdone='1' ))) and ( inspevnt.inspkey = eleminsp.inspkey ) and ( eleminsp.elemkey = elemdefs.elemkey ) and ( eleminsp.elemkey = condumdl.elemkey ) and ( eleminsp.envkey = condumdl.envkey ) and ( elemdefs.smartflag = '0') and (condumdl.mokey = '00') and ( coptions.optionname = 'DEFAULT_SCENARIO') and ( scenparam.sckey = coptions.optionval) and ( scenparam.scparam = 'EW') and ( statmdls.mokey = '00') and (statmdls.elemkey = eleminsp.elemkey) and ( statmdls.envkey = eleminsp.envkey) GROUP BY bridge.bridge_id, eleminsp.strunitkey, eleminsp.elemkey, eleminsp.envkey, eleminsp.quantity, inspevnt.inspdate, inspevnt.inspkey, eleminsp.qtystate1, eleminsp.qtystate2,
AASHTO Pontis Users Manual D-35
R E P O R T
R E F E R E N C E
eleminsp.qtystate3, eleminsp.qtystate4, eleminsp.qtystate5, elemdefs.statecnt, elemdefs.elemnum, condumdl.failagcyco, scenparam.scparamvalue, elemdefs.elemweight, bridge.brkey ORDER BY bridge.bridge_id ASC, eleminsp.strunitkey ASC, elemdefs.elemnum ASC, eleminsp.envkey ASC
Computed Fields
ProfileString ("PONTIS44.INI", "Site", "Department", ' ') ProfileString ("PONTIS44.INI", "Site", "Office", ' ') ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') eleminsp_elemkey +'/'+ eleminsp_envkey eleminsp_qtystate1 / eleminsp_quantity *100 eleminsp_qtystate2 / eleminsp_quantity *100 eleminsp_qtystate3 / eleminsp_quantity *100 eleminsp_qtystate4 / eleminsp_quantity *100 eleminsp_qtystate5 / eleminsp_quantity *100 if(scenparam_scparamvalue = 'FAILCOST', condumdl_failagcyco, unitvalue) eleminsp_quantity * elemunitvalue eleminsp_qtystate1 / eleminsp_quantity (eleminsp_qtystate2 * (1 - (1 / (elemdefs_statecnt - 1)))) / (eleminsp_quantity) (eleminsp_qtystate3 * (1 - (2 * (1 / (elemdefs_statecnt - 1))))) / eleminsp_quantity (eleminsp_qtystate4 * (1 - (3 * (1 / (elemdefs_statecnt - 1))))) / eleminsp_quantity (eleminsp_qtystate5 * (1 - (4 * (1 / (elemdefs_statecnt - 1))))) / eleminsp_quantity hlth_cs1 + hlth_cs2 + hlth_cs3 + hlth_cs4 + hlth_cs5 tev * tot_elm_hlth (cumulativeSum(cev for group 1) / cumulativeSum(tev for group 1)) cumulativeSum(tev for group 1) cumulativeSum(cev for group 1) "Page" + page() + " of " + pagecount () left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]") Describe ("DataWindow.Print.DocumentName") f_get_currency_symbol ()
D-36
R E P O R T
R E F E R E N C E
Retrieval Criteria
elemdefs_elemnum (element number)
Report Definitions
SELECT b.elemkey, b.envkey, count(b.brkey), sum(b.quantity), sum(b.qtystate1), sum(b.qtystate2), sum(b.qtystate3), sum(b.qtystate4), sum(b.qtystate5), elemdefs.elemnum, elemdefs.paircode as unitsmet, elemdefs.statecnt FROM eleminsp b, elemdefs WHERE ( elemdefs.elemkey = b.elemkey ) and ( ( b.inspkey = (select max(i.inspkey) from inspevnt i where (i.brkey = b.brkey) and (i.inspdate = (select max(inspdate) from inspevnt g where g.brkey=b.brkey and g.elinspdone='1'))) ) ) GROUP BY b.elemkey, b.envkey, elemdefs.elemnum, elemdefs.statecnt, unitsmet ORDER BY elemdefs.elemnum ASC, b.envkey ASC
D-37
R E P O R T
R E F E R E N C E
Computed Fields
ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') ProfileString ("PONTIS44.INI", "Site", "Department", ' ') ProfileString ("PONTIS44.INI", "Site", "Office", ' ') sum_qtystate1 / sum_b_quantity sum_qtystate2 / sum_b_quantity sum_qtystate3 / sum_b_quantity sum_qtystate4 / sum_b_quantity sum_qtystate5 / sum_b_quantity sum(sum_b_quantity for group 1) sum(sum_qtystate1 for group 1) sum(sum_qtystate1 for group 1) / sum(sum_b_quantity for group 1) sum(sum_qtystate2 for group 1) sum(sum_qtystate2 for group 1) / sum(sum_b_quantity for group 1) sum(sum_qtystate3 for group 1) sum(sum_qtystate3 for group 1) / sum(sum_b_quantity for group 1) sum(sum_qtystate4 for group 1) sum(sum_qtystate4 for group 1) / sum(sum_b_quantity for group 1) sum(sum_qtystate5 for group 1) sum(sum_qtystate5 for group 1) / sum(sum_b_quantity for group 1) Describe ("DataWindow.Print.DocumentName") left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]") "Page" + page() + " of " + pagecount ()
D-38
R E P O R T
R E F E R E N C E
Retrieval Criteria
brkey (bridge key)
Report Definitions
SELECT bridge.brkey, bridge.bridge_id, bridge.struct_num, inspevnt.suff_rate, bridge.fips_state, bridge.facility, bridge.location, roadway.on_under, roadway.kind_hwy, roadway.levl_srvc, roadway.routenum, roadway.dirsuffix, bridge.bb_pct, bridge.district, bridge.county, bridge.placecode, roadway.kmpost / 1.609344 as milepost, bridge.featint, bridge.latitude, bridge.longitude, bridge.nstatecode, bridge.bb_brdgeid, bridge.appspans, bridge.mainspans, bridge.materialmain, bridge.designmain, bridge.materialappr, bridge.designappr, bridge.dkstructyp, bridge.dksurftype, bridge.dkmembtype, bridge.dkprotect, bridge.yearbuilt,
D-39
R E P O R T
R E F E R E N C E
bridge.yearrecon, bridge.servtypon, bridge.servtypund, roadway.lanes, bridge.sumlanes, roadway.bypasslen / 1.609344 as bypasslen_eng, roadway.adttotal, roadway.truckpct, roadway.adtyear, bridge.maxspan / 0.3048 as maxspan_eng, bridge.length / 0.3048 as length_eng, bridge.lftcurbsw / 0.3048 as lftcurbsw_eng, bridge.rtcurbsw / 0.3048 as rtcurbsw_eng, roadway.roadwidth / 0.3048 as roadwidth_eng, bridge.deckwidth / 0.3048 as deckwidth_eng, roadway.aroadwidth / 0.3048 as aroadwidth_eng, bridge.bridgemed, bridge.deck_area / 0.09290304 as deck_area_eng, bridge.skew, bridge.strflared, bridge.vclrover / 0.3048 as vclrover_eng, bridge.refvuc, bridge.vclrunder / 0.3048 as vclrunder_eng, bridge.refhuc, bridge.hclrurt / 0.3048 as hclrurt_eng, bridge.hclrult / 0.3048 as hclrult_eng, inspevnt.inspkey, inspevnt.inspdate, inspevnt.nbinspdone, inspevnt.brinspfreq, inspevnt.lastinsp, inspevnt.nextinsp, inspevnt.fcinspdone, inspevnt.fcinspreq, inspevnt.fcinspfreq, inspevnt.fcnextdate, inspevnt.fclastinsp, inspevnt.uwinspdone, inspevnt.uwinspreq, inspevnt.uwinspfreq, inspevnt.uwlastinsp, inspevnt.uwnextdate, inspevnt.osinspdone, inspevnt.osinspreq, inspevnt.osinspfreq, inspevnt.oslastinsp, inspevnt.osnextdate, inspevnt.elinspdone,
D-40 AASHTO Pontis Users Manual
R E P O R T
R E F E R E N C E
inspevnt.elinspfreq, inspevnt.elinspdate, inspevnt.elnextdate, roadway.defhwy, bridge.paralstruc, roadway.trafficdir, bridge.tempstruc, roadway.nhs_ind, bridge.nbislen, roadway.tollfac, roadway.funcclass, bridge.histsign, bridge.owner, bridge.custodian, inspevnt.dkrating, inspevnt.suprating, inspevnt.subrating, inspevnt.culvrating, inspevnt.chanrating, bridge.irtype, bridge.ortype, bridge.irload, bridge.orload, bridge.designload, bridge.posting, inspevnt.oppostcl, inspevnt.railrating, inspevnt.arailratin, inspevnt.transratin, inspevnt.aendrating, inspevnt.strrating, inspevnt.deckgeom, inspevnt.underclr, inspevnt.wateradeq, inspevnt.appralign, inspevnt.scourcrit, bridge.nbiimpcost, bridge.propwork, bridge.nbirwcost, bridge.implen / 0.3048 as implen_eng, bridge.nbitotcost, roadway.adtfuture, bridge.nbiyrcost, roadway.adtfutyear, bridge.navcntrol, bridge.navvc / 0.3048 as navvc_eng, bridge.navhc / 0.3048 as navhc_eng, inspevnt.pierprot,
AASHTO Pontis Users Manual D-41
R E P O R T
R E F E R E N C E
bridge.lftbrnavcl / 0.3048 as lftbrnavcl_eng FROM bridge, roadway, inspevnt WHERE ( roadway.brkey = bridge.brkey ) and ( inspevnt.brkey = bridge.brkey ) and ( inspevnt.inspkey = (select max(inspkey) from inspevnt i where i.brkey = bridge.brkey and i.inspdate = (select max(inspdate) from inspevnt j where j.brkey = bridge.brkey))) and ( roadway.on_under = (select min(on_under) from roadway r where roadway.brkey = r.brkey ))
Headquarter Element Report
SELECT structure_unit.strunitlabel, elemdefs.elemnum, envtdefs.envtnum, elemdefs.elemkey, eleminsp.pctstate2, eleminsp.qtystate2 / p.factor as qtystate2, eleminsp.pctstate3, eleminsp.qtystate3 / p.factor as qtystate3, eleminsp.pctstate4, eleminsp.qtystate4 / p.factor as qtystate4, eleminsp.pctstate5, eleminsp.qtystate5 / p.factor as qtystate5, eleminsp.pctstate1, eleminsp.qtystate1 / p.factor as qtystate1, elemdefs.paircode AS unitsmet FROM eleminsp, elemdefs, envtdefs, structure_unit, metric_english p WHERE ( elemdefs.elemkey = eleminsp.elemkey and p.paircode = elemdefs.paircode) and ( envtdefs.envkey = eleminsp.envkey) and ( structure_unit.brkey = eleminsp.brkey) and ( structure_unit.strunitkey = eleminsp.strunitkey) and ( ( eleminsp.brkey = :bridgenumb ) AND ( eleminsp.inspkey = :as_inspkey ) )
D-42
R E P O R T
R E F E R E N C E
Computed Fields
ProfileString ("PONTIS44.INI", "Site", "Department", ' ') ProfileString ("PONTIS44.INI", "Site", "Office", ' ') ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') if(inspevnt_nbinspdone = "1", string(inspevnt_inspdate) , string(inspevnt_lastinsp)) if(inspevnt_fcinspreq = "Y", string(inspevnt_fcinspfreq, "### months") , "NA") if(inspevnt_fcinspdone = "1", string(inspevnt_inspdate), if(inspevnt_fcinspreq = "Y", string(inspevnt_fclastinsp), "NA")) if(inspevnt_fcinspreq = "Y", string(inspevnt_fcnextdate), "NA") if(inspevnt_uwinspreq = "Y", string(inspevnt_uwinspfreq, "## months"), "NA") if(inspevnt_uwinspdone = '1', string(inspevnt_inspdate), if(inspevnt_uwinspreq = "Y", string( inspevnt_uwlastinsp), "NA")) if(inspevnt_uwinspreq = "Y", string(inspevnt_uwnextdate), "NA") if(inspevnt_osinspreq = "Y", string(inspevnt_osinspfreq, "## months"), "NA") if(inspevnt_osinspdone = "1", string(inspevnt_inspdate) , if(inspevnt_osinspreq = "Y", string(inspevnt_oslastinsp) , "NA")) if(inspevnt_osinspreq = "Y", string(inspevnt_osnextdate) , "NA") if( roadway_on_under = "1", string( roadway_lanes , "0#"), "Unknown") bridge_irload/1.8/0.9072 bridge_orload/1.8/0.9072 Describe ("DataWindow.Print.DocumentName") "Page" + page() + " of " + pagecount () left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]") string( elemdefs_elemnum ,"")+"/"+string( envtdefs_envtnum ,"")
D-43
R E P O R T
R E F E R E N C E
Retrieval Criteria
brkey (bridge key)
Report Definitions
SELECT bridge.brkey, bridge.bridge_id, bridge.struct_num, inspevnt.suff_rate, bridge.fips_state, bridge.facility, bridge.location, roadway.on_under, roadway.kind_hwy, roadway.levl_srvc, roadway.routenum, roadway.dirsuffix, bridge.bb_pct, bridge.district, bridge.county, bridge.placecode, roadway.kmpost / 1.609344 as milepost, bridge.featint, bridge.latitude, bridge.longitude, bridge.nstatecode, bridge.bb_brdgeid, bridge.appspans, bridge.mainspans, bridge.materialmain, bridge.designmain, bridge.materialappr, bridge.designappr, bridge.dkstructyp, bridge.dksurftype, bridge.dkmembtype, bridge.dkprotect, bridge.yearbuilt,
D-44
R E P O R T
R E F E R E N C E
bridge.yearrecon, bridge.servtypon, bridge.servtypund, roadway.lanes, bridge.sumlanes, roadway.bypasslen / 1.609344 as bypasslen_eng, roadway.adttotal, roadway.truckpct, roadway.adtyear, bridge.maxspan / 0.3048 as maxspan_eng, bridge.length / 0.3048 as length_eng, bridge.lftcurbsw / 0.3048 as lftcurbsw_eng, bridge.rtcurbsw / 0.3048 as rtcurbsw_eng, roadway.roadwidth / 0.3048 as roadwidth_eng, bridge.deckwidth / 0.3048 as deckwidth_eng, roadway.aroadwidth / 0.3048 as aroadwidth_eng, bridge.bridgemed, bridge.deck_area / 0.09290304 as deck_area_eng, bridge.skew, bridge.strflared, bridge.vclrover / 0.3048 as vclrover_eng, bridge.refvuc, bridge.vclrunder / 0.3048 as vclrunder_eng, bridge.refhuc, bridge.hclrurt / 0.3048 as hclrurt_eng, bridge.hclrult / 0.3048 as hclrult_eng, inspevnt.inspkey, inspevnt.inspdate, inspevnt.nbinspdone, inspevnt.brinspfreq, inspevnt.lastinsp, inspevnt.nextinsp, inspevnt.fcinspdone, inspevnt.fcinspreq, inspevnt.fcinspfreq, inspevnt.fcnextdate, inspevnt.fclastinsp, inspevnt.uwinspdone, inspevnt.uwinspreq, inspevnt.uwinspfreq, inspevnt.uwlastinsp, inspevnt.uwnextdate, inspevnt.osinspdone, inspevnt.osinspreq, inspevnt.osinspfreq, inspevnt.oslastinsp, inspevnt.osnextdate, inspevnt.elinspdone,
AASHTO Pontis Users Manual D-45
R E P O R T
R E F E R E N C E
inspevnt.elinspfreq, inspevnt.elinspdate, inspevnt.elnextdate, roadway.defhwy, bridge.paralstruc, roadway.trafficdir, bridge.tempstruc, roadway.nhs_ind, bridge.nbislen, roadway.tollfac, roadway.funcclass, bridge.histsign, bridge.owner, bridge.custodian, inspevnt.dkrating, inspevnt.suprating, inspevnt.subrating, inspevnt.culvrating, inspevnt.chanrating, bridge.irtype, bridge.ortype, bridge.irload, bridge.orload, bridge.designload, bridge.posting, inspevnt.oppostcl, inspevnt.railrating, inspevnt.arailratin, inspevnt.transratin, inspevnt.aendrating, inspevnt.strrating, inspevnt.deckgeom, inspevnt.underclr, inspevnt.wateradeq, inspevnt.appralign, inspevnt.scourcrit, bridge.nbiimpcost, bridge.propwork, bridge.nbirwcost, bridge.implen / 0.3048 as implen_eng, bridge.nbitotcost, roadway.adtfuture, bridge.nbiyrcost, roadway.adtfutyear, bridge.navcntrol, bridge.navvc / 0.3048 as navvc_eng, bridge.navhc / 0.3048 as navhc_eng, inspevnt.pierprot,
D-46 AASHTO Pontis Users Manual
R E P O R T
R E F E R E N C E
bridge.lftbrnavcl / 0.3048 as lftbrnavcl_eng FROM bridge, roadway, inspevnt WHERE ( roadway.brkey = bridge.brkey ) and ( inspevnt.brkey = bridge.brkey ) and ( inspevnt.inspkey = (select max(inspkey) from inspevnt i where i.brkey = bridge.brkey and i.inspdate = (select max(inspdate) from inspevnt j where j.brkey = bridge.brkey))) and ( roadway.on_under = (select min(on_under) from roadway r where roadway.brkey = r.brkey ))
Headquarter Element Report
SELECT structure_unit.strunitlabel, elemdefs.elemnum, envtdefs.envtnum, elemdefs.elemkey, eleminsp.pctstate2, eleminsp.qtystate2 / p.factor as qtystate2, eleminsp.pctstate3, eleminsp.qtystate3 / p.factor as qtystate3, eleminsp.pctstate4, eleminsp.qtystate4 / p.factor as qtystate4, eleminsp.pctstate5, eleminsp.qtystate5 / p.factor as qtystate5, eleminsp.pctstate1, eleminsp.qtystate1 / p.factor as qtystate1, elemdefs.paircode AS unitsmet FROM eleminsp, elemdefs, envtdefs, structure_unit, metric_english p WHERE ( elemdefs.elemkey = eleminsp.elemkey and p.paircode = elemdefs.paircode) and ( envtdefs.envkey = eleminsp.envkey) and ( structure_unit.brkey = eleminsp.brkey) and ( structure_unit.strunitkey = eleminsp.strunitkey) and ( ( eleminsp.brkey = :bridgenumb ) AND ( eleminsp.inspkey = :as_inspkey ) )
Element Inspection Information
D-47
R E P O R T
R E F E R E N C E
FROM eleminsp, structure_unit, elemdefs, envtdefs WHERE (eleminsp.brkey = :bridgenumb ) and ( eleminsp.inspkey = :as_inspkey ) and ( structure_unit.brkey = eleminsp.brkey) and ( structure_unit.strunitkey = eleminsp.strunitkey) and ( elemdefs.elemkey = eleminsp.elemkey) and ( envtdefs.envkey = eleminsp.envkey)
Bridge Notes
SELECT inspevnt.inspdate, inspevnt.inspname, inspevnt.inspusrkey, inspevnt.notes, bridge.bridge_id, inspevnt.insptype, inspevnt.nbinspdone, inspevnt.elinspdone, inspevnt.uwinspdone, inspevnt.fcinspdone, inspevnt.osinspdone FROM inspevnt, bridge WHERE ( bridge.brkey = inspevnt.brkey ) and ( ( bridge.brkey = :bridgenumb ) ) ORDER BY inspevnt.inspdate DESC, inspevnt.insptype ASC
Work Candidates Report
SELECT insp_wcand.wckey, insp_wcand.wc_id, kcl2.label, kcl1.label, insp_wcand.agency_status, insp_wcand.agency_priority, insp_wcand.assigned, insp_wcand.workrecdate FROM insp_wcand, kind_code_labels kcl1,
D-48
R E P O R T
R E F E R E N C E
kind_code_labels kcl2 WHERE ( (kcl1.label_type = 'OB') and (kcl1.kind = insp_wcand.objkind ) and ( kcl1.code = insp_wcand.objcode ) ) and ( (kcl2.label_type = 'AC') and (kcl2.kind = insp_wcand.actkind) and ( kcl2.code = insp_wcand.actcode ) ) and ( insp_wcand.brkey = :bridgenumb )
Computed Fields
ProfileString ("PONTIS44.INI", "Site", "Department", ' ') ProfileString ("PONTIS44.INI", "Site", "Office", ' ') ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') if(inspevnt_nbinspdone = "1", string(inspevnt_inspdate) , string(inspevnt_lastinsp)) if(inspevnt_fcinspreq = "Y", string(inspevnt_fcinspfreq, "### months") , "NA") if(inspevnt_fcinspdone = "1", string(inspevnt_inspdate), if(inspevnt_fcinspreq = "Y", string(inspevnt_fclastinsp), "NA")) if(inspevnt_fcinspreq = "Y", string(inspevnt_fcnextdate), "NA") if(inspevnt_uwinspreq = "Y", string(inspevnt_uwinspfreq, "## months"), "NA") if(inspevnt_uwinspdone = '1', string(inspevnt_inspdate), if(inspevnt_uwinspreq = "Y", string( inspevnt_uwlastinsp), "NA")) if(inspevnt_uwinspreq = "Y", string(inspevnt_uwnextdate), "NA") if(inspevnt_osinspreq = "Y", string(inspevnt_osinspfreq, "## months"), "NA") if(inspevnt_osinspdone = "1", string(inspevnt_inspdate) , if(inspevnt_osinspreq = "Y", string(inspevnt_oslastinsp) , "NA")) if(inspevnt_osinspreq = "Y", string(inspevnt_osnextdate) , "NA") if( roadway_on_under = "1", string( roadway_lanes , "0#"), "Unknown") bridge_irload/1.8/0.9072 bridge_orload/1.8/0.9072 if( insp_wcand_assigned = 1, 'Yes', 'No') Describe ("DataWindow.Print.DocumentName") "Page" + page() + " of " + pagecount () left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]") string( elemdefs_elemnum ,"")+"/"+string( envtdefs_envtnum ,"")
D-49
R E P O R T
R E F E R E N C E
Retrieval Criteria
elemdefs_elemnum (element number)
Report Definitions
SELECT b.elemkey, b.envkey, count(b.brkey), sum(b.quantity / p.factor), sum(b.qtystate1 / p.factor), sum(b.qtystate2 / p.factor), sum(b.qtystate3 / p.factor), sum(b.qtystate4 / p.factor), sum(b.qtystate5 / p.factor), d.elemnum, p.englishunit, d.statecnt FROM eleminsp b, elemdefs d, metric_english p WHERE ( d.elemkey = b.elemkey ) and ( p.paircode = d.paircode ) and ( ( b.inspkey = (select max(i.inspkey) from inspevnt i where (i.brkey = b.brkey) and (i.inspdate = (select max(inspdate) from inspevnt g where g.brkey=b.brkey and g.elinspdone='1'))) ) ) GROUP BY b.elemkey, b.envkey, d.elemnum, d.statecnt, p.englishunit ORDER BY d.elemnum ASC, b.envkey ASC
D-50
R E P O R T
R E F E R E N C E
Computed Fields
ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') ProfileString ("PONTIS44.INI", "Site", "Department", ' ') ProfileString ("PONTIS44.INI", "Site", "Office", ' ') sum_qtystate1 / sum_b_quantity sum_qtystate2 / sum_b_quantity sum_qtystate3 / sum_b_quantity sum_qtystate4 / sum_b_quantity sum_qtystate5 / sum_b_quantity sum(sum_b_quantity for group 1) sum(sum_qtystate1 for group 1) sum(sum_qtystate1 for group 1) / sum(sum_b_quantity for group 1) sum(sum_qtystate2 for group 1) sum(sum_qtystate2 for group 1) / sum(sum_b_quantity for group 1) sum(sum_qtystate3 for group 1) sum(sum_qtystate3 for group 1) / sum(sum_b_quantity for group 1) sum(sum_qtystate4 for group 1) sum(sum_qtystate4 for group 1) / sum(sum_b_quantity for group 1) sum(sum_qtystate5 for group 1) sum(sum_qtystate5 for group 1) / sum(sum_b_quantity for group 1) Describe ("DataWindow.Print.DocumentName") left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]") "Page" + page() + " of " + pagecount ()
D-51
R E P O R T
R E F E R E N C E
Report Definitions
SELECT bridge.brkey, bridge.bridge_id, bridge.facility, inspevnt.inspkey, inspevnt.nbi_rating, inspevnt.suff_rate, inspevnt.suff_prefx, inspevnt.dkrating, inspevnt.suprating, inspevnt.subrating, inspevnt.chanrating, inspevnt.culvrating FROM bridge, inspevnt WHERE ( bridge.brkey = inspevnt.brkey ) and ( inspevnt.inspkey = (select max(inspkey) from inspevnt i where i.brkey = bridge.brkey and i.inspdate = (select max(inspdate) from inspevnt j where j.brkey=bridge.brkey and j.nbinspdone='1' ))) ORDER BY bridge.bridge_id ASC
Computed Fields
ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') ProfileString ("PONTIS44.INI", "Site", "Department", ' ') ProfileString ("PONTIS44.INI", "Site", "Office", ' ') (cumulativeSum(cev for group 1) / cumulativeSum(tev for group 1)) * 100 Describe ("DataWindow.Print.DocumentName") "Page" + page() + " of " + pagecount () left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]")
D-52
R E P O R T
R E F E R E N C E
Report Definitions
SELECT elcatdfs.ecatname, matdefs.matlname, pont_work.ykey, sum(pont_work.agcycost) as mrrneeds, sum(pont_work.userbenf) as needsben, scenario.sckey, scenario.scenname, elcatdfs.ecatkey, matdefs.matlkey FROM pont_work, scenario, elcatdfs, elemdefs, matdefs WHERE ( scenario.sckey = :as_sckey) and ( pont_work.sckey = scenario.sckey ) and ( ( pont_work.objkind = '1' ) and ( elemdefs.elemkey+'' = pont_work.objcode ) ) and ( matdefs.matlkey = elemdefs.matlkey ) and ( elemdefs.ecatkey = elcatdfs.ecatkey ) and (( pont_work.pontwcstatus = 1 ) or ( pont_work.sysflag2 = '8') or ( pont_work.sysflag9 = '1' )) GROUP BY scenario.sckey, scenario.scenname, elcatdfs.ecatkey, elcatdfs.ecatname, matdefs.matlkey, matdefs.matlname, pont_work.ykey
D-53
R E P O R T
R E F E R E N C E
Computed Fields
ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') ProfileString ("PONTIS44.INI", "Site", "Department", ' ') ProfileString ("PONTIS44.INI", "Site", "Office", ' ') "MR&R Needs" + "(" + sCurrency + ")" "MR&R Benefits" + "(" + sCurrency + ")" sum (presrslt_mrrneeds for group 3) sum (presrslt_needsben for group 3) f_get_currency_symbol () Describe ("DataWindow.Print.DocumentName") "Page" + page() + " of " + pagecount () left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]")
D-54
R E P O R T
R E F E R E N C E
Retrieval Criteria
elemdefs_elemnum (element number) elemdefs_envtnum (environment number)
Report Definitions
SELECT condumdl.failprob, condumdl.failagcyco, condumdl.failuserco, condumdl.optyrcost, actmodls.mokey, actmodls.elemkey, actmodls.envkey, actmodls.skey, actmodls.akey, actmodls.prob1, actmodls.prob2, actmodls.prob3, actmodls.prob4,
D-55
R E P O R T
R E F E R E N C E
actmodls.prob5, actmodls.ltcost, actmodls.varunitco, statmdls.optfrac, statmdls.actrec, statmdls.unitben, statedfs.statenum, statedfs.stateshort, mrractdf.akey, mrractdf.actnum, mrractdf.actlong, elemdefs.elemnum, elemdefs.elemlong, elemdefs.paircode as costunits, elemdefs.scaleshort, elemdefs.scaleunit, elemdefs.scalemet, elemdefs.paircode as unitsmet, elemdefs.statecnt, envtdefs.envtnum, envtdefs.envtshort FROM condumdl, statmdls, actmodls, statedfs, mrractdf, elemdefs, envtdefs WHERE ( statmdls.mokey = actmodls.mokey ) and ( condumdl.mokey = actmodls.mokey ) and ( condumdl.elemkey = actmodls.elemkey ) and ( condumdl.envkey = actmodls.envkey ) and ( actmodls.elemkey = statmdls.elemkey ) and ( actmodls.envkey = statmdls.envkey ) and ( actmodls.skey = statmdls.skey ) and ( statedfs.elemkey = actmodls.elemkey ) and ( statedfs.skey = actmodls.skey ) and ( mrractdf.elemkey = actmodls.elemkey ) and ( mrractdf.skey = actmodls.skey ) and ( mrractdf.akey = actmodls.akey ) and ( elemdefs.elemkey = actmodls.elemkey ) and ( envtdefs.envkey = actmodls.envkey ) and ( actmodls.mokey = '00' ) ORDER BY actmodls.elemkey ASC, actmodls.envkey ASC, actmodls.skey ASC, actmodls.akey ASC
D-56
R E P O R T
R E F E R E N C E
Computed Fields
f_get_currency_symbol () ProfileString ("PONTIS44.INI", "Site", "Department", ' ') ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') ProfileString ("PONTIS44.INI", "Site", "Office", ' ') string (elemdefs_elemnum) + "(" + string (envtdefs_envtnum) + ")" elemdefs_elemlong + "(" + envtdefs_envtshort + ")" "Unit Cost" + "(" + sCurrency + ")" "Cost" + "(" + sCurrency + ")" "Long-Term Optimal Unit Cost" + "(" + sCurrency + ") :" "Element Failure Unit Costs" + "(" + sCurrency + ")" statmdls_optfrac * 100 if (actmodls_akey = statmdls_actrec, ">>", " ") Describe ("DataWindow.Print.DocumentName") "Page" + page() + " of " + pagecount () left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]")
D-57
R E P O R T
R E F E R E N C E
Retrieval Criteria
sckey (scenario key, programmed by Pontis) pont_work_ykey (program year) pont_work_pontwcstatus (programmed by Pontis) brkey (bridge key)
Report Definitions
SELECT bridge.brkey, bridge.bridge_id, bridge.facility, pont_work.witemkey, pont_work.strunitkey, pont_work.ykey, pont_work.pontwcstatus, pont_work.agcycost, pont_work.userbenf, pont_work.sckey, elemdefs.elemnum, elemdefs.elemshort, kind_code_labels.label FROM bridge, pont_work, elemdefs, kind_code_labels WHERE ( ( pont_work.sckey = :as_sckey ) and ( bridge.brkey = pont_work.brkey ) and ( pont_work.objkind = '1' ) and ( elemdefs.elemkey = pont_work.objcode ) and (( pont_work.pontwcstatus = 1 ) or ( pont_work.sysflag2 = '8' ) or ( pont_work.sysflag9 = '1' )) and ( kind_code_labels.label_type = 'AC' ) and
D-58
R E P O R T
R E F E R E N C E
SELECT structure_unit.brkey, structure_unit.strunitkey, structure_unit.strunitlabel, structure_unit.strunitdescription FROM structure_unit WHERE structure_unit.brkey = :as_brkey and structure_unit.strunitkey = :an_strunitkey
Computed Fields
ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') ProfileString ("PONTIS44.INI", "Site", "Department", ' ') ProfileString ("PONTIS44.INI", "Site", "Office", ' ') "Cost" + "(" + sCurrency + ")" "Benefit" + "(" + sCurrency + ")" f_get_currency_symbol () Describe ("DataWindow.Print.DocumentName") left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]") "Page" + page() + " of " + pagecount ()
D-59
R E P O R T
R E F E R E N C E
Retrieval Criteria
bridge_brkey (bridge key)
Report Definitions
SELECT bridge.brkey, bridge.bridge_id, bridge.facility FROM bridge WHERE bridge.brkey = bridge.brkey
Programmed Project List
SELECT bridge.brkey, bridge.bridge_id, bridge.facility, projects.projkey, projects.project_id, projects.proj_status, projects.progyear, projects.proj_status, prj_witems.witemkey, prj_witems.strunitkey, prj_witems.cost, prj_witems.benefit, k1.label as ob_label, k2.label as ac_label,
D-60
R E P O R T
R E F E R E N C E
prj_programs.prog_id FROM bridge, projects, prj_witems, prj_programs, kind_code_labels k1, kind_code_labels k2 WHERE ( bridge.brkey = prj_witems.brkey) and ( projects.projkey = prj_witems.projkey ) and ( prj_programs.progkey = projects.progkey ) and ( prj_witems.objkind = k1.kind ) and ( prj_witems.actkind = k2.kind ) and ( prj_witems.objcode = k1.code ) and ( prj_witems.actcode = k2.code ) and ( k1.label_type = 'OB' ) and ( k2.label_type = 'AC' ) and ( bridge.brkey = :as_brkey)
Inspector-Recommended Candidates List
SELECT insp_wcand.wckey, insp_wcand.wc_id, insp_wcand.brkey, insp_wcand.strunitkey, insp_wcand.agency_status, insp_wcand.agency_priority, insp_wcand.assigned, insp_wcand.workrecdate, k1.label as ob_label, k2.label as ac_label FROM insp_wcand, kind_code_labels k1, kind_code_labels k2 WHERE ( insp_wcand.objkind = k1.kind ) and ( insp_wcand.actkind = k2.kind ) and ( insp_wcand.objcode = k1.code ) and ( insp_wcand.actcode = k2.code ) and ( k1.label_type = 'OB' ) and ( k2.label_type = 'AC' ) and ( insp_wcand.brkey = :as_brkey)
Pontis-Generated Candidates List
D-61
R E P O R T
R E F E R E N C E
pont_work.agcycost, pont_work.userbenf, pont_work.pontwcstatus, pont_work.assigned, pont_work.sysflag3, k1.label as ob_label, k2.label as ac_label FROM scenario, pont_work, kind_code_labels k1, kind_code_labels k2 WHERE ( scenario.sckey = pont_work.sckey) and ( pont_work.objkind = k1.kind ) and ( pont_work.actkind = k2.kind ) and ( pont_work.objcode = k1.code ) and ( pont_work.actcode = k2.code ) and ( k1.label_type = 'OB' ) and ( k2.label_type = 'AC' ) and (( pont_work.pontwcstatus = 1 ) or ( pont_work.sysflag2 = '8') or ( pont_work.sysflag9 = '1' )) and ( pont_work.brkey = :as_brkey)
Structure Unit Columns
SELECT structure_unit.brkey, structure_unit.strunitkey, structure_unit.strunitlabel, structure_unit.strunitdescription FROM structure_unit WHERE structure_unit.brkey = :as_brkey and structure_unit.strunitkey = :an_strunitkey
Computed Fields
f_get_currency_symbol() ProfileString("PONTIS44.INI","Site","Agency",'') ProfileString("PONTIS44.INI","Site","Department",'') ProfileString("PONTIS44.INI","Site","Office",'') Describe("DataWindow.Print.DocumentName") "Page " + page() + " of " + pageCount() left(dayname(today()),3) + " " + string(today(), "[shortdate] [time]") "Cost" + "(" + sCurrency + ")" "Benefit" + "(" + sCurrency + ")"
D-62
R E P O R T
R E F E R E N C E
Retrieval Criteria
projects_progyear (Program Year) projects_proj_status (Project Status) prj_programs_prog_id (Program ID)
Report Definitions
SELECT projects.project_id, projects.projname, projects.progyear, projects.proj_acttype, projects.proj_status, projects.indirectben, projects.indirectcost, projects.agencyrank, projects.programrank, prj_programs.prog_id, prj_programs.progname, prj_witems.witemkey, prj_witems.cost, prj_witems.benefit FROM projects, prj_witems, prj_programs, WHERE ( projects.projkey = prj_witems.projkey ) and ( projects.progkey = prj_programs.progkey )
D-63
R E P O R T
R E F E R E N C E
Computed Fields
f_get_currency_symbol() "Benefit" + "(" + sCurrency + ")" "Cost" + "(" + sCurrency + ")" ProfileString("PONTIS44.INI","Site","Agency",'') ProfileString("PONTIS44.INI","Site","Department",'') ProfileString("PONTIS44.INI","Site","Office",'') ( projects_indirectben +sum( prj_witems_benefit for group 2 )) / ( projects_indirectcost + sum( prj_witems_cost for group 2 ) ) projects_indirectcost + sum( prj_witems_cost for group 2 ) projects_indirectben + sum( prj_witems_benefit for group 2 ) "Page " + page() + " of " + pageCount() left(dayname(today()),3) + " " + string(today(), "[shortdate] [time]") Describe("DataWindow.Print.DocumentName")
D-64
R E P O R T
R E F E R E N C E
Retrieval Criteria
projects_project_id (project ID) projects_proj_acttype (predominant action type of the project) projects_progyear (program year) projects_proj_status (project status) projects_district (district) projects_routenum (route number) projects_beginkmpost (beginning kmpost for the project) projects_endkmpost (ending kmpost for the project) prj_programs_prog_id (program ID)
Report Definitions
SELECT projects.projkey, projects.project_id, projects.projname, projects.proj_acttype, projects.progyear, projects.proj_status, projects.indirectben, projects.indirectcost, projects.agencyrank, projects.programrank, sum(prj_witems.cost) as direct_cost, sum(prj_witems.benefit) as direct_benefit, projects.district, projects.projenddate, projects.proj_review_status, projects.scen_treat, projects.routenum,
D-65
R E P O R T
R E F E R E N C E
projects.beginkmpost, projects.endkmpost, projects.contract_id, projects.contractor, projects.estcost, projects.contractcost, projects.finalcost, projects.avgsuffrate, projects.avghindex, prj_programs.prog_id, prj_programs.progname FROM projects, prj_witems, prj_programs WHERE ( prj_witems.projkey = projects.projkey ) and ( prj_programs.progkey = projects.progkey ) GROUP BY projects.projkey, projects.project_id, projects.projname, projects.proj_acttype, projects.progyear, projects.proj_status, projects.indirectben, projects.indirectcost, projects.agencyrank, projects.programrank, projects.district, projects.projenddate, projects.proj_review_status, projects.scen_treat, projects.routenum, projects.beginkmpost, projects.endkmpost, projects.contract_id, projects.contractor, projects.estcost, projects.contractcost, projects.finalcost, projects.avgsuffrate, projects.avghindex, prj_programs.prog_id, prj_programs.progname
Funding Sources
D-66
R E P O R T
R E F E R E N C E
prj_fundsrc.fs_name, prj_fundsrc.fs_type FROM prj_prjfund, prj_fundsrc WHERE ( prj_prjfund.fskey = prj_fundsrc.fskey ) and ( prj_prjfund.projkey = :as_projkey )
Work Items
SELECT prj_witems.witemkey, prj_witems.brkey, prj_witems.strunitkey, prj_witems.objkind, prj_witems.objcode, prj_witems.actkind, prj_witems.actcode, prj_witems.cost, prj_witems.benefit, k1.label as object, k2.label as action FROM prj_witems, kind_code_labels k1, kind_code_labels k2 WHERE prj_witems.objkind = k1.kind and prj_witems.actkind = k2.kind and prj_witems.objcode = k1.code and prj_witems.actcode = k2.code and k1.label_type = 'OB' and k2.label_type = 'AC' and prj_witems.projkey = :as_projkey
Work Item Structure Unit Columns
SELECT structure_unit.brkey, structure_unit.strunitkey, structure_unit.strunitlabel, structure_unit.strunitdescription FROM structure_unit WHERE structure_unit.brkey = :as_brkey and structure_unit.strunitkey = :an_strunitkey
Work Item Quantity/Units Columns
SELECT quantity, metricunit FROM elemdefs, metric_english, prj_witems WHERE prj_witems.witemkey = :as_witemkey and prj_witems.objkind ='1' and prj_witems.objcode = elemdefs.elemkey and metric_english.paircode = elemdefs.paircode
D-67
R E P O R T
R E F E R E N C E
Computed Fields
f_get_currency_symbol() ProfileString("PONTIS44.INI","Site","Agency",'') ProfileString("PONTIS44.INI","Site","Office",'') ProfileString("PONTIS44.INI","Site","Department",'') "Cost" + "(" + sCurrency + ")" "Benefit" + "(" + sCurrency + ")" projects_indirectcost + direct_cost projects_indirectben + direct_benefit ( projects_indirectben + direct_benefit ) / ( projects_indirectcost + direct_cost ) Describe("DataWindow.Print.DocumentName") left(dayname(today()),3) + " " + string(today(), "[shortdate] [time]") "Page " + page() + " of " + pageCount()
D-68
R E P O R T
R E F E R E N C E
Report Definitions
SELECT prj_programs.progkey, prj_programs.prog_id, prj_programs.progname, prj_programs.progstatus, prj_progfund.ykey, sum(prj_progfund.progbudg) as budget, sum(projects.indirectcost) as actualdirect, sum(prj_witems.cost) as actualindirect FROM prj_programs, prj_progfund, projects, prj_witems WHERE (prj_witems.projkey = projects.projkey) and (projects.progkey = prj_programs.progkey) and (prj_programs.progkey = prj_progfund.progkey) and (projects.progyear = prj_progfund.ykey) and (prj_programs.progstatus = '0') GROUP BY prj_programs.progkey, prj_programs.prog_id, prj_programs.progname, prj_programs.progstatus, prj_progfund.ykey ORDER BY prj_programs.prog_id ASC, prj_progfund.ykey ASC
D-69
R E P O R T
R E F E R E N C E
Computed Fields
f_get_currency_symbol() "Actual " + "(" + sCurrency + ")" "Budgeted " + "(" + sCurrency + ")" ProfileString("PONTIS44.INI","Site","Agency",'') ProfileString("PONTIS44.INI","Site","Office",'') ProfileString("PONTIS44.INI","Site","Department",'') actualdirect + actualindirect sum( budget for group 1 ) sum( actual for group 1 ) Describe("DataWindow.Print.DocumentName") left(dayname(today()),3) + " " + string(today(), "[shortdate] [time]") " Page " + page() + " of " + pageCount()
D-70
R E P O R T
R E F E R E N C E
Report Definitions
SELECT prj_progfund.ykey, prj_progfund.progbudg, prj_programs.prog_id, prj_fundsrc.fs_name, prj_programs.progkey FROM prj_progfund, prj_fundsrc, prj_programs WHERE ( prj_fundsrc.fskey = prj_progfund.fskey ) and ( prj_programs.progkey = prj_progfund.progkey ) and ( ( prj_programs.progstatus = '0' ) )
Computed Fields
ProfileString("PONTIS44.INI","Site","Agency",'') ProfileString("PONTIS44.INI","Site","Department",'') ProfileString("PONTIS44.INI","Site","Office",'') Describe("DataWindow.Print.DocumentName") progkey + "Total" left(dayname(today()),3) + " " + string(today(), "[shortdate] [time]") "Page " + page() + " of " + pageCount() crosstabsum(1) prog_id + " Total" sum(val for group 1) sum(grand_sum_val for group 1) "Grand Total" sum(val for all ) sum(grand_sum_val for all )
D-71
R E P O R T
R E F E R E N C E
Retrieval Criteria
sckey (scenario key, programmed by Pontis) brkey (bridge key) pont_work_ykey (program year) pont_work_pontwcstatus (programmed by Pontis)
Report Definitions
SELECT p1.sckey, bridge.brkey, bridge.bridge_id, bridge.featint, p1.ykey, sum(p1.agcycost) as cost, sum(p1.userbenf) as benefit, sum(p1.userbenf)/sum(p1.agcycost) as bcr FROM pont_work p1, bridge WHERE ( ( p1.sckey = :sc_sckey) and ( p1.pontwcstatus = 1 ) and ( bridge.brkey = p1.brkey) ) GROUP BY p1.sckey, bridge.brkey, bridge.bridge_id, bridge.featint, p1.ykey
Action Labels
SELECT k1.label as ob_label, k2.label as ac_label FROM pont_work p1, kind_code_labels k1, kind_code_labels k2 WHERE ( p1.sckey = :as_sckey ) and ( p1.brkey = :as_brkey ) and ( p1.ykey = :an_ykey ) and ( p1.witemkey = (select min(witenkey)
D-72 AASHTO Pontis Users Manual
R E P O R T
R E F E R E N C E
from pont_work p2 where p2.sckey = p1.sckey and p2.brkey = p1.brkey and p2.ykey = p1.ykey and p2.pontwcstatus = 1 and p2.agcycost = (select max(agcycost) from pont_work p3 where p3.sckey = p1.sckey and p3.brkey = p1.brkey and p3.ykey = p1.ykey and p3.pontwcstatus = 1) ) ) and ( p1.pontwcstatus = 1 ) and ( p1.objkind = k1.kind ) and ( p1.actkind = k2.kind ) and ( p1.objcode = k1.code ) and ( p1.actcode = k2.code ) and ( k1.label_type = 'OB' ) and ( l2.label_type = 'AC' )
Computed Fields
f_get_currency_symbol() ProfileString("PONTIS44.INI","Site","Agency",'') ProfileString("PONTIS44.INI","Site","Office",'') ProfileString("PONTIS44.INI","Site","Department","") "Cost" + "(" + sCurrency + ")" "Benefit" + "(" + sCurrency + ")" Describe("DataWindow.Print.DocumentName") "Page " + page() + " of " + pageCount() left(dayname(today()),3) + " " + string(today(), "[shortdate] [time]")
D-73
R E P O R T
R E F E R E N C E
Retrieval Criteria
sckey (scenario key, programmed by Pontis) brkey (bridge key) pont_work_ykey (program year) pont_work_agcycost (agency cost) pont_work_userbenf (user benefits) pont_work_pontwcstatus (work candidate status) pont_work_assigned pont_work_sysflag1 pont_work_sysflag2 pont_work_sysflag3 pont_work_sysflag4 pont_work_sysflag5 pont_work_sysflag6 pont_work_sysflag7 pont_work_sysflag8 pont_work_sysflag9 pont_work_sysflag10 pont_work_genflagpm pont_work_genflagsr pont_work_genflagrh pont_work_genflagpu pont_work_genflagup pont_work_genflagpg
Report Definitions
SELECT p1.sckey, bridge.brkey, bridge.bridge_id, p1.ykey,
D-74
R E P O R T
R E F E R E N C E
p1.witemkey, p1.strunitkey, p1.agcycost, p1.userbenf, p1.pontwcstatus, p1.assigned, p1.explic, p1.sysflag1, p1.sysflag2, p1.sysflag3, p1.sysflag4, p1.sysflag5, p1.sysflag6, p1.sysflag7, p1.sysflag8, p1.sysflag9, p1.sysflag10, p1.genflagpm, p1.genflagsr, p1.genflagrh, p1.genflagpu, p1.genflagup, p1.genflagpg, k1.label as ob_label, k2.label as ac_label FROM pont_work p1, kind_code_labels k1, kind_code_labels k2, bridge WHERE ( ( p1.sckey = :as_sckey) and ( bridge.brkey = p1.brkey) and ( p1.objkind = k1.kind ) and ( p1.actkind = k2.kind ) and ( p1.objcode = k1.code ) and ( p1.actcode = k2.code ) and ( k1.label_type = 'OB' ) and ( k2.label_type = 'AC' ) )
Structure Unit Columns
SELECT structure_unit.brkey, structure_unit.strunitkey, structure_unit.strunitlabel, structure_unit.strunitdescription FROM structure_unit WHERE structure_unit.brkey = :as_brkey and structure_unit.strunitkey = :an_strunitkey
D-75
R E P O R T
R E F E R E N C E
Computed Fields
f_get_currency_symbol() ProfileString("PONTIS44.INI","Site","Agency",'') ProfileString("PONTIS44.INI","Site","Office",'') ProfileString("PONTIS44.INI","Site","Department","") "Cost" + "(" + sCurrency + ")" "Benefit" + "(" + sCurrency + ")" Describe("DataWindow.Print.DocumentName") "Page " + page() + " of " + pageCount() left(dayname(today()),3) + " " + string(today(), "[shortdate] [time]")
D-76
R E P O R T
R E F E R E N C E
Report Definitions
SELECT scenario.sckey, scenario.scenname FROM scenario WHERE scenario.sckey = :as_sckey
Age Distribution
D-77
R E P O R T
R E F E R E N C E
Current Needs
SELECT sum(agcycost) as need FROM pont_work p1 WHERE sckey = :sckey and ykey = (select min(ykey) from pont_work p2 where p1.sckey = p2.sckey) and (( p1.pontwcstatus = 1 ) or ( p1.sysflag2 = '8') or ( p1.sysflag9 = '1' ))
Element Distribution
SELECT v_elem_dist_report3.elemdistcat, v_elem_dist_report3.totalquantity, v_elem_dist_report3.quantity1, v_elem_dist_report3.quantity2, v_elem_dist_report3.quantity3, v_elem_dist_report3.quantity4, v_elem_dist_report3.quantity5, v_elem_dist_report3.sumtev, v_elem_dist_report3.sumcev FROM v_elem_dist_report3
Future Needs
SELECT sckey, ykey, sum(agcycost) as needs, sum(agcycost * pontwcstatus) as cost FROM pont_work WHERE sckey = :sckey and (( pont_work.pontwcstatus = 1 ) or ( pont_work.sysflag2 = '8') or ( pont_work.sysflag9 = '1' )) GROUP BY sckey, ykey ORDER BY sckey ASC, ykey ASC
Health Index Graph
SELECT ykey, sum(tev) as net_tev, sum(hindex*tev/100) as net_cev FROM futmetric WHERE sckey = :sckey GROUP BY ykey
Health Index Report
SELECT ykey, sum(tev) as net_tev, sum(hindex*tev/100) as net_cev FROM futmetric WHERE sckey = :sckey
D-78
R E P O R T
R E F E R E N C E
SELECT bridge.brkey, inspevnt.inspkey, inspevnt.inspdate, inspevnt.nbinspdone, inspevnt.nextinsp, inspevnt.elinspdone, inspevnt.elnextdate, inspevnt.uwinspdone, inspevnt.uwnextdate, inspevnt.fcinspdone, inspevnt.fcnextdate, inspevnt.osinspdone, inspevnt.osnextdate FROM bridge, inspevnt WHERE ( inspevnt.brkey = bridge.brkey ) ORDER BY bridge.brkey ASC, inspevnt.inspdate DESC, inspevnt.inspkey DESC
Material Distribution Graph
SELECT v_mat_dist_report2.materialtype, v_mat_dist_report2.deckarea, v_mat_dist_report2.bridgecount, v_mat_dist_report2.displayorder FROM v_mat_dist_report2 ORDER BY v_mat_dist_report2.displayorder ASC
Material Distribution Report
SELECT v_mat_dist_report2.materialtype, v_mat_dist_report2.deckarea, v_mat_dist_report2.bridgecount, v_mat_dist_report2.displayorder FROM v_mat_dist_report2 ORDER BY v_mat_dist_report2.displayorder ASC
Sufficiency Distribution Graph
D-79
R E P O R T
R E F E R E N C E
Computed Fields
ProfileString ("PONTIS44.INI", "Site", "Department", ' ') ProfileString ("PONTIS44.INI", "Site", "Office", ' ') ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') f_get_currency_symbol () "Total Maintenance, Rehabilitation and Replacement Cost" + " (" + sCurrency + "):" If( SumTEV <> 0 , (SumCEV/SumTEV)*100, 0) If(Sum(SumTEV) <> 0 , (Sum(SumCEV)/Sum(SumTEV))*100, 0) "Total Needs" + " (" + scurrency + ")" "Programmed Work" + " (" + scurrency + ")" sum( needs for group 1 ) sum( cost for group 1 ) net_cev / net_tev * 100 if(inspevnt_nbinspdone = '1', if(daysafter(inspevnt_inspdate, today()) <= 180, if(getrow() = 1, 1, if(bridge_brkey[-1] <> bridge_brkey, 1, 0)), 0), 0) if(inspevnt_nbinspdone = '1', if(daysafter(today(), inspevnt_nextinsp) <= 180 and daysafter(today(), inspevnt_nextinsp) >= 0, if(getrow() = 1, 1, if(bridge_brkey[-1] <> bridge_brkey, 1, 0)), 0), 0) if(inspevnt_nbinspdone = '1', if(daysafter(inspevnt_nextinsp, today()) > 0, if(getrow() = 1, 1, if(bridge_brkey[-1] <> bridge_brkey, 1, 0)), 0), 0) if(inspevnt_elinspdone = '1', if(daysafter(inspevnt_inspdate, today()) <= 180, if(getrow() = 1, 1, if(bridge_brkey[-1] <> bridge_brkey, 1, 0)), 0), 0) if(inspevnt_elinspdone = '1', if(daysafter(today(), inspevnt_nextinsp) <= 180 and daysafter(today(), inspevnt_nextinsp) >= 0, if(getrow() = 1, 1, if(bridge_brkey[-1] <> bridge_brkey, 1, 0)), 0), 0) if(inspevnt_elinspdone = '1', if(daysafter(inspevnt_nextinsp, today()) > 0, if(getrow() = 1, 1, if(bridge_brkey[-1] <> bridge_brkey, 1, 0)), 0), 0) if(inspevnt_uwinspdone = '1', if(daysafter(inspevnt_inspdate, today()) <= 180, if(getrow() = 1, 1, if(bridge_brkey[-1] <> bridge_brkey, 1, 0)), 0), 0) if(inspevnt_uwinspdone = '1', if(daysafter(today(), inspevnt_nextinsp) <= 180 and daysafter(today(), inspevnt_nextinsp) >= 0, if(getrow() = 1, 1, if(bridge_brkey[-1] <> bridge_brkey, 1, 0)), 0), 0) if(inspevnt_uwinspdone = '1', if(daysafter(inspevnt_nextinsp, today()) > 0, if(getrow() = 1, 1, if(bridge_brkey[-1] <> bridge_brkey, 1, 0)), 0), 0) if(inspevnt_fcinspdone = '1', if(daysafter(inspevnt_inspdate, today()) <= 180, if(getrow() = 1, 1, if(bridge_brkey[-1] <> bridge_brkey, 1, 0)), 0), 0) if(inspevnt_fcinspdone = '1', if(daysafter(today(), inspevnt_nextinsp) <= 180 and daysafter(today(), inspevnt_nextinsp) >= 0, if(getrow() = 1, 1, if(bridge_brkey[-1] <> bridge_brkey, 1, 0)), 0), 0)
D-80
R E P O R T
R E F E R E N C E
if(inspevnt_fcinspdone = '1', if(daysafter(inspevnt_nextinsp, today()) > 0, if(getrow() = 1, 1, if(bridge_brkey[-1] <> bridge_brkey, 1, 0)), 0), 0) if(inspevnt_osinspdone = '1', if(daysafter(inspevnt_inspdate, today()) <= 180, if(getrow() = 1, 1, if(bridge_brkey[-1] <> bridge_brkey, 1, 0)), 0), 0) if(inspevnt_osinspdone = '1', if(daysafter(today(), inspevnt_nextinsp) <= 180 and daysafter(today(), inspevnt_nextinsp) >= 0, if(getrow() = 1, 1, if(bridge_brkey[-1] <> bridge_brkey, 1, 0)), 0), 0) if(inspevnt_osinspdone = '1', if(daysafter(inspevnt_nextinsp, today()) > 0, if(getrow() = 1, 1, if(bridge_brkey[-1] <> bridge_brkey, 1, 0)), 0), 0) sum(nb_last6 for all) sum(nb_next6 for all) sum(nb_overdue for all) sum(el_last6 for all) sum(el_next6 for all) sum(el_overdue for all) sum(uw_last6 for all) sum(uw_next6 for all) sum(uw_overdue for all) sum(fc_last6 for all) sum(fc_next6 for all) sum(fc_overdue for all) sum(os_last6 for all) sum(os_next6 for all) sum(os_overdue for all) sum( bridgecount for all ) sum( deckarea for all ) count(brkey for group 1) sum(if(suffcat = 2 or suffcat = 3, 1, 0)) round(sum( suff_rate for all DISTINCT if(suff_rate<>99,brkey,'')) / count(brkey for all DISTINCT if(suff_rate<>99,brkey,'')) ,1) left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]") "Page" + page() + " of " + pagecount () Describe ("DataWindow.Print.DocumentName")
D-81
R E P O R T
R E F E R E N C E
Report Definitions
SELECT scenario.scenname, scenario.sckey, pont_work.ykey, sum(agcycost) - sum(agcycost * pontwcstatus) as back FROM scenario, pont_work WHERE ( scenario.sckey = :as_sckey ) and ( scenario.sckey = pont_work.sckey ) and (( pont_work.pontwcstatus = 1 ) or ( pont_work.sysflag2 = '8') or ( pont_work.sysflag9 = '1' )) GROUP BY scenario.sckey, scenario.scenname, pont_work.ykey
Repairs
SELECT ykey, sum(agcycost * pontwcstatus) as repaircost, sum(agcycost) - sum(agcycost * pontwcstatus) as repairback FROM pont_work WHERE ( sckey = :as_sckey ) AND ( ykey = :an_ykey ) AND ( objkind = '1' ) AND (( pont_work.pontwcstatus = 1 ) or ( pont_work.sysflag2 = '8') or ( pont_work.sysflag9 = '1' )) GROUP BY ykey
Replacements
SELECT ykey, sum(agcycost * pontwcstatus) as replcost, sum(agcycost) - sum(agcycost * pontwcstatus) as replback FROM pont_work, actypdfs WHERE (actkind = '1') and
D-82
R E P O R T
R E F E R E N C E
( actcode = actypdfs.tkey) AND ( actypdfs.atypcat = '1') AND ( pont_work.objcode <> 1 ) AND (( pont_work.pontwcstatus = 1 ) or ( pont_work.sysflag2 = '8' ) or ( pont_work.sysflag9 = '1' )) and ( sckey = :as_sckey ) AND ( ykey = :an_ykey ) GROUP BY ykey
Improvements
SELECT ykey, sum(agcycost * pontwcstatus) AS impcost, sum(agcycost) - sum(agcycost * pontwcstatus) AS impback FROM pont_work, actypdfs WHERE ( actkind = '1' ) AND ( actcode = actypdfs.tkey ) AND ( actypdfs.atypcat <> '1' ) AND ( objkind <> '1' ) AND ( ( pont_work.pontwcstatus = 1 ) or ( pont_work.sysflag2 = '8' ) or ( pont_work.sysflag9 = '1' ) ) and ( sckey = :as_sckey ) AND ( ykey = :an_ykey ) GROUP BY ykey ORDER BY ykey ASC
Computed Fields
ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') ProfileString ("PONTIS44.INI", "Site", "Department", ' ') ProfileString ("PONTIS44.INI", "Site", "Office", ' ') "Preservation "+if(sCurrency <> "?", "(" + sCurrency + ")","") "Replacements "+if(sCurrency <> "?", "(" + sCurrency + ")","") "Improvements & Other"+if(sCurrency <> "?", "(" + sCurrency + ")","") "Total "+if(sCurrency <> "?", "(" + sCurrency + ")","") f_get_currency_symbol() "Page" + page() + " of " + pagecount () Describe ("DataWindow.Print.DocumentName") left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]")
D-83
R E P O R T
R E F E R E N C E
Report Definitions
SELECT netmetric.sckey, netmetric.ykey, netmetric.dim1val, netmetric.dim2val, netmetric.dim3val, netmetrci.dim4val, netmetric.strucneed as structcnt, netmetric.needs as needs, netmetric.benneeds as needben, netmetric.progwork as cost, netmetric.benwork as benefit, netmetric.strucdont as structdone, scenario.scenname, budgmtrx.budget FROM netmetric, scenario, budgmtrx WHERE ( scenario.sckey = netmetric.sckey ) and ( budgmtrx.bukey = scenario.bukey ) and ( budgmtrx.ykey = netmetric.ykey ) and ( netmetric.sckey = :as_sckey )
D-84
R E P O R T
R E F E R E N C E
Computed Fields
f_get_currency_symbol () "Cost" + "(" + sCurrency + ")" "Benefit" + "(" + sCurrency + ")" ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') ProfileString ("PONTIS44.INI", "Site", "Department", ' ') ProfileString ("PONTIS44.INI", "Site", "Office", ' ') sum (needben for group 1) sum (needs for group 1) sum (cost for group 1) sum (benefit for group 1) sum (struccnt for group 1) sum (structdone for group 1) sum (needs for group 2) sum (needben for group 2) sum (cost for group 2) sum (benefit for group 2) sum (struccnt for group 2) sum (structdone for group 2) sum (cost for all) sum (benefit for all) sum (structdone for all) left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]") "Page" + page() + " of " + pagecount () Describe ("DataWindow.Print.DocumentName")
D-85
R E P O R T
R E F E R E N C E
Report Definitions
SELECT netmetric.sckey, scenario.scenname, netmetric.ykey, budgmtrx.budget FROM scenario, budgmtrx, netmetric WHERE ( scenario.bukey = budgmtrx.bukey ) and ( netmetric.sckey = scenario.sckey ) and ( ( netmetric.sckey = :as_sckey ) AND ( budgmtrx.ykey = netmetric.ykey ) ) GROUP BY netmetric.sckey, scenario.scenname, netmetric.ykey, budgmtrx.budget ORDER BY netmetric.sckey ASC, netmetric.ykey ASC
District
SELECT netmetric.sckey, netmetric.ykey, netmetric.dim1val, netmetric.dim2val, netmetric.dim3val, netmetric.dim4val, netmetric.struccount, netmetric.strucneed, netmetric.strucdone, netmetric.needs, netmetric.progwork, netmetric.benneeds, netmetric.benwork FROM netmetric
D-86
R E P O R T
R E F E R E N C E
WHERE ( netmetric.sckey = :as.sckey ) AND ( netmetric.ykey = :an_ykey ) ORDER BY netmetric.sckey ASC, netmetric.ykey ASC, netmetric.dim1val ASC
Functional Class
SELECT netmetric.sckey, netmetric.ykey, netmetric.dim1val, netmetric.dim2val, netmetric.dim3val, netmetric.dim4val, netmetric.struccount, netmetric.strucneed, netmetric.strucdone, netmetric.needs, netmetric.progwork, netmetric.benneeds, netmetric.benwork FROM netmetric WHERE ( netmetric.sckey = :as.sckey ) AND ( netmetric.ykey = :an_ykey ) AND ORDER BY netmetric.sckey ASC, netmetric.ykey ASC, netmetric.dim2val ASC
NHS
SELECT netmetric.sckey, netmetric.ykey, netmetric.dim1val, netmetric.dim2val, netmetric.dim3val, netmetric.dim4val, netmetric.struccount, netmetric.strucneed, netmetric.strucdone, netmetric.needs, netmetric.progwork, netmetric.benneeds, netmetric.benwork FROM netmetric WHERE ( netmetric.sckey = :as.sckey ) AND ( netmetric.ykey = :an_ykey ) AND ORDER BY netmetric.sckey ASC, netmetric.ykey ASC, netmetric.dim3val ASC
D-87
R E P O R T
R E F E R E N C E
System
SELECT netmetric.sckey, netmetric.ykey, netmetric.dim1val, netmetric.dim2val, netmetric.dim3val, netmetric.dim4val, netmetric.struccount, netmetric.strucneed, netmetric.strucdone, netmetric.needs, netmetric.progwork, netmetric.benneeds, netmetric.benwork FROM netmetric WHERE ( netmetric.sckey = :as.sckey ) AND ( netmetric.ykey = :an_ykey ) AND ORDER BY netmetric.sckey ASC, netmetric.ykey ASC, netmetric.dim4val ASC
Computed Fields
ProfileString ("PONTIS44.INI", "Site", "Office", ' ') ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') ProfileString ("PONTIS44.INI", "Site", "Department", ' ') f_get_currency_symbol() "Cost" + "(" + sCurrency + ")" "Benefit" + "(" + sCurrency + ")" sum(netmetric_benneeds for group 1) sum(netmetric_progwork for group 1) sum(netmetric_benwork for group 1) sum(netmetric_struccount for group 1) sum(netmetric_strucdone for group 1) sum(netmetric_needs for group 1) sum(netmetric_needs for all) sum(netmetric_benneeds for all) sum(netmetric_progwork for all) sum (netmetric_benwork for all) sum(netmetric_struccount for all ) sum(netmetric_strucdone for all) "Page" + page() + " of " + pagecount () Describe ("DataWindow.Print.DocumentName") left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]")
D-88
R E P O R T
R E F E R E N C E
Report Definition
SELECT futmetric.sckey, futmetric.brkey, futmetric.ykey, futmetric.hindex, futmetric.suff_rating, futmetric.suff_prefix, futmetric.rating_nbi, futmetric.rating_deck, futmetric.rating_sup, futmetric.rating_sub, futmetric.rating_culv, futmetric.rating_str, futmetric.rating_dkgeo, futmetric.rating_undcl, bridge.bridge_id, bridge.facility FROM futmetric, bridge WHERE (bridge.brkey = futmetric.brkey) and (sckey = :as_sckey) ORDER BY bridge_id ASC, ykey ASC
D-89
R E P O R T
R E F E R E N C E
Computed Fields
ProfileString("PONTIS44.INI","Site","Agency",'') ProfileString("PONTIS44.INI","Site","Department",'') ProfileString("PONTIS44.INI","Site","Office",'') Describe("DataWindow.Print.DocumentName") left(dayname(today()),3) + " " + today() " Page " + page() + " of " + pageCount()
D-90
R E P O R T
R E F E R E N C E
Report Definition
SELECT sckey, ykey, dim1val, dim2val, dim3val, dim4val, struccount, healthindex, suffrating_1, suffrating_2, suffrating_3, suffrating_4, nbirating_1, nbirating_2, elig_rehab, elig_repl, elig_not FROM netmetric WHERE sckey = :as_sckey ORDER BY ykey ASC, dim1val ASC, dim2val ASC, dim3val ASC, dim4val ASC
D-91
R E P O R T
R E F E R E N C E
SELECT s1.scparamvalue as sr1, s2.scparamvalue as sr2, s3.scparamvalue as sr3 FROM scenparam s1, scenparam s2, scenparam s3 WHERE (s2.sckey = s1.sckey) and (s3.sckey = s1.sckey) and (s1.scparam = 'S1') and (s2.scparam = 'S2') and (s3.scparam = 'S3') and (s1.sckey = :as_sckey)
Computed Fields
f_get_currency_symbol() ProfileString("PONTIS44.INI","Site","Agency",'') ProfileString("PONTIS44.INI","Site","Department",'') ProfileString("PONTIS44.INI","Site","Office",'') sum( struccount for group 1 ) sum( suffrating_1 for group 1 ) sum( suffrating_2 for group 1 ) sum( suffrating_3 for group 1 ) sum( suffrating_4 for group 1 ) sum( nbirating_1 for group 1 ) sum( nbirating_2 for group 1 ) sum( elig_rehab for group 1 ) sum( elig_repl for group 1 ) sum( elig_not for group 1 ) 'SR <' + scenparam_sr1 'SR ' + scenparam_sr1 + ' - ' + scenparam_sr2 'SR ' + scenparam_sr2 + ' - ' + scenparam_sr3 'SR >' + scenparam_sr3 Describe("DataWindow.Print.DocumentName") left(dayname(today()),3) + " " + string(today(), "[shortdate] [time]") "Page " + page() + " of " + pageCount()
D-92
R E P O R T
R E F E R E N C E
Retrieval Criteria
elemdefs_elemnum (element number) elemdefs_ecatkey (element category) elemdefs_matlkey (material)
Report Definitions
SELECT pont_work.sckey, scenario.scenname, elemdefs.ecatkey, elemdefs.elemkey, elemdefs.elemnum, elemdefs.elemlong, elemdefs.matlkey, pont_work.ykey, sum(pont_work.agcycost) as needs, sum(pont_work.agcycost * pont_work.pontwcstatus) as progwork, sum(pont_work.userbenf) as needbenf, sum(pont_work.userbenf * pont_work.pontwcstatus) as progbenf, FROM pont_work, scenario, elemdefs WHERE ( scenario.sckey = pont_work.sckey ) and ( pont_work.objkind = '1') and ( elemdefs.elemkey = pont_work.objcode ) and ( pont_work.sckey = :sc_key ) and (( pont_work.pontwcstatus = 1 ) or ( pont_work.sysflag2 = '8') or ( pont_work.sysflag9 = '1' )) GROUP BY pont_work.sckey, scenario.scenname, elemdefs.ecatkey, elemdefs.elemkey, elemdefs.elemnum, elemdefs.elemlong, elemdefs.matlkey, pont_work.ykey
D-93
R E P O R T
R E F E R E N C E
Computed Fields
f_get_currency_symbol () ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') ProfileString ("PONTIS44.INI", "Site", "Department", ' ') ProfileString ("PONTIS44.INI", "Site", "Office", ' ') "Benefit" + "(" + sCurrency + ")" "Cost" + "(" + sCurrency + ")" sum (needs for group 2) sum (needbenf for group 2) sum (progwork for group 2) sum (progbenf for group 2) sum (progwork for group 1) sum (progwork for all) "Page" + page() + " of " + pagecount () Describe ("DataWindow.Print.DocumentName") left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]")
D-94
R E P O R T
R E F E R E N C E
D.38 PROG008: Annual Needs and Programmed Work by Element and Category
This report summarizes the needs and programmed work over time by element category and element for the current Pontis scenario. For each simulation year, the report shows results by element category and element. Shown for each element are the quantity of the element with needs, programmed work (work modeled by Pontis as being programmed given the budget constraint), potential benefits of meeting all needs, benefits of the programmed work, and number of structures for which work is programmed.
Retrieval Criteria
elemdefs_elemnum (element number) elemdefs_ecatkey (element category) pont_work_ykey (year)
Report Definitions
SELECT pont_work.ykey, pont_work.sckey, elcatdfs.ecatname, elemdefs.ecatkey, elemdefs.elemnum, elemdefs.elemshort, sum(pont_work.quantity) AS elemquant, sum(pont_work.agcycost) AS needs, sum(pont_work.userbenf) AS benefits, sum(pont_work.agcycost * pont_work.pontwcstatus) AS progwork, sum(pont_work.userbenf * pont_work.pontwcstatus) AS progbenf, FROM pont_work, elcatdfs, elemdefs WHERE pont_work.sckey = :as_sckey AND elcatdfs.ecatkey = elemdefs.ecatkey AND pont_work.objkind = '1' AND pont_work.objcode = elemdefs.elemkey AND (( pont_work.pontwcstatus = 1 ) or ( pont_work.sysflag2 = '8') or ( pont_work.sysflag9 = '1' )) GROUP BY pont_work.ykey, pont_work.sckey, elemdefs.ecatkey, elcatdfs.ecatname, elemdefs.elemnum, elemdefs.elemshort
D-95
R E P O R T
R E F E R E N C E
Computed Fields
f_get_currency_symbol () ProfileString ("PONTIS44.INI", "Site", "Department", ' ') ProfileString ("PONTIS44.INI", "Site", "Office", ' ') ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') "Benefits" + "(" + sCurrency + ")" "Costs" + "(" + sCurrency + ")" sum (needs for group 2) sum (benefits for group 2) sum (progwork for group 2) sum (progbenf for group 2) sum (needs for group 1) sum (benefits for group 1) sum (progwork for group 1) sum (progbenf for group 1) "Page" + page() + " of " + pagecount () Describe ("DataWindow.Print.DocumentName") left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]")
D-96
R E P O R T
R E F E R E N C E
Retrieval Criteria
as_sckey (scenario) elcatdfs_elcatkey (element category) matdefs_matlkey (material)
Report Definitions
SELECT scenario.sckey, scenario.scenname, elcatdfs.ecatkey, elcatdfs.ecatname, matdefs.matlkey, matdefs.matlname, pont_work.ykey, sum(pont_work.agcycost) as needs, sum(pont_work.userbenf) as needbenf, sum(pont_work.agcycost * pont_work.pontwcstatus) as progwork, sum(pont_work.userbenf * pont_work.pontwcstatus) as progbenf, FROM pont_work, scenario, elcatdfs, elemdefs, matdefs WHERE ( scenario.sckey = :as_sckey) and ( pont_work.sckey = scenario.sckey ) and ((pont_work.objkind = '1' ) and ( elemdefs.elemkey = pont_work.objcode ) ) and ( matdefs.matlkey = elemdefs.matlkey ) and ( elemdefs.ecatkey = elcatdfs.ecatkey ) and (( pont_work.pontwcstatus = 1 ) or ( pont_work.sysflag2 = '8') or ( pont_work.sysflag9 = '1' )) GROUP BY scenario.sckey, scenario.scenname,
D-97
R E P O R T
R E F E R E N C E
elcatdfs.ecatkey, elcatdfs.ecatname, matdefs.matlkey, matdefs.matlname, pont_work.ykey ORDER BY elcatdfs.ecatkey ASC, matdefs.matlkey ASC, pont_work.ykey ASC
Computed Fields
f_get_currency_symbol() ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') ProfileString ("PONTIS44.INI", "Site", "Department", ' ') ProfileString ("PONTIS44.INI", "Site", "Office", ' ') "Benefit" + "(" + sCurrency + ")" "Cost" + "(" + sCurrency + ")" sum (structdone for group 3) sum (needbenf for group 3) sum (needs for group 3) sum(progwork for group 3) sum(progbenf for group 3) left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]") "Page" + page() + " of " + pagecount () Describe ("DataWindow.Print.DocumentName")
D-98
R E P O R T
R E F E R E N C E
Report Definitions
SELECT bridge.district, pont_work.ykey, sum(pont_work.agcycost * pont_work.pontwcstatus) as costtot, sum(pont_work.userbenf * pont_work.pontwcstatus) as bentot, scenario.sckey, scenario.scenname FROM bridge, pont_work, scenario WHERE ( bridge.brkey = pont_work.brkey ) and ( pont_work.sckey = scenario.sckey ) and (( pont_work.pontwcstatus = 1 ) or ( pont_work.sysflag2 = '8') or ( pont_work.sysflag9 = '1' )) and ( pont_work.objkind = '1' ) and GROUP BY scenario.sckey, scenario.scenname, bridge.district, pont_work.ykey
Computed Fields
ProfileString ("PONTIS44.INI", "Site", "Office", ' ') ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') ProfileString ("PONTIS44.INI", "Site", "Department", ' ') crosstabsum(1) crosstabsum(2) scenname + " Total" sum(cost_tot for group 2) sum(ben_tot for group 2) sum(grand_sum_val for group 2) sum(grand_sum_ben for group 2) Describe ("DataWindow.Print.DocumentName") left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]") "Page" + page() + " of " + pagecount ()
D-99
R E P O R T
R E F E R E N C E
D.41 PROG011: Total Preservation Needs and Programmed Work Over Time
This report summarizes total preservation needs and programmed work for each simulation year of the current Pontis scenario. Shown in the report are the preservation needs, programmed work (work modeled by Pontis as being programmed given the budget constraint), potential benefits of meeting all needs, benefits of the programmed work, percent of the needs that are programmed, and number of structures for which work is programmed. This information is shown in tabular format, with a graph summarizing needs and programmed work by year. Note that the report shows preservation work only. Not included is work involving structure replacement, widening, raising or strengthening.
Report Definitions
SELECT pont_work.sckey, scenario.scenname, pont_work.ykey, pont_work.agcycost as needs, pont_work.userbenf as needsben, pont_work.agcycost * pont_work.pontwcstatus as progwork, pont_work.userbenf * pont_work.pontwcstatus as progbenf, FROM pont_work, scenario WHERE ( scenario.sckey = pont_work.sckey ) and ( pont_work.sckey = :as_sckey ) and (( pont_work.pontwcstatus = 1 ) or ( pont_work.sysflag2 = '8') or ( pont_work.sysflag9 = '1' )) and ( pont_work.objkind = '1' ) and ORDER BY pont_work.ykey ASC
Programmed Year
SELECT ykey, count(distinct pont_work.brkey) as count_bridge FROM pont_work WHERE (pont_work.sckey = :as_sckey) and (pont_work.ykey = :an_ykey) and (pont_work.objkind = '1') and (pont_work.pontwcstatus = 1) GROUP BY ykey
Computed Fields
ProfileString ("PONTIS44.INI", "Site", "Department", ' ') ProfileString ("PONTIS44.INI", "Site", "Office", ' ')
D-100
R E P O R T
R E F E R E N C E
ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') f_get_currency_symbol () "Cost" + "(" + sCurrency + ")" "Benefit" + "(" + sCurrency + ")" sum (pont_work_needs for group 1) sum (pont_work_needsben for group 1) sum (progwork for group 1) sum (progbenf for group 1) sum (progwork for group 1)/sum (pont_work_needs for group 1) * 100 sum (progwork for all) sum(count_bridge for all) Describe ("DataWindow.Print.DocumentName") left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]") "Page" + page() + " of " + pagecount ()
D-101
R E P O R T
R E F E R E N C E
D-102
R E P O R T
R E F E R E N C E
Report Definitions
SELECT budgsets.buname, budgsets.notes, costsets.coname, costsets.cocostix, costsets.codate, budgsets.budate, costsets.notes, imprsets.imname, imprsets.imdate, imprsets.notes, polsets.podate, polsets.notes, scenario.scenname, scenario.userkey, scenario.modtime, scenario.notes, scenario.sckey, scenario.mokey, scenario.agcypolsetkey, polsets.poname, costsets.cokey, imprsets.imkey, polsets.pokey, mrrmodls.moname, budgsets.bukey, mrrmodls.notes, coptions.optionval as discrate, s1.scparamvalue as cf, s2.scparamvalue as cm, s3.scparamvalue as dp, s4.scparamvalue as dy, s5.scparamvalue as f1, s6.scparamvalue as f2, s7.scparamvalue as fx, s8.scparamvalue as hz, s9.scparamvalue as mx, s10.scparamvalue as rc, s11.scparamvalue as rx, s12.scparamvalue as y1, s13.scparamvalue as y2 FROM budgsets, costsets, imprsets, polsets, scenario,
D-103
R E P O R T
R E F E R E N C E
mrrmodls, coptions, scenparam s1, scenparam s2, scenparam s3, scenparam s4, scenparam s5, scenparam s6, scenparam s7, scenparam s8, scenparam s9, scenparam s10, scenparam s11, scenparam s12, scenparam s13 WHERE ( scenario.pokey = polsets.pokey ) and ( scenario.imkey = imprsets.imkey ) and ( scenario.cokey = costsets.cokey ) and ( scenario.bukey = budgsets.bukey ) and ( mrrmodls.mokey = scenario.mokey ) and ( coptions.optionname = 'DISCRATE') and ( s1.sckey = scenario.sckey) and ( s2.sckey = scenario.sckey) and ( s3.sckey = scenario.sckey) and ( s4.sckey = scenario.sckey) and ( s5.sckey = scenario.sckey) and ( s6.sckey = scenario.sckey) and ( s7.sckey = scenario.sckey) and ( s8.sckey = scenario.sckey) and ( s9.sckey = scenario.sckey) and ( s10.sckey = scenario.sckey) and ( s11.sckey = scenario.sckey) and ( s12.sckey = scenario.sckey) and ( s13.sckey = scenario.sckey) and ( s1.scparam = 'CF') and ( s2.scparam = 'CM') and ( s3.scparam = 'DP') and ( s4.scparam = 'DY') and ( s5.scparam = 'F1') and ( s6.scparam = 'F2') and ( s7.scparam = 'FX') and ( s8.scparam = 'HZ') and ( s9.scparam = 'MX') and ( s10.scparam = 'RC') and ( s11.scparam = 'RX') and ( s12.scparam = 'Y1') and ( s13.scparam = 'Y2') and ( scenario.sckey = :as_sckey)
D-104 AASHTO Pontis Users Manual
R E P O R T
R E F E R E N C E
SELECT costmtrx.ucreplace, polmatrx.dsswell, costmtrx.hrdetourco, costmtrx.kmdetourco, costmtrx.acccost, costmtrx.dim2val FROM costmtrx, polmatrx WHERE ( costmtrx.dim2val = polmatrx.dim2val ) and ( costmtrx.dim3val = polmatrx.dim3val ) and ( costmtrx.dim4val = polmatrx.dim4val ) and ( ( costmtrx.dim1val = '01' ) AND ( polmatrx.adtclass = '03' ) AND ( costmtrx.dim3val = '01' ) AND ( costmtrx.dim4val = '01' ) AND ( costmtrx.cokey = :cokeyarg ) AND ( polmatrx.pokey = :pokeyarg ) )
Scenario Improvement Detail
SELECT imprmtrx.raisecriticaladt, imprmtrx.raisecriticalbypasslen, imprmtrx.replacecriticaladt, imprmtrx.replacecriticalbypasslen, imprmtrx.strdetoursminthresh, imprmtrx.strdetoursmaxthresh, imprmtrx.detspeedfactor, imprmtrx.imkey, imprsets.imname, imprsets.notes, imprsets.imdate FROM imprmtrx, imprsets WHERE ( imprsets.imkey = imprmtrx.imkey ) and ( ( imprmtrx.imkey = :imkeyarg ) )
D-105
R E P O R T
R E F E R E N C E
Agency Policy
SELECT agencypolsets.agcypolsetname, agencypolrule.agcypolrulekey, agencypolrule.priority, agencypolrule.description FROM agencypolsets, agencypolrule WHERE ( agencypolrule.agcypolsetkey = agencypolsets.agcypolsetkey) AND ( agencypolsets.agcypolsetkey = :agcykeyarg )
Computed Fields
ProfileString ("PONTIS44.INI", "Site", "Office", ' ') ProfileString ("PONTIS44.INI", "Site", "Department", ' ') ProfileString ("PONTIS44.INI", "Site", "Agency", ' ') left (dayname (today()), 3) + " " + string (today (), "[shortdate] [time]") "Page" + page() + " of " + pagecount () Describe ("DataWindow.Print.DocumentName")
D-106