You are here:

Pavement Management Interface

Cityworks Paver Interface 2.2 is a Cityworks add-on designed for organizations that use PAVER, the U.S. Army Construction Engineering Research Laboratories (USACERL) program for pavement management. Cityworks provides the work management system and access to the geodatabase for PAVER through the interface.

Designed to fully leverage the GIS investment, Paver Interface eliminates the need for costly duplication of asset data. Pavement managers create and maintain pavement (asset) inventory in the geodatabase, rather than building a database as tabular entries and shape files with unique identifiers in PAVER. Pavement inventory is managed within the geodatabase and exported to PAVER via the Cityworks interface, which links the geodatabase fields to corresponding fields in PAVER.

The geodatabase serves as the central asset repository open to multiple applications, thereby promoting a truly enterprise-wide solution. Pavement Management Interface also provides a communication link between Cityworks and PAVER to pass information back and forth between the two programs. Sharing data, such as pavement inventory, work orders, and inspections, increases the overall efficiency by utilizing the strengths of both Cityworks and PAVER.

Pavement inventory, work activities, and inspections are established and maintained in the Cityworks work management system. This information is exported to PAVER to calculate the PCI (Pavement Condition Index), perform pavement analysis, and utilize past pavement work histories to predict future pavement conditions. PAVER is also of significant value in planning pavement maintenance and rehabilitation (M&R) because it can set priorities of work to be done according to pavement condition and/or limit the work to a budgeted amount and available resources. This information can be used to schedule and track the recommended work activities. PCI, last construction date, and current surface type can also be imported into the geodatabase and symbolized on the map.

It is recommended, although not required, that pavement surveys be collected and stored in Cityworks, then exported to PAVER. This way if anything happens to the PAVER database, it can be recreated through the interface as the assets are maintained in the geodatabase and the inspections in the Cityworks database. As part of the GIS and Cityworks databases, the information would be part of a regular backup. Also, the Pavement Management Interface does not currently provide the ability to import inspections from PAVER to Cityworks. If pavement condition surveys are captured in PAVER and the inspection data is needed in Cityworks, it will need to be entered into Cityworks manually or converted.

Pavement Management Interface is comprised of two major components:

Configure the mapping between database tables.
Import/Export between Cityworks and PAVER.

Last updated 12/19/2019.