Post-Pontis Optimizer (PPO)& Bridge Data ArchiverPontis Users Group MeetingSeptember 23-24 2009September 23-24, 2009

Richard Thompson, P.E.Bridge Management Engineer

Allen R. Marshall, PrincipalTransportation Management Groupg g g

Structure & Bridge Divisionp g p

Cambridge Systematics, Inc.

Backgroundg

• Needed to develop budget by Work Type

• Current Pontis Program can only specify overall budget

• In 2004 VDOT recommended Pontis enhancement to support multiple funding constraints

E l 2008 id tifi d f di d b 32

• Early 2008 identified funding and began 3-month process to add feature

Design Featuresg

• Add a supplemental program outside Pontis to pp p ghandle What-if analysis

• Used procedure that would read data from• Used procedure that would read data from Pontis

• Develop budget based on multiple work types

• Budget for 10 year period• Budget for 10 year period

• Use in both Oracle and Sybase operations

3

Advantagesg

• Takes advantage of existing effort in developing deterioration modelsp g

• Allow VDOT to customize program p gsimulation process

• Low risk, rapid development approach

4

Criteria

All l lt ti f b id d i• Allow only one alternative for a bridge during analysis period

• Support 5 program work types

• Assign all work for year on bridge to most expensive work type

• Looks at all 10 years rather that 1 year at a time

5

time

System Stepsy p

• Program develops 11 simulations in Pontis– Year 0 – $0 in all 10 years– Year 1 – 10 unlimited dollars in simulation year & $0 in

other yearsy

• System builds project alternatives for each bridge

• User specifies max. funds by work type by year

• System uses IBCR in selecting projects

6

• Calculate and store for use in Pontis

Approachpp

Robot – Done once annually (time consuming)y ( g)• Automatically runs 11 scenarios in Pontis• Creates set of alternatives

Optimizer (PPO)• Used to optimize budget allocations• Used to optimize budget allocations• Constraints are given by year & work type• Benefits (User & HI) are calculated for 10 yearsBenefits (User & HI) are calculated for 10 years• Rerun and/or saved for use in Pontis

7

Pontis• Display detailed budgeted work needs by bridge

Robot

• Before Running, Update data in Default Scenario

• Clear past PPO scenarios

• Run Robot to create Pontis ScenariosPontis Scenarios

• Once complete, user can close the program

8• Run only once at central location

PPO Log-on Screeng

• Run in districts

• Select database

• Connect

9

PPO Input Screenp

• Select the District

• Enter costs for work types by year

• Enter a description for the trial run (optional)

• Select Run –takes a few minutes to run

10

PPO Results - Budget g

• Report shows Bridges – in inventory, y,– number needing work– Number with budgeted

workwork

• Budget Input by manager

11

PPO Results – Funds Spentp

• Report shows Funds Spent in pProgram by Work Type and Year

12

PPO Results – Network Condition

P id H lth• Provides avg. Health Index for all bridges in district by year y yand 10 year average

• Provides avg. Sufficiency Rating for all bridges in gdistrict by year and 10 year average

13

PPO Results – Benefits Obtained

• Provides Benefits Obtained for Health Index & User plus Total Benefit ($)

14

PPO Results – Other Actions

• PPO Scenario can be saved for use in Pontis

• PPO Scenario can be printed out

• Return to PPO input screen to try other scenarios

• Leave program15

• Leave program

PPO Results – Printed Reportp

Sample Reportp p

16

PPO Pontis Reportsp

• 2 reports (based on existing Pontis reports) can be produced on PPO data in Pontis

– Modified Plan001 gives information on work budgeted by year and bridge

– Modified Plan004 gives detailed information for each bridge on work budgetedfor each bridge on work budgeted

17

PPO Pontis ReportspModified Plan001

18

PPO Pontis Reportsp

ModifiedModified Plan004

19

Next Stepsp

• Review element definitions for proper informationp p

• Review field data for bad data

• Review element models for– Rate of deteriorationRate of deterioration– Condition improvement after work performed

• Review Rules in Scenarios• Consider enhancements for longer time horizons (20

years) and more work type allocations20

years) and more work type allocations

Conclusion

• Used to optimize budget allocationsp g• Constraints are given by year & work type• Relatively quick, scenarios and results can be rerun

or saved for use in Pontis• Displays detailed information by bridge on future

budgeted work needsbudgeted work needs

21

Pontis Bridge Data Archiverg

• Provides real-time archiving of individual record gchanges

• Stores record snapshots on each change• Permits post-change review of changes by bridge or

inspector, or date range• Incorporates mainframe history from one-time• Incorporates mainframe history from one-time

download• Simple trigger-based auditing• Coverage – bridges, inspections, roadways, structure

units, and element inspections, with agency sibling tables

22

tables

Pontis Bridge Data Archiverg

• Oracle-specific tool, no SQL Server or SQL Anywhere p , Q Q yimplementation

• Relies on Materialized Views for reporting• Live data change reports using Ad Hoc SQL

supported• Easy to link change history to current inventory• Easy to link change history to current inventory

records• Change records s are sequenced and timestamped to

manage chronological sequence• Tracks all DML - insert, delete, update

W k ith f t d li t/ b23

• Works with any front-end – client/server or web• Delete tracking will support future recovery capability

Pontis Bridge Data Archiverg

• Works behind the scenes with Pontis 4 x (tested with• Works behind the scenes with Pontis 4.x (tested with 4.3/4.4/4.5)

• Reports written in Infomaker 10 ( future 11.2)p ( )• Works with Pontis 5.0 framework (September 2007)• Upgrade will be required for 5.1 compatibility• No .NET code• All server side

D t i t f t tili th O l Fi• Does not interface to or utilize the Oracle Fine Grained Auditing tools.

24

Pontis Bridge Data Archiverg

25

Pontis Bridge Data Archiverg

• Infomaker reportsp• Dynamic contents based

on query page selections• Tied into the Pontis 5.0

framework

26

Pontis Bridge Data Archiverg

• Oracle database views sequence, consolidate and group ChangesVi bit• Views are a wee bit complicated

• Generic dependence onGeneric dependence on Pontis 5.0/4.5 database schemaS h h i ht• Schema changes might impact archiver

27

Pontis Bridge Data Archiverg

• Oracle materialized views underlie reports

• Materialized views are h t i l thsomewhat simpler than

underlying views• Permits access toPermits access to

change data from data warehouseR b ilt VDOT d fi d• Rebuilt on VDOT-defined schedule or on-demand if needed

28

Future Directions

• Pontis 5.1 framework conversion• Add more change report and selection options• Extend coverage to other data tables• Incorporate automatic purging/expiration• Incorporate delete recover from change log• Incorporate change alerts• Rearchitect to take advantage of Oracle built-in Fine

Grained Auditing (FGA)Grained Auditing (FGA)

29

Contact Information

Dick Thompson, P.E.Virginia Department Of Transportation(804) 786-1024Richard.Thompson@VDOT.Virginia.gov

William Robert, Principal & Dmitry Gurenich, PhD.Cambridge Systematics, Inc.(617) 354-0167wrobert@camsys.com

Allen R. Marshall, PrincipalCambridge Systematics, Inc.(617) 234-0429

30

amarshall@camsys.com