Pavement 2.0 Guide Introduction

Pavement is comprised of two major components, configuring the mapping between database tables and importing and exporting between Cityworks and Pavement.

Cityworks Pavement 2.0 is a Cityworks app designed for organizations that use PAVER, a program for pavement management created by the U.S. Army Construction Engineering Research Laboratories (USACERL). Cityworks provides the work management system and access to the geodatabase through the Pavement app.

Designed to fully leverage the GIS investment, Pavement 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 Pavement. Pavement inventory is managed within the geodatabase and exported to Pavement via Cityworks, which links the geodatabase fields to corresponding fields in Pavement.

The geodatabase serves as the central asset repository open to multiple applications, thereby promoting a truly enterprise-wide solution. Pavement 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 Pavement.

Pavement inventory, work activities, and inspections are established and maintained in Cityworks. This information is exported to Pavement to calculate the PCI (Pavement Condition Index), perform pavement analysis, and utilize past pavement work histories to predict future pavement conditions. Pavement 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.

PREREQUISITES: The configured UID must be unique. Since many of the pavement work orders are issued against individual pavement sections, the user-defined identifier for those PAVER1 All product names, logos, brands, trademarks, and registered trademarks are property of their respective owners. All company, product, and service names used in this manual are for identification purposes only. Use of these names, logos, trademarks, and brands does not imply endorsement. PAVER™ is either a registered trademark or trademark of the US Army Corps of Engineers. sections must have a one-to-one relationship to the geodatabase assets. The work activities in PAVER and the work order descriptions in Cityworks relevant to pavement management must have identical names. If they are not identical, the Cityworks work orders will be listed in Pavement work form but will not be available for updating the condition assessment. Use the activities in PAVER as the work order descriptions in Cityworks. It is recommended that the work activities and codes are copied from Pavement and pasted into Admin as the work order template codes and descriptions. The Project Name field in the Pavement database is mapped to the Project Name field in the Cityworks database. That field is limited to 12 characters in the Pavement database, so project names in Cityworks cannot exceed that limit. Users of Pavement must have 15.4.1 or newer of Cityworks, which works with PAVER 7 and newer.

BEST PRACTICE: Pavement surveys should be collected and stored in Cityworks, then exported to PAVER. This way if anything happens to the Pavement 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.

NOTE: You can view the API documentation for Pavement by querying <server>/Services/General/PavementManagementInterface/help.

IMPORTANT: If you are moving from the old Cityworks Paver Interface to the Pavement app, be aware that Pavement uses the PAVER native import file formats which doesn't allow for populating the object ID in the PAVER system ID. If you are upgrading from Cityworks Paver Interface to the Pavement app, please contact customer support for assistance with the migration.

NOTE: All images were taken on a Google Chrome browser using the Light theme, and all steps, fields, and images are based on the latest version of Cityworks. There may be slight differences (i.e., functionality, fields, color branding, etc.) depending on other browsers and themes used and the current version of Cityworks you have installed.