R.U.M.S.
(Right of Way and
Utilities Management System)
Overview
Right of Way Functions
Incorporated into RUMS





Right-of-Way Management (appraisal, acquisition,
improvement removal, relocation, legal, donation,
grave relocation)
Utility Management (design, easements, facility
adjustments)
Assignment Tracking (assignee, due and complete
dates, units of production)
Contract Management (contracts, task orders,
subcontractors, assignment-based security)
Property Management (sale, lease, property
grouping, historical tracking)
Problems Faced Before RUMS






Legacy System did not focus users on critical dates, allowing
milestones to be missed without warning
Inaccessibility of right-of-way data for management analysis
Legacy System made searching and updating information
difficult
Legacy System did not collect all important information forcing
users to enter such information in comments or not at all
Correspondence formats used throughout the state were not
standardized
Completion of correspondence and internal documentation
laborious
Accomplishments of RUMS







Addresses needs at all levels - from data entry through
management
Emphasizes management focus on advertisement date and
project status
Organizes all important RW&U information
Provides intuitive navigation for novice and advanced users
(increased productivity)
Eliminates redundant data entry in completing forms used
internally and those used externally to communicate with
citizens
Enables inquiry users to access information through browser
Contains extensive online help and tutorials to flatten learning
curve
RUMS Project Development Steps












As-Is / To-Be Analysis
Early Prototype
Design and Initial Data Model
Full Prototype (Functional Version 0.5)
Program Specs and Final Data Model
Development and Testing
Training (Just-in-time and repeatable)
Conversion for Pilot
Pilot (single district - 3 weeks)
Conversion for state-wide implementation
State-wide implementation
Maintenance
Highlighting a RUMS Feature Forms Processing







Standardized forms (i.e., internal memoranda, external
correspondence, etc.) for all RUMS users
User presented with forms applicable to the screen currently
being viewed in RUMS - eliminating the need to search through
a myriad of unrelated forms
Forms populated with information from the RUMS database eliminating redundant data entry
Forms can be modified with full power of Microsoft Word
Forms can be updated remotely - user does not have to be in
the RUMS application
Completed forms stored in RUMS for viewing
“Sandbox” concept allows new forms to be created without
updates to RUMS software
Web Based Reporting






Reports defined with Crystal Report Writer
Reports executed on “Cizer” (third-party product) Web Server
and viewable by users via the Web Browser
Web server is a powerful machine, and has fast connection to
database, allowing efficient execution of Crystal Reports
Cizer allows scheduling of reports and can limit the number of
simultaneous reports processing against the database
Client is not locked while report is executing
Needs of 500 inquiry users satisfied via Web
Technology Utilized








Oracle 8i
Visual Basic 6.0
Sheridan VB Extensions: Data Widgets, Active
TreeView, Designer Widgets
MS Word 2000 / VBA (with Word 97 compatibility)
Mercury Testing Tools: TestDirector / LoadRunner /
WinRunner
Crystal Report Writer
Cizer (Web Enabled Report Execution)
ADABAS SQL Gateway (interface to other system)
Current Status / Enhancements

User base broadening based on system success and
understanding of capability

Pursuing Web-enablement opportunity

Flexible system architecture allowing system
enhancements/expansions to be made (over 200)

Software copyrighted has been obtained
Contacts
C.L. “Les” Griggs, Jr.
RUMS Project Manager
Right of Way and Utilities Division
VDOT Central Office
(804) 786-2917
griggs_cl@vdot.state.va.us