a conceptual framework for an enterprise ......planning, engineering, and mapping, and are strongly...

A CONCEPTUAL FRAMEWORK FOR AN ENTERPRISE-WIDE

GEOSPATIALLY ENABLED INFORMATION MANAGEMENT

SYSTEM FOR TRANSPORTATION RIGHT-OF-WAY

BUSINESS PROCESSES

Kavya Sambana

Thesis submitted to the faculty of the Virginia Polytechnic Institute and State University in

partial fulfillment of the requirements for the degree of

Master of Science

In

Civil Engineering

Kathleen L. Hancock, Chair

Gerardo W. Flintsch

Pamela M. Murray-Tuite

May 13, 2010

Falls Church, Virginia

Keywords: Right-of-Way (ROW), Geospatial Decision Making Activities (GDMA),

Geographical Information System (GIS), Parcel Tracking (PT), Geospatial Enablement (GE),

Uniform Modeling Language (UML)

A CONCEPTUAL FRAMEWORK FOR AN ENTERPRISE-WIDE

GEOSPATIALLY ENABLED INFORMATION MANAGEMENT

SYSTEM FOR TRANSPORTATION RIGHT-OF-WAY

BUSINESS PROCESSES

Kavya Sambana

ABSTRACT

Right-of-way business processes have been identified as one of the areas where information

bottlenecks occur in transportation agencies, not only because of the amount of information

involved, but also because of the interdependent nature of these activities. Transportation

projects are associated with parcels whose status change during and after the project based on

information from right-of-way activities. Geospatially enabled decision making tools enhance

data interpretation as well as data retrieval of this information. By using enterprise-level

applications, information sharing between the transportation agency, other jurisdictions, and the

public becomes more efficient. Being able to quickly visualize the status of parcels in a

geospatial environment further enhances the management of resources which, in turn, improves

timely project delivery. This thesis presents a conceptual framework for an information

management system and its geospatial enablement through a logical model for Geospatial

Decision Making Activities (GDMA) in transportation right-of-way offices. The logical model

for GDMA, presented in Unified Modeling Language, includes state machine diagram and data

flow diagram models for tracking the parcel and capturing the geospatial enablement of right-of-

way activities.

iii

ACKNOWLEDGEMENTS

I would like to thank my advisor Dr. Kathleen Hancock for granting me the opportunity

to work on this project and making the journey through my Masters a great learning experience. I

am ever grateful for her constant support and encouragement that helped me to complete my

Masters successfully.

I would like to thank my committee members, Dr. Pamela Murray-Tuite and Dr. Flintsch

for their valuable suggestions and advice through the entire research process. My sincere thanks

are due to Marija Telbis-Forster at Virginia Tech, for all her support and co-operation. I also

would like to thank Neelima Ghanta and and Qifeng Lu for their research contribution in

designing various individual components of the overall logical model, and also for their valuable

guidance in my initial days of Masters. I would like to further extend my special thanks to

Neelima, for her constant source of encouragement and her continuing support.

DEDICATIONS

I would like to dedicate this thesis to my parents and my sister, for their unconditional

love and their constant support in my academic pursuits. Without their encouragement and

support I wouldn‟t have been where I am right now. Finally, I would like to thank all my friends

who have always been there and extended their support during my weakest times.

iv

Table of Contents

Abstract……………………………………………………………………...……………...ii

Acknowledgements………………………………………………………………………...iii

Dedications……………………………………....................................................................iii

Table of Contents…………………………………………………………………………..iv

List of Figures………………………………………………………………………….…..vi

List of Tables……………………………………………………………………………...vii

1 INTRODUCTION…………………………………………………………………….1

1.1 Research Objective .............................................................................................. 3

1.2 Research Approach .............................................................................................. 3

1.3 Thesis Contribution .............................................................................................. 4

1.4 Thesis Organization ............................................................................................. 5

2 LITERATURE REVIEW……………………………………………………………6

2.1 Right-Of-Way Information Management systems............................................... 6

2.1.1 Stand-alone Systems ................................................................................... 7

2.1.2 Small Enterprise Systems ........................................................................... 8

2.1.3 Large Enterprise Systems ........................................................................... 9

2.2 Geographical Information Management Systems In Right-Of-Way ................. 12

2.2.1 Stand-alone Systems ................................................................................. 12

2.2.2 Small Enterprise Systems ......................................................................... 13

2.2.3 Large Enterprise Systems ......................................................................... 14

2.2.4 Vendor Provided Systems ......................................................................... 15

2.3 Summary ............................................................................................................ 16

3 AN ENTERPRISE WIDE INFORMATION MANAGEMENT SYSTEM FOR

TRANSPORTATION RIGHT-OF-WAY ACTIVITIES………………………....18

3.1 Introduction ........................................................................................................ 20

3.2 Background ........................................................................................................ 21

3.2.1 Current Right-of-Way Information Management for Transportation Real

Estate Offices. ........................................................................................... 21

3.2.2 Logical Model Design............................................................................... 24

3.3 Proposed Model Architecture ............................................................................ 26

v

3.4 Model Development........................................................................................... 31

3.4.1 Behavioral Model Views .......................................................................... 31

3.4.2 Interaction Model Views........................................................................... 41

3.4.3 Structural Model Views ............................................................................ 44

3.5 Conclusions And Future Work .......................................................................... 50

4 A FRAMEWORK FOR GEOSPATIALLY ENABLING THE BUSINESS AND

INFORMATION OF TRANSPORTATION RIGHT-OF-WAY ACTIVITIES...55

4.1 Introduction ........................................................................................................ 56

4.2 State Of The Practice ......................................................................................... 57

4.3 Geospatial Decision Making Activities ............................................................. 59

4.3.1 Parcel Tracking ......................................................................................... 59

4.3.2 Geospatial Enablement ............................................................................. 68

4.4 Significance........................................................................................................ 72

4.5 Conclusion ......................................................................................................... 74

5 MODELING AND EVALUATING - GEOSPATIAL DECISION MAKING

ACTIVITIES (GDMA)…………………………...………………………………...77

5.1 GDMA Model .................................................................................................... 77

5.1.1 Parcel Tracking State Machine Model ...................................................... 79

5.1.2 Geospatial Enablement Data Flow Model ................................................ 89

5.2 GDMA Model Evaluation.................................................................................. 96

5.2.1 GDMA Evaluation Process ....................................................................... 97

5.2.2 GDMA Evaluation Results ....................................................................... 97

6 CONCLUSIONS AND RECOMMENDATIONS………………………...……..101

6.1 Conclusions ...................................................................................................... 101

6.2 Recommendations ............................................................................................ 102

References………………………………………………………………..…………….104

Appendix A: Summary of Right-of-Way Information/Content Management Systems by

State…………………………………………………………………………………......108

Appendix B: Right-of-Way Business Process Diagrams……….………………….…...114

Appendix C: UML Diagram Documentation………………………………….………..121

vi

List of Figures

Figure 3.1: UML diagrams included in the model and their classification .................................. 26

Figure 3.2: Agency actors identified in the right-of-way system ................................................. 28

Figure 3.3: Human actors identified in the developed right-of-way system logical model .......... 29

Figure 3.4: Overall Right-of-Way Process Flow .......................................................................... 30

Figure 3.5: Component model view of the Overall Right-Of-Way system in UML depicting the

other integrated external systems .................................................................................................. 31

Figure 3.6: Business Process Model diagram for Relocation planning ........................................ 33

Figure 3.7: Sequence Diagram for the use case „REL_Open Site Office‟ .................................... 42

Figure 3.8: Communication Diagram for the use case „REL_Open Site Office‟ ......................... 43

Figure 3.9: Class Model diagram for Relocation planning ........................................................... 45

Figure 3.10: Component Model diagram for Relocation planning ............................................... 47

Figure 3.11: Package model diagram illustrating relocation use cases packages ......................... 49

Figure 4.1: Logical Flow Chart for Parcel Tracking..................................................................... 61

Figure 5.1: Parcel Tracking State Machine Model Diagram ........................................................ 82

Figure 5.2: Overview of Geospatial Enablement Data Flow Diagram Model ............................. 90

Figure 5.3: Geospatial Enablement Data Flow Diagram for Project Development ..................... 91

Figure 5.4: Geospatial Enablement Data Flow Diagram for Appraisal ........................................ 92

Figure 5.5: Geospatial Enablement Data Flow Diagram for Relocation ...................................... 93

Figure 5.6: Geospatial Enablement Data Flow Diagram for Property Management .................... 94

vii

List of Tables

Table 3.1: Examples of right-of-way systems currently in use by various agencies .................... 22

Table 3.2: List of Activities captured in the Business Process Model of the right-of-way system

....................................................................................................................................................... 34

Table 3.3: Summary of Use Cases for Relocation planning ......................................................... 40

Table 4.1: Summary of systems with geospatial technology applications in Right-of-Way Offices

....................................................................................................................................................... 58

Table 4.2: Attributes or States in Parcel Tracking of GDMA ...................................................... 62

Table 4.3: Identified Right-of-Way Activities for Geospatial Enablement .................................. 69

Table 5.1: State Machine Diagram Elements ............................................................................... 78

Table 5.2: Data Flow Diagram Components ................................................................................ 79

Table 5.3: Summary of resources for Geospatial Enablement ..................................................... 95

Table 5.4: Summary of changes to GDMA model based on evaluation process ......................... 99

1

1 INTRODUCTION

Right-of-way (ROW) or Real Estate offices in state transportation agencies are

responsible for the appraisal, acquisition, management of land required for federally funded

highway projects and the relocation of those directly impacted by the purchase of that land. The

document and data intensive nature of these activities support the need for electronic

management of information [1]. The automation of right-of-way business functions and

development of business models for an information management system using geospatial

technology provide consistency and efficiency in managing this information effectively.

Many states have streamlined data entry, display, archiving and sharing of information

for one or more of the principal functional areas [1, 2]. However, few have taken advantage of

geographic information systems (GIS) which is closely tied to right-of-way activities particularly

those related to parcel data and the defined transportation right-of-way which are geospatial in

nature [1]. This research focuses on developing a feasible framework for geospatially enabling

the management of information for these right-of-way activities to help improve business

performance. It includes the identification of how right-of-way offices in various transportation

agencies currently use GIS and the state of the practice on the implementation of enterprise-wide

information management systems. With this understanding, this research developed a logical

model for geospatially enabling activities in an enterprise-wide information system for managing

right-of-way business process and information. The enterprise of right-of-way activities consists

of four major functions; Appraisal, Acquisition, Relocation, and Property Management [3, 4].

2

Other areas that are often part of the business of right-of-way offices include aspects of

planning, engineering, and mapping, and are strongly associated with geospatially intense data.

GIS has been used extensively by transportation agencies to support such activities [2, 5, 6].

Similarly, utility management and outdoor advertisement activities have also begun to use GIS

applications [5, 6]. Although several transportation agencies have used GIS as a stand-alone

application for these and other related right-of-way activities, an operational centralized and

systematic enterprise-wide geospatially enabled information management system for principal

right-of-way activities had not been identified at the time of this research as indicated by the

results of a literature survey shown in Appendix A.

Thus, the need exists for the development of a conceptual framework for a geospatially

enabled enterprise-wide right-of-way information management system to meet the business

needs and data processing requirements across the right-of-way office. The implementation of

such a system could result in an increase in the overall organizational efficiency by improving

personnel efficiency and project delivery time, improving the coordination between activities and

communication between individual sections of the right-of-way offices, and enhancing effective

decision making.

This research identifies the opportunities for geospatial enablement in the right-of-way

business process and captures the flow of geospatial data in a prototypical geospatial right-of-

way information management system logical model. This is accomplished by building a

Geospatial Decision Making Activities (GDMA) logical model that reflects two primary aspects

of the geospatial decision making activities. First, the model tracks the flow of the geospatial

parcel data across the right-of-way project process, captured under Parcel Tracking (PT).

Second, it identifies areas where decision making could be enhanced through electronic linking,

3

querying and presentation of data that has a geospatial component associated with it, designated

as geospatial enablement (GE).

1.1 Research Objective

The goal of this research was to develop a conceptual framework for a geospatially

enabled enterprise information management system for state transportation right-of-way offices.

The objectives were to:

Understand the current state of the practice of enterprise-wide geospatially enabled right-

of-way information management systems in transportation agencies;

Identify and define geospatial decision making activities for principal areas in the right-

of-way business process;

Develop a logical model with the corresponding state machine and data flow diagram

models that would explicitly enable the tracking of a parcel in a geospatial environment,

capture the geospatial activities and structure the flow of geospatial data within an

enterprise information management system.

1.2 Research Approach

The first step in the research was to define the current state of the practice of enterprise-

wide geospatially enabled right-of-way information management systems in state transportation

agencies through a literature review. The next step was to develop the logical model for the

enterprise-wide information management system and to identify what activities could be

4

geospatially enabled as well as what data was necessary to track parcels through the process.

From this a Geospatial Decision Making Activities (GDMA) model for right-of-way business

process was developed. A threefold approach was employed, which constituted of:

Conceptualizing the overall business processes of right-of-way offices and their

geospatial decision making activities, including Parcel Tracking and Geospatial

Enablement and standardizing the framework for the model. The business process

diagrams are shown in Appendix B.

Building the overall and GDMA logical models in Uniform Modeling Language (UML)

using Enterprise Architect [7], which are included in Appendix C.

Evaluating the model through detailed discussions with the Utility and Right of Way

Section of PennDOT Office.

1.3 Thesis Contribution

The overall and GDMA models are expected to serve as frameworks for state

transportation agencies to use in developing systems to meet their specific requirements to

geospatially enable right-of-way business processes. This includes:

Providing structure and knowledge base for transportation agencies for integrating geospatial

technology into enterprise-wide right-of-way information management system

Providing insight on the flow of geospatial parcel data within the right-of-way offices to

visualize the significance of incorporating GDMA.

Contributing to the development of new integrated geospatial right-of-way information

management systems or the improvement of existing systems

5

1.4 Thesis Organization

This thesis follows the alterative manuscript format for dissertations/theses, and is

organized into six chapters. Chapter 1 presents an introduction, research objectives, approach

and contribution of the thesis. Chapter 2 presents a review of relevant literature. The first

manuscript presented in Chapter 3 provides a background of the research that describes the

overall logical model of an enterprise-wide information management system. The second

manuscript in Chapter 4 describes the framework developed for geospatial decision making

activities. Chapter 5 presents an overview of the developed model in UML using state machine

and data flow diagrams, along with the model evaluation process that was performed with the

cooperation of PennDOT. Finally, Chapter 6 presents the conclusions and recommendations for

further research.

6

2 LITERATURE REVIEW

A review of the current state of the practice in information management systems for

transportation agency right-of-way business activities and other relevant agency information

systems was conducted followed by a review of the current architecture and implementation of

geospatial capabilities for management systems in right-of-way.

2.1 Right-Of-Way Information Management systems

Electronic management of information is an important step in improving the efficiency of

any data intensive task. Several states have implemented different types of information

management systems at different levels in their right-of-way or real estate offices. These systems

vary from those that perform a specific activity to comprehensive systems that operate at an

enterprise-wide level. This section provides an overview of existing systems for right-of-way in

use at the time of this research.

These systems have been categorized into three general groups: Standalone Individual

Systems, Small Enterprise Systems, and Large Enterprise Systems and Integrated Systems.

Appendix A summarizes Information/Content Management Systems across states.

7

2.1.1 Stand-alone Systems

Several standalone systems are currently in use by the state transportation agencies.

Typically these systems were developed for a specific activity within the right-of-way project

process like asset management, acquisition, outdoor advertising, etc.

Examples of these standalone systems include the Indiana DOT and Maryland DOT.

Indiana has a Land Record System (LRS) that maintains a database of all the land records [8]. It

is used to track project and parcel activities for the Property Management function. Maryland

has a standalone application for acquisition activities called the Office of Real Estate

Management System (OREMS) which uses a database to store and manage acquisition

information [9, 10]. South Carolina also has a system for their acquisition activities, using a

centralized computer database. It further has an integrated document repository to manage the

right-of-way acquisition activities [9, 11]. New York has an in-house application used to track

payments and generate pay packages [9]. This system is considered a stand-alone system but

may have the capability to link to other processes in design, planning and right-of-way mapping.

A different type of stand-alone system is Wisconsin‟s Transportation Utility and

Management System (TUMS), which is used across the state for highway projects to identify,

track and manage correspondence between offices in accordance with the WisDOT guide to

utility coordination. [12].

An information system under development for determining relocation assistance benefits

for displaced residents and businesses is AASHTO‟s Turbo Relocation. This system is being

developed by Balanced Environmental Management Systems (BEM), in cooperation with

AASHTO and the Turbo Relocation Task Force to provide an interactive software product to

assist states in consistently calculating relocation benefits [13].

8

2.1.2 Small Enterprise Systems

Small enterprise systems either manage information for more than one principal area of

the right-of-way management processes or focus on a single activity, such as document

management across the right-of-way office or agency.

Right of Way Management Information System (ROWMIS), developed by Caltrans, is an

example of one such small enterprise system [12]. This system helps to facilitate the planning

and management of highway projects and parcel acquisition across the state of California. It is a

web-based application with a secure centralized database containing project, parcel and

acquisition information. The system currently does not include appraisal and relocation

assistance apart from the capability to generate forms. Right-of-way Information System

(ROWIS) of Texas, built on SQL Server, is another such system that captures data related to

project setup, mapping, funding, appraisal, negotiations, and eminent domain [11]. This system

also does not include relocation and property management of the right-of-way project process.

Missouri‟s inventory management system called the Realty Asset Inventory (RAI) is a

small enterprise system that is used statewide to manage Missouri‟s realty assets and to identify

properties that are no longer needed for highway purposes [12, 14]. RAI is a computerized

relational database system that documents all sales, leases and excess properties with additional

reference to other realty of interest, such as environmental, cultural, historical, and wetland

mitigation sites. However, the system does not consider other aspects of right-of-way like

appraisal and relocation. It does include an embedded right-of-way parcel acquisition database

that documents acquisition information. Similarly, Nebraska has an application that uses a Lotus

based system that interacts with DB2 and MicroStation called the Automated Right-of-way

Management System (ARMS) [11]. This includes project tracking data and a document

9

generation capability. This system focuses on appraisal with some of the negotiation modules but

does not include relocation and property management aspects of the right-of-way management.

Image Records Management System (IRMS) is another example of a small enterprise

system for Connecticut which creates and tracks the right-of-way documents using an Oracle

database [15]. Although, this system only manages the documents, it is categorized as a small

enterprise system for its enterprise-wide usage. North Dakota uses a small-scale enterprise-level

application called the Records Information Management System (RIM) consisting of multiple

databases which are integrated with File-Net to manage right-of-way records and files [9].

2.1.3 Large Enterprise Systems

Several states have more comprehensive enterprise systems that include most of the

major right of way activities. Virginia‟s Right-of-Way Utilities Management System (RUMS) is

a web-based system that runs on an Oracle database to track the real estate acquisition process on

a project-by-project basis and includes a powerful document management feature [1]. It supports

the right of way and utilities business from the estimate stage through condemnation by tracking

evaluations, negotiations, legal functions, relocation of families and businesses, disposition of

improvements and the relocation of utility facilities. Real Estate Management Information

System (REMIS) of Michigan is also a fully integrated enterprise level information management

system for right-of-way activities featuring immediate updating of reports and schedules [16].

REMIS provides easy access to data through organized folders within the system such as job

folder, parcel folder, relocation folder, condemnation folder etc. Both, RUMS and REMIS

capture most of the functional areas in right-of-way.

10

Real Estate Automated Data System (READS) of Wisconsin (WisDOT) and Appraisal,

Acquisition, and Relocation System (AARS) of the Louisiana Department of Transportation and

Development (LA DOTD) also have large enterprise systems. READS allows users to obtain

status updates on any parcel through streamlining and simplifying the daily highway/real estate

operations [17]. This automated system includes extensive data tracking, report generation and

analysis for acquisition, land inventory, cost estimation, litigation, accounting, property

management, appraisals and relocation. AARS is a web based intranet/internet application using

Oracle database and includes detailed appraisal, acquisition and relocation workflow processing

needs as defined by the LA DOTD Real Estate Section [9, 18].

Other states that have automated Right of Way processes at an enterprise-wide level

include Oregon and Pennsylvania. Oregon‟s Right of Way Data Management System (RWDMS)

is an enterprise content management initiative for right of way project processes [19, 20]. The

system assists in the effective management of the state‟s database of assets through ODOT's

Intranet and FileNet programs. Pennsylvania Department of Transportation‟s (PennDOT) system

called the Right of Way Office Information System is a state-wide system that standardized the

property information into a single electronic case folder for each land parcel. PennDOTs

comprehensive management tool incorporates innovative data-integration capabilities and

supports Right-of-Way appraisal, negotiation, relocation, and property management [6, 21]. It

also includes administration of the project, appraisers and district activities, and tracking of legal

information, along with the management of contracts, task orders, and subcontractors.

Nevada DOTs Right of Way Information Network (IRWIN) is another example of an

integrated system for the management of their right of way information to facilitate streamlined

workflow and common interface solutions [22, 23]. The system supports inventory, access,

11

retrieval, management and reporting of all DOT right-of-way properties and allows users to track

work processes and access stored documents from a centralized information center. The system

integrates with NDOT's GIS, Public Lands Survey System data and video logging system,

electronic document management system and NDOT's Integrated Financial System.

Washington State Department of Transportation is another example for an integrated

system. Its web-based Right-of-Way Management System, known as the Integrated Realty

Information System (IRIS), has helped in structuring their land acquisition processes [12]. The

system provides advanced reporting and management workflow that helps WSDOT with the

efficient management of the property acquisitions, financial data, and project/property costs.

WSDOT plans to expand the system to integrate with GIS to further advance its capabilities by

locating the properties affected by an acquisition and displaying them geospatially.

In general these, larger enterprise systems enable data sharing across divisions of right-

of-way but do not necessarily communicate with other major information systems transportation

agencies. Alabama is one exception that integrates its right of way system with its

Comprehensive Project Management System (CPMS), along with several other systems

including Disadvantaged Business Enterprises program (DBE), Right-of-Way, Storm Water,

Consultant Management, State-wide Transportation Improvement Program (STIP) and

Transportation Economic Land Use System (TELUS) [24]. The right-of-way management sub

system includes 6 major processes; project status, right-of-way mapping, appraisal status,

acquisition, relocation, and leased property as well as a comprehensive reporting module.

Review of the literature indicates that there are several information systems being used

by transportation agencies to support right-of-way activities. Many states employ stand-alone

12

applications while a much smaller number have larger enterprise systems covering all the major

right-of-way business processes.

2.2 Geographical Information Management Systems In Right-Of-Way

The use of geographic information system (GIS) as an analysis and decision making tool

in state transportation agencies has been increasing steadily since the early 1990's. A number of

agencies use GIS to manage, analyze and disseminate geospatial information, making data more

accessible to the decision maker and enhancing the data interpretation capability. When location

is brought to bear on any fundamentally spatial activity, such as transportation, managing and

analyzing information is more effective and powerful.

Thus, geospatial enablement of an information management system adds value to the

system by enabling new methods of integration and ways of visual interpretation of data. Several

stand-alone and some enterprise level applications of GIS are currently in use by transportation

right-of-way offices. Similar to section 2.1, this section groups systems according to their

complexity from stand-alone system to geospatially-enabled information management systems.

In addition, a section on vendor software designed for right-of-way applications is provided.

2.2.1 Stand-alone Systems

Most stand-alone systems use GIS to enhance data viewing and extraction capabilities

and not as an analysis tool. Maryland‟s MdProperty View is an individual system that includes

scanned images of property maps and digitized parcel centroids which link each property to the

State Department of Assessments and Taxation‟s parcel database [6]. The Office of Real Estate

13

uses this system to obtain parcel information for obtaining property information for the

acquisition of right of way for transportation projects. In Texas, San Antonio‟s Right of Way

Application is an Internet-based tool which provides users with access to scanned images of all

past and current right-of-way maps by interactively selecting a location in the district from

pointing and clicking on a GIS interface. San Antonio District right of way professionals, as well

as other DOT employees, use this system to view project information from any computer

connected to the internet/intranet [6].

Geographical Information System based Management Information System (GISMIS)

used by New Jersey integrates its digitized document database with geospatial highway database

of digital roadway plans and right-of-way maps [25]. This is a standalone system used for the

effective management and retrieval of requested documents from a very large scanned digital

document database.

New Mexico‟s Non-Right of Way (NRW) Parcel & Improvement Inventory system is a

standalone GIS application that enables automated generation of NRW Parcel and Improvement

Inventory summary sheets which include geospatial view of parcel locations [6].

Florida has integrated GIS into several departments in its right-of-way office [26]. As an

example, Outdoor Advertising Inventory Management System (ODAMIS) is a client/server

application created specifically for the regulation of outdoor advertising signs. GIS enables users

to view sign locations on a map.

2.2.2 Small Enterprise Systems

As discussed earlier in Section 2.1.2, small enterprise systems either manage information

for more than one principal area of the right-of-way management processes or focus on a single

14

activity across right-of-way office or agency. Highway Access Management System (HAMS) of

Wisconsin can be categorized as a small enterprise-level information management system that

brings together diverse information for managing driveway permits and land division reviews [6,

12]. HAMS has combined the capabilities of several components into one geospatially driven

web interface, enabling straightforward interaction between end-users and the system.

2.2.3 Large Enterprise Systems

Large scale enterprise systems using GIS have only been implemented in Minnesota at

the time of this research, although several states have plans to add GIS capabilities. Right-of-

way Electronic Acquisition Land Management System (REALMS) is a larger enterprise-wide

system that is used by the Minnesota Department of Transportation to support right-of-way

acquisition and land management functions [12]. This web-based, online system allows users to

quickly access and search right-of-way information, visualize and track parcel geometry, and

customize and generate reports. Users are able to search for a record in REALMS and view it in

the map view as well as search for REALMS data in the map and view information from the

REALMS database, thus providing an enhanced integrated geospatial capability to the system.

The following systems have specific plans to incorporate GIS into their systems but are

not currently geospatially enabled. Right of Way Management System (RWMS) of Florida is a

large web-based enterprise system used to record and track all right-of-way activities including

acquisition, eminent domain, relocation, property management, business damages, contracting,

appraisal, cost estimating and funds management using Hummingbird DM product [9, 27].

Although the system currently has no integrated GIS, it has the capability to integrate geospatial

technologies and Florida is working on a building an enterprise GIS. Mississippi‟s Right of Way

15

Parcel Tracking System (PTS), which has the capability to interface with a GIS in the future,

currently manages information flow of the full range of right-of-way activities that include title,

parcel deed, development, appraisal, negotiation/acquisition, relocation, eminent domain,

hazardous material sites and improvements [28].

Oregon‟s FileNet Enterprise Content Management (ECM) application enables access to

the right-of-way data (township, range, file number, record number, deed date, history of deed

sales etc) of each parcel to its users [14]. The data was captured and indexed by the placement of

centriods. Oregon is expecting that the legal description creation process and the appraisal

description process will be automated, after which, relocation, condemnation, acquisition

activities are anticipated to be moved into the system. Eventually, ODOT plans to expand the

application to make mass acquisition cost estimates based on historical data and prices and to

access all documents through a GIS interface that displays the parcel polygon instead of the

current centroids.

2.2.4 Vendor Provided Systems

Off-the-shelf systems developed by vendors include Land and Right-of-Way Acquisition

Management & Record Keeping by the Diversified Energy Software Solutions (DESS) [29]. It is

advertised as a secure systematic application that streamlines the entire life-cycle of the land and

right of way acquisition process, and rapidly provides acquisition and property information. It

covers several right-of-way areas like, Agent Daily Report Logs, Documents and Digital

Content, Agent-Owner Contact Diaries, Court Orders, Tract Financials, Project Financials, On-

Demand Reporting, GIS Map Integration, Special Provisions, Owner Contact Records,

Condemnation, Tie Plats, Title Opinions, Negotiations, On-Demand Searching and Personnel

16

Task Tracking. Similarly, Balanced Environmental Management (BEM) Systems has developed

a system called Paecetrak which is a web-based, GIS-enabled application advertised to manage

the acquisition of properties for transportation system right-of-way [30]. This system is currently

being used for NJTransit capital programs.

DREAMaps is yet another off-the-shelf application developed by Smart Data Strategies

Inc [31]. It is a web-based, GIS-enabled commercial application for right-of-way Management

that has a modular architecture allowing seamless integration by wrapping around existing

workflows with web and desktop platform compatibility, web browser support, and product

security. Illinois‟s Aeronautical Land Acquisition System (ALAS) that has been developed to

analyze and aid in the decision-making process of the property in those areas that are being

considered for the airport and related facilities, is built on Dream Maps [6]. This system also has

an electronic file cabinet module that allows users to scan and link documents to related parcels.

2.3 Summary

This discussion shows that GIS has emerged as an important tool for achieving

standardization and coordination for data analysis and sharing across right-of-way organizations.

Individual applications have limited but measurable benefits for right-of-way. Small enterprise

systems enhance capabilities across one or two areas of right-of-way offices. Large systems

cover multiple right-of-way areas but are not currently integrated with an enterprise GIS. This

identifies the need to provide states with a template for developing an enterprise wide

geospatially enabled information management system to help enhance the overall right-of-way

project process.

17

With data centrally accessible and efficiently organized, the possibilities for extraction

and analysis are greatly expanded. Geospatial integration will help streamline projects from the

initial planning stages through construction and maintenance phases. Further, some

transportation agencies are migrating to maintaining geospatial data warehouses where layers of

information are maintained and served out to agency stakeholders. Integrating information

management systems with these geospatial warehouses is necessary to the effective

implementation of a geospatially enabled system.

This research identifies the need for a comprehensive geospatially enabled application

covering the principal activities of right-of-way. The developed framework is expected to serve

as a working template for state right-of-way offices to move to such an enterprise-wide

geospatially enabled information management system.

18

3 AN ENTERPRISE WIDE INFORMATION MANAGEMENT SYSTEM FOR TRANSPORTATION RIGHT-OF-WAY

ACTIVITIES

Kavya Sambana

Graduate Assistant, Via Department of Civil and Environmental Engineering

Virginia Polytechnic Institute and State University,

1101 King St. Suite 610, Alexandria VA 22314

Phone: 703-349-9820

FAX: 703-518-3145

[email protected]

Kathleen L. Hancock, Ph.D., P.E.

Director, Center for Geospatial Information Technology

Associate Professor, Via Department of Civil and Environmental Engineering

Virginia Polytechnic Institute and State University,

1101 King St. Suite 610, Alexandria VA 22314

Phone: 703-518-2718

FAX: 703-518-3145

[email protected]

19

ABSTRACT

Given the current state of technology with service oriented architecture, decentralized

information and desktop access to cloud computing and data management, enterprise systems for

managing the information associated with business operations are necessary for improving

efficiency and quality while optimizing resources. In transportation agencies, this is particularly

true in the data intense real estate offices that purchase and manage right-of-way property prior

to construction. This paper presents a structure for a logical model of an enterprise-wide

information management system for transportation right-of-way activities. The business

processes are based on the federal requirements as mandated by the Uniform Act and outlined in

the Federal Highway Administration‟s Office of Real Estate Services Project Development

Guide for appraisal, acquisition, relocation, and property management. The logical model is

developed using unified modeling language, which is considered to be a standard computer

system modeling language rich in well-defined graphical notations for representing complex

systems and provides the structure for developing an operational information management

software program.

20

3.1 Introduction

The information intense activities of transportation agencies which manage the appraisal,

acquisition and management of land required for highway projects and the relocation of those

directly impacted by the purchase of that land, are often attributed as one of the reasons for

delays in transportation projects. With the increased attention to on-time performance, the need

for more effective management of right-of-way information has been identified as a priority for

these agencies. Use of information technology for automating and right-of-way data entry,

archiving, display and sharing of information for one or more of these principal functional areas

has been in practice by several states and currently provide many benefits to the user [1, 2]. To

fully realize the potential of effectively managing information, an enterprise-wide approach to

coordinating the information associated with right-of-way programs is necessary, and would

result in greater efficiency and improved project delivery, as well as improved interoperability

and data consistency throughout the transportation agency [3]. To assist agencies with building

or expanding these information management capabilities, a standardized framework based on

FHWA‟s Project Development Guide [4], and Uniform Act [5], for such a system has been

developed and presented in this paper.

A summary of how transportation right-of-way offices are currently using information

systems is presented, followed by a discussion of a detailed modeling approach employed for

developing the proposed right-of-way system logical model using unified modeling language

(UML). The model has been designed to encompass the four primary functional areas that exist

in state transportation real estate offices: appraisal, acquisition, relocation, and property

21

management. Geospatial enablement and interoperability with other information systems are also

included in the logical model framework.

3.2 Background

3.2.1 Current Right-of-Way Information Management for Transportation Real

Estate Offices.

Electronic management of information is a principal step in improving the efficiency of

any data intensive task. Several states have implemented information management systems at

different levels in their right-of-way or real estate offices. These systems vary from individual

applications for a specific activity to more comprehensive systems that operate across several

activities. A brief overview of some existing right-of-way systems is summarized in Table 3.1.

Individual systems typically support a single activity. They include applications

developed to manage limited data using desktop computers, or assist in specific computations

with the help of excel spreadsheets, or in generating pay packages or specific documents using

pre-defined templates. Some systems manage information for more than one principal area in a

right-of-way office or focus on a single activity, such as document management, across all areas

in a right-of-way office. These systems are classified as small enterprise systems. More

comprehensive systems that include the majority of right-of-way functional areas are classified

as large enterprise systems and range from customized enterprise database management systems

to complex information management systems such as Alabama‟s Comprehensive Project

Management System (CPMS). CPMS is a broad system that integrates its right-of-way system

with a larger project management system and several other systems like Disadvantaged Business

22

Enterprises program (DBE), Right-of-Way, Storm Water, Consultant Management, State-wide

Transportation Improvement Program (STIP) and Transportation Economic Land Use System

(TELUS) [6]. The right-of-way management system that forms a sub-system to the CPMS

includes six major processes; project status, right-of-way mapping, appraisal status, acquisition,

relocation, and leased property management.

Table 3.1: Examples of right-of-way systems currently in use by various agencies

System Agency/State

Primary Functional areas of

Application

Ind

ivid

ua

l S

yst

ems

Outdoor Advertising Inventory

Management System (ODAIMS) [7] Florida Outdoor advertising signs regulation

Office of Real Estate Management

System (OREMS) [8, 9] Maryland Acquisition

Right of Way Parcel Acquisition

database [8] Missouri Acquisition

Transportation Utility and

Management System (TUMS) [10] Wisconsin

Management and tracking of correspondences

between offices

Sm

all

En

terp

rise

Sy

stem

s

Right of Way Management

Information System (ROWMIS)

[10]

California Planning and Management of highway

projects; Parcel acquisitions

Image Records Management System

(IRMS) [8] Connecticut

Document Management for right-of-way

documents and maps

Realty Asset Inventory Management

System (RAI) [10] Missouri

Management of Realty assets, sales, leases

and excess properties

Integrated Right-of-Way

Information Network (IRWIN) [11,

12]

Nevada Property acquisition and property

management

Automated Right-of-Way

Management System (ARMS) [13] Nebraska Appraisal; Negotiation (partly),

Records Information Management

System (RIM) [8] North Dakota Management of right-of-way records and files

Right-of-Way Information System

(ROWIS) [13] Texas

Management of data related to project setup,

mapping, funding, appraisal, negotiations and

eminent domain

In-house system [8] Utah Electronic content management

Highway Access Management

System (HAMS) [10] Wisconsin

Management of information related to

driveway permits and land division reviews.

23

Table 3.1: Examples of right-of-way systems currently in use by various agencies (Cont.)

System Agency/State

Primary Functional areas of

Application

La

rge

En

terp

rise

Sy

stem

s

Comprehensive Project

Management System(CPMS) [6] Alabama

Right-of-way subsystem includes project

status, right-of-way mapping, appraisal status,

acquisition, relocation, and leased property

Right-of-Way Management System

(RWMS) [14] Florida

Includes most of the functional areas of the

right-of-way; Integrates Electronic Document

Management System

Land Record System (LRS) [15] Indiana Maintenance of database of land records;

Tracks the status of each parcel

Appraisal, Acquisition, and

Relocation System (AARS) [5,16] Louisiana Appraisal, Acquisition and Relocation

Real Estate Management

Information System (REMIS) [17] Michigan


right-of-way

Right-of-Way Electronic

Acquisition Land Management

System (REALMS) [10]

Minnesota Right-of-way acquisition and land

management

Right-of-Way Parcel Tracking

System (PTS) [18] Mississippi

Management of information flow of the full

range of right-of-way activities

Right-of-Way Data Management

System (RWDMS) [19, 20] Oregon

Enterprise content management initiative for

right-of-way processes

Right-of-Way Office Information

System [1, 21] Pennsylvania

Appraisal, Acquisition, Relocation and

Property Management

Right-of-Way Utilities Management

System (RUMS) [1, 22] Virginia


right-of-way

Real Estate Automated Data System

(READS) [23] Wisconsin


right-of-way

From the literature, information systems with varying levels of complexity and breadth

are currently in use. Only a small percentage are as comprehensive as CPMS and even fewer are

geospatially enabled and integrated into the overall business of a state transportation agency. To

24

assist agencies to move to this level, a logical model has been developed, which captures the

mandated aspects of the Uniform Act and includes hooks to the larger transportation agency

enterprise and the incorporation of geospatial functionality. This provides the necessary

flexibility to allow agencies at any stage of incorporating information management to take

advantage of any or all components of the framework. This paper provides an overview of the

model which will be available through NCHRP 8-55A, Developing a Logical Model for a Geo-

Spatial Right-Of-Way Land Management System [24].

3.2.2 Logical Model Design

In the terminology of software and information systems, the design and implementation

of an information system primarily consists of Conceptual, Logical and Physical Data Modeling,

prior to the actual system development [25, 26]. The Conceptual and Logical Modeling captures

the data, processes, activities and functions of a given business for which the information system

is being developed, while the Physical Modeling describes how the system is implemented in

terms of computer hardware/software, database files, information system screens etc. The

conceptual and the logical model designs are developed prior to the Physical Model design,

which in combination are used for eventual software development.

UML is an accepted set of notation techniques for visually defining, documenting and

representing software intensive systems [27]. This uniform design supports the portability of

framework development for any given model and provides an appropriate platform for modeling

a rigorous and traceable information system for complex right-of-way activities. The model

views available in UML can be divided into two sets; Behavioral Model Views and Structural

Model Views, as shown in Figure 3.1.

25

The Behavioral Model Views capture the dynamic behavior of the system over time [27,

28]. This dynamic view for the system is demonstrated by four UML models or diagrams:

Business Process Model (or Analysis model), Use Case Model, Communication Diagrams, and

Sequence Diagrams. The Business Process Model captures the broad outline of procedures and

the sequence of activities that drive the business. The Use Case Model defines the features or

requirements expected to be provided by the system and captures the interactions within the

system and with entities that are external to the system. Sequence Diagrams and Communication

Diagrams are forms of Interaction Model Views, and are encompassed in the individual use

cases and illustrate the communication between the objects and the messages that trigger those

communications.

The Structural Modeling View defines the static architecture of a model [27, 28]. It

models the elements that constitute the system and the relationships and dependencies between

the elements. The Structural Modeling View consists of three models: Class Model Diagrams,

Component Model Diagrams, and Package Model Diagrams. Class Model Diagrams reflect the

logical structure of the system by capturing the attributes and behavior of the model in its static

view and illustrating the relationships between the classes and interfaces. Component Model

Diagrams depict how a system is decomposed into various components that can illustrate the

structure of arbitrarily complex systems. Package Model Diagrams demonstrate the organization

of packages and their elements, and thus help in organizing use case diagrams, class diagrams, or

other UML diagrams.

The proposed overall right-of-way model supports the abstraction of right-of-way

information and activities that facilitate the design of a comprehensive right-of-way information

management system, with the help of the above described UML Model Views. These individual

26

models depict explicit yet complimentary perspectives of the overall model. A more

comprehensive description and the application of these UML modeling views for designing the

right-of-way system logical model are described in detail in the following sections.

Figure 3.1: UML diagrams included in the model and their classification

3.3 Proposed Model Architecture

Enterprise architecture planning is the preliminary step to modeling any enterprise-wide

information management system [29]. Defining the enterprise, identifying the actors, outlining

the business processes, and developing the relationships to entities - whether actors, systems or

Model

Behavioral

Model Views

Structural

Model Views

Business

Process Model

Component

Model

Use Case

Model

Class Model

Interaction

Model Views

Package Model

Communication

Diagrams

Sequence

Diagrams

27

business processes - outside the enterprise, are necessary to building the model. Since a primary

purpose of the system is to achieve interoperability, the enterprise has to accommodate areas that

will share substantial right-of-way information.

Owing to the complex and diverse nature of business processes throughout the right-of-

way office, it is necessary to define an appropriate scope of the enterprise before designing the

system. Because every state transportation right-of-way office is structured differently to meet

the unique requirements of that state, the scope of the enterprise for this model was identified to

capture the activities outlined in the Office of Real Estate Services Project Development Guide

[4], which was developed by FHWA to provide guidance to the states and local jurisdictions that

use Federal dollars for transportation improvement projects, and to meet the Federal

requirements of the Uniform Act [5]. In addition to project management, the four functional

areas in the model are appraisal or property valuation, acquisition, relocation, and property

management. The enterprise also includes activities related to land being considered during early

project development.

The next step is to identify the major governing actors which include both individual

human and agency actors that are expected to interact with the system. This helps in identifying

roles and establishing responsibilities of the actors prior to model development. This, in turn,

helps in establishing enterprise-wide right-of-way activities associated with these actors,

ensuring interoperability across the enterprise system. This also helps in reducing conflicts that

might arise in building the model and provides further clarity to the right-of-way activities

included in the logical model. Figures 3.2 and 3.3 illustrate the actors and their relationships in

UML notation.

28

The next component of developing the architecture is capturing activities that make up

the business of right-of-way offices as described in the Project Development Guide. This initial

business modeling was fundamental to conceptualizing the right-of-way project processes and

served as the base for modeling the system in UML.

Figure 3.2: Agency actors identified in the right-of-way system

_ uc Agency Actors

Planning Department

Treasury

Disposition Committee

Legal Office RoW Office

State DOT

State

Local Acquisition Agency

FHWA

29

Figure 3.3: Human actors identified in the developed right-of-way system logical model

Figure 3.4 gives an overview of the business process diagram for the overall right-of-way

process, with the core areas that make up the enterprise addressed in this research highlighted in

light brown near the center of the figure. Similar diagrams were developed for each of these core

areas. Interoperability with the larger transportation enterprise is incorporated in the system

design by identifying discrete external systems and including these interactions with right-of-

way activities. Figure 3.5 outlines the major systems in UML representation that interact with the

overall right-of-way system.

30

Figure 3.4: Overall Right-of-Way Process Flow

31

Figure 3.5: Component model view of the Overall Right-Of-Way system in UML depicting

the other integrated external systems

3.4 Model Development

3.4.1 Behavioral Model Views

Based on the process flow diagrams the detailed model was built using the components

defined in section 3.3 and shown in Figure3.1.

cmp Component Model - Ov erall ROW

Financial Information

System

Project Management

Information System

FHWA Annual

Reporting System

Local Gov ernment

Systems

Document

Management System

Parcels

Turbo Relocation (or

Similar)

MLS (External Real

Estate System)

Env ironmental System

Geospatial

Warehouse

Tax Information System

Highway Right of Way

ROW Director

(from Human Actors)

Project Manager

(from Human Actors)

Project Closing

Project Dev elopment

Major ROW Functions

«invokes»

«precedes»

«invokes»

«invokes»

«precedes»

32

3.4.1.1 Business Process Model

The Business Process Model, also called the analysis model, is a simplified form of an

activity model that captures the broad outline and procedures that govern the business processes,

in this case, activities in a right-of-way office. The business process model helps in clearly

mapping the scope of the entire system through different activities. For this purpose activity

organizes and specifies the participation of subordinate behaviors, such as sub-activities or

actions, to reflect the control and data flow of a process [28].

This model provides the primary of the proposed system design and is instrumental in

capturing significant activities, events, resources, inputs and outputs that are associated with the

right-of-way business processes. As an example, the upper half of Figure 3.6 shows the Business

Process Model for „relocation planning‟, which focuses on recognizing, at an early stage, any

problems associated with the displacement of individuals, families, or businesses before the

commencement of actions that cause these displacements. The primary actors in the relocation

planning process, identified as a part of the model architecture (Figure 3.4), consist of the

Relocation agent and the Displacing agency.

The relocation agent first identifies parcels with people or businesses that require

relocation assistance from the available list of acquired parcels. This is modeled as the activity

labeled „REL_parcels for relocation‟. Relocation notices specified by the Guide are distributed to

potentially displaced individuals/organization, to help in resolving any identified problems,

minimize the adverse impacts on the displaced persons, and expedite the overall progress. The

activity „Rel_Notices‟ is modeled as a composite activity in the UML design, as denoted by the

infinity symbol in the activity box, and consists of several sub-activities related to each of the

individual notices. The individual activities associated with „Rel_Notices‟ are executed, the

33

status of the affected parcels is updated to reflect the activity. Table 3.2 provides a summary of

all the activities included in the Business Process Model.

Figure 3.6: Business Process Model diagram for Relocation planning

act REL_Relocation Planning Activ ity

REL_Notices

Displacing AgencyREL_Open Site Office

Require Site

Office?

Inv entory of Parcels with

Displaced Persons

REL_Parcels for Relocation

Relocation Agent

Certified Lawful

Presence in US? Hardship?

REL_No Relocation Assistance

REL_Update Distribution

Status(es) In the Inv entory of

Parcels with Displaced Persons

(from REL_Relocation Planning)

REL_Geospatial

Enablement - Parcel

for Relocation


REL_Notices


REL_Open Site Office




Parcels with Displaced

PersonsDisplacing Agency

(from REL_Use Case Model Package)

Relocation Agent


REL_Check on the Displaced

Persons eligibility for serv ices


REL_Check on the

Displaced Persons

eligibility for serv ices

No

No No

«precedes»

«precedes»

<<implement>>

Yes

Yes

<<implement>><<implement>>

<<implement>>

Yes

<<implement>>

«precedes»

<<implement>>

34

Table 3.2: List of Activities captured in the Business Process Model of the right-of-way system

* Activities in bold indicate those that have further levels that are not shown in the table

LEVEL

I

LEVEL

II

LEVEL

III

LEVEL

IV*

Project

Development

Project

Establishment

Initial

Planning

Planning

Alignment

Evaluation

Parcel Identification

Identification of

Environmental

impacts

Acquisition cost

estimation

Relocation Survey

and cost estimation

Environmental

study

Hazardous Waste

Site Evaluation

Final Alignment

Selection

Early

Acquisition

Project

Authorization

Project

Agreement

Encumber

Funds

ROW

Mapping and

Engineering

Utility

Relocation

and

Management

Staff

Identification

Analyze Resources

Identify Staff

Requirements

35

Table 3.2: List of Activities captured in the Business Process Model of the right-of-way system (Cont.)


LEVEL

I

LEVEL

II

LEVEL

III

LEVEL

IV*

Staff

Identification

Initiate Contracts

Hire Staff

Assign Staff

Project

Development

Parcel

Identification

& Cost

Estimation

Type of acquisition

Parcel Alignment

Inspection

Total Parcel

Partial Parcel

ROW Cost Estimate

Current & Completed

Project Displacement

Analysis

Relocation Problems

Analysis

Relocation Survey

Survey of

Replacement

Properties

Title

Documents

Alternate

Recommended

Techniques

Title Search

Title Assurance

Title Insurance

Title Abstract and

Title Opinion

Certificate of Title

Temporary and

Permanent Easements

Minor Acquisitions

Low Value Parcel

Acquisitions

Identification

of Parcel

Type

36



LEVEL

I

LEVEL

II

LEVEL

III

LEVEL

IV*

Major

ROW

functions

Corridor

Management

Appraisal

APP_Parcel for

Appraisal

APP_Initial Review

APP_Assign Appraiser

APP_Contract

Appraiser

APP_Value Donation

APP_Waiver

APP_Waiver of Regulation($10K or

$25K)

APP_Low Value Appraisal

APP_Minimum Payment Method

APP_Process

APP_Determination of Appraisal

Technique

APP_Parcel Evaluate

APP_Minimum Standards

Appraisal

APP_Detailed Appraisal

APP_Appraisal Review

APP_Appraisal Review

APP_Develop a new appraisal

APP_Perform Deficient Appraisal by

Appraiser

APP_Prepare Review Appraisal

Certificate

APP_Update Appraisal

APP_Arrange Appraisal Reviewer

APP_Appraiser

Certificate

APP_Establish Just

Compensation

37



LEVEL

I

LEVEL

II

LEVEL

III

LEVEL

IV*

Major

ROW

functions

Acquisition

ACQ_Pre-negotiation

ACQ_Additional Factors for

Consideration and Processing

ACQ_Assign Negotiator

ACQ_Contract Negotiator

ACQ_Coordinate with Other Offices

ACQ_Prepare Conveyance

Documents

ACQ_Prepare Notices

ACQ_Process Dedication

ACQ_Process Donation

ACQ_Start Closing Process

ACQ_Start Negotiation Process

ACQ_Transfer Federal Lands (DOD,

DVA, BIA)

ACQ_Update Parcel Record

ACQ_Negotiation

ACQ_Accelerated

Negotiations/negotiations by mail

ACQ_Commencement of personal

contact negotiations

ACQ_Attach Negotiator Log

ACQ_Detailed Negotiation Process

ACQ_Document and End Negotiation

ACQ_Follow up by Phone Contact

ACQ_Mail Written Offer and

Acquisition Related Documents

ACQ_Obtain Property Encumbrance

releases

ACQ_Prepare Documents and Update

Parcel Records

ACQ_Provide Written Offer and

Acquisition Related Documents

ACQ_Schedule Meeting

ACQ_Closing

ACQ_Pay Just Compensation

ACQ_Prepare Settlement Statement

and Deed

ACQ_Process Documents: Tax

Forms, Titles, etc

38



LEVEL

I

LEVEL

II

LEVEL

III

LEVEL

IV*

Major

ROW

functions

Relocation

REL_Relocation Planning

REL_Check on the Displaced Persons

eligibility for services

REL_No relocation Assistance

REL_Update Distribution Status(es)

In the Inventory of Parcels with

Displaced Persons


REL_Notices


REL_Services

REL_Available Properties for Sale

and Lease , Community Amenities

REL_Last Resort Housing Planning

REL_Link to MLS (External Real

Estate System)

REL_Conduct Personal Interview

REL_Determination of Occupant

Needs

REL_Determine Eligibility for Each

Type of Payments

REL_Explanation of Services,

Available Payments and Eligibility

Requirements

REL_Provide advisory assistance

(Assistance with Claim forms)

REL_Replacement Dwelling

Assignment

REL_Assistance

Payments

REL_Moving Expense Process

REL_Replacement Housing

Payment Process

REL_Claim and Tax-Form Process

Property

Management

PM_Pre-Construction

Property Management

PM_Improvement Disposition

PM_Personal Property

PM_Rental

PM_ Requirement Type

39



LEVEL

I

LEVEL

II

LEVEL

III

LEVEL

IV*

Property

Management

PM_Duirng

Construction Property

Management

Grading

PM_Post-Construction

Property Management

PM_Excess

PM_ROW Disposal

PM_ROW Management

PM_Sale

PM_Rodent Control

PM_Security

Inspection

PM_Hazardous

Materials

PM_Acquired Property

PM_Construction

Project

Closing

Update Excess

to Inventory

Review

Project Plans

Accumulate

and Store

Records

Status Report

ROW

Certification

State defined

Processes

Final Claims

Close

Accounting

Re-open if

necessary

Encroachment

Cleaning

Excess

Property

Construction

40

3.4.1.2 Use Case Model

The second component of the Behavioral Modeling Diagrams is the Use Case Model.

While the Business Process Model describes both the behavior and the information flows within

the right-of-way system, the Use Case Model provides the system‟s functionality in terms of

actors, use cases, and the relationship between them. A use case denotes a collection of actions

performed by a user (or sub-system) of an enterprise system. This helps in establishing the roles

of the actors by exclusively identifying the functions within the system that are performed by

that specific actor.

This model is usually represented as one or more actors associated with one or more use

cases, as shown in the second half of Figure 3.6. Each of the actors in the use case model

represents a role that is played either by a person or sub-system engaged in the reasonable

functioning of the main system; and each use case represents a discrete unit of work to be

implemented by the main system in collaboration with one or more actors. For example, the use

case diagram for „relocation planning‟ outlines five goals or use cases to be realized by the

system, as required by the identified actors: displacing agency and relocation agent. These five

use cases are summarized in Table 3.3.

Table 3.3: Summary of Use Cases for Relocation planning

Functional area (or

sub-system) Use Case(s)

Relocation Planning

REL_Geosptial Enablement – Parcel for Relocation


REL_Notices

REl_Check on displaced persons eligibility for services

REL_Update Distribution Status(es) in the Inventory of


41

Use Case Models also help in providing traceability or the manner of implementation in the

proposed system for the defined business processes. The use cases identified in the model are

linked back to the business process model with <<implementation>> links to symbolize the

dependant relationship between the models. This feature is used to link model elements or sets of

elements that represent the same idea across model views. For example, Figure 3.6 illustrates

how the business processes of relocation planning are implemented by the corresponding use

cases. To elaborate further, the activity „Parcels for relocation‟ that is defined as identifying the

parcels required for relocation, is implemented by the use case „REL_Geosptial Enablement –

Parcel for Relocation‟ identified in the use case model. Thus, as the model is developed and all

the functional processes and activities are designed and linked to the use cases, the accountability

for each element in the model is established through traceability.

3.4.2 Interaction Model Views

The use case model is further enhanced through the interaction model which is composed

of sequence and communication diagrams. These diagrams are “embedded” in the use case

diagrams and describe the steps taken to carry out the use case.

3.4.2.1 Sequence Diagrams

Sequence diagrams graphically portray the workflow of the implementation of a use case.

These diagrams are primarily composed of objects and the messages dispatched between the

objects that helps in capturing a dynamic view of the system. They typically illustrate the

interaction of the user with the objects and components in the order required to execute a use

42

case. For example, a sequence diagram anchored under the use case „Open Site Office‟ is

illustrated in Figure 3.7.

Figure 3.7: Sequence Diagram for the use case ‘REL_Open Site Office’

The diagram depicts the sequence of steps implemented to realize the goal of „REL_Open

Site Office‟. The decision about „Site_Office_Requirement‟ is first made during project

development prior to acquisition. This requirement is addressed by the Relocation Agent to open

the site office or implement the current use case with the Displacing Agency acting as the

controller. Thus, site office is opened by the displacing agency according to this requirement and

the attributes of the „REL_Site_Office‟ class, which are described in detail under the Class

model, are updated. Simultaneously, as the decision for „Site_Office_Requirement is made, the

status of site office for the corresponding parcel file is updated to either in progress or N/A. As

the goal of the use case is achieved, and the attribute „Status_Site_Office_Establishment‟ of an

instance of the class: „REL_Site_Office‟ is updated indicating its completion.

43

Similarly, the sequence diagrams for other use cases are modeled in relation to the

methods and events supported by the corresponding classes.

3.4.2.2 Communication Diagrams

The communication diagrams represent a combination of information taken from Class,

Sequence, and Use Case model diagrams describing both the static structure and dynamic

behavior of a system. While sequence diagrams model the time ordering of messages,

communication diagrams model the organization of messages i.e., while sequence diagrams

show the order in which the interactions take place, communication diagrams represent which

elements interact with one another. The communication diagrams are also “embedded” in the

corresponding use cases.

Figure 3.8: Communication Diagram for the use case ‘REL_Open Site Office’

Figure 3.8 shows the communication diagram for the use case „REL_Open Site Office‟.

Though semantically it provides the same information as that of the above described sequence

44

diagram, it depicts the inter-object relationships and the exchange of messages among Relocation

Agent, Displacing Agency, Status_Site office and the instance of the class „REL_Site Office‟.

The exchanged communications are labeled in the diagram as 1.1, 1.2, 1.3, and 2.1 to illustrate

the order of the messages exchanged.

3.4.3 Structural Model Views

3.4.3.1 Class Model

A class is defined as an element or an entity of a given system that captures certain

unique features and functionalities of the entity in the form of attributes and methods. A class

model provides an overview of these classes, attributes and their relationships. These diagrams

reflect a static view of the system by depicting what classes interact but not what happens with

their interaction.

For the right-of-way information system, the class model has been developed in

reference to the Business Process Model. The class model for the current system is developed

such that allows it is independent of any language/platform. The classes in this model are

comprised of three elements, the class name, attributes of the class and their behavior. Figure 3.9

illustrates the class diagram for „relocation planning‟, which is a part of the class model for

relocation. The class diagram in the figure depicts the flowing classes:

REL_Notices

REL_Site_Office

REL_Relocation_Planning_Information

REL_Additional Relocation information

Realization and association connectors are used to capture the relationships between

these classes. REL_Relocation_Planning_Information and REL_Additional Relocation

45

information classes are connected with a realization, which is used when the source object

implements or realizes the destination. On the other hand

REL_Relocation_Planning_Information is connected to REL_Notices through a simple

association, which implies a generalized relationship shared by the two model elements. Since

class diagram provides a static view of the system, not all the classes are modeled to have

relationships with other elements in the model, like the REL_Site_Office shown in Figure 3.9.

Figure 3.9: Class Model diagram for Relocation planning

class REL_Relocation Planning Class Model

REL_Notices

- 90 day Notice (with 30 day specific notice distrbuted)?: boolean

- Additional Information (if applicable): char

- Date _Of_General Information Notice: Date

- Date of initiation of negotiations: Date

- Date of locating at least one replacement dwelling: Date

- Date_Of_Date of issuing notice: Date

- Date_Of_Notice of Relocation Eligibil ity: Date

- General Information Notice Distributed?: boolean

- Information about advisory services: boolean

- Instructions about moving: boolean

- Language of notices: char

- Notice of Intent to Acquire distributed?: boolean

- Notice of Relocation Eligibil ity Distrbuted?: boolean

+ Parcel_ID: int

+ Project_ID: int

+ Project_Parcel_ID: int

- Relocation payments description: boolean

# Status _REL_Notice Distribution: Flag

- Vacate property before Negotiations?: boolean

REL_Relocation_Planning_Information

+ Parcel_ID: int

- Possible_shortage_of_dwellings_for_the_above_people: boolean

- Presence_of_large_families?: boolean

- Presence_of_Low-income_elderly_people?: boolean

- Presence_of_People_with_disabilities?: boolean

+ Project_ID: int


- Relocation_Planning_Information_Availabil ity: boolean

REL_Site_Office

- Hours of operation: char

- Location (point): Geosptial_Reference

+ Parcel_ID: int

+ Project_ID: int


+ Relocation_Agent_ID: int

# Site_Office_Requirement: char

- Status_Site_Office_Establishement: Flag

REL_Additional Relocation information

- Basis for determination: char

- Denial_of_relocation_benefits_impacts_adversely_any_family_member: boolean

- Denial_of_relocation_benefits_impacts_adversely_the_continued_existence_of_family_unit: boolean

- Denial_of_relocation_benefits_impacts_adversely_the_health_or_safety_of_family_member: boolean

- Description of the comparable dwelling: char

- Each family member, either citizen or national of the US or legal alien in the US: boolean

- In case of incorporated business, farm, or nonprofit organization, corporation is authorized: boolean

- Individual, either citizen or national of the US or legal alien in the US: boolean

- Location: char

- Owner of unincorporated business, farm, or nonprofit organization, either citizen or national of the US or legal alien in the US: boolean

+ Parcel_ID: int

- Price used to set upper l imit of replacement housing payment: int

+ Project_ID: int


- Rent used to set upper l imit of replacement housing payment: int

- Required certification: Document

46

Separate compartments are used in the representation of classes to illustrate the class

name, attributes, and operations. For the classes depicted in Figure 3.9, the compartment below

the class name captures their respective attributes. The notation that precedes the attribute

indicates the visibility of the element according to the following:

+ Symbol indicates public level of visibility

- Symbol indicates the attribute is private

# Symbol indicates the attribute is protective

Data elements identified in NCHRP Research Results Digest 310 for Integrating Geo-

Spatial Technologies into Right-of-Way Data Management Process [1], helped in providing the

necessary knowledge base for modeling the classes and their attributes for the enterprise-wide

right-of-way logical model.

3.4.3.2 Component Model

The component model shows the structural components of a software system along with

the organization and dependencies among these components. This model, like the class model,

represents a static view of the system depicting the components that contain one or more classes

or interfaces. The components act as the building blocks for the actual information system. Thus,

the component model diagrams help provide a higher level view of the structure of the large and

complex right-of-way information management system.

Figure 3.10 shows the component model diagram for relocation planning linked with

various UML „connectors‟. The six planning components shown in Figure 3.10 include:

Displacing Agency

Notices

47

Site_Office

Parcel

Planning Department

Figure 3.10: Component Model diagram for Relocation planning

The names of those components that are derived from another package in the overall

model are preceded with the deriving package name, as seen for the components

Displacing_Agency and Parcel that are derived from the primary REL_Component Model

Package and Component Model Package-Overall ROW, respectively. The inter-relationships

between the components are illustrated with various connectors as shown in Figure 3.10. The

„assembly connector‟ links the provided interfaces supplied by the Planning_Department to the

analysis Business Process Model

LEGEND for Component Interfaces

Port1 Required Interface

«interface»

Interface1

Port1

Provided Interface

Required Interface

48

required interfaces specified by the Parcel. A lollipop symbol indicates an implemented interface

and a socket symbol indicates a required interface as shown in the legend. Additional Relocation

Information from the planning department acts as the providing interface to update the required

interface of the Parcel: Attributes/Status. Similarly, notice distribution status acts as the provided

interface for the Notices component. Information flow is used to model the flow of information

between elements, and is used in Figure 3.10 to map the flow between the Displacing Agency

and Site_Office and Site_Office and the Parcel.

3.4.3.3 Package Model

The package model helps in establishing localized system boundaries within the

enterprise by grouping coupled activities within the system. It helps in semantically providing a

structure to all the other UML model views, includes the larger system engineering issues, and

illustrates how the system is decomposed into categories that represent the logical relationships

and dependencies among those categories.

Each of the use case, class, and component models is grouped by their related behavior or

state into packages. For example, as shown in the Figure 3.11, the use case model for relocation

has been grouped into three packages:

REl_Relocation Planning

REL_Relocation Services

REL_Relocation Assistance Payments

The dependencies between the three packages is captured through the connectors labeled

as <<precedes>>, indicating the order of implementation of these packages. As shown in the

49

diagram, use cases grouped under REL_Relocation Planning package model are implemented

prior to both the REL_Services and REL_ Relocation Assistance Payments.

Figure 3.11: Package model diagram illustrating relocation use cases packages

Similarly, uses cases grouped under the REL_Services package occur prior to

REL_Relocation Assistance Payments. Interactions between the major actors and packages are

also illustrated in the package diagram. The dependency connector with the labels <<invokes>>

and <<trace>> between the Relocation Agent, Displacing Agency and the packages in Figure

50

3.11, illustrate the role of the actors in these packages either as directly invoking or tracing the

implementation of the corresponding use cases in the package.

3.5 Conclusions And Future Work

Use of an integrated and interoperable enterprise-wide information management system

for right-of-way business processes could improve efficiency and on-time project delivery for

transportation agencies. Development of an effective right-of-way information management

system requires precisely modeling the activities and information that make up the business.

This study presents an overview of the design of a UML-based enterprise-wide

information management system logical model of this business process for federally funded

highway projects. The model is expected to:

Provide a template for state transportation agencies to support the development of an

enterprise-wide right-of-way information management system that has the flexibility to

meet the unique needs of individual agencies.

Establish a standard structure and vocabulary for effectively processing and sharing right-

of-way information to improve enterprise-wide business activities.

Assist transportation agencies in planning for implementing a system that would integrate

and interact with other existing enterprise-level information systems in the agency, prior

to the investment of funds.

Enhance the integration of the right-of-way business processes into the state agency‟s

overall project delivery process.

51

Although the model provides the necessary structure for building a right-of-way system,

it does not include software development. Business processes identified in the model are

consistent with current federal requirements for right-of-way offices, and the model is designed

to achieve interoperability across right-of-way activities, and to facilitate data integration across

the organization. The design is expected to act as a flexible blueprint for state transportation

agencies to implement an enterprise-wide information management system, accommodating the

unique needs of individual agencies. The full model is available as a part of National Highway

Research Program (NCHRP) Project 08-55A [24].

Acknowledgments

This paper resulted from the research project 08-55A “Developing a Logical Model for a

Geo-Spatial Right-Of-Way Land Management System” sponsored by the National Highway

Cooperative Research Program (NCHRP) of the Transportation Research Board. Thanks are due

to the various state agency personnel for their valuable input and time in providing information

used in the development of the model. The authors would also like to thank the NCHRP 8-55A

panel members for their invaluable information and support throughout the research.

References

1. Hancock, K. (2006). “Integrating Geo-Spatial Technologies into Right-of-Way Data

Management Process.” Contractor‟s Final Report, National Cooperative Highway

Research Program Project 8-55, Transportation Research Board, Washington DC.

<http://onlinepubs.trb.org/onlinepubs/nchrp/nchrp_rrd_310.pdf>

http://onlinepubs.trb.org/onlinepubs/nchrp/nchrp_rrd_310.pdf

52

2. Ghanta N, “Integrating Geospatial Technologies into the Property Management Process Of

The Transportation Right-Of-Way”. Falls Church, Virginia, 2007.

3. Hancock, K. (2006) “Geospatially Enabling Information Management for Right-of-Way

Activities” 86th

Transportation Research Record, Washington DC.

4. Federal Highway Administration. (2006). “Project Development Guide (PDG).”

<http://www.fhwa.dot.gov/realestate/pdg.htm> [Retrieved on 08/15/07]

5. “Uniform Relocation Assistance and Real Property Acquisition Policies Act of 1970 (Uniform

Act)"., amended by Public Law 91-646, Public Law 100-17, Public Law 102-240, Public Law

105-117”. http://www.fhwa.dot.gov/realestate/act.htm [Retrieved on 09/06/09]

6. Gravley R., “ALDOT's Comprehensive Project Management System (CPMS)”, Southern States

and Federal Transportation Finance Conference, Alabama, 2008.

7. Office of Real Estate Services. (2004a). “Outdoor Advertising-State Study, State of Florida

Outdoor Advertising – Automated Data Gathering System, A Case Study.” United States,

Federal Highway Administration, Florida.

< http://www.fhwa.dot.gov/REALESTATE/oacases/casefl.htm>

8. Oregon Department of Transportation (ODOT), (2008), “Enterprise Content Management

Systems (Right of Way)”, United States, Subcommittee on Right-of-Way and Utilities

(AASTHO), Washington, DC.

<http://cms.transportation.org/sites/rightofway/docs/RWorEnterpriseContentMgmtSys3408

.do>

9. Federal Highway Administration. (2004). “Congratulations to the Winners of the 2004

Excellence in Right-of-Way Awards”. FHWA-HEP-04-010, Washington, DC.

10. Ordway, D., Whaley, J. (2008). “Geographical Information Systems Applications For

Transportation Right-of-Way”, Summary Report on a Follow-Up Peer Exchange, Lee‟s

Summit, Missouri, July 22-24, 2008,

<http://www.gis.fhwa.dot.gov/documents/rightOfWay.asp#missouri> [Retrieved on

03/27/09];

11. “Office of Real Estate Services – Newsletter”, Federal Highway Administration, Issue 2009.

<http://www.fhwa.dot.gov/realestate/newsletter/second2009.pdf> [Retrieved on 08/06/09]

12. “NDOT Integrated Right of Way Information Network (IRWIN) Phases 1 and 2”, ITIS, Inc.

<http://itis-corp1.com/index.php?page=irwin-phase-2> [Retrieved on 08/06/09]

http://www.fhwa.dot.gov/realestate/pdg.htm

http://www.fhwa.dot.gov/REALESTATE/oacases/casefl.htm

http://cms.transportation.org/sites/rightofway/docs/RWorEnterpriseContentMgmtSys3408.do

http://cms.transportation.org/sites/rightofway/docs/RWorEnterpriseContentMgmtSys3408.do

http://www.gis.fhwa.dot.gov/documents/rightOfWay.asp#missouri

http://www.fhwa.dot.gov/realestate/newsletter/second2009.pdf

http://itis-corp1.com/index.php?page=irwin-phase-2

53

13. New Jersey Department of Transportation, (2004), “Survey - Right-of-Way information

system”, United States, Subcommittee on Right-of-Way and Utilities (AASTHO), Washington,

DC.

<http://cms.transportation.org/sites/rightofway/docs/Survey_Right_of_Way_Information_Syste

m.pdf>

14. Federal Highway Administration “GIS in Right of Way Scan, Tallahassee, Florida,” (2004),

Washington, DC. <http://www.fhwa.dot.gov/realestate/scans/talafreport.htm>

15. Indiana Department of Transportation, Office of Real Estate (2006) “Property Management

Manual.” Indianapolis. <http://www.in.gov/indot/files/05.PropertyManagementManual12-

05.pdf>

16. Xriver Technologies LLC (2008). “Appraisal, Acquisition, & Relocation System (AARS)”,

United States. <http://www.xrivertech.com/Common/CaseStudies/CaseStudy_AARS.PDF>

17. Michigan Department of Transportation. (2003). “Real Estate Management Information

System.” Subcommittee on Right-of-Way and Utilities (AASTHO), Exhibit F, Michigan.

18. Petyon, L., Mississippi Department of Transportation. (2002). “ROW Parcel Tracking System

Detailed requirements/Functional design document.” United States, Subcommittee on Right-of-

Way and Utilities (AASTHO), Exhibit H, Mississippi.

19. Oregon Department of Transportation (2006) “Right of Way Data Management System

(RWDMS)” ODOT Surveyors Conference.

<http://oregonwatertrails.org/ODOT/HWY/GEOMETRONICS/docs/RWDMS.pdf>


Excellence in Right-of-Way Awards”. Washington, DC.

< http://www.fhwa.dot.gov/REALESTATE/rowea.htm>

21. Bentley Systems Inc. “Bentley Right Of Way Office For The Web”,

<ftp://ftp2.bentley.com/dist/collateral/Bentley_20Right_20of_20Way_20for_20the_20Web

_20Spec_20Sheet_2C_20Low_20Respdflo.pdf> [Retrieved on 08/06/09]

22. Virginia Department of Transportation. (2008) “Right of Way Utilities Management System

(RUMS)” Virginia, <http://virginiadot.org/business/row-rums.asp> [Retrieved on 08/06/09]

23. MSI Data Systems Inc. (2008). “READS - Automated Software for State Government

Highways/Real Estate Operation”. Mequon, WI <http://www.msidata.com/products/reads>

[Retrieved on 07/16/2009]

http://cms.transportation.org/sites/rightofway/docs/Survey_Right_of_Way_Information_System.pdf


http://www.fhwa.dot.gov/realestate/scans/talafreport.htm

http://www.in.gov/indot/files/05.PropertyManagementManual12-05.pdf


http://www.xrivertech.com/Common/CaseStudies/CaseStudy_AARS.PDF

http://oregonwatertrails.org/ODOT/HWY/GEOMETRONICS/docs/RWDMS.pdf

http://www.fhwa.dot.gov/REALESTATE/rowea.htm

ftp://ftp2.bentley.com/dist/collateral/Bentley_20Right_20of_20Way_20for_20the_20Web_20Spec_20Sheet_2C_20Low_20Respdflo.pdf


http://virginiadot.org/business/row-rums.asp

http://www.msidata.com/products/reads

54

24. Hancock, K. (2009). Developing a Logical Model for a Geo-Spatial Right-Of-Way Land

Management System. Washington, D.C: National Cooperative Highway Research Program

Project 08-55 A, Transportation Research Board.

<http://144.171.11.40/cmsfeed/TRBNetProjectDisplay.asp?ProjectID=2326>

25. Nicewarner N., (2004) “Why Have Conceptual, Logical, and Physical Data Modeling?...to

enforce standards and reduce confusion” PowerBuilder Developers Journal, SYS-CON

Media, Inc. <http://pbdj.sys-con.com/node/106944>

26. Tim Bryce. (2006). “Logical vs. Physical Design: Do You Know the Difference?” M.

Bryce & Associates (MBA). Florida <http://it.toolbox.com/blogs/irm-blog/logical-vs-

physical-design-do-you-know-the-difference-9011>

27. Wikipedia: The Free Encyclopedia. (2009). "Unified Modeling Language". Wikimedia

Foundation, Inc. <http://en.wikipedia.org/wiki/Unified_Modeling_Language> [Retrieved

05/03/09]

28. Sparx Systems Pty Ltd. (2007). “UML Tutorials”

<http://www.sparxsystems.com/resources/index.html > [Retrieved on 09/15/08];

29. Spewak S. H. and Hill, S. C., (1992) “Enterprise Architecture Planning: Developing a

Blueprint for Data, Applications and Technology” John Wiley & Sons, Inc., New York.

http://144.171.11.40/cmsfeed/TRBNetProjectDisplay.asp?ProjectID=2326

http://pbdj.sys-con.com/node/106944

http://it.toolbox.com/blogs/irm-blog/logical-vs-physical-design-do-you-know-the-difference-9011

http://it.toolbox.com/blogs/irm-blog/logical-vs-physical-design-do-you-know-the-difference-9011

http://en.wikipedia.org/wiki/Unified_Modeling_Language

http://www.sparxsystems.com/resources/index.html

55

4 A FRAMEWORK FOR GEOSPATIALLY ENABLING THE BUSINESS AND INFORMATION OF TRANSPORTATION

RIGHT-OF-WAY ACTIVITIES

Kavya Sambana1

Kathleen L. Hancock, Ph.D., P.E.2

ABSTRACT:

Right-of-Way offices in state transportation agencies are primarily responsible for

property appraisal, acquisition, relocation of the affected, and management of the acquired

property. Geographical Information Systems are closely linked to these activities because of the

geospatial nature of parcel data and the transportation right-of-way. Integrating geospatial

capabilities into an information management system can substantially enhance the right-of-way

business process. This paper presents a theoretical framework for geospatially enabling the

business and information of transportation right-of-way activities by conceptualizing a

Geospatial Decision Making Activities (GDMA) framework for transportation right-of-way

offices. Geospatial enablement uses GIS as a platform to integrate geospatial information with

the right-of-way services for the establishment of a standard infrastructure to share data across

the agency enterprise. The current GDMA framework facilitates the integration of right-of-way

activities with a geospatial warehouse architecture. The GDMA models the tracking of the

detailed status of parcels through the right of way process, as well as geospatial enablement

activities in Right-of-Way business processes. The framework is expected to serve as a

knowledge base for transportation agencies to incorporate geospatial capabilities into their

information management tools.

1. Graduate Assistant, Via Department of Civil and Environmental Engineering

2. Director, Center for Geospatial Information Technology & Associate Professor, Via Department of Civil and Environmental Engineering

56

4.1 Introduction

Geospatial technology is playing an increasingly major role in managing information in

and across various sectors like energy, telecommunications, government, transportation, defense,

tourism, natural resources, and many others, by providing the ability to collect, manage and

visualize geographically referenced data and information. When location is brought to bear on

any fundamentally spatial activity, such as transportation, managing and analyzing information is

more efficient and effective. Thus, geospatial enablement of an information management system

adds value to the system by improving how information is integrated, visualized, and used for

decision making. Because of the geospatial nature of parcels and transportation infrastructure,

right-of-way offices in transportation agencies can benefit from incorporating this technology

into their business process.

One of the initial efforts to evaluate the use of Geographical Information Systems (GIS)

in right-of-way offices was provided by the Federal Highway Administration's Office of Real

Estate Services through the 2004 GIS in Right of Way Scan (1). This was followed by A Saka‟s

study „Geographic Information System Implementation of State Department of Transportation

Right-of-Way Programs‟, which highlighted the state of the practice for using GIS in right-of-

way activities at that time (2). These efforts were expanded by K Hancock as reported in the

National Cooperative Highway Research Program (NCHRP) Research Results Digest 310 (3).

This study highlighted the need for the automation of Right-of-Way activities and the

development of data-integration models using geospatial technologies to enable easy and

efficient access to information in the right-of-way offices of transportation agencies. This has

been followed by two peer exchanges in 2007 and 2008 sponsored by FHWA, to promote and

57

encourage both the exchange of experiences and knowledge on GIS applications in the right-of-

way area (4) (5).

Based on this, the National Cooperative Highway Research Program sponsored Project 8-

55A for “Developing a Logical Model for a Geo-Spatial Right-Of-Way Land Management

System”, which developed a logical model for a geospatially enabled information management

system (6). This model provides a template for developing a system to manage the business of

the four primary functional areas in right-of-way offices; appraisal, acquisition, relocation, and

property management. This paper presents the theoretical framework for the geospatial

enablement aspect of the logical model through the Geospatial Decision Making Activities

(GDMA).

A short overview of the current state of the practice is followed by a discussion of the

architecture of GDMA, which includes a structure to track the detailed status of parcels through

the right-of-way business process and incorporate geospatial analysis into those activities that

can benefit from this technology through two sub-models, Parcel Tracking and Geospatial

Enablement.

4.2 State Of The Practice

Use of geospatial technology and GIS in transportation agencies has been increasing

steadily since its inception. Almost state agencies use GIS at some level to manage, analyze and

disseminate data and information. This use varies from desktop-based applications to more

comprehensive Enterprise Geographic Information Systems (EGIS). A summary of applications

of geospatial technology currently in use by transportation right-of-way offices is provided in

58

Table 4.1. These systems range from small systems supporting a single activity to systems used

for more than one principal area to large or integrated systems that support a majority of right-of-

way functional areas.

Table 4.1: Summary of systems with geospatial technology applications in Right-of-Way

Offices

System Agency/State Purpose

Ind

ivid

ual

Syst

ems

County Assessors Mapping

Program (CAMP) (5) Arkansas

Enables geospatially-referenced cadastral

mapping system

ALAS

Aeronautical Land Acquisition

System (4; 7)

Illinois

Provides oversight of real estate acquisition and

property management of a large complex airport

project geospatially.

MdProperty View (7) Maryland Is used for viewing parcel information for the

acquisition of right-of-way geospatially.

GISMIS

Geographical Information System

based Management Information

System (8)

New Jersey

Helps in managing and retrieving digital

roadway plans and ROW maps from the GIS

based highway database.

Non-Right of Way Parcel &

Improvement Inventory system

(7)

New Mexico

Used for mapping and generating NRW Parcel

and Improvement Inventory information

geospatially.

DESS AMS

Land and Rights-of-Way

Automated Management &

Tracking (9)

Diversified

Energy Software

Solutions (DESS)

Deals with acquisition, relocation and property

management processes, with GIS map

integration.

BEM Systems Inc (10) Paecetrak Tracks the acquisition process for NJTransit

capital programs

Sm

all

En

terp

rise

Sy

stem

s

ROWMIS

Right of Way Management

Information System (5)

California

Deals with planning and Management of

highway projects; Parcel acquisitions with

geospatially-enabled data analysis and

integration

IRMS

Image Records Management

System (11)

Connecticut

Provides access to documents, maps and

associated parcel data and is currently being

upgraded for GIS integration

RAI

Realty Asset Inventory

Management System (4; 5)

Missouri

Deals with the management of realty assets,

sales, leases and excess properties; Accepts

GPS coordinates associated for location

attribute in the database

FileNET ECM FileNet Enterprise

Content Management (5) Oregon

Enables access to the geospatial ROW data for

each parcel

HAMS

Highway Access Management

System (5)

Wisconsin Deals with driveway permits and land division

reviews with a spatially driven web interface

59

Table 4.1: Summary of systems with geospatial technology applications in Right-of-Way

Offices (Cont.)

System Agency/State Purpose

Larg

e /

Inte

gra

ted

En

terp

rise

Sy

stem

s

Right-of-Way Electronic

Acquisition Land Management

System (REALMS) (5)

Minnesota

Deals with acquisition and land management

with integration of ROW maps with ArcGIS

server (REALMSMaps)

Integrated Right-of-Way

Information Network (IRWIN)

(12; 13)

Nevada

Deals with acquisition and property

management and was scheduled to integrate

with NDOT's GIS, video logging system, and

other external system by 2009

As demonstrated in Table 4.1, few states have a broad geospatially-enabled enterprise

level system although several have plans to enable existing systems (7).

4.3 Geospatial Decision Making Activities

Right-of-way business processes can use geospatial capabilities for visualization, analysis

and enhanced decision making. This paper proposes a framework called Geospatial Decision

Making Activities (GDMA). This framework has been structured in two sub-components, Parcel

Tracking and Geospatial Enablement. Parcel Tracking tracks the detailed state of a parcel, as it is

managed through the right-of-way project. Geospatial Enablement identifies the potential right-

of-way activities that could benefit from geospatial enablement.

4.3.1 Parcel Tracking

The primary objective of parcel tracking is to provide a visual method to track activities

associated with parcels to manage resources and to provide right-of-way personnel with a tool

for improving efficiency and timely project delivery. Information associated with Parcel

Tracking either indicate completion of a key process, availability of important information that

60

outline the future course of right-of-way activities or signify the occurrence of certain major

right-of-way decisions. This information is divided into three categories; milestones, flags, and

values. Milestones represent critical phases in right-of-way project management and act as

project checkpoints. Milestones can either take a „value‟ or a „flag‟, and they serve as progress

markers. For example, the identified milestones for parcel appraisal include, Appraisal

Technique, Status: Appraisal Review, and Just Compensation. These three milestones indicate

respectively the decision on the appraisal technique for parcel, status of completion of appraisal

review, and the availability of just compensation value, which are critical to monitor the progress

of appraisal. Flags capture the state of completion of activities or processes within each

functional area of right-of-way business, and help to validate the project‟s progression. For

example, the parcel tracking attribute „Status: Appraiser Assignment‟ captures the state of

progress or completion of the task of assigning an appraiser for the parcel. Values capture

important information about parcel entities that add significant value to project scheduling, and

which help to visualize and evaluate parcels in a geospatial environment. For instance,

„Appraisal type‟ is an important decision during parcel appraisal, and is captured as a value in

Parcel Tracking.

Figure 4.1 shows the representation of the captured attributes or states of parcel tracking

framework in a logical process flow chart, and Table 4.2 summarizes these modeled states and

includes a brief description of each state. The states or attributes of parcel tracking correspond to

the activities modeled in the overall logical model (6) in accordance with Federal Highway

Administration‟s Project Development Guide (14).

61

Figure 4.1: Logical Flow Chart for Parcel Tracking

62

Table 4.2: Attributes or States in Parcel Tracking of GDMA

*Attributes/States in bold represent milestones for parcel tracking

Attribute/State* Type Description

Pro

ject

Dev

elo

pm

ent

Project Number Value Project associated with parcel. Number generated by the

Project Management System.

Project Parcel

Number Value

Unique parcel number that is project specific. Parcel

status is tracked through the right-of-way project process

using this number.

Parcel Type of

Take Value

Identifies whether whole take or a partial take. May take

the values: Whole/Partial.

Parcel Land Use Value

Identifies the highest and best use of parcel. Available

land use or zoning classification for parcel obtained from

primary parcel cadastre database. Parcel land use types

could include: Residential, Industrial, Commercial,

Recreational, Special purpose, Agricultural,

Undeveloped.

Ap

pra

isa

l

Status: APP Flag Indicates progress of parcel appraisal. Activated at

initiation of appraisal process.

Appraisal Type Value

Indicates type of parcel valuation as: Donation; Waiver;

or Appraisal. The type of appraisal can also be defined

as the „format required‟ for appraisal based on these

three types.

Appraiser Type Value Identifies type of Appraiser employed. May take the

value: staff / fee (contract) appraisers.

Status : Appraiser

Assignment Flag

Indicates appraiser assignment progress. Is activated at

initiation of assignment.

Status : Parcel

Evaluation &

Inspection

Flag Initiated when parcel is evaluated after the parcel visit

Utilities Value

Identifies if any utilities have been identified on the

parcel. May take a value describing the specific utility,

or N/A if none identified.

Appraisal

Technique Value

Identifies the method employed for appraisal or

valuation. May take the value: Minimum Standards

Appraisal-Short Appraisal, Minimum Standards

Appraisal-Value Finding Appraisal, Detailed Appraisal-

Cost Approach, Detailed Appraisal-Sales comparison,

Detailed Appraisal-Income Approach or others as

defined by agency.

63

Table 4.2: Attributes or States in Parcel Tracking of GDMA (Cont.)



Ap

pra

isa

l

Appraisal Complexity Value

Identifies the complexity of appraisal process for

parcel. May take a value that captures a categorical or

relative value based on factors that affect the time and

resources required to appraise parcel. This state can

also help in tracking parcel assignment load of

individual appraisers.

Status : Specialty

Appraisal Flag Is activated if a specialty appraisal is warranted.

Status : Appraiser

Certificate Flag

Is activated when the preparation of the certificate is

initiated by the appraiser.

Status : Appraisal

Review Flag

Is activated at the initiation of the Appraisal Review

process.

Appraisal Reviewer

Type Value

Identifies type of appraisal reviewer employed for the

parcel. May take the value: staff / fee (contract).

Status : Review

Appraiser Certificate Flag

Is activated when preparation of the certificate by the

review appraiser is initiated.

Just Compensation Value

Identifies the progress of establishing just

compensation. May take the value: Established /

Approved.

Status : Appraisal

Report Flag

Is activated when preparation of appraisal report is

initiated.

Acq

uis

itio

n

Status: ACQ Flag Indicates progress of parcel acquisition. Activated at

initiation of acquisition process.

Acquisition Type Value Identifies type of acquisition. May take the value:

Federal, Dedication, Donations or Purchase.

Status : Negotiator

Assignment Flag Is activated when negotiator is assigned.

Negotiator Type Value Identifies the type of negotiator employed. May take

value: staff / contract.

Acquisition

Additional Factors Value

Identifies additional factors that might affect the

negotiation/acquisition process. May take values:

assessments, functional replacement, inverse

condemnation, uneconomic remnants, tenant-owned

improvements, owner retention of improvements,

Hardship and protective buying, railroad parcels, N/A.

64




Status : Negotiation Flag Is activated at commencement of negotiations.

Acq

uis

itio

n

Owner

Correspondence Value

Identifies correspondence to the owner. May take the

value: personal contact, accelerated mail, other means.

Type of Purchase Value Identifies category of parcel for acquisition. May take

values: ROW / Uneconomic Remnant.

Type of Negotiation Value

Identifies the negotiation method employed. May take

values: Administrative Settlement, Alternate Dispute

Resolution (ADR), Legal/Condemnation, or methods

defined by the state.

Settlement Amount

Comparison Value

Compares the final settlement amount with the

established just compensation. May take values: Same

as Just Compensation, More than just compensation.

Status : Property

Encumbrance Release Flag

Is activated when efforts are initiated to obtain

property encumbrance releases on the parcel.

Status: Settlement

Amount Payment Flag

Is activated when closing documents and other tax

related forms are processed. Status is completed when

final payment is made available to the owner.

Status : Acquisition

Claim Forms Flag

Is activated when final acquisition claim forms are

processed.

Rel

oca

tion

Status : Site Office Flag Indicates whether parcel has associated site office, as

identified during the project development.

Status : REL Flag

Is activated when the parcel is identified as requiring

relocation services and the relocation process is

initiated.

Primary Relocation

Indicator Value

Identifies the type of relocation based on the property

or person to be displaced. May take the values:

Residential, Non-Residential, Personal Property, state

defined, N/A.

65




Rel

oca

tion

Secondary Relocation

Indicator Value

More specific identification of type of relocation. This

indicator identifies categories under each general

relocation indicator. May take values:

Residential Persons eligible to receive advisory services

Persons occupying real property to be acquired Persons

occupying real property adjacent to that being acquired who

are caused substantial economic injury by the acquisition;

Persons who, as a result of the project, move or move personal

property from real property not being acquired for the project;

Persons who move into property after acquisition and are

aware that they will have to move

Non-residential relocation, Business

Farm

Non-profit organization (NPO).

Commercial sign, billboard (or similar)

Personal Property Disposal

Moved by Owner

Status : Relocation

Services Flag

Is activated at the initiation of relocation service offer

at interview with owner.

Status : Notice

Distribution Value

Indicates progress of distribution of notices to the

displaced person

Status: Determination

of Occupant Needs Flag

Is flagged based on the progress of the identification

and establishment of the needs the displaced person(s).

Replacement

Dwelling Value

Identifies the status of identified comparable dwelling.

May take values: Assigned, Accepted, Referred, Not

available, Not accepted.

Last Resort Housing

Assignment Value

Identifies LRH. May take value: Assigned, Accepted,

Referred, Not available, Not accepted.

Status : DSS

Inspection I Flag Is activated at completion of first DSS Inspection.

Status : DSS

Inspection II Flag Is activated at completion of second DSS Inspection.

66




Rel

oca

tion

Status : Relocation

Assistance Payments Flag

Is activated at initiation of the process to provide

assistance payments. Is concluded when all eligible

payments are made and all relevant forms are

processed.

Status : Relocation

Moving Expense

Payment

Flag Is activated at completion of moving expense

payments.

Residential Moving

Expense Payment

Method

Value

Identifies method employed for establishing amount

for moving eligible items for residential relocation.

May take values: Actual cost method; Schedule

method; Self-Move; or state defined.

Mobile Home

Moving Expense

Category

Value

Identifies category of moving expenses for mobile

home. May take values: Owner and occupant; Owner

not occupant, or Tenant.

Non-Residential

Moving Expense

Payment Method

Value

Identifies method employed for establishing moving

and business reestablishment costs, farm, or a non-

profit organization (NPO). May take values: Actual

Cost Method; Fixed in-lieu Payment; Self-Move; or

state defined.

Replacement Housing

Payment Method Value

Identifies method employed for establishing

replacement housing payment. May take values: RHP

with Home Owner for at least 180 Days; RHP with

Home Owner for 90-179 days, Tenants for at Least 90

Days; RHP with tenant less than 90 days.

Status : Replacement

Housing Payment Flag

Indicates progress of replacement housing payment to

displaced person(s).

Displaced Person

Move Value

Indicates the status of a displaced person‟s move. May

take values: Scheduled, Moved, or N/A.

Status : Replacement

Housing Payment

Appeal

Flag Is activated if an appeal is initiated.

Status : Relocation

Claim and Tax Forms Flag

Is activated when processing is initiated for final

relocation tax and claim forms. Is concluded when all

forms are processed and relocation payments are made

available to the displaced person or organization.

67




Pro

per

ty M

an

ag

emen

t

Status : PM Flag Is activated with the initiation of Property

Management activities when parcel is acquired.

Requirement Type Value Identifies parcel requirement type. May take values:

Substantially excess / Substantially ROW.

Rental Type Value Identifies type of property rental. May take values:

Rent to original occupant, Interim Tenant, N/A.

Property Disposition

Type Value

Identifies type of property disposition. May take

values: Improvements, Personal Property, Rental.

Personal Property

Disposition Type Value

Identifies personal property disposition. May take

values: Agency Retention, Sale, Demolition, N/A.

Improvement

Disposition Type Value

Identifies type of improvement disposition. May take

values: Agency Retention, Sale, Demolition, N/A.

Status : Clearance Flag

Is activated when parcel is identified for clearance. Is

concluded when parcel is clear or certified for

construction.

Personal Property

Clearance Value

Identifies required percentage of Personal Property

Clearance.

Improvement

Disposition Clearance Value

Identifies percentage of Improvement Disposition

Clearance.

Status : Grading Flag Indicates the status of grading according to the defined

flag codes.

Disposing Parcel

Type Value

Identifies type of parcel for disposition. May take

values: ROW, Excess, or more specific like access

point.

Status : Parcel

Disposition Flag

Is activated when parcel (excess/row) is identified for

disposition and is flagged for completion when the

parcel is sold.

Excess/ROW

Management Type Value

Identifies how the excess land or ROW, which is no

longer required, is managed when it is not disposed.

May take the values: Rent, Lease, Internal

Maintenance, or Other.

Status : Hazardous

Material Mitigation Flag

Is activated when parcel is identified as requiring

mitigation of hazardous materials. Is concluded when

hazardous materials have been mitigated.

Hazardous Material

Mitigation Value Identifies type of required Hazardous Mitigation.

Rodent Control Value Identifies rodent control activities. May take values:

Single occurrence, Under contract, NA

Security Inspection Value Identifies security inspection activities. May take

values: Single occurrence, Under contract, NA

68




Pro

ject

Clo

sin

g

Notice to Proceed Value

Identifies type of notice to proceed which is issued

prior to the construction. May take values:

Outstanding, Conditional, Final Notice.

Status : ROW

Certification Flag Is activated when ROW certificate is issued.

Status : Federal

Voucher Letter Flag

Is activated when final federal voucher letter is

submitted.

4.3.2 Geospatial Enablement

Geospatial Enablement models activities that could benefit from geospatial visualization

and analysis within the right-of-way office. In addition to specifying the activity, it also identifies

the required geospatial data, other external resources, and components required to accomplish

that activity in a geospatial environment.

Activities during the project development phase that could benefit from geospatial

integration include alignment selection, conducting environmental studies, evaluating hazardous

waste sites, indentifying parcels required for the project, defining the type of take of the

identified parcel, and analyzing their complexity. One of the primary resources for these

activities and other indentified geospatial activities consists of the parcel cadastre layer

maintained by the state or exclusively by the right-of-way office on a project-by-project basis

(15). Additional geospatial layers, include existing roadway layer, new right-of-way layer or

ROW plans, imagery, utilities, external environmental system, and lease or property

management system.

69

Identified activities for geospatial enablement during appraisal, include reviewing

parcel(s) for value or complexity, evaluating elevation changes affecting the adjoining property,

determining the appraisal technique, valuating the parcel through sales comparison method,

identifying parcels requiring specialty appraisal, and identifying those that have utilities. For

relocation, geospatial enablement can help in identifying the parcels that require relocation,

available properties where the displaced persons or business can be relocated, and the possible

parcels or areas for relocating utilities that exist on right-of-way parcels. For property

management, these activities consist of determining the parcel requirement type, analyzing the

clearance or demolition status of parcel property, determining the cost of earthwork for grading,

justifying the disposal of parcels, and indentifying excess land. Additional resources for these

activities can include a wide range of geospatial layers like topography, soil data, vegetation,

demographic data, and other external resources or systems like appraisal system and historical

parcel sales records etc. Table 4.3 describes these identified activities grouped by right-of-way

functional areas.

Table 4.3: Identified Right-of-Way Activities for Geospatial Enablement

Geospatial Activity Description

Pro

ject

Dev

elo

pm

ent

Identify parcels during

alignment selection

Overlay and analyze multiple layers affecting

alignment selection.

Estimate right-of-way cost for alignment

selection.

Identify Environmental

Impacts Overlay and analyze multiple layers that could

support identification of environmental impacts

during the roadway alignment selection. Perform environmental

studies and hazardous

waste sites evaluation

70

Table 4.3: Identified Right-of-Way Activities for Geospatial Enablement (Cont.)

Geospatial Activity Description P

roje

ct D

evel

op

men

t Identify parcels for right-

of-way

Identify parcels by overlaying the Parcel Cadastre

layer with the Road Design layer.

Define parcel type of take

and divide parcel to

ROW/Excess

Analyze each selected parcel to determine if it is

a Whole or Partial take.

Identify complexity

Analyze each selected parcel for complexity (See

Geospatial Activities under Appraisal and

Relocation for more detailed descriptions.)

Ap

pra

isa

l

Initial Parcel Review for

Value/Complexity

Determine appraisal complexity by overlaying

and analyzing multiple layers including elevation,

utilities, land use, imagery etc.

Elevation Changes

affecting the

parcel/property

Analyze the elevation that would affect the

property with the new roadway.

Determine Appraisal

Technique

Determine the method of appraisal employed for

the parcel by interfacing with an external

appraisal system.

Sales Comparison

Analyze and determine appraisal value for paired

sales (sales comparison method), by interfacing

with available historical parcel sales records.

Specialty Appraisal

Identify and extract parcels requiring specialty

appraisal by analyzing the existence of special

properties on each parcel.

Identification of Parcels

with utilities

Identify and extract parcels with subsurface,

surface and aerial utility facilities by overlaying

and analyzing with utilities layer (electricity,

natural gas, water, sewage etc.).

71

Table 4.3: Identified Right-of-Way Activities for Geospatial Enablement (Cont.)

Geospatial Activity Description R

elo

cati

on

Identify parcels for

requiring relocation

Identify and extract parcels that require relocation

assistance by analyzing each parcel‟s relocation

indicators.

Identify available

properties for sale, lease,

community amenities

Identify possible locations for relocation, by

analyzing and overlaying multiple layers

including demographic data and interfacing with

external real estate management system or

lease/sale property management system.

Identify available areas for

relocating utilities

Determine possible areas for adjusting the

effected utilities by overlaying utilities layer with

multiple layers including roadway ROW layer,

parcel cadastre layer, and road network layer.

Pro

per

ty m

an

ag

emen

t

Parcel Requirement Type

Determine the requirement type of each parcel,

either as substantially excess or substantially

ROW, by overlaying ROW project parcels using

the new ROW roadway layer.

Clearance/Demolition

Analyze and identify level and type of clearance

required for personal property/improvement

clearance, and display the clearance status

thematically.

Grading

Determine cut and fill volumes, and total cost for

the earthwork for the new roadway by overlaying

and analyzing multiple layers including,

topography/elevation of terrain and soil type

layer.

Display the grading status for each parcel.

Justification of ROW /

Excess Disposal

Analyze and justify right-of-way

(access/relinquishment/lease) and excess land

disposal by overlaying multiple layers including

roadway network (for highway safety, traffic

demand), soil type layer vegetation layer etc.

Manage Excess lands

Identify and extract excess land based on the

analyzed parcel requirement type, and by

overlaying the new roadway right-of-way.

72

The GDMA framework, through Parcel Tracking and Geospatial Enablement, is expected

to serve as a knowledge base for the right-of-way offices in state transportation agencies for

integrating geospatial capabilities to better manage the right-of-way business process.

4.4 Significance

Geospatially enabling the management of right-of-way activities provides a wide range of

capabilities that can enhance decision making and improve transportation performance measures,

particularly on-time project delivery. It also helps to explore the spatial relationships across

right-of-way parcels, proposed roadway right-of-way, existing properties, utilities and other

surrounding features, as well as providing enhanced insight and better understanding than static

figures or tables of numbers. Thus, incorporating geospatial technology can extend the

capabilities of managing right-of-way information. This section provides an overview of the

benefits that can be obtained with GDMA.

GDMA helps in providing the right-of-way offices with:

Improved tracking and scheduling of right-of-way project progress

Tracking parcel data is an integral and important part of right-of-way activities to ensure

adherence to project schedules and minimize costs due to delays. Viewing states in a GIS

interface provides another alternative for visualizing and evaluating parcels, personnel and

projects.

73

Improved communication in right-of-way offices

Visualizing information in GIS facilitates better communication in right-of-way offices by

providing increased situational awareness among and across operational areas through

interdependency and shared requirements.

Enhanced right-of-way project decision making

Having situational awareness for successful decision making is important to a broad range of

complex business systems. This can be displayed in a geospatial environment by visually

identifying current and potential delays in various phases of the project. Visualizing parcel

states spatially and relative to one another can inform decision makers of potential locational

aspects as well as standard business considerations.

New options for analyzing activities

Modeling data in a geospatial environment provides enhanced analysis capabilities for many

right-of-way activities, such as, identifying parcels during alignment selection, analyzing

elevation changes of the new roadway right-of-way affecting adjoining property, justifying

the disposal of excess lands, etc.

Greater knowledge about parcel location and enhanced understanding of spatial context

A geospatially enabled right-of-way system enables right-of-way personnel to visualize the

parcel in a larger context with respect to the location of other project parcels and spatial

features like utilities, existing right-of-way/roadway, wetlands, protected land use etc. Thus,

it enhances the contextual understanding of parcels for acquisition, relocation and property

management.

74

Geospatially enabling the management of information through GDMA supports access to

comprehensive tracking and visualization of parcel data, provides new and increased methods for

analyzing data, and improves complex decision making for right-of-way activities.

4.5 Conclusion

The framework for Geospatial Decision Making Activities provides a conceptual basis for

geospatial enabling the right-of-way business process. Implementing GDMA could enable

decision-makers in right-of-way offices to make better-informed decisions, and help increase

efficiency while adhering to on-time project delivery. In summary, the paper presents a structure

to:

Provide knowledge basis for right-of-way offices to integrate geospatial information into

their business

Develop a comprehensive parcel tracking process in a geospatial environment

Contribute to the improvement of existing individual right-of-way departments by capturing

the geospatial decision making activities for appraisal, acquisition, relocation and property

management.

Increase awareness among of the benefits and significance of incorporating geospatial

decision making activities.

References

1. Federal Highway Administration. GIS in Right of Way Scan. Tallahassee, Florida : Office

of Real Estate Services, Federal Highway Administration, 2004.

75

2. Saka, Anthony A. Geographic Information System Implementation of State Department of

Transportation Right-of-Way Programs. Office of Real Estate Services. Washington, DC :

Federal Highway Administration, 2004. DTFH61-03-H-00121.

3. Hancock, Kathleen L. Integrating Geospatial Technologies into the Right-of-Way Data-

Management Process. Washington, D.C : National Cooperative Highway Research Program

Research Results Digest 310, Transportation Research Board, 2006. 01039144.

<http://onlinepubs.trb.org/onlinepubs/nchrp/nchrp_rrd_310.pdf>.

4. Federal Highway Administration. Peer Exchange on Applications of Geographic

Information Systems in the Right-of-Way Area. Lee's Summit, Missouri : Federal Highway

Administration, 2007.

5. Federal Highway Administration. Peer Exchange on Applications of Geographic

Information Systems in the Right-of-Way Area. Lee's Summit, Missouri : Federal Highway

Administration, 2008.

6. Hancock, Kathleen L. Developing a Logical Model for a Geo-Spatial Right-Of-Way Land

Management System. Washington, D.C : National Cooperative Highway Research Program

Project 08-55 A, Transportation Research Board, 2009.

<http://144.171.11.40/cmsfeed/TRBNetProjectDisplay.asp?ProjectID=2326>.

7. Hancock, Kathleen L. Integrating Geospatial Technologies into the Right-of-Way Data-

Management Process: Appendixes A through F. Alexandria, VA : Transportation Research

Board, 2006. National Cooperative Highway Research Program Web-Only Document 95.

8. Kaan, Ozbay and Nebahat, Noyan. Geographical Information System based management

Information System (GISMIS). Washington DC : 82nd Transportation Research Record,

January 2003.

9. Diversified Energy Software Solutions (DESS) LLC. Land Management Solutions.

Diversified Energy Software Solutions . [Online] [Cited: 08 06, 2009.]

<http://www.desoftsol.com/solutions/AMS.html>.

10. BEM Systems, Inc. Paecetrak : Right-of-Way Acquisition Support System (Version 4.0).

BEM Systems, Inc. [Online] [Cited: 08 06, 2009.]

<www.bemcorp.net/webcop/paecetrakweb/web/Brochure.pdf>.

11. John, Durling O. Image Records Management System. Connecticut Geo-Focus. 2009, Vol.

2, 3.

76

12. Halana, Salazar and Eric, Warmath. Nevada Department of Transportation (NDOT)

Efforts to Integrate Right-of-Way (ROW) Information and Geographic Information Systems

(GIS). Office of Real Estate Services – Newsletter. 2009.

13. Susan, Marlow. Transportation Projects Simplified with GIS Integration. Right of Way

Magazine. 2007, November/December, pp. 42-45.

14. Federal Highway Administration. Project Development Guide (PDG). [Online] [Cited: 08

15, 2007.] <http://www.fhwa.dot.gov/realestate/pdg.htm>.

15. Federal Geographic Data Committee. Cadastral Data Content Standard for the National

Spatial Data Infrastructure, Version 1.4. Reston, Virginia: Subcommittee on Cadastral Data,

2008.

77

5 MODELING AND EVALUATING - GEOSPATIAL DECISION MAKING ACTIVITIES (GDMA)

The conceptual framework for the Geospatial Decision Making Activities, established in

Chapter 4, is used to develop a logical model that integrates seamlessly with the overall logical

model presented in Chapter 3. The current chapter provides a detailed modeling approach for the

design of GDMA in Unified Modeling Language (UML) using standard UML. This chapter also

presents evaluation that was performed to ensure that the Parcel Tracking and Geospatial

Enablement components of the GDMA model effectively represent the flow of parcel and

geospatial data within a transportation agency‟s right-of-way system.

5.1 GDMA Model

The two sub-components of GDMA, Parcel Tracking (PT) and Geospatial Enablement

(GE) are modeled in UML using State Machine and Data Flow Diagram Models, respectively,

using Enterprise Architect, a Computer Aided Software Engineering (CASE) tool developed by

Sparx Systems Pty Ltd [7].

State Machine diagrams, also referred to as State Diagrams, illustrate various states of an

object and the transitions between those states, along with the source or triggering events that

cause the state changes [32]. State machine diagrams provide a dynamic modeling technique to

capture the behavior of an instance of a single class within a system. In its broad sense, a state

represents a particular stage in the behavioral pattern of an object. In a state diagram, these states

are represented in rounded rectangles labeled with their name. Transitions between states are

78

triggered from events. These triggering events invoke the corresponding methods of a state that

result in the change of state of an object. These methods are displayed in the compartment below

the name of a state, and are preceded by the reserved words „do/entry/exit‟ indicating the action

of the operation. Table 5.1 provides an overview of the elements used in a State Machine Model.

Table 5.1: State Machine Diagram Elements

Representation Description

State : Represents a stage in the behavior pattern

of an entity

Method : Represents a UML operation (Captured

in the compartment below the state name)

Initial element : Represents a pseudo-states

indicating the start of flow

Exist Point : Represents a pseudo-states indicating

where the flow is exited

Transition : Defines logical movement from one

state to another

Class : Represents an object that reflects its

structure and behavior within the system through its

attributes and methods. Class name precedes the

source package name in the class model

Package : Contains a collection of classes grouped

under a common name.

Information flow : Represents flow of information

between two elements in the diagram

Initial

Exit

Transition

<<flow>>

79

Data Flow Diagrams (DFD) help to model the system as a network of processes illustrating

the way in which data flows between elements in a system and with other external entities.

Primarily components of a typical data flow include: entity, process, data store, flow connectors,

and the diagram gate [32]. Table 5.2 gives an overview of these elements used in the modeling of

data flow diagrams.

Table 5.2: Data Flow Diagram Components

Representation Description

Entity

Process

Data Store

Data Flow

Diagram Gate

5.1.1 Parcel Tracking State Machine Model

The Parcel Tracking (PT) State Machine Diagram is captures the states of a parcel to

assist in visually following its status through the right-of-way project process. A parcel

undergoes several state changes during its lifecycle, from identification as a right-of-way parcel

to project closing, and allocation as excess or right-of-way. These changes are based on

corresponding ownership details, property valuations, legal procedures, and relocation activities,

which are triggered by different personnel and, in some cases, by contractors. The State Diagram

80

Model for PT shown in Figure 5.1 maps parcel data across the enterprise in a simple yet

comprehensive way and captures the appropriate attributes from the right-of-way data or class

model that triggers the state changes.

The initial transition for parcel tracking is denoted by the Initial element, representing the

default state of parcel at the start of parcel tracking or a right-of-way project. In most right-of-

way offices this initial state could be triggered by the right-of-way activity start date. An event

that enables the parcel transition from one state to another state is reflected through the triggered

operation, and captured under the state method. For example, the state „Project Number‟ is

controlled by the method „entry/Project_ID‟. Methods within the states are controlled by the

attributes of classes modeled in the overall right-of-way system. The triggering methods for each

parcel state are captured in the model using an information flow directed from the source classes

or packages. Tracing the information from the overall class model maintains the integrity of

Parcel Tracking model with the overall right-of-way logical model.

A triggered method may not always readily obtain the necessary information from the

overall logical class model in the right-of-way system. Sometimes the actions are abstracted to

derive the relevant information from one or more related classes and/or class packages of the

overall logical model. Such states are identified in blue text in Figure 5.1. For example, for the

state „Appraisal Type‟, the attribute „Appraisal_type‟ is derived from the „APP_Appraisal

Process Elements‟ package and „APP_Waiver_Establish_Value‟ class.

The states in the model represent the attributes of the parcel class which are categorized

as milestones, flags, and values, as discussed in Chapter 4. Milestones are highlighted in yellow

states, while flags are shown in red text, to provide visual clarity to the model. All parcel

attributes that include flags, values and milestones, are linked to the overall class model with the

81

information flow connector. Attributes categorized as flags, may have a value or be updated to

denote progress or completion stage based on timestamps governed by the start and end dates of

associated composite activities. With this understanding of flag, various states in the PT model,

categorized reflect the progress of a corresponding activity for the parcel, allowing the parcel to

be accordingly visualized in a geospatial environment. For example, the state „Status : Parcel

Evaluation & Inspection‟, reflects the progress of the activity for parcel evaluation. This flag

state can take multiple values or status based on when contact is made with the owner or when

the parcel is evaluated after the parcel visit. Along with other parcel states, these flags are

described accordingly in the model Table 4.2, but are not modeled at a greater level of detail due

to diverse protocols that govern the implementation and execution of flags for each individual

activity.

Four major states „Status_APP, Status_ACQ, Status_REL and Status_PM‟, are designed

as Composite states, with enclosed sub-states. These composite states model more complex

behavior of the system when there is more than one hierarchical level. For example, these states

are updated as the parcel traverses through related activities within the individual functional

areas for Appraisal, Acquisition, Relocation and Property Management, respectively. The

complete PT State Diagram Model is illustrated in Figure 5.1

82

Figure 5.1: Parcel Tracking State Machine Model Diagram

stm PT_State Machine Diagram Model

«Flag»

Status: APP

«Value»

Project Number

+ entry / Project_ID

«Value»

Project Parcel Number

+ entry / Project_Parcel_ID

«Value»

Parcel Take

+ entry / Type_Of_Take

«Value»

Parcel Land Use

+ entry / Parcel_Type/Parcel_Zoning

«Value»

Appraisal Complexity

+ entry / Complexity_Of_Appraisal

«Value»

Appraisal Type

+ entry / Appraisal_Type

«Value»

Appraiser Type

+ entry / Appraiser_Type

«Value»

Just Compensation

+ entry / Just_Compensation_value

«Value»

Appraisal Technique

+ entry / Appraisal_Technique

«Flag»

Status : Appraisal Report

+ entry / Status_Appraisal_Report_Availablity

«Flag»

Status : Appraisal Rev iew

+ entry / Status_Appraisal_Review

«Flag»

Status : Appraiser Assignment

+ entry / Status_Appraiser_Assignment

«Flag»

Status : Appraiser Certificate

+ entry / Status_Appraisal_Certificate_Issuance

«Flag»

Status : Parcel Ev aluation & Inspection

+ entry / Status_Parcel_Evaluation_&_Inspection

«Flag»

Status : Specialty Appraisal

+ entry / Status_Speciality_Appraisal

«Value»

Utilities

+ entry / Util ities_Affected

«Value»

Appraisal Rev iewer Type

+ entry / Appraisal_Reviewer_Type

«Flag»

Status : Rev iew Appraiser Certificate

+ entry / Status_Review_Appraiser_Certificate

«Flag»

Status: ACQ

«Value»

Acquisition Type

+ entry / Acquisition_Type

«Flag»

Status : Negotiator Assignment

+ entry / Status_Negotiator_Assignment

«Flag»

Negotiator Type

+ entry / Negotiator_Type

«Value»

Acquisition Additional Factors

+ entry / Add_Factor_Description

«Flag»

Status : Negotiation

«Value»

Owner Correspondence

+ entry / Status_Corresponence_with_Owner

«Value»

Type of Purchase

+ entry / Type_Of_Purchase

«Value»

Type of Negotiation

+ entry / Settlement_Type

«Value»

Settlement Amount Comparision

+ entry / Settlement_Amount_&Just_Compensattion_Comparision

«Flag»

Status : Property Encumbrance Release

+ entry / Status_Property-Encumbrance_release

«Flag»

Status: Settlement Amount Payment

+ entry / Payment_Of_ACQ_Settlement_Amount

«Flag»

Status : Acquisition Claim Forms

+ entry / Status_ACQ_Calim_Forms_Processing

«Flag»

Status : REL

«Value»

Primary Relocation Indicator

+ entry / Primary_Relocation_Indicator

«Value»

Secondary Relocation Indicator

+ entry / Secondary_Relocation_Indicator

«Flag»

Status : Relocation Serv ices

«Value»

Status : Notice Distribution

+ entry / Status _REL_Notice Distribution

«Flag»

Status : Site Office

+ entry / Status_Site_Office_Establishement

«Flag»

Status: Determination of Occupant Needs

+ entry / Status_Determination_of_Occupant_Needs

«Value»

Replacement Dwelling

+ entry / Replacement_Dwelling_Level

«Value»

Last Resort Housing Assignment

+ entry / Assignment_of_Last_Resort_Housing_Progress

«Flag»

Status : DSS Inspection I

+ entry / Status_Of_ DSS Inspection I

«Flag»

Status : DSS Inspection II

+ entry / Status_Of_ DSS Inspection II

«Flag»

Status : Relocation Assistance Payments

«Flag»

Status : Relocation Mov ing Expense Payment

«Value»

Residential Mov ing Expense Payment Method

+ entry / Fixed_Residential_Payment type (Method)

«Value»

Mobile Home Mov ing Expense Category

+ entry / Category_of_Mobile_Home_for_Moving_Expense_Calculation

«Value»

Non-Residential Mov ing Expense Payment Method

+ entry / Non-Residential_Moving_Expense_Payment_Method

«Value»

Replacement Housing Payment Method

+ entry / Resident type (Time of stay, ownership)

«Flag»

Status : Replacement Housing Payment

+ entry / Status_of_Payment_of_Replacement_Housing

«Value»

Displaced Person Mov e

+ entry / Displaced_Person_Move_Information

«Flag»

Status : Replacement Housing Payment Appeal

+ entry / Status _of_any_Replacement_Housing_Payment_Appeal(s)

«Flag»

Status : Relocation Claim and Tax Forms

+ entry / Status_of_Processing_Relocation_Claim_&_Tax_Forms

«Flag»

Status : PM

«Value»

Requirement Type

+ entry / Parcel_Requirement_Type

«Value»

Property Disposition Type

+ entry / Parcel_Disposition_Type

«Value»

Rental Type

+ entry / Type_of_rental

«Flag»

Status : Clearance

+ entry / Status_Clearance

«Value»

Personal Property Disposition Type

+ entry / Personal_Property_Disposition_Type

«Value»

Personal Property Clearance

+ entry / Personal_Property_Clearance

«Value»

Improv ement Disposition Type

+ entry / Improvement_Disposition_Type

«Value»

Improv ement Disposition Clearance

+ entry / Improvement_Disposition_Clearance

«Flag»

Status : Grading

+ entry / Status_of_Grading

«Flag»

Status : Parcel Disposition

«Value»

Excess/ROW Management Type

+ entry / Parcel_Type_For_Disposition

«Value»

Disposing Parcel Type


«Flag»

Status : Hazardous Material Mitigation

+ entry / Staus_Hazardous_Mitigation

«Value»

Security Inspection

+ entry / Security_Inspection_Type

«Value»

Rodent Control

+ entry / Rodent_Control_Type

«Value»

Notice to Proceed

+ entry / Type_of_Notice_to_Proceed

«Flag»

Status : ROW Certification

+ entry / Status_of_RoW_Certificate

«Flag»

Status : Federal Voucher Letter

+ entry / Status_OF_Federal_Voucher_Letter

Final

Class Model Model Package -

Ov erall ROW::Project

Cadastral Elements::Cadastral_Parcel

APP_Waiv er Class Elements::APP_Waiv er_Establish_Value

APP_Appraisal Process Elements

(from APP_Class Model Package)

APP_Appraisal Process

Elements::APP_Appraiser

APP_Class Model Package::

APP_Appraiser_Assignment

APP_Appraisal Process Elements::

APP_Inspect_&_Ev aluate_Parcel

APP_Detailed Appraisal Ev aluation Class Elements

(from APP_Appraisal Process Elements)

APP_Minimum Standard Appraisal Class Elements


APP_Detailed Appraisal Ev aluation

Class Elements::

APP_Speciliaty_Appraisal

APP_Class Model Package::APP_Appraiser_Certificate

APP_Appraisal Rev iew Class Elements::

APP_Appraisal_Rev iewer _Assignment


APP_Rev iew_Appraiser _Certificate

APP_Class Model Package::APP_Just_Compensation


Appraisal_Report

ACQ_Pre-Negotiation Elements::

ACQ_Acquisition_Type


ACQ_Negotiator_Assignment

ACQ_Negotiation Elements::

ACQ_Negotiator


ACQ_Additional_Factors


ACQ_Contact_Owner

ACQ_Detailed Negotiation Elements

(from ACQ_Negotiation Elements)

ACQ_Detailed Negotiation

Elements::

ACQ_Settlement_Amount


ACQ_Property-Encumbrance_releases

ACQ_Closing Elements::

ACQ_Just_Compensation


ACQ_Negotiation_Closing_Documents

ROW Parcel

REL_Class Model Package::REL_Parcel

for Relocation

REL_Relocation Planning Elements::

REL_Notices


Elements::REL_Site_Office

REL_Relocation Serv ices Elements::

REL_Serv ices_Initiativ e


REL_Replacement_Dwelling_Assignment


REL_Residential Replacement Housing

Determination

REL_Relocation Serv ices

Elements::REL_Housing of

Last Resort

REL_Mov ing Expense Process Elements::

REL_Fixed_Residential_Mov ing_Expense_Payments


REL_Mov ing Expenses for Mobile Home

REL_Non-Residential Mov ing Expense Payment

(from REL_Moving Expense Process Elements)

REL_Replacement Housing Payment

Process Elements::REL_Residential

Replacement Housing Payment

Determination


Elements::REL_Claim and Tax Related

Processing

REL_Replacement Housing Payment Process Elements

(from REL_Relocation Assistance Payments Elements)

PM_Pre-Construction Elements::

PM_Requirement_Type

PM_Pre-Construction Elements

(from PM_Class Model Package)


PM_Property_Rental


PM_Clearance/Demolition

PM_During Construction Elements::

PM_Grading

PM_Post-Construction Elements


PM_Class Model Package::

PM_Rodent Control


PM_Security Inspection

PM_Class Model Package::PM_HazMat

Mitigation

Project Closing Elements::

Notice_to_Proceed

Project Closing Elements::Project_Closing

Initial

«Value»

Hazardous Material Mitigation

+ entry / Hazardous_Mitigation_Type

States in Blue represent: Attributes of the Parcel Log that are

not related to any existing attribute; But, are derived from two

or more classes or updated according to the corresponding

activity in the ROW Parcel records.

States in Yellow represent: Milestones

States in Red represent: Flags. These flags may be invoked

by the time stamps corresponding to the respective activities.

«Type»

State

«Type»

State

«Type»

State

LEGEND

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

83

Figure 5.1: Parcel Tracking State Machine Model Diagram (Cont.)


«Flag»

Status: APP

«Value»

Project Number


«Value»



«Value»

Parcel Take


«Value»

Parcel Land Use


«Value»



«Value»

Appraisal Type


«Value»

Appraiser Type


«Value»

Just Compensation


«Value»

Appraisal Technique


«Flag»



«Flag»



«Flag»



«Flag»



«Flag»



«Flag»



«Value»

Utilities


«Value»



«Flag»



«Flag»

Status: ACQ

«Value»

Acquisition Type


«Flag»



«Flag»

Negotiator Type


«Value»



«Flag»


«Value»



«Value»

Type of Purchase


«Value»

Type of Negotiation


«Value»



«Flag»



«Flag»



«Flag»



«Flag»

Status : REL

«Value»



«Value»



«Flag»


«Value»



«Flag»



«Flag»



«Value»



«Value»



«Flag»



«Flag»



«Flag»


«Flag»


«Value»



«Value»



«Value»



«Value»



«Flag»



«Value»



«Flag»



«Flag»



«Flag»

Status : PM

«Value»

Requirement Type


«Value»



«Value»

Rental Type


«Flag»

Status : Clearance


«Value»



«Value»



«Value»



«Value»



«Flag»

Status : Grading


«Flag»


«Value»



«Value»



«Flag»



«Value»

Security Inspection


«Value»

Rodent Control


«Value»

Notice to Proceed


«Flag»



«Flag»



Final


















Class Elements::









Appraisal_Report






ACQ_Negotiator




ACQ_Contact_Owner




Elements::








ROW Parcel


for Relocation


REL_Notices









Determination



Last Resort










Determination



Processing




PM_Requirement_Type




PM_Property_Rental




PM_Grading




PM_Rodent Control




Mitigation


Notice_to_Proceed


Initial

«Value»










«Type»

State

«Type»

State

«Type»

State

LEGEND

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

84



«Flag»

Status: APP

«Value»

Project Number


«Value»



«Value»

Parcel Take


«Value»

Parcel Land Use


«Value»



«Value»

Appraisal Type


«Value»

Appraiser Type


«Value»

Just Compensation


«Value»

Appraisal Technique


«Flag»



«Flag»



«Flag»



«Flag»



«Flag»



«Flag»



«Value»

Utilities


«Value»



«Flag»



«Flag»

Status: ACQ

«Value»

Acquisition Type


«Flag»



«Flag»

Negotiator Type


«Value»



«Flag»


«Value»



«Value»

Type of Purchase


«Value»

Type of Negotiation


«Value»



«Flag»



«Flag»



«Flag»



«Flag»

Status : REL

«Value»



«Value»



«Flag»


«Value»



«Flag»



«Flag»



«Value»



«Value»



«Flag»



«Flag»



«Flag»


«Flag»


«Value»



«Value»



«Value»



«Value»



«Flag»



«Value»



«Flag»



«Flag»



«Flag»

Status : PM

«Value»

Requirement Type


«Value»



«Value»

Rental Type


«Flag»

Status : Clearance


«Value»



«Value»



«Value»



«Value»



«Flag»

Status : Grading


«Flag»


«Value»



«Value»



«Flag»



«Value»

Security Inspection


«Value»

Rodent Control


«Value»

Notice to Proceed


«Flag»



«Flag»



Final


















Class Elements::









Appraisal_Report






ACQ_Negotiator




ACQ_Contact_Owner




Elements::








ROW Parcel


for Relocation


REL_Notices









Determination



Last Resort










Determination



Processing




PM_Requirement_Type




PM_Property_Rental




PM_Grading




PM_Rodent Control




Mitigation


Notice_to_Proceed


Initial

«Value»










«Type»

State

«Type»

State

«Type»

State

LEGEND

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

85



«Flag»

Status: APP

«Value»

Project Number


«Value»



«Value»

Parcel Take


«Value»

Parcel Land Use


«Value»



«Value»

Appraisal Type


«Value»

Appraiser Type


«Value»

Just Compensation


«Value»

Appraisal Technique


«Flag»



«Flag»



«Flag»



«Flag»



«Flag»



«Flag»



«Value»

Utilities


«Value»



«Flag»



«Flag»

Status: ACQ

«Value»

Acquisition Type


«Flag»



«Flag»

Negotiator Type


«Value»



«Flag»


«Value»



«Value»

Type of Purchase


«Value»

Type of Negotiation


«Value»



«Flag»



«Flag»



«Flag»



«Flag»

Status : REL

«Value»



«Value»



«Flag»


«Value»



«Flag»



«Flag»



«Value»



«Value»



«Flag»



«Flag»



«Flag»


«Flag»


«Value»



«Value»



«Value»



«Value»



«Flag»



«Value»



«Flag»



«Flag»



«Flag»

Status : PM

«Value»

Requirement Type


«Value»



«Value»

Rental Type


«Flag»

Status : Clearance


«Value»



«Value»



«Value»



«Value»



«Flag»

Status : Grading


«Flag»


«Value»



«Value»



«Flag»



«Value»

Security Inspection


«Value»

Rodent Control


«Value»

Notice to Proceed


«Flag»



«Flag»



Final


















Class Elements::









Appraisal_Report






ACQ_Negotiator




ACQ_Contact_Owner




Elements::








ROW Parcel


for Relocation


REL_Notices









Determination



Last Resort










Determination



Processing




PM_Requirement_Type




PM_Property_Rental




PM_Grading




PM_Rodent Control




Mitigation


Notice_to_Proceed


Initial

«Value»










«Type»

State

«Type»

State

«Type»

State

LEGEND

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

86



«Flag»

Status: APP

«Value»

Project Number


«Value»



«Value»

Parcel Take


«Value»

Parcel Land Use


«Value»



«Value»

Appraisal Type


«Value»

Appraiser Type


«Value»

Just Compensation


«Value»

Appraisal Technique


«Flag»



«Flag»



«Flag»



«Flag»



«Flag»



«Flag»



«Value»

Utilities


«Value»



«Flag»



«Flag»

Status: ACQ

«Value»

Acquisition Type


«Flag»



«Flag»

Negotiator Type


«Value»



«Flag»


«Value»



«Value»

Type of Purchase


«Value»

Type of Negotiation


«Value»



«Flag»



«Flag»



«Flag»



«Flag»

Status : REL

«Value»



«Value»



«Flag»


«Value»



«Flag»



«Flag»



«Value»



«Value»



«Flag»



«Flag»



«Flag»


«Flag»


«Value»



«Value»



«Value»



«Value»



«Flag»



«Value»



«Flag»



«Flag»



«Flag»

Status : PM

«Value»

Requirement Type


«Value»



«Value»

Rental Type


«Flag»

Status : Clearance


«Value»



«Value»



«Value»



«Value»



«Flag»

Status : Grading


«Flag»


«Value»



«Value»



«Flag»



«Value»

Security Inspection


«Value»

Rodent Control


«Value»

Notice to Proceed


«Flag»



«Flag»



Final


















Class Elements::









Appraisal_Report






ACQ_Negotiator




ACQ_Contact_Owner




Elements::








ROW Parcel


for Relocation


REL_Notices









Determination



Last Resort










Determination



Processing




PM_Requirement_Type




PM_Property_Rental




PM_Grading




PM_Rodent Control




Mitigation


Notice_to_Proceed


Initial

«Value»










«Type»

State

«Type»

State

«Type»

State

LEGEND

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

87



«Flag»

Status: APP

«Value»

Project Number


«Value»



«Value»

Parcel Take


«Value»

Parcel Land Use


«Value»



«Value»

Appraisal Type


«Value»

Appraiser Type


«Value»

Just Compensation


«Value»

Appraisal Technique


«Flag»



«Flag»



«Flag»



«Flag»



«Flag»



«Flag»



«Value»

Utilities


«Value»



«Flag»



«Flag»

Status: ACQ

«Value»

Acquisition Type


«Flag»



«Flag»

Negotiator Type


«Value»



«Flag»


«Value»



«Value»

Type of Purchase


«Value»

Type of Negotiation


«Value»



«Flag»



«Flag»



«Flag»



«Flag»

Status : REL

«Value»



«Value»



«Flag»


«Value»



«Flag»



«Flag»



«Value»



«Value»



«Flag»



«Flag»



«Flag»


«Flag»


«Value»



«Value»



«Value»



«Value»



«Flag»



«Value»



«Flag»



«Flag»



«Flag»

Status : PM

«Value»

Requirement Type


«Value»



«Value»

Rental Type


«Flag»

Status : Clearance


«Value»



«Value»



«Value»



«Value»



«Flag»

Status : Grading


«Flag»


«Value»



«Value»



«Flag»



«Value»

Security Inspection


«Value»

Rodent Control


«Value»

Notice to Proceed


«Flag»



«Flag»



Final


















Class Elements::









Appraisal_Report






ACQ_Negotiator




ACQ_Contact_Owner




Elements::








ROW Parcel


for Relocation


REL_Notices









Determination



Last Resort










Determination



Processing




PM_Requirement_Type




PM_Property_Rental




PM_Grading




PM_Rodent Control




Mitigation


Notice_to_Proceed


Initial

«Value»










«Type»

State

«Type»

State

«Type»

State

LEGEND

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

88


Thus, parcel tracking is abstracted in UML to represent the finite states of a parcel,

transitions between these states and the triggering actions for these states using a State Diagram

Model. Identified states that represent the stages of a parcel during the course of a right-of-way

project process, help in tracking the parcel visually in a geospatial environment and helps in

understanding functionalities that affect the various states.


«Flag»

Status: APP

«Value»

Project Number


«Value»



«Value»

Parcel Take


«Value»

Parcel Land Use


«Value»



«Value»

Appraisal Type


«Value»

Appraiser Type


«Value»

Just Compensation


«Value»

Appraisal Technique


«Flag»



«Flag»



«Flag»



«Flag»



«Flag»



«Flag»



«Value»

Utilities


«Value»



«Flag»



«Flag»

Status: ACQ

«Value»

Acquisition Type


«Flag»



«Flag»

Negotiator Type


«Value»



«Flag»


«Value»



«Value»

Type of Purchase


«Value»

Type of Negotiation


«Value»



«Flag»



«Flag»



«Flag»



«Flag»

Status : REL

«Value»



«Value»



«Flag»


«Value»



«Flag»



«Flag»



«Value»



«Value»



«Flag»



«Flag»



«Flag»


«Flag»


«Value»



«Value»



«Value»



«Value»



«Flag»



«Value»



«Flag»



«Flag»



«Flag»

Status : PM

«Value»

Requirement Type


«Value»



«Value»

Rental Type


«Flag»

Status : Clearance


«Value»



«Value»



«Value»



«Value»



«Flag»

Status : Grading


«Flag»


«Value»



«Value»



«Flag»



«Value»

Security Inspection


«Value»

Rodent Control


«Value»

Notice to Proceed


«Flag»



«Flag»



Final


















Class Elements::









Appraisal_Report






ACQ_Negotiator




ACQ_Contact_Owner




Elements::








ROW Parcel


for Relocation


REL_Notices









Determination



Last Resort










Determination



Processing




PM_Requirement_Type




PM_Property_Rental




PM_Grading




PM_Rodent Control




Mitigation


Notice_to_Proceed


Initial

«Value»










«Type»

State

«Type»

State

«Type»

State

LEGEND

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

89

5.1.2 Geospatial Enablement Data Flow Model

Geospatial Enablement (GE) framework is captured in UML using Data Flow Diagrams.

Data flows are defined for the GE model to illustrate activities that can be geospatially enabled

as tabulated in Table 4.1. This model helps in capturing the high-level system overview, which

would help designers during the initial analysis and implementation stages of developing an

integrated geospatial information management system to visualize the flow of geospatial data

within the system.

The package diagram that gives an overview of the GE data flow diagrams is shown in

Figure 5.2. It shows the data flow diagram packages for the four functional areas, Project

Development, Appraisal, Relocation, and Property Management. As, indicated in Chapter 4, no

GE activities were identified for Acquisition or Project Closing. Figure 5.2 also shows the major

geospatial resources from a GIS warehouse that constitute common enabling infrastructure.

These layers along with other resources from the geospatial warehouse provide the required

inputs for processes captured in the data flow diagrams for the individual right-of-way functional

areas, shown in Figures 5.3 through 5.6.

The data stores highlighted in red represent geospatial layers, while others denote

standard databases. Red data flow connectors represent the geospatial data flow that results in the

creation of new layers or databases. They represent relations between critical layers in the

warehouse. For example, the relation between the ROW Project Parcels and Parcel Cadastre

Layer, and New Roadway ROW and the Roadway ROW layer, are illustrated through red data

flow connectors. Table 5.3 summarizes the resources in the GE model.

90

Figure 5.2: Overview of Geospatial Enablement Data Flow Diagram Model

91

Figure 5.3: Geospatial Enablement Data Flow Diagram for Project Development

dfd Project Dev elopment: Geospatial Enablement

GIS Warehouse

New roadway

ROW

Parcel_Cadastre

Layer

VideoLogRoadway ROW

layer

ROW Project

Parcels

Define

Parcel

Type of

Take :

Spatial

Analysis

Alignment

Selection :

Spatial

Analysis

ROW Mapping

and Engineering

Environmental/

Hazardous

Sites : Spatial

Analysis

Environmental

System/ Other

Spatial

Analysis :

Overlay &

Extraction

Identify

parcels for

right-of-way

Divide

Parcel(s) :

Spatial

Analysis

Thematic

/ Visual

Display

Thematic

/ Visual

Display

Imagery

Divide & Redefine

ROW Project

Parcels

ROW Project

Parcels

Identification

«trace»

Alignment

Selection

«trace»

«trace»«trace»

ROW

Plans

ROW

Plans

«trace»

Environmental &

Hazardous waste sites

Evaluation/Study Reports

92

Figure 5.4: Geospatial Enablement Data Flow Diagram for Appraisal

dfd APP: Geospatial Enablement

Appraisal SystemHistorical parcel

sales Records

GIS Warehouse

ROW Project

Parcels

New roadway

ROW

Parcel_Cadastre

Layer

Parcels with

special properties

VideoLog

Util ities

ROW Parcel

Util ities

APP :

Initial

Review

(Visual

Display)

Sales

Comparison

(Data

Analysis)

Data

Query/

Extraction/

Overlay

Spatial

Analysis :

3D Analyst

Thematic

/ Visual

Display

Thematic

/ Visual

Display

Appraisal

Technique

(Data

Analysis)

Data

Query/

Extraction

Roadway ROW

layer

Imagery

Identification

of Parcels

with util ities

Appraisal_Technique

«trace»

«trace»

«trace»

Special

Property

Identification

«trace»

«trace»

«trace»

«trace»

Effect of

Elevation

Changes

«trace»

93

Figure 5.5: Geospatial Enablement Data Flow Diagram for Relocation

dfd REL: Geospatial Enablement

Demographic Data

Layer

Candidate Parcel

Inventory for

Displaced Persons

Lease/Sale

property

management

system

GIS Warehouse

ROW Project

Parcels

Parcel_Cadastre

Layer

Data Query

(Extraction)

Parcels for /

Requiring

Relocation

Spatial

Analysis /

Modeling

Util ities

Spatial

Analysis :

Overlay /

Spatial

Query

Candidate Parcel

Inventory for

Relocating or

Adjusting Util ities

Thematic /

Visual

Display

Thematic /

Visual

Display

Transportation

Roadway Network

Suitable

Parcels

«trace»

Parcel Land Use

or Primary

Relocation

Indicator

«trace»«trace»

Needs of the

Displaced

Socio-Economic

Factors

«trace»

Suitable

Parcel(s) /

Location(s)

«trace»

Parcel(s)

Identification

94

Figure 5.6: Geospatial Enablement Data Flow Diagram for Property Management

dfd PM: Geospatial Enablement

PM :

Clearance

/Demolition

PM :

Grading

PM :

Requirement

Type

PM : ROW /

Excess

Disposal

JustificationExcess Property

Topography Layer

Soil Data Layer

GIS Warehouse

ROW Project

Parcels

New roadway

ROW

Spatial

Analysis :

Overlay

Data Query

(Extraction)

Surface

Analysis :

Cut/Fil l

(3D-Analyst)Spatial

Analysis :

Modeling

Visual

Analysis /

Data

Query

Parcel_Cadastre

Layer

Transportation

Roadway Network

Vegetation Layer

Thematic /

Visual

Display

Thematic /

Visual

Display

Roadway ROW

layer

Update:

Parcel_Requirement_Type

«trace»

«trace»

Excess Land

Identification

Area of Parcel in ROW

Boundary/Area

Cost of

earthwork

Type & Level

of Clearance

«trace»

«trace»

Thematic Maps/

Justification

Models

Highway

Safety/

Traffic

Demand

Status_of_Clearance

Status_of_Grading

«trace»

Soil Type

Vegetation

Classification

Improvement_Disposition_Type /

Personal_Property_Disposition_Type

LandUse/

Zoning

«trace»

Terrain /

Elevation

Soil

Type

Boundary/Area

«trace»

95

Table 5.3: Summary of resources for Geospatial Enablement

Type Resource Description G

eosp

ati

al

Layer

Parcel Cadastre Layer Statewide Cadastre layer or project-by-project

generated parcel layer for use by ROW.

Transportation Roadway

Network Statewide network of roadways layer.

Roadway ROW Layer Statewide roadway right-of-way layer.

New roadway ROW

Changes to roadway ROW layer based on new

transportation project. Usually CAD drawings

maintained by the state transportation agency.

VideoLog Photographs of continuous views from a road

and associated parcels.

Imagery Aerial imagery of the parcel/roadway/ parcel

property, and other related photographic data.

Topography Statewide topography layer containing

topographic contours.

Soil Data Statewide soil layer containing 'soil types' and

the related soil data.

Vegetation Statewide vegetation layer containing

'vegetation classification' and other related data.

Utilities Statewide utilities layer(s).

Demographic Data Layer Statewide demographic layer containing

demographic characteristics.

Exte

rnal

Syst

em

ROW Mapping and Engineering

Division

Department that prepares the right-of-way plans

for the project.

External Environmental System

System facilitating the required NEPA

environmental analysis and Hazardous waste

sites evaluation.

External Appraisal System System that helps in identifying the required

technique for parcel appraisal.

External Historical Parcel Sales

Records

System that provides the records for data

analysis during sales comparison.

External Lease/Sale Property

Management System

Systems like Zillow, MLS or other equivalent

that provides information of available property

for relocating the displaced.

96

Table 5.3: Summary of resources for Geospatial Enablement (Cont.)

Type Resource Description D

ata

base

ROW Project Parcels

Parcels identified as part of new transportation

project. Total parcels may be maintained or

parcels may be split into ROW and excess.

Either a linked table to the state cadastral layer

or a separate geospatial layer maintained by the

state transportation agency or ROW office.

ROW Parcel Utilities Selection from statewide utilities layer(s)

Parcels with special properties Selection from Cadastral layer or from ROW

project parcel layer.

Candidate Parcel Inventory for

Displaced Persons

Selection from the state cadastral layer or sale

and/or lease property database.

Candidate Parcel Inventory for

Relocating or Adjusting Utilities Selection from the statewide utilities layer(s).

Excess Property

Linked table to the statewide Cadastral layer or

a separate geospatial layer maintained by the

state transportation agency or the ROW office.

5.2 GDMA Model Evaluation

The GDMA model was evaluated through detailed discussions with a state transportation

agency, Pennsylvania Department of Transportation (PennDOT), to determine if the model

accurately represented how a right-of-way office would track and visualize parcel status and

whether the model has identified the appropriate activities that could benefit from geospatial

enablement. This section presents a brief overview of the evaluation process along with

resulting modifications to the model.

97

5.2.1 GDMA Evaluation Process

GDMA was evaluated through a face-to-face meeting with right-of-way personnel in

each of the primary functional areas, Appraisal, Acquisition, Relocation, and Property

Management, as well as the ROW director for Project Development and Project Closing. After

an overall discussion, processes in each area for the Parcel Tracking and Geospatial Enablement

models were presented and evaluated for practicality and accuracy, and to ensure that the

information captured in the model is compliant with their business practices. The presentation

provided a background of the research, purpose of the meeting, and an overview of the GDMA

model framework The parcel tracking logical flow chart, Figure 4.1, list and description of

attributes of the parcel tracking model, Table 4.2, and list of identified geospatial enablement

activities, Table 4.3, were presented. Discrepancies or variations with the model were

documented, and the model was updated appropriately. The State Diagram and Data Flow

Diagram models presented in the previous section include these modifications.

5.2.2 GDMA Evaluation Results

The GDMA framework was noted to be beneficial for enhancing right-of-way business

practices by the ROW personnel. Based on their comments several changes and additional ideas

have been incorporated to both the Parcel Tracking and Geospatial Enablement components as

documented in Table 5.4 and summarized below.

One critical aspect of the feedback for the Parcel Tracking model consisted specifically

identifying milestones separately from general status for parcels as they move through each of

98

the business functional areas. PennDOT personnel indicated that they have milestone clear dates

to track project progress.

PennDOT personnel indicated that Problem Analysis, Appraisal Review, and Settlement

Value are the tracking milestones, which are captured in the PT State diagram model under

„Appraisal Technique‟, „Status: Appraisal Review‟, and „Just Compensation‟. For, Appraiser

assignment state, it was noted that the appraiser certification has to be verified and that it can act

as a status flag during the process of assigning an appraiser. In addition, PennDOT personnel

suggested that appraiser workload assignment can also be mapped visually in the model based on

the complexity of appraisal process. This has been incorporated in the model by adding the state

„Appraiser Complexity‟. Further, it was noted that „Appraisal Type‟ is referred to as „format

required‟; and „Appraisal Technique‟ as „valuation techniques‟ in their right-of-way office.

Since, the terms are agency specific, appropriate modifications have been made to the

description of states to reflect these considerations, without changing their current names.

In the areas of acquisition and property management, milestones for parcel tracking were

identified, and suggestions for relocation include adding an additional category under the state,

„Secondary Relocation Indicator‟ to address the presence of billboards and commercial signs on

parcels. Additionally, the process „Spatial Analysis: Overlay / Spatial Query‟, for locating

suitable parcels for realigning utilities is identified and added in the model. Finally, under project

closing, two states, „Notice to Proceed‟, and „Federal Voucher Letter‟ have been added to the PT

model.

Additional geospatial activities were suggested for the Geospatial Enablement Model,

especially in the appraisal process, and were added to the model along with the required

resources. These activities included three dimensional modeling to visualize elevation changes

99

and their effects on after property value, locating properties with street view images for initial

appraisal review, comparing paired sales with available historical data in a geospatial

environment, and locating parcels with utilities. These changes to the GE model have been

incorporated by adding the data flow processes: Sales Comparison (Data Analysis), Spatial

Analysis: 3D Analyst, Data Query/ Extraction / Overlay (for the identification of parcels with

utilities). Associated resources added to the model include, „VideoLog Layer‟ and „External

Historical Parcel Sales Records‟.

Table 5.4: Summary of changes to GDMA model based on evaluation process

Model Object affected Functional Area Description of Change

Parc

el T

rack

ing

State - Parcel type of take Project

Development

Renamed Parcel Type to Parcel type of

take

State - Appraisal Type Appraisal

Noted under the state description that it

can be otherwise defined as „format

required‟

State - Appraisal

Technique Appraisal

Noted under the state description that it

can be otherwise defined as „valuation

technique‟

State - Status : Appraiser

Assignment Appraisal

Noted under the state description that

verifying appraiser certification acts as

a checkmark or requirement for

determining appraiser assignment.

State - Appraisal

Complexity Appraisal

Added to capture the complexity of

parcel appraisal

State - Utilities Appraisal Added to identify the utilities (if any)

present on the right-of-way parcel

State - Secondary

Relocation Indicator Relocation

Modified the categories under the state

description to address billboards and

commercial signs on parcel.

State - Notice to Proceed Project Closing

Added to identify the type of notice

issued for proceeding with roadway

construction

State - Status : Federal

Voucher Letter Project Closing

Added to identify the submission of

federal voucher letter

States - Milestones Parcel Tracking

Identified milestones from the existing

flags and values, are added to

Appraisal, Acquisition, Relocation and

Property Management

100

Table 5.4: Summary of changes to GDMA model based on evaluation process (Cont.)

Model Object affected Functional Area Description of Change

Geo

spati

al

En

ab

lem

ent

Layer -VideoLog Appraisal

Added for identifying the parcels

during alignment selection, locating

properties during initial appraisal

review, and for determining the

complexity of appraisal.

Layer : Utilities Appraisal

Added to facilitate the identification of

parcels with utilities and locating the

possible areas for adjusting the utilities.

External Resource-

Historical Parcel Sales

Records

Appraisal

Added to facilitate the geospatial

activity associated with sales

comparison.

Geospatial Activity- Sales

Comparison (Data

Analysis)

Appraisal Added to incorporate paired sales

comparison with historical data.

Geospatial Activity-

Spatial Analysis : 3D

Analyst

Appraisal Added to analyze the effect of elevation

changes on adjoining property

Geospatial Activity- Data

Query/ Extraction /

Overlay

Appraisal Added to identify parcels with utilities

Geospatial Activity-

Spatial Analysis: Overlay

/ Spatial Query

Relocation

Added to locate suitable parcels for

adjusting or relocating the affected

utilities.

External Resource :

Historical Parcel Sales

Records

Appraisal

Added to facilitate the geospatial

activity associated with sales

comparison.

This chapter presented the logical model for Geospatial Decision Making Activities, with

a detailed description of the Parcel Tracking State Machine diagram and Geospatial Enablement

Data Flow diagram. It also described the evaluation efforts undertaken with the PennDOT ROW

personnel by presenting the evaluation process and the suggested changes.

101

6 CONCLUSIONS AND RECOMMENDATIONS

This chapter presents the conclusions of the research and recommendations for future work.

6.1 Conclusions

Available literature identifies the need for a comprehensive enterprise-level geospatially-

enabled information management system for right-of-way activities. This research presented an

overview of the design of a UML-based logical model for a right-of-way information

management system, which is expected to provide a flexible blueprint for state transportation

agencies to implement an enterprise-wide information management system, accommodating the

unique needs of individual agencies. The overall logical model is expected to assist

transportation agencies in their planning for implementing a system that would integrate and

interact with other existing enterprise-level information systems, prior to the investment of funds.

The research then focused on developing the framework for Geospatial Decision

Making Activities (GDMA) to provide the required knowledge base for right-of-way offices to

integrate geospatial technology into their business. The GDMA framework, developed in

coordination with the overall logical model, captures the comprehensive parcel tracking process

through the Parcel Tracking (PT) sub-model. The GDMA framework is also expected to

contribute to the improvement of existing individual right-of-way offices, through the Geospatial

Enablement (GE) sub-model, which models the geospatial decision making activities for

different right-of-way functional areas that could benefit from being geospatially enabled.

102

The GDMA model is expected to serve as a template for the use by state transportation

agencies to help develop systems for geospatially enabling the right-of-way business practices,

meeting their specific requirements. It helps in increasing the accessibility of the parcel status to

efficiently manage workloads and also provide required parcel information to an external GIS

warehouse, which could, in turn, help in building a larger integrated enterprise system. Such a

model would provide a mechanism for improving data sharing, management and analysis across

transportation agencies.

The model has been evaluated for its practicality and implementability with PennDOT

Utility and Right of Way Section, and has been modified to reflect their recommendations. The

flexible yet compact framework of the model enables transportation agencies to customize their

existing right-of-way systems or to begin the process of designing a new comprehensive

geospatially enabled system. The PT state machine diagram and GE data flow diagram models

provide the necessary understanding of the functionality of the GDMA framework for

developing such geospatially enabled information management systems.

6.2 Recommendations

Future research consists of expanding the state machine diagrams for the individual states

included in the parcel tracking model to capture the internal transitions within each state. This

helps in enhancing the GDMA model by capturing the detailed flow of data within the enterprise

system required for incorporating parcel tracking. Individual milestones and flags captured in the

parcel tracking component can also be elaborated with appropriate data-integration models to

further capture the information flow required for the execution of each state. Also,

103

implementation or user-interface models can be designed for the developed logical model, to

capture the required artifacts for building and managing the enterprise-wide geospatially enabled

information system in a real-time environment.

104

REFERENCES

1. Hancock, Kathleen L (2006). Integrating Geospatial Technologies into the Right-of-Way

Data-Management Process. National Cooperative Highway Research Program Research

Results Digest 310. Transportation Research Board, Washington, D.C. December 2006.

<http://onlinepubs.trb.org/onlinepubs/nchrp/nchrp_rrd_310.pdf>

2. Ghanta N (2007), “Integrating Geospatial Technologies into the Property Management

Process Of The Transportation Right-Of-Way”. Master‟s Thesis Virginia Polytechnic

Institute and State university,, Falls Church, Virginia.

3. Federal Highway Administration. (2006). Project Development Guide (PDG).

<http://www.fhwa.dot.gov/realestate/pdg.htm> [Retrieved on 08/15/07]

4. Federal Highway Administration. (2006). Real Estate Acquisition Guide For Local

Public Agencies. <http://www.fhwa.dot.gov> [Retrieved on 08/15/07]

5. Saka, Anthony A. (2004) Geographic Information System Implementation of State

Department of Transportation Right-of-Way Programs. Office of Real Estate Services.

Washington, DC : Federal Highway Administration, July 2004. DTFH61-03-H-00121.

<http://www.fhwa.dot.gov/realestate/rowsurvjuly04.htm>

6. Hancock, Kathleen L. (2006) Integrating Geospatial Technologies into the Right-of-Way

Data-Management Process: Appendixes A through F. National Cooperative Highway

Research Program Web-Only Document 95, Transportation Research Board, June 2006.

Alexandria, VA <http://onlinepubs.trb.org/onlinepubs/nchrp/nchrp_w95.pdf>

7. Sparx Systems Pty Ltd. (2007). Enterprise Architect - UML CASE Tool - Desktop,

Professional and Corporate Editions, Version 7.0 [Software]. Available from

<http://www.sparxsystems.com.au/products/ea/index.html>

8. Indiana Department of Transportation, Office of Real Estate (2006). Property

Management Manual. Indianapolis.

<http://www.in.gov/indot/files/05.PropertyManagementManual12-05.pdf>

http://onlinepubs.trb.org/onlinepubs/nchrp/nchrp_rrd_310.pdf

http://www.fhwa.dot.gov/realestate/pdg.htm

http://www.fhwa.dot.gov/

http://www.fhwa.dot.gov/realestate/rowsurvjuly04.htm

http://onlinepubs.trb.org/onlinepubs/nchrp/nchrp_w95.pdf

http://www.sparxsystems.com.au/products/ea/index.html


105

9. Oregon Department of Transportation (ODOT), (2008), “Enterprise Content

Management Systems (Right of Way)”, United States, Subcommittee on Right-of-Way

and Utilities (AASTHO), Washington, DC.

<http://cms.transportation.org/sites/rightofway/docs/RWorEnterpriseContentMgmtSys34

08.do>


Excellence in Right-of-Way Awards”. FHWA-HEP-04-010, Washington, DC.

11. New Jersey Department of Transportation, (2004), “Survey - Right-of-Way information

system”, United States, Subcommittee on Right-of-Way and Utilities (AASTHO),

Washington, DC.

<http://cms.transportation.org/sites/rightofway/docs/Survey_Right_of_Way_Information

_System.pdf>

12. Ordway, D., Whaley, J. “Geographical Information Systems Applications For

Transportation Right-of-Way”, Summary Report on a Follow-Up Peer Exchange, Lee‟s

Summit, Missouri, July 22-24, 2008,

<http://www.gis.fhwa.dot.gov/documents/rightOfWay.asp#missouri> [Retrieved on

03/27/09];

13. “AASHTO Turbo Relocation Win”, BEM Systems, Inc.

<http://www.bemsys.com/index.php?option=com_content&view=article&id=45:aashto-

turbo-relocation-win&catid=20:recent-news&Itemid=27> [Retrieved on 08/06/09]

14. Federal Highway Administration. (2007) “Peer Exchange on Applications of Geographic

Information Systems in the Right-of-Way Area”. Lee's Summit, Missouri. August 2007.

<www.gis.fhwa.dot.gov/gisrow.asp>

15. John, Durling O. (2009). “Image Records Management System”. Connecticut Geo-Focus.

2009, Vol. 2, 3. Connecticut Geospatial Newsletter Fall‟09-Connecticut Geospatial

Information Systems Council. East Hartford, Connecticut.

<http://www.ct.gov/gis/lib/gis/CT_Geospatial_Newsletter_Fall09.pdf>

16. Michigan Department of Transportation. (2003). “Real Estate Management Information

System.” Subcommittee on Right-of-Way and Utilities (AASTHO), Exhibit F, Michigan.

http://cms.transportation.org/sites/rightofway/docs/RWorEnterpriseContentMgmtSys3408.doc

http://cms.transportation.org/sites/rightofway/docs/RWorEnterpriseContentMgmtSys3408.doc



http://www.gis.fhwa.dot.gov/documents/rightOfWay.asp#missouri

http://www.bemsys.com/index.php?option=com_content&view=article&id=45:aashto-turbo-relocation-win&catid=20:recent-news&Itemid=27

http://www.bemsys.com/index.php?option=com_content&view=article&id=45:aashto-turbo-relocation-win&catid=20:recent-news&Itemid=27

http://www.gis.fhwa.dot.gov/gisrow.asp

http://www.ct.gov/gis/lib/gis/CT_Geospatial_Newsletter_Fall09.pdf

106

17. MSI Data Systems Inc. (2008). “READS - Automated Software for State Government

Highways/Real Estate Operation”. Mequon, WI

<http://www.msidata.com/products/reads> [Retrieved on 07/16/2009]

18. Xriver Technologies LLC (2008). “Appraisal, Acquisition, & Relocation System

(AARS)”, United States

<http://www.xrivertech.com/Common/CaseStudies/CaseStudy_AARS.PDF>

19. Oregon Department of Transportation (2006) “Right of Way Data Management System

(RWDMS)” ODOT Surveyors Conference.

<http://oregonwatertrails.org/ODOT/HWY/GEOMETRONICS/docs/RWDMS.pdf>


Excellence in Right-of-Way Awards”. Washington, DC.

<http://www.fhwa.dot.gov/REALESTATE/rowea.htm>

21. Bentley Systems Inc. “Bentley Right Of Way Office For The Web”,

<ftp://ftp2.bentley.com/dist/collateral/Bentley_20Right_20of_20Way_20for_20the_20W

eb_20Spec_20Sheet_2C_20Low_20Respdflo.pdf> [Retrieved on 08/06/09]

22. “Office of Real Estate Services – Newsletter”, Federal Highway Administration, Issue

2009. <http://www.fhwa.dot.gov/realestate/newsletter/second2009.pdf> [Retrieved on

08/06/09]

23. “NDOT Integrated Right of Way Information Network (IRWIN) Phases 1 and 2”, ITIS,

Inc. <http://itis-corp1.com/index.php?page=irwin-phase-2> [Retrieved on 08/06/09]

24. Gravley R. (2008). “ALDOT's Comprehensive Project Management System (CPMS)”,

Southern States and Federal Transportation Finance Conference, Alabama.

25. Kaan, Ozbay and Nebahat, Noyan. (2003). “Geographical Information System Based

Management Information System (GISMIS)”. 82nd Transportation Research Record,

January 2003. Washington DC.

26. Office of Real Estate Services. (2004a). “Outdoor Advertising-State Study, State of

Florida Outdoor Advertising – Automated Data Gathering System, A Case Study.”

United States, Federal Highway Administration, Florida

<http://www.fhwa.dot.gov/REALESTATE/oacases/casefl.htm>

http://www.msidata.com/products/reads

http://www.xrivertech.com/Common/CaseStudies/CaseStudy_AARS.PDF

http://oregonwatertrails.org/ODOT/HWY/GEOMETRONICS/docs/RWDMS.pdf

http://www.fhwa.dot.gov/REALESTATE/rowea.htm



http://www.fhwa.dot.gov/realestate/newsletter/second2009.pdf

http://itis-corp1.com/index.php?page=irwin-phase-2

http://www.fhwa.dot.gov/REALESTATE/oacases/casefl.htm

107

27. Federal Highway Administration. (2004), “GIS in Right of Way Scan, Tallahassee,

Florida,” July 2004. Washington, DC.

<http://www.fhwa.dot.gov/realestate/scans/talafreport.htm>

28. Petyon, L., Mississippi Department of Transportation. (2002). “ROW Parcel Tracking

System Detailed requirements/Functional design document.” United States,

Subcommittee on Right-of-Way and Utilities (AASTHO), Exhibit H, Mississippi.

29. “Land & Right of Way Acquisition Management and Record Keeping”, Diversified

Energy Software Solutions (DESS) LLC.

<http://www.desoftsol.com/solutions/AMS.html> [Retrieved on 08/06/09]

30. “Paecetrak : Right-of-Way Acquisition Support System (Version 4.0)”, BEM Systems,

Inc. <www.bemcorp.net/webcop/paecetrakweb/web/Brochure.pdf> [Retrieved on

08/06/09]

31. “DREAMaps for Real Property Intelligence”, Smart Data Strategies, Inc.

<http://www.sds-inc.com/products.htm#> [Retrieved on 08/06/09]

32. Ambler, S. W. (2004). “The Object Primer 3rd Edition: Agile Model Driven

Development With UML 2”. New York: Cambridge University Press. Retrieved From :

<http://www.Agilemodeling.Com/Artifacts/>

http://www.fhwa.dot.gov/realestate/scans/talafreport.htm

http://www.desoftsol.com/solutions/AMS.html

http://www.bemcorp.net/webcop/paecetrakweb/web/Brochure.pdf

http://www.sds-inc.com/products.htm

http://www.agilemodeling.com/Artifacts/%3e

108

Appendix A:

Summary of Right-of-Way Information/Content Management Systems

by State

Standalone

Individual

Systems

Small

Enterprise

Systems

Large Enterprise

Systems

Integrated

Systems

Alabama

Provides access to extensive project and

financial information by integrating to other

external systems [24]

Comprehensive

Project

Management

System (CPMS)

None

(i) ROW forms a subsystem of CPMS (ii) Includes 6 major

processes : Project Status, ROW Mapping, Appraisal

Status, Acquisition, Relocation ,Leased Property (iii) Includes

comprehensive reporting

Alaska --

Arizona --

In house system using access databases,

excel spreadsheets and Microsoft word

document templates [9]

Yes

Currently none

but in the

process of

integration

(i) Templates for acquisition activities alone (ii) Web based

system in the process of development

A geospatially-referenced cadastral

mapping system for Arkansas in

cooperation with the Arkansas

Assessment Coordination Department

(AACD), the Arkansas Geographic

Information Office (AGIO), and

participating counties [12]

County

Assessors

Mapping

Program

(CAMP)

Yes (i) A two-phased project with phase one completed that

used centroids to upload parcel data

California

A web-based user interface java

application with a secure centralized

database and standard input/output

that has been developed in-house by

Caltrans to facilitate planning and

management of highway projects and

parcel acquisition [12]

Right of Way

Management

Information

System (ROWMIS)

Plans to

integrate in

future

(i) Contains project, parcel and acquisition information

(ii) Plans to develop: a forms generation capability for

ROWMIS, add utilities, railroad, and relinquishment

information to the database, and further enhance

information regarding condemnation, estimating,

structures, and relocation assistance modules

Colorado --

Connecticut

ROW files are created and tracked

using Oracle database with an intranet

based Project Management system that

has been developed internally [15]

Image Records

Management

System (IRMS)

Plans to

upgrade with

GIS integration

and internet

access to

general public

in future

(i) System deals with Document Management alone for

the related ROW documents and maps

Delaware --

District of Columbia --

Uses a web-based application

developed internally that includes

modules for recording and tracking all

the Right of Way activities using DB/2

[27]

Right of Way

Management System

(RWMS)

Has capability

for integration.

But currently

none

(i) Application covers various aspects like Acquisition,

Eminent Domain, Relocation, Property Management,

Business Damages, Contracting, Appraisal, Cost

Estimating and Funds Management (ii) Uses

Hummingbird DM product for electronic content

management and currently no Electronic Document

Management System is integrated within

A client/server application written in

VB6 utilizing an ORACLE database that

has been created specifically for the

regulation of outdoor advertising signs.

[26]

Outdoor Advertising

Inventory

Management System

(ODAIMS)

Yes (i) Utilizes Microsoft-s MapPoint Application for viewing

sign locations on a map

Name and Category of the SystemCurrent state of RoW activity

management system ( Brief

Description)

Systems across various State DOTs

Geospatial

CapabilitiesAdditional Information

State /

Organization

Arkansas

Florida

109

sambank

Text Box

*Italicized systems interact with GIS or have an integrated geosptial capability at present or under consideration for implementaitonin in the near future

Kavya

Sticky Note

MigrationConfirmed set by Kavya

Kavya

Sticky Note

Accepted set by Kavya

Standalone

Individual

Systems

Small

Enterprise

Systems

Large Enterprise

Systems

Integrated

Systems



Description)

Geospatial


State /

Organization

Georgia

To track the project activity from concept to

construction with ROW managing specific

parcel data and progress for each project in

their work program [2]

Project Information

System (Tpro)None

(i) Shares and tracks project data between various offices

across the state.

Hawaii --

IdahoUses an in-house system utilizing Access

database [11]

Illinois

A geospatially enabled information

management system to assist in

managing the ROW process [6, 14]

Aeronautical Land

Acquisition System

(ALAS)

Yes

(i) Provides oversight of real estate acquisition and

property management of a large complex airport project

(ii) Electronic file cabinet allows users to scan and link

documents to related parcels

Indiana

Contains database of all land records for

use in its Property Management function.

[8]

Land Record System

(LRS)None

(i) Tracks project and parcel activities in the database of all

land records.

Iowa --

Kansas --

Kentucky --

Louisiana

Uses a web-based intranet/internet

application using Oracle database that

was designed by Xybernaut Solutions

LLC [9, 18]

Appraisal,

Acquisition, and

Relocation System

(AARS)

In progress

(i) Includes detailed appraisal, acquisition, and

relocation workflow processing needs as defined by the

DOTD Real Estate Section.

MaineBeing developed by bearing point (KPMG)

[11]

Realty Management

System (RMS)None

(i) A proposed database to better manage the myriad

of data created in the right of way/property process

Uses a Visual Basic .net application using

Oracle database to handle the acquisition

activities in the state [9,10]

Office of Real Estate

Management system

(OREMS)

None

(i) For acquisition activities alone (ii) Uses Crystal Reports

software exclusively and not integrated (iii) Web based

system in the process of development

Standalone system that includes

scanned images of property maps and

digitized parcel centroids which link

each property to the State Department

of Assessments and Taxation’s parcel

database [6]

MdProperty View GIS for viewing(i) System is used to obtain parcel information for the

acquisition of right of way for transportation projects.

Massachusetts --

Michigan

ROW activities are maintained and tracked

using a comprehensive oracle based

system that features immediate updation of

reports, schedules etc [16]

Real Estate

Management

Information System

(REMIS)

None

(i) Maintains project/job data, parcel data, tracks

payments/all costs and includes detailed reports (ii) Ease of

access to data through organized folders within the system

like job folder, parcel folder, relocation folder, condemnation

folder etc

Minnesota

Web-based, online, statewide system to

support all right of way acquisition and

land management functions that allows

users to quickly access and search

ROW information, visualize and track

parcel geometry, and customize and

generate ROW reports [12]

Right-of-Way

Electronic

Acquisition Land

Management

System(REALMS)

planned to

spatially-enable

the digital

parcels by

linking ROW

maps to an

ArcGIS server

(REALMSMaps

(i) used VB.NET in conjunction with Oracle to modify

RUMS to meet Mn/DOT's business needs (ii) REALMS

deals with acquisition, management, and disposal of

real estate & also offers legal descriptions and property

appraisal information for the electronic parcel files.(iii)

Converting ROW maps into standardized digital parcels

to make REALMS spatially-enabled : provide a spatial

view of the data housed in the system

Maryland

110

sambank

Text Box


Standalone

Individual

Systems

Small

Enterprise

Systems

Large Enterprise

Systems

Integrated

Systems



Description)

Geospatial


State /

Organization

MississippiSQL based (might have been converted

to Oracle database) [28]

Right of Way Parcel

Tracking System

(PTS)

Plans to

interface with

GIS application

(i) Manages information flow of the full range of right-of-

way activities that include title, parcel deed,

development, appraisal, negotiation/acquisition,

relocation, utility relocation, eminent domain,

hazardous material sites and improvements

Uses a Lotus Notes based acquisition

information system to document the

acquisition information [9]

Right of Way Parcel

Acquisition databaseNone

(i) Deals with acquisition process alone (ii) The system would

be embedded into the recently developed web based Realty

Asset Inventory system to manage the realty assets of the

department efficiently.

Statewide, computerized, relational

database that allows staff to identify all

the DOT's realty assets and assists in

identifying properties that are no longer

needed for highway purposes [12, 14]

Realty Asset

Inventory

Management

System (RAI)

Process of

enhancing

(i) Houses documentation on all sales, leases, and

excess properties, as well as references to other realty

of interest, such as environmental, cultural, historical,

and wetland mitigation sites

Montana --

Nebraska

Uses a Lotus based underlying system that

interfaces with DB2 and micro-station

systems. [11]

Automated Right-of-

Way Management

System (ARMS)

None currently

(i) Sub-systems deal with much of the appraisal and some of

the negotiations (ii) Does not include relocation, property

management or ROW Management (iii) Has project tracking

data, document generation capability

Nevada

Designed (by Smart Data Strategies) to

implement a modern property inventory

management system which supports

inventory, access, retrieval and

management reporting of all DOT right

of-way property [22, 23]

Integrated

Right-of-Way

Information

Network

(IRWIN)

Yes

(i) Integrate with NDOT's GIS, Public Lands Survey

System data, and video logging system, electronic

document management system and NDOT's Integrated

Financial System (ii) Allow users to track work

processes and access stored documents from a

centralized information center; (iii) Deals only with

Property acquisition and property management module

but lacks appraisal and relocation module

New Hampshire --

New Jersey

System integrates the digitized

document database with a GIS based

highway database of digital roadway

plans and ROW maps [25]

Geographical

Information System

based Management

Information System

(GISMIS)

Yes

(i) For effective management and retrieval of requested

documents from a very large scanned digital document

database

New MexicoGeospatial information system for

mapping [6]

Non-Right of Way

(NRW) Parcel &

Improvement

Inventory system

Yes

(i) Used for land engineering bureau (iI) System enables

automated generation of NRW Parcel and Improvement

Inventory summary sheets along with the capability of

geospatial view of parcel locations.

New York

In-house system developed is specifically

used to track payments and generate the

pay packages. [9

Q & A (Symantec)

productNone

(i) Would be enhanced to web based with an electronic

document storage capability (ii) The system is tied to other

processes like Design, Planning and ROW Mapping

North Carolina --

North DakotaUses Access Database integrated with

FileNet (that stores ROW files) [9]

Record Information

Management System

(RIM)

None (i) Consists multiple databases

Ohio --

Oklahoma --

Missouri

111

sambank

Text Box


Standalone

Individual

Systems

Small

Enterprise

Systems

Large Enterprise

Systems

Integrated

Systems



Description)

Geospatial


State /

Organization

Enterprise content management initiative

for the right of way project processes [19,

20]

Right of Way Data

Management System

(RWDMS)

(i) Handles critical data storage, task assignments and

tracking, automated production of all acquisition and

relocation forms, and production of needed management

performance reports (ii) Being considered for its automation

of the acquisition process, such as appraisal, negotiation

and the title/closing processes.

Application enables access to the ROW

data regarding each parcel [12]

FileNet Enterprise

Content

Management (ECM)

Yes

(i) DOT is expecting that the legal description creation

process and the appraisal description process will be

automated next, after which relocation, condemnation,

acquisition activities are anticipated to be moved into

the system

Pennsylvania

State wide system that helped in

standardizing all the property information

into a single electronic case folder for each

land parcel [6,21]

Right of Way Office

Information System None

(i) Incorporates innovative data-integration capabilities and

supports Right-of-Way appraisal, negotiation, relocation, and

property management

Puerto Rico --

Rhode Island --

South Carolina

Uses a mainframe computer database with

Oracle, some in Sequel Server and Access

Data bases with an integrated Microsoft

SharePoint document repository to

manage ROW acquisition activities [9, 11]

Software AG Entire

ConnectionCurrently none (i) Acquisition alone

South Dakota

In-house system developed is specifically

used to track payments and generate the

pay packages. [11]

AgWare

Tennessee --

Texas SQl server based system [11]

Right-of-Way

Information System

(ROWIS)

None(i) Captures data related to project setup, mapping, funding,

appraisal, negotiations and eminent domain

Utah

Uses a system with Oracle database that

has been designed in conjunction with

Project Management software custom

written for UDOT [9]

In-house system None(i) Uses Hummingbird DM product for electronic content

management

Vermont --

Virginia

Web based system that runs on an Oracle

database that helps to track the acquisition

process on a project-by-project basis [6]

Right-of-Way Utility

Management System

(RUMS)

None

(i) Supports the right of way and utilities business from the

estimate stage through condemnation by tracking

evaluations, negotiations, legal functions, the relocation of

families and businesses, the disposition of improvements,

the execution of utility easement agreements, and the

relocation of utility facilities. It is also used in the

management and disposition of surplus/residue properties

and in managing consultant contracts. (ii) System includes

powerful document management features

Washington

Web based Commercial off the shelf

system (developed by Smart Data

Strategies) [12]

Real Estate

Map

Information

System

(REMIS)/

Integrated

Realty

Information

System (IRIS)

GIS portion is

being

developed

(i) Supports ad-hoc reporting tool (ii) Includes

information about acquisitions, relocation and property

management activities (iii) Integrates external systems

like WSDOTs financial management system etc, for

advanced management workflow and reporting

capabilities

West Virginia --

Oregon

112

sambank

Text Box


Standalone

Individual

Systems

Small

Enterprise

Systems

Large Enterprise

Systems

Integrated

Systems



Description)

Geospatial


State /

Organization

Wisconsin

A automated software solution with tracking

and production system that streamlines,

organizes, and simplifies daily

Highways/Real Estate operations [17]

Real Estate

Automated Data

System (READS)

None

(i) Any piece of data can be merged throughout various

reports, letters, and documents, to reduce process time.(ii)

Allows extensive data tracking, analysis, reporting, and

document generation for all aspects of Highways/Real

Estate operation from start to finish. (iii) Covers acquisition,

lands inventory, cost estimation, reporting, litigation,

accounting, property management, appraisals, relocation,

deeds

Statewide database/application to reduce

the time and resources required to identify,

track, and manage correspondence

between the necessary parties during the

lifetime of the highway project, in

accordance with the WisDOT Guide to

Utility Coordination.[12]

Transportation Utility

Management System

(TUMS)

None

Web portal that brings together diverse

information to deal with all questions

related to driveway permits and land

division reviews. [12]

Highway Access

Management

System (HAMS)

Yes

(i) Combines the capabilities of several components

into one spatially driven web interface, enabling

straightforward interaction between end-users and the

system

Wyoming --

AASHTO/BEM

(Balanced

Environmental

Management)

Systems

Developed in cooperation with AASHTO

and the Turbo Relocation Task Force to

assist their users in determining and

calculating the relocation assistance

benefits that displaced residents and

businesses are entitled to under the

Uniform Relocation Act [13]

Turbo Relocation

Diversified

Energy Software

Solutions (DESS)

The DESS AMS is a secure systematic

application that will streamline the

entire life-cycle of the land and right of

way acquisition process, and provide

acquisition & property information more

rapidly [29]

Land and Right-of-

Way Acquisition

Management &

Record Keeping

(i) Covers the following ROW areas: Agent Daily Report

Logs; Documents & Digital Content; Agent-Owner

Contact Diaries; Court Orders; Tract Financials; Project

Financials

On-Demand Reporting; GIS Map Integration; Special

Provisions; Owner Contact Records; Condemnation;

Tie Plats; Title Opinions; Negotiations; On-Demand

Searching; Personnel Task Tracking

Smart Data

Strategies

The web-based, GIS-enabled

commercial off the shelf application for

Right-of-Way Management that has a

modular architecture allowing seamless

integration by wrapping around existing

workflows with web and desktop

platform compatibility, web browser

support, and product security. [31]

DREAMaps(i) Uses an enterprise approach and is built upon core

ESRI GIS technology

BEM Systems Inc

Web-based, GIS enabled application

developed to manage the complicated

process of acquiring properties

for transportation system right-of-way

for NJTransit capital programs [30]

Paecetrak

(i) The system is used as a project management tool to

track the acquisition process, beginning with the

initial identification of a potential right-of-way alignment

through parcel selection, title search, appraisal,

environmental remediation cost estimate preparation,

the offer to acquire, and potential condemnation

proceedings.


Off the shelf systems

Wisconsin

113

114

Appendix B:

Right-of-Way Business Process Diagrams

PROPERTY/ASSET MANAGEMENT

RELOCATIONACQUISITION

Establish project through programming

TIP/STIP

Project Management and Internal Auditing:Billing and Reimbursement

Functional Monitoring and SeparationFederal, State, and Local Liaison

Risk ManagementRecords Management and Retention

Adherence to Uniform Act and other Federal Statutes

Process Payment

Identify project staff

Select alignments

Authorize project

ROW

Accumulate and store records

No

Close accounting

ROW Engineering and Mapping

Relocation and Replacement Properties Surveys

Analysis of Current Government Displacements

Analysis of Relocation Problems

Perform environmental

studies &hazardous waste sites evaluation

Field Survey of SitesState Environmental Agency InvolvementLegal Involvement

Acquire Title Assurances

Realignment Needed?

CORRIDOR MANAGEMENT

Status Report

Utilities Involved?

UTILITY RELOCATION & MANAGEMENT

PLANNING

Identify parcels

Identify environmental

impacts

Estimate acquisition costs

Estimate relocation costs

Select final alignment

Perform ROW Cost Analysis

Identify parcels

No

Yes

General Information Notice / Project Authorization Date

Project Agreement Contract

ROW Plans

OVERALL PROCESS FLOW

No

Yes

APPRAISAL

Excess

Perform encroachment clearing

Encroachments? Yes

Add Excess to inventory

Outstanding Condemnations

Set up “take up” project or other state-defined process

No

Yes

Submit final claims for payment

Re-open project to pay costs

OUTDOOR ADVERTISING

Certify completion of ROW activities

Perform new hires or initiate contracts

Review final project plans

CONSTRUCTIONRight-of-Way Certification

Parcel Records

Project Documents

ROW Plans

Displaced Persons Records

Acquisition payments to owners

Relocation payments to displaced entities

FHWA payments to agency

Other project costs (includes staff time)

Record Tracking

Financial Tracking

Area included in this project

Area outside this project

Process to be included

Process that can be geospatially enabled

Required Document

Local Project with Federal Aid

Define parcel typeDivide parcel to ROW/

uneconomic remnant, etc

Agency/contract Personnel Tracking

Property Dispostition

Modified:09/09/09

Process that is state specific

Activity to be included

Identify Hardship and Initiate Protective Buying (If necessary)

Encumber Funds

Revenue

Other Information

Systems

Financial

Project

FHWA Reporting

Facilities

Local Government Systems

Geospatial Warehouse

Document Management

System

MLS (External Real Estate System)


Federal Land Management

System

Excess Land Management

System

Environmental System

Inverse Condemnation

115

kavyas

Text Box

Figure B1: Process flow diagram for Overall Right-of-Way business

APPRAISALDefine parcel

Initial Parcel Review for Value / Complexity

Appraiser

Contract Appraiser

Type

Contract Staff

Appraisal request

Low value appraisal

Minimum payment method

No

Yes

Waiver

Contact ownerVisit property

with owner

Inspect property

Evaluate property

No

Yes

Appraisal

Determine appraisal technique

Appraisal technique

type

Cost approach

Sales comparison

Income approach

type

State specific

Short appraisal

Value-finding appraisal

MinimumStandardsAppraisal

DetailedAppraisal

Specialty appraisal

Assign Appraiser

Assign Appraiser

Contract Appraiser

Contract Staff

Assign Appraiser

Yes

Specialty Appraisal

No

Prepare Appraisal Report/Certificate

Appraisal Certificate

Appraisal Reviewer

Contract Reviewer

Contract Staff

Assign Reviewer

Perform Appraisal Review

Accept appraisal

Deficient appraisal

Prepare Review Appraisal Certificate

Review Appraisal Certificate

Yes

No

Establish Just Compensation

Approved Just Compensation

Donation

ACQUISITION

Modified:March, 2010

Value Donation

To Acquisition

Link to Appraisal System

LEGEND



Process that can be geospatially enabled


Required Document



116

kavyas

Text Box

Figure B2: Process flow diagram for business functional area of Appraisal

Mail Written Offer, Summary

Statement, deed/option form,

plat, brochure

Accept offer? No

Contract with third

party (negotiator)

Assign agency

official

Payment before

Possession

Yes

Documentation

Requirements

Obtain property

encumbrance releases

Prepare Settlement

Statement and Deed

Pay Just Compensation

Acquisition

type?Purchase

Process

Donation

Donations

Process

Dedication

Dedications

PRE-NEGOTIATION

NEGOTIATIONS

Prepare Conveyance

Documents

Prepare Notices

Coordinate with other

offices

Negotiation

commencementFirst offer by mail/

Accelerated negotiations

Personal contact

negotiations

Schedule meeting

Submit Written Offer,

Summary Statement, deed/

option form, plat, brochure

Negotiation

optionsAdministrative

Settlement

Establish

Administrative

Settlement amount

Alternate Dispute

Resolution (ADR)

Establish settlement

amount

State defined

alternative

State specific

alternative

Negotiate?

Yes

No

Legal/

Condemnation

state specific

activity

Accept offer?

Yes

No

Prepare updated

Conveyance Documents

Prepare updated

Conveyance Documents

Uneconomic

remnant?

Yes

Document and end

negotiations

No

Additional

factors?

No

Yes

Assessments

Functional Replacement

Inverse Condemnation

Tenant-owned Improvements

Owner Retention of

Improvements

Hardship and Protective Buying

CLOSING

Process documents:

tax forms, titles, etc

For each parcel/

remnant

Follow up by phone

contact

Schedule meeting and

present updated offer

RELOCATION

PROPERTY

MANAGEMENT

Revised offers

Status reports

Activity reports

Negotiator

Contract Negotiator

Contract Staff

Assign Negotiator

PROPERTY

MANAGEMENT

Prepare Conveyance

Documents

Updated:

March 2010ACQUISITION

Updated through

process

LEGEND



Process that can be geospatially

enabled


Required Document



117

kavyas

Text Box

Figure B3: Process flow diagram for business functional area of Acquisition

Initiate Relocation

General Information

Notice

Notice of Relocation

Eligibility

Comparable Dwelling

Notification

Ninety-Day Notice

(with 30-day Specific

Notice if req’d)

Require Site

Office?Open Site OfficeYes

Certified Lawful

Presence in US?Hardship?

Persons occupying

real property to be

acquired

Type of

Relocation?

Identify Parcels for

Relocation

Identify available Properties for Sale and

Lease, Community Amenities

Candidate Inventory

for Displaced Persons

Perform Decent, Safe, Sanitary

(DSS) Inspection

Inventory of Parcels with

persons to be displaced

1stDSS Inspection

Report

Offer Replacement Housing

Options

Require transportation

Determine if displacement exists:

(occupant eligibility for services)

Persons occupying

adjacent property

(Advisory Services

only)

Persons who move

because non-

residential property

is being acquired

Occupants who

rent DOT-owned

property prior to

construction

No No

Yes Yes Yes

Link to MLS/rental (External Real

Estate System)

Explain services,

available payments, and

eligibility requirements

Determine eligibility for

each type of payment

Determine occupant

needs

Estimate Relocation

Assistance Payments

Provide advisory assistance:

Information on Federal and state programs

Assistance with all claim forms

Identify available comparable

replacement housing

Comparable

replacement housing

available

Residential

Perform Last Resort Housing

PlanningNo

Transport to offered

replacement housingYes

Select replacement

housing

No

Perform 2nd DSS Inspection

prior to purchase/rent

2ndDSS Inspection

Report

Yes

No

Personal

property only Non-Residential

No

No

Yes

No

Yes

Yes

No

Link to TurboRelocation

Relocation Survey

No

Relocation Services

Relocation Planning

Modified

March 2010

Conduct personal interview

Eligible for

relocation

assistance

Yes

No

Planning Dept

RELOCATION

Yes

Match Line

LEGEND




enabled


Required Document



118

kavyas

Text Box

Figure B4: Process flow diagram for business functional area of Relocation

Type of RHP

Calculate RHP for

Homeowner of at least

180 days

Calculate RHP for tenant

of less than 90 days

Review Special Circumstances

Pay RHP

Replacement

Housing Available?

Exceeds

payment limits?

Calculate Actual Cost

Payment for Move

If required, calculate:

Alternate Actual Payment:

Loss of Tangible Property or

Substitute Equipment

Calculate Fixed In-lieu

Payment

Calculate Re-establishment

Expense Payment

Type of

relocation

Payment?

Calculate Last Resort Housing

Payment

Moving Expense

Type?

Owner in Mobile HomeOwner Not Occupant of

Mobile HomeTenant in Mobile Home

Determination:

Realty vs. Personal Goods

Mobile Home vs. Site

Owner vs. Tenant

Calculate Moving Expense Payment

Special

Circumstances

Exist

Calculate occupancy

Appeal RHPRespond to

appeal

Relocation Assistance

Payments

Type of

Relocation?Non-residential

Mobile Home

Eligible

for moving

expenses

Yes

Residence (not mobile home)

Calculate Moving Expense Payment

Eligible

for replacement

housing payment

(RHP)

No

No Yes

Yes

Yes

No

No

Yes

No

Yes

Process claim and tax-related

forms

Link to TurboRelocation

No

Eligible

for Fixed In-

Lieu?

Yes

No

Calculate RHP for

Homeowner or tenant of 90-

179 days

Pay Moving Expense payment Pay Moving Expense payment

LEGEND




enabled


Required Document



Match Line

119

kavyas

Text Box

Figure B4: Process flow diagram for business functional area of Relocation (Cont.)

PROPERTY

MANAGEMENTRequirement type

Property

disposition

Personal

Property

Agency

RetentionSale Clearance

Personal

Property

Rental

Prepare

Maintenance

Agreement

Establish rental

rates

Select tenant

Prepare lease

agreement

Relocation

Appraisal

Improvements

Improvements

Owner

Retention

Sale State

specific use

Clearance /

Demolition

Grading

CONSTRUCTION

Property disposition

Justification

State specific rules

Marketing

Parcel Sale

Excess

DisposalSale ExcessDisposal

ROW

JustificationAirspace

Marketing

Highway

Maintenance

Highwy Access

Management

ROW Leasing

No

Relinquishment

ROW Disposal

Access Disposal

Yes

Add to excess

lands

Security inspections

Rodent control

Hazardous

Materials

Pre-construction

During

construction

Post-construction

Manage excess

lands

Udated:

03/2010

Coordinate with

other offices

Acquisition

LEGEND




enabled


Required Document



120

kavyas

Text Box

Figure B5: Process flow diagram for business functional area of Property Management

121

Appendix C:

UML Diagram Documentation

122

Appendix C1:

High level UML Diagrams for Overall right-of-way logical

model

123

Model Overview

Figure: C1-1

124

Business Process Diagram - Overall ROW - (Analysis diagram)

Business process diagram for a ROW Project

Figure: C1- 2

Use Case Diagram - Overall ROW - (Package diagram)

Use case model for the overall ROW Project

Figure: C1-3

125

Class Diagram - Overall ROW - (Logical diagram)

Figure: C1-4

Component Diagram - Overall ROW - (Component diagram)

Figure: C1-5

126

Business Process Model - Overall ROW - (Logical diagram)

Figure: C1-6

127

Project Development Activity Model - (Activity diagram)

Figure: C1-7

act Project Dev elopment Activ ity Model

Project Establishment Initial Planning

Project Authorization

ROW Mapping and

Engineering

Utilities

involved?

Staff Identification

Encumber Funds

Project Agreement /

Contract Application

Utility Relocation and

Management

Parcel Identification &

Cost Estimation

Realignment

Necessary?Title Documents

Identification of Parcel

Type

Parcel TypeGeospatial

Parcel Layer

ROW Plans

Early Acquisition

(Protectiv e Buying)Hardship?

FHWA

State DOT

Mapping Personnel

ROW Director

Project Agreement

ROW Director

(from Human Actors)

Mapping Personnel

(from Human Actors)

State DOT

(from Agency Actors)

FHWA


(from Project Development Package)

Project

Establishment


Initial Planning


Protectiv e Buying


Project Authorization


Project Agreement


Encumber Funds(from Project Development Package)

ROW Mapping and

Engineering


Utility Relocation

and Management


Staff Identification


Parcel Identification &

Cost Estimation


Title Documents


Identification of

Parcel Type


Geospatial

Enablement Acquisition Agency


Acquisition

Agency(GLOBAL)(from APP_Business Process Model Packag)

Project Manager

Project Manager

(from Human Actors)

«extend»

«extend»

«extend»«refine»

No

«extend»

Yes

Yes

<<implement>>

<<implement>>

<<implement>>

<<implement>>

«representation»

<<Impement>>

<<implement>>

«extend» «extend»

«extend»

Yes No

128

Major ROW Functions Activity Model - (Activity diagram)

Figure: C1- 8

act Major ROW Functions Activ ity Model

Appraisal (APP)

Acquisition (ACQ) Relocation (REL)

Property

Management (PM)

Payment

Corridor

Management

(from Major ROW Functions Package)

Appraisal (APP)


Acquistion (ACQ)


Relocation (REL)


Property Management

(PM)


Payment


Corridor

Management

ROW DirectorProject Manager

Project Manager

(from Human Actors) ROW Director

(from Human Actors)

«extend»

«extend»

<<Impement>><<implement>>

«precedes»

«precedes»

«extend»

«extend»

«extend»«extend»

129

Project Closing - (Activity diagram)

Figure: C1-9

act Project Closing

Rev iew Project

Plans

Property

Disposition?Excess PropertyUpdate Excess to

Inv entoryEncroachments?

Encroachment

clearing

ROW Certification Status Report

Accumulate and

Store Records

ROW CertificateConstruction

Final Claims

Close Accounting

State defined

Processes

Outstanding

Condemnation?

Re-open if necessary

(from Project Closing Package)

Rev iew Project

Plans


Excess Property


Geospatial

Enablement-Update

Excess to Inv entory


Encroachment

clearing


ROW Certification(from Project Closing Package)

Construction


Accumulate and

Store Records


Status Report


State defined

Processes


Final Claims


Close Accounting


Re-open if necessary

Geospatial Data -

Parcels, Roads,

Right-of-Way

Acquisition Agency


Acquisition

Agency(GLOBAL)(from APP_Business Process Model Packag)

FHWA

FHWA


No

no

yes

<<implement>>

«extend»«extend»«extend»

«extend»

«precedes»

Yes

«extend»

«extend»

<<implement>>

130

Appraisal Activity Model - (Activity diagram)

Figure: C1- 10

131

APP_Appraisal - (Activity diagram)

Figure: C1-11

act APP_Appraisal

APP_Approv ed

Just Compensation

Acquisition

Agency(GLOBAL) Geospatial Data - Parcels,

Right-of-Way

Appraisal

Type-Donation?

APP_Value Donation APP_Appraisal

ProcessAPP_Waiv er

APP_Establish Just

Compensation

APP_Initial Rev iew

Acquisition Agency


(from APP_Use Case Model Package)

APP_Geosaptial

Enablement : Parcel,

Right Of Way


APP_Initial Rev iew


APP_Donation


APP_Appraisal

Process


APP_Establish Just

Compensation


APP_Waiv er

Staff

Appraiser

available?

APP_Assign Appraiser APP_Contract

Appraiser


APP_Assign

Appraiser (from APP_Use Case Model Package)

APP_Contract

Appraiser

Appraiser


APP_Appraisal

ReportA

APP_Appraiser

Certificate

APP_Inv entory - Parcel

for Appraisal

APP_Appraiser

Certificate

APP_Appraisal Rev iew


APP_Appraisal

Rev iew

APP_Parcel for

Appraisal


APP_Appraiser

Certificate

Waiver?APP_Appraiser

<<implement>>

<<implement>>

Yes

<<implement>>

implements

No

<<implement>>

Yes

<<implement>>

implements

<<implement>>

<<implements>>

No

«flow»

Yes

<<implements>>

«flow»

No

132

Acquisition Activity Model - (Activity diagram)

Figure: C1-12

133

ACQ_Pre-negotiation Activity - (Activity diagram)

Figure: C1-13

act ACQ_Pre-negotiation Activ ity

Federal

Land?

ACQ_Process

Dedication ACQ_Process

Donation

ACQ_Update Parcel

Record

ACQ_Start Closing

Process

ACQ_Prepare Notices

Additional

Factors?

ACQ_Start Negotiation

Process

ACQ_Prepare

Conv eyance

Documents

ACQ_Coordinate with

Other Offices

ACQ_Additional

Factors for

Consideration and

Processing

Acquiring Agency

(from ACQ_Pre-negotiation Package)

ACQ_Process

Dedication


ACQ_Process

Donation


ACQ_Update Parcel

Record


ACQ_Prepare

Conv eyance

Documents


ACQ_Prepare Notices


ACQ_Coordinate with

Other Offices


ACQ_Additional

Factors for

Consideration and

Processing

Acquiring Agency

(from Acquisition Model Package)

ACQ_Transfer

Federal Lands

(DOD, DVA, BIA)


ACQ_Transfer

Federal Lands (DOD,

DVA, BIA)

Negotiator

type?

ACQ_Contract

Negotiator

ACQ_Assign

Negotiator

ACQ_Prepare

Conv eyance

Documents


ACQ_Contract

Negotiator


ACQ_Assign

Negotiator

Dedication? Donation?

Status/Activ ity

Reports

Yes

<<implement>>

«precedes»

«precedes»

«precedes»

Federal Land Transfer

Purchase

<<implement>>

<<implement>>

«precedes»

No

<<implement>>

Dedication

Donation


<<implement>>

<<implement>>

No

<<implement>>

<<implement>>

No

134

ACQ_Negotiation Activity - (Activity diagram)

Figure: C1-14

act ACQ_Negotiation Activ ity

Accelerated

Negotiations

applicable?

ACQ_Mail Written Offer

and Acquisition Related

Documents

ACQ_Follow up by

Phone Contact

ACQ_Schedule Meeting

ACQ_Prov ide Written

Offer and Acquisition

Related Documents

ACQ_Prepare

Documents and Update

Parcel Records

Accept

Offer?

Relocation

Involved?

ACQ_Start Closing

Process

Uneconomic

Remnant?

ACQ_Document and End

Negotiation

Owner

Negotiator

ACQ_Attach Negotiator

Log

ACQ_Detailed

Negotiation Process

ACQ_Update Parcel

Records

Acquiring Agency

(from ACQ_Negotiation Package)

ACQ_Prepare

Documents and

Update Parcel

Records


ACQ_Mail Written Offer

and Acquisition Related

Documents


ACQ_Follow up

Phone Contact


ACQ_Schedule

Meeting


ACQ_Prov ide Written

Offer and Acquisition

Related Documents


ACQ_Update Parcel

Record


ACQ_Document and

End Negotiation


ACQ_Attach

Negotiator's Log


ACQ_Detailed

Negotiation Process

Owner


Negotiator


Acquiring Agency


ACQ_Obtain Property

Encumbrance releases


ACQ_Obtain Property

Encumbrance releases

ACQ_Accelerated

Negotiations/negotiations

by Mail

ACQ_Commencement of

personal contact

negotiations

<<implement>>

«precedes»

«precedes»

<<implement>>

No

<<implement>>

«precedes»

«precedes»

<<implement>>

«precedes»

«precedes»

«precedes»

«precedes»

«precedes»

<<implement>>

<<implement>>

Yes

<<implement>>

<<implement>>

No

Yes

<<implement>>

<<implement>>

Yes

<<implement>>

<<implement>>

Yes

No

No

<<implement>>

135

ACQ_Closing Activity - (Activity diagram)

Figure: C1- 15

act ACQ_Closing Activ ity

ACQ_Prepare

Settlement Statement

and Deed

ACQ_Update Acquisition

Record for the Acquired

Parcel

ACQ_Pay Just

Compensation

ACQ_Process

Documents: Tax Forms,

Titles, etc

PM_Property

Management

Acquiring Agency

(from ACQ_Closing Package)

ACQ_Prepare

Settlement Statement

and Deed


ACQ_Update

Acquisition Record

for the Acquired

Parcel


ACQ_Pay Just

Compensation


ACQ_Process

Documents: Tax

Forms, Titles, etc

Acquiring Agency


«precedes»

«precedes»

«precedes»


<<implement>>

<<implement>>

<<implement>>

«flow»

136

Relocation Activity Model - (Activity diagram)

Figure: C1- 16

137

REL_Relocation Planning Activity - (Activity diagram)

Figure: C1-17

act REL_Relocation Planning Activ ity

REL_Notices

Displacing AgencyREL_Open Site Office

Require Site

Office?

Inv entory of Parcels with

Displaced Persons


Relocation Agent

Certified Lawful

Presence in US? Hardship?

REL_No Relocation Assistance





REL_Geospatial

Enablement - Parcel

for Relocation


REL_Notices






Parcels with Displaced

PersonsDisplacing Agency


Relocation Agent


REL_Check on the Displaced

Persons eligibility for serv ices


REL_Check on the

Displaced Persons

eligibility for serv ices

No

No No

«precedes»

«precedes»

<<implement>>

Yes

Yes


<<implement>>

Yes

<<implement>>

«precedes»

<<implement>>

138

REL_Relocation Services Activity - (Activity diagram)

Figure: C1-18

act REL_Relocation Serv ices Activ ity

REL_ Link to MLS (External

Real Estate System)

REL_ Av ailable Properties for

Sale and Lease, Community

Amenities

Candidate Parcel Inv entory for

Displaced Persons - Layer, 1st

DSS Inspection Report, 2nd

DSS Inspection Report,

Assignment Status

REL_Replacement Dwelling

Assignment

Displacing Agency

REL_Explanation of Serv ices,

Av ailable Payments and Eligibility

Requirements

REL_Determination of Occupant

Needs

REL_Determine Eligibility for Each

Type of Payments

Eligible for

relocation

assistance?

REL_Conduct Personal Interv iew

REL_Prov ide adv isory assistance

(Assistance with claim forms)

Type of

Relocation -

Residential?

Availabil ity of

Comparable

Replacement

Housing?

REL_ Last Resort Housing

PlanningRelocation Agent

(from REL_Relocation Services)

REL_Explanation of

Serv ices and

Av ailable Payments

and Eligibility

Requirements


REL_Determination of

Occupant Needs


REL_Determine

Eligibility for Each

Type of Payments


REL_Personal

Interv iew


REL_Prov ide

adv isory assistance

(Assistance with

claim forms)


REL_Link to MLS(

External Real Estate

System)


REL_Geospatial

Enablement Av ailable

Properties for Sale and

Lease, Community

Amenities


REL_Replacement

Dwelling Assignment


REL_Last Resort

Housing Planning

Displacing Agency


Relocation Agent


REL_No Relocation

Assistance

Yes

Yes

No

<<implement>>

<<implement>>

No

«extend»

<<implement>>

«precedes»

«extend»«precedes»

<<implement>>

<<implement>>

<<implement>>

<<implement>>

<<implement>>

<<implement>> <<implement>><<implement>>

Yes

139

REL_Relocation Assistance Payments Activity - (Activity diagram)

Figure: C1-19

act REL_Relocation Assistance Payments Activ ity

Displacing Agency

REL_Mov ing Expense

Process

REL_ Replacement Housing

Payment Process

REL_ Claim and Tax-Form

Process

(from REL_Relocation Assistance Payments)

REL_Mov ing

Expense Process


REL_Replacement

Housing Payment


REL_Claim and

Tax-Form Process

Displacing Agency


«precedes»

«precedes»

«precedes»

<<implement>>


<<implement>>

140

Property Management Activity Model - (Activity diagram)

Figure: C1-20

141

PM_Pre-Construction Activity - (Activity diagram)

Figure: C1- 21

act PM_Pre-Construction Activ ity

PM_

Improv ement

Disposition

PM_RentalProperty

Disposition?

PM_Requirement Type

PM_Personal

Property

(from PM_Pre-Construction Package)

PM_Parcel

Requirement Type -

GEOSPATIAL

ENABLEMENTPM personnel

(from Human Actors)

APP_Appraisal

Personal

Property?

Parcel Database Geospatial

Parcel Layer

(from Business Process Model Package - Overall ROW)

ROW Plans


Yes

No

No

<<implement>>

Yes

142

PM_During Consturction Activity - (Activity diagram)

Figure: C1-22

act PM_During Consturction Activ ity

PM_Grading

Geospatial Data.

(from PM_During Construction Package)

PM_Contract

(from PM_During Construction Package)

PM_Grading -

GEOSPATIAL

ENABLEMENT

PM_Contract

PM personnel

(from Human Actors)

PM_ROW

Database

<<implement>>

«extend»

<<implement>>

143

PM_Post- Construction Activity - (Activity diagram)

Figure: C1-23

act PM_Post- Construction Activ ity

Property

Disposition?

PM_Sale

ROW

Disposal?

PM_ROW Disposal PM_ROW

Management

Excess

Disposa?

PM_Excess

PM_Rodent Control PM_Security

Inspection

PM_Hazardous

Material Mitigation

ROW

Yes No

Excess

144

Class Model - Overall ROW - (Logical diagram)

Figure: C1-24

145

Figure: C1-24 (cont.)

146

Cadastral Elements - (Logical diagram)

Figure: C1- 25

class Cadastral Elements

Cadastral_Reference

- Another_metadata_file(If_datum_not_unique_for_entire_jurisdiction): char

+ Control_ID: int

- Coordinate_System: char

- Coordinate_System_Description: char

- Date_Coordinate: Date

- Date_Monument: Date

- Date_of_File: Date

- East_X: Geosptial_Reference

- Elevation-Z: Geosptial_Reference

- Elevation_Accuracy: char

- Elevation_Datum: char

- Elevation_Units: Geosptial_Reference

- Horizontal_Accuracy: char

- Horizontal_and_Vertical_Datum: int

- Horizontal_Datum: char

- Jurisdiction_Contact: char

- Jurisdiction_Name: char

- Monument_Surveyor: char

- Monument_Type: char

- North_Y: Geosptial_Reference

- Units_Of_Measure: char

Geosptial_Reference

- Date_Of_Orthophotos: int

- Datums: int

- Jurisdiction: char

- Monumneted_points: int

- NGRS_Coordinate_System: char

- Orthography: int

- Terrain_Information: char

Cadastral_Parcel

- APP_Type: char

- Basis_Of_Assessment: char

- Date_Of_File: Date

- Improved: char

- Interpretation_Of_Assessment_Classification: char

- Jurisdiction_Name: char

- Jurisdiction_Parcel_Contact: char

- Owner_Name: char

- Owner_Type: char

- Parcel_Area: double

- Parcel_Centroid: Geosptial_Reference

+ Parcel_ID: int

- Parcel_Outline: Geosptial_Reference

- Parcel_Street_Address: char

- Parcel_Type: char

- Parcel_Zoning: char

- Primary_Value_Classification: char

- Public_Parcel_Name: char

- Secondary_Value_Classification: char

- Source_Reference: char

- Source_Reference_Date: int

- Tax_Bill_Mailing_Address: char

- Total_Value: int

- Value_Of_Improvements: int

- Value_Of_Land: int

147

Transportation Elements - (Logical diagram)

Figure: C1-26

class Transportation Elements

Transportation_Project

- Alignment: Geosptial_Reference

- Alignment_From_end_point: Geosptial_Reference

- Alignment_To_end_point: Geosptial_Reference

+ Project_ID: int

- Right_of_way_limits: Geosptial_Reference

Transportation_Centerlines_(FTRP)

+ Authority_ID: int

- Date_Centerline: Date

- Elevation: Geosptial_Reference

- FTRP-Feature_type: char

- Horizontal_accuracy: Geosptial_Reference

- Horizontal_accuracy_measuremen_method: Geosptial_Reference

- Latitude: Geosptial_Reference

- Location_description: char

- Logitude: Geosptial_Reference

- Status_Tranportation_Centerline: char

+ Transportation_Segment_reference_point_ID: int

- Vertical_accuracy: Geosptial_Reference

- Vertical_accuracy_measurement_method: Geosptial_Reference

Transportation_Centerlines

+ Authority ID: int

- Date_Tranportaion_Centerline: Date

- From-End-Point: Geosptial_Reference

- FTSeg-Feature-Type (Optional): char

- Intermediate-Point(when_applicable): Geosptial_Reference

- Length-Accuracy-Measurement-Method: char

- Length (Optional and Recommended): int

- Path-Description: char

- State: char

- Status_Tranportation_Centerline: char

- To-End-Point: Geosptial_Reference

+ Transportation-Segment-ID: int

Transportation Centerlines Connectiv ity table

+ Authority ID: int

- Date_Of_Creation_Of_Connectivity: Date

- FTSeg-Offset-%: Geosptial_Reference

- Offset-%-Accuracy-Description: char

- Status_Centerline_Connectivity: char

+ Transportation-Segment-ID: int

+ Transportation Segment reference point ID: int

Transportation Centerlines Relating Attributes of FTRP &

FTSeg

- Attribute-Name: char

- Attribute-Value: int

+ Authority ID: int

- Date_Of_Creation: Date

- End offset: Geosptial_Reference

- Start offset: Geosptial_Reference

+ Transportation reference point ID or Segment ID: int

Transportation Centerlines Equiv alency table


- End offset: Date

+ Equivalent_FTRP_ID or Equivalent_FTSeg_ID: int

+ Reference-FTRP-ID or Reference-FTSeg-ID: int

- Start offset: Geosptial_Reference

- Status: char

Transportation Centerlines Authority description

- Authority-Address: char

- Authority-City: char

- Authority-Country: char

- Authority-Index-Access- Information: char

- Authority-Information (optional): char

- Authority-Postal-Code: int

- Authority-State-or-Province: char

+ Authority ID: int

- Authority Name: char

- Contact-Electronic-Mail - Address: char

- Contact-Facsimile-Telephone (optional): char

- Contact-Instructions: char

- Contact-Person-Primary: char

- Contact-URL (optional): char

- Contact-Voice-Telephone: char


- Status: char

148

Project Development - (Logical diagram)

Figure: C1-27

class Project Dev elopment

Authorize_Project

+ Project ID: int

- Project_Transportation: Transportation_Project

Parcels_For_Alignmnet

- Date Source Reference: Date

- Parcel Photographs: BLOB

- Parcel_Boundary: Transportation_Centerlines_(FTRP)

+ Parcel_ID: int

- Parcel_Inspection: boolean

+ Project ID: int

- Source Reference: char

- Type_Of_Acquisition(Whole/Partial): char

Acquisition cost estimation

- Initial_Total_Acquisition_Estimate: int

+ Project_ID: int

+ RoW_Administrator_ID: int

Relocation Surv ey and cost Estimation

- Initial_Relocatoin_Cost_Estimate: int

+ Project_ID: int

- Relocation_Details: Document

- Relocation_Situation: char

+ RoW_Administrato_ID: int

# Site_Office_Requirement: char

Protectiv e_Buying

+ Parcel_ID: int

+ Project_ID: int

- Protective_Buying_Acquisition_Cost: int

Non_Federal_Fund_Share

- Fund_Amount: int

+ Project_ID: int

- Source_Funds(Local/State/Credit): char

Parcel_Title


- Title_Assurance: boolean

- Title_Certificate: Document

- Title_Search_Method: char

Staff_Identification

+ Project_ID: int

- Staff_Address: char

- Staff_Contact: char

+ Staff_ID: int

- Staff_Name: char

- Staff_Type(Assigned/Hired): char

- Task_Responsible: char

Project_Parcels

- Date Source Reference: Date

+ Parcel ID: int

- Parcel_Boundary: Transportation_Centerlines_(FTRP)

- Parcel_RoW_Cost_Estimate: int

+ Project ID: int

- Source Reference: char

Class Model Model

Package - Ov erall

ROW::ROW Parcel

Cadastral Elements::

Cadastral_Parcel

149

Major ROW functions - (Logical diagram)

Figure: C1-28

Project Closing - (Logical diagram)

Figure: C1-29

Appraisal - (CompositeStructure diagram)

Figure: C1-30

class Major ROW functions

Appraisal

Acquisition Relocation

Property_Management

class Project Closing

Project_Closing

- Any_Outstanding_Condemenations_Idenitfied: boolean

- Encroacments_Identified: boolean

- Excess_Property_Disposed: boolean

- Final_Claims_Processed: boolean

- Project_Accountin_Closed: boolean

+ Project_ID: int

- Project_Plans_Reviewed: boolean

- Records_Stored_and_Accumlated: boolean

- Status_OF_Federal_Voucher_Letter: Flag

- Status_of_RoW_Certificate: Flag

Notice_to_Proceed

- Additional_Comments: char

- Date_of_Issuance_of_Notice: Date

+ Project_ID: int

- Type_of_Notice_to_Proceed: char

150

APP_Class Model - (Logical diagram)

Figure: C1-31

151

Acquisition - (CompositeStructure diagram)

Figure: C1- 32

ACQ_Class Model - (Logical diagram)

Figure: C1-33

152

Relocation - (CompositeStructure diagram)

Figure: C1- 34

REL_Class Model - (Logical diagram)

Figure: C1-35

153

Property_Management - (CompositeStructure diagram)

Figure: C1-36

PM_Class Model - (Logical diagram)

Figure: C1-37

154

Component Model - Overall ROW - (Component diagram)

Figure: C1-38

cmp Component Model - Ov erall ROW

Financial Information

System

Project Management

Information System

FHWA Annual

Reporting System

Local Gov ernment

Systems

Document

Management System

Parcels

Turbo Relocation (or

Similar)

MLS (External Real

Estate System)

Env ironmental System

Geospatial

Warehouse


Highway Right of Way

ROW Director

(from Human Actors)

Project Manager

(from Human Actors)

Project Closing

Project Dev elopment

Major ROW Functions

«invokes»

«precedes»

«invokes»

«invokes»

«precedes»

155

Project Development Component Model - (Component diagram)

Figure: C1-39

Major ROW functions Component Model - (Component diagram)

Figure: C1-40

cmp Major ROW functions Component Model

Appraisal Acquisition

RelocationProperty Management

156

Project Closing - (Component diagram)

Figure: C1-41

Appraisal - (CompositeStructure diagram)

Figure: C1-42

157

APP-Component Model - (Component diagram)

Figure: C1-43

Acquisition - (CompositeStructure diagram)

Figure: C1- 44

ACQ_Componenet Model - (Component diagram)

158

Figure: C1-45

Relocation - (CompositeStructure diagram)

Figure: C1-46

REL_Component Model - (Component diagram)

Figure: C1-47

159

Property Management - (CompositeStructure diagram)

Figure: C1-48

PM_Component Model - (Component diagram)

Figure: C1-49

160

Appendix C2:

UML Diagrams for GDMA logical model

161

Geospatial Decision Making Activities - (Package diagram)

Figure: C2-1

Parcel Tracking (PT) - (Package diagram)

Figure: C2-2

PT_State Machine Diagram Model - (StateMachine diagram)

162

Figure: C2-3


«Flag»

Status: APP

«Value»

Project Number


«Value»



«Value»

Parcel Take


«Value»

Parcel Land Use


«Value»



«Value»

Appraisal Type


«Value»

Appraiser Type


«Value»

Just Compensation


«Value»

Appraisal Technique


«Flag»



«Flag»



«Flag»



«Flag»



«Flag»



«Flag»



«Value»

Utilities


«Value»



«Flag»



«Flag»

Status: ACQ

«Value»

Acquisition Type


«Flag»



«Flag»

Negotiator Type


«Value»



«Flag»


«Value»



«Value»

Type of Purchase


«Value»

Type of Negotiation


«Value»



«Flag»



«Flag»



«Flag»



«Flag»

Status : REL

«Value»



«Value»



«Flag»


«Value»



«Flag»



«Flag»



«Value»



«Value»



«Flag»



«Flag»



«Flag»


«Flag»


«Value»



«Value»



«Value»



«Value»



«Flag»



«Value»



«Flag»



«Flag»



«Flag»

Status : PM

«Value»

Requirement Type


«Value»



«Value»

Rental Type


«Flag»

Status : Clearance


«Value»



«Value»



«Value»



«Value»



«Flag»

Status : Grading


«Flag»


«Value»



«Value»



«Flag»



«Value»

Security Inspection


«Value»

Rodent Control


«Value»

Notice to Proceed


«Flag»



«Flag»



Final


















Class Elements::









Appraisal_Report






ACQ_Negotiator




ACQ_Contact_Owner




Elements::








ROW Parcel


for Relocation


REL_Notices









Determination



Last Resort










Determination



Processing




PM_Requirement_Type




PM_Property_Rental




PM_Grading




PM_Rodent Control




Mitigation


Notice_to_Proceed


Initial

«Value»










«Type»

State

«Type»

State

«Type»

State

LEGEND

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

163

Figure: C2-3 (Cont.)


«Flag»

Status: APP

«Value»

Project Number


«Value»



«Value»

Parcel Take


«Value»

Parcel Land Use


«Value»



«Value»

Appraisal Type


«Value»

Appraiser Type


«Value»

Just Compensation


«Value»

Appraisal Technique


«Flag»



«Flag»



«Flag»



«Flag»



«Flag»



«Flag»



«Value»

Utilities


«Value»



«Flag»



«Flag»

Status: ACQ

«Value»

Acquisition Type


«Flag»



«Flag»

Negotiator Type


«Value»



«Flag»


«Value»



«Value»

Type of Purchase


«Value»

Type of Negotiation


«Value»



«Flag»



«Flag»



«Flag»



«Flag»

Status : REL

«Value»



«Value»



«Flag»


«Value»



«Flag»



«Flag»



«Value»



«Value»



«Flag»



«Flag»



«Flag»


«Flag»


«Value»



«Value»



«Value»



«Value»



«Flag»



«Value»



«Flag»



«Flag»



«Flag»

Status : PM

«Value»

Requirement Type


«Value»



«Value»

Rental Type


«Flag»

Status : Clearance


«Value»



«Value»



«Value»



«Value»



«Flag»

Status : Grading


«Flag»


«Value»



«Value»



«Flag»



«Value»

Security Inspection


«Value»

Rodent Control


«Value»

Notice to Proceed


«Flag»



«Flag»



Final


















Class Elements::









Appraisal_Report






ACQ_Negotiator




ACQ_Contact_Owner




Elements::








ROW Parcel


for Relocation


REL_Notices









Determination



Last Resort










Determination



Processing




PM_Requirement_Type




PM_Property_Rental




PM_Grading




PM_Rodent Control




Mitigation


Notice_to_Proceed


Initial

«Value»










«Type»

State

«Type»

State

«Type»

State

LEGEND

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

164



«Flag»

Status: APP

«Value»

Project Number


«Value»



«Value»

Parcel Take


«Value»

Parcel Land Use


«Value»



«Value»

Appraisal Type


«Value»

Appraiser Type


«Value»

Just Compensation


«Value»

Appraisal Technique


«Flag»



«Flag»



«Flag»



«Flag»



«Flag»



«Flag»



«Value»

Utilities


«Value»



«Flag»



«Flag»

Status: ACQ

«Value»

Acquisition Type


«Flag»



«Flag»

Negotiator Type


«Value»



«Flag»


«Value»



«Value»

Type of Purchase


«Value»

Type of Negotiation


«Value»



«Flag»



«Flag»



«Flag»



«Flag»

Status : REL

«Value»



«Value»



«Flag»


«Value»



«Flag»



«Flag»



«Value»



«Value»



«Flag»



«Flag»



«Flag»


«Flag»


«Value»



«Value»



«Value»



«Value»



«Flag»



«Value»



«Flag»



«Flag»



«Flag»

Status : PM

«Value»

Requirement Type


«Value»



«Value»

Rental Type


«Flag»

Status : Clearance


«Value»



«Value»



«Value»



«Value»



«Flag»

Status : Grading


«Flag»


«Value»



«Value»



«Flag»



«Value»

Security Inspection


«Value»

Rodent Control


«Value»

Notice to Proceed


«Flag»



«Flag»



Final


















Class Elements::









Appraisal_Report






ACQ_Negotiator




ACQ_Contact_Owner




Elements::








ROW Parcel


for Relocation


REL_Notices









Determination



Last Resort










Determination



Processing




PM_Requirement_Type




PM_Property_Rental




PM_Grading




PM_Rodent Control




Mitigation


Notice_to_Proceed


Initial

«Value»










«Type»

State

«Type»

State

«Type»

State

LEGEND

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

165



«Flag»

Status: APP

«Value»

Project Number


«Value»



«Value»

Parcel Take


«Value»

Parcel Land Use


«Value»



«Value»

Appraisal Type


«Value»

Appraiser Type


«Value»

Just Compensation


«Value»

Appraisal Technique


«Flag»



«Flag»



«Flag»



«Flag»



«Flag»



«Flag»



«Value»

Utilities


«Value»



«Flag»



«Flag»

Status: ACQ

«Value»

Acquisition Type


«Flag»



«Flag»

Negotiator Type


«Value»



«Flag»


«Value»



«Value»

Type of Purchase


«Value»

Type of Negotiation


«Value»



«Flag»



«Flag»



«Flag»



«Flag»

Status : REL

«Value»



«Value»



«Flag»


«Value»



«Flag»



«Flag»



«Value»



«Value»



«Flag»



«Flag»



«Flag»


«Flag»


«Value»



«Value»



«Value»



«Value»



«Flag»



«Value»



«Flag»



«Flag»



«Flag»

Status : PM

«Value»

Requirement Type


«Value»



«Value»

Rental Type


«Flag»

Status : Clearance


«Value»



«Value»



«Value»



«Value»



«Flag»

Status : Grading


«Flag»


«Value»



«Value»



«Flag»



«Value»

Security Inspection


«Value»

Rodent Control


«Value»

Notice to Proceed


«Flag»



«Flag»



Final


















Class Elements::









Appraisal_Report






ACQ_Negotiator




ACQ_Contact_Owner




Elements::








ROW Parcel


for Relocation


REL_Notices









Determination



Last Resort










Determination



Processing




PM_Requirement_Type




PM_Property_Rental




PM_Grading




PM_Rodent Control




Mitigation


Notice_to_Proceed


Initial

«Value»










«Type»

State

«Type»

State

«Type»

State

LEGEND

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

166



«Flag»

Status: APP

«Value»

Project Number


«Value»



«Value»

Parcel Take


«Value»

Parcel Land Use


«Value»



«Value»

Appraisal Type


«Value»

Appraiser Type


«Value»

Just Compensation


«Value»

Appraisal Technique


«Flag»



«Flag»



«Flag»



«Flag»



«Flag»



«Flag»



«Value»

Utilities


«Value»



«Flag»



«Flag»

Status: ACQ

«Value»

Acquisition Type


«Flag»



«Flag»

Negotiator Type


«Value»



«Flag»


«Value»



«Value»

Type of Purchase


«Value»

Type of Negotiation


«Value»



«Flag»



«Flag»



«Flag»



«Flag»

Status : REL

«Value»



«Value»



«Flag»


«Value»



«Flag»



«Flag»



«Value»



«Value»



«Flag»



«Flag»



«Flag»


«Flag»


«Value»



«Value»



«Value»



«Value»



«Flag»



«Value»



«Flag»



«Flag»



«Flag»

Status : PM

«Value»

Requirement Type


«Value»



«Value»

Rental Type


«Flag»

Status : Clearance


«Value»



«Value»



«Value»



«Value»



«Flag»

Status : Grading


«Flag»


«Value»



«Value»



«Flag»



«Value»

Security Inspection


«Value»

Rodent Control


«Value»

Notice to Proceed


«Flag»



«Flag»



Final


















Class Elements::









Appraisal_Report






ACQ_Negotiator




ACQ_Contact_Owner




Elements::








ROW Parcel


for Relocation


REL_Notices









Determination



Last Resort










Determination



Processing




PM_Requirement_Type




PM_Property_Rental




PM_Grading




PM_Rodent Control




Mitigation


Notice_to_Proceed


Initial

«Value»










«Type»

State

«Type»

State

«Type»

State

LEGEND

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

167



«Flag»

Status: APP

«Value»

Project Number


«Value»



«Value»

Parcel Take


«Value»

Parcel Land Use


«Value»



«Value»

Appraisal Type


«Value»

Appraiser Type


«Value»

Just Compensation


«Value»

Appraisal Technique


«Flag»



«Flag»



«Flag»



«Flag»



«Flag»



«Flag»



«Value»

Utilities


«Value»



«Flag»



«Flag»

Status: ACQ

«Value»

Acquisition Type


«Flag»



«Flag»

Negotiator Type


«Value»



«Flag»


«Value»



«Value»

Type of Purchase


«Value»

Type of Negotiation


«Value»



«Flag»



«Flag»



«Flag»



«Flag»

Status : REL

«Value»



«Value»



«Flag»


«Value»



«Flag»



«Flag»



«Value»



«Value»



«Flag»



«Flag»



«Flag»


«Flag»


«Value»



«Value»



«Value»



«Value»



«Flag»



«Value»



«Flag»



«Flag»



«Flag»

Status : PM

«Value»

Requirement Type


«Value»



«Value»

Rental Type


«Flag»

Status : Clearance


«Value»



«Value»



«Value»



«Value»



«Flag»

Status : Grading


«Flag»


«Value»



«Value»



«Flag»



«Value»

Security Inspection


«Value»

Rodent Control


«Value»

Notice to Proceed


«Flag»



«Flag»



Final


















Class Elements::









Appraisal_Report






ACQ_Negotiator




ACQ_Contact_Owner




Elements::








ROW Parcel


for Relocation


REL_Notices









Determination



Last Resort










Determination



Processing




PM_Requirement_Type




PM_Property_Rental




PM_Grading




PM_Rodent Control




Mitigation


Notice_to_Proceed


Initial

«Value»










«Type»

State

«Type»

State

«Type»

State

LEGEND

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

168



«Flag»

Status: APP

«Value»

Project Number


«Value»



«Value»

Parcel Take


«Value»

Parcel Land Use


«Value»



«Value»

Appraisal Type


«Value»

Appraiser Type


«Value»

Just Compensation


«Value»

Appraisal Technique


«Flag»



«Flag»



«Flag»



«Flag»



«Flag»



«Flag»



«Value»

Utilities


«Value»



«Flag»



«Flag»

Status: ACQ

«Value»

Acquisition Type


«Flag»



«Flag»

Negotiator Type


«Value»



«Flag»


«Value»



«Value»

Type of Purchase


«Value»

Type of Negotiation


«Value»



«Flag»



«Flag»



«Flag»



«Flag»

Status : REL

«Value»



«Value»



«Flag»


«Value»



«Flag»



«Flag»



«Value»



«Value»



«Flag»



«Flag»



«Flag»


«Flag»


«Value»



«Value»



«Value»



«Value»



«Flag»



«Value»



«Flag»



«Flag»



«Flag»

Status : PM

«Value»

Requirement Type


«Value»



«Value»

Rental Type


«Flag»

Status : Clearance


«Value»



«Value»



«Value»



«Value»



«Flag»

Status : Grading


«Flag»


«Value»



«Value»



«Flag»



«Value»

Security Inspection


«Value»

Rodent Control


«Value»

Notice to Proceed


«Flag»



«Flag»



Final


















Class Elements::









Appraisal_Report






ACQ_Negotiator




ACQ_Contact_Owner




Elements::








ROW Parcel


for Relocation


REL_Notices









Determination



Last Resort










Determination



Processing




PM_Requirement_Type




PM_Property_Rental




PM_Grading




PM_Rodent Control




Mitigation


Notice_to_Proceed


Initial

«Value»










«Type»

State

«Type»

State

«Type»

State

LEGEND

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

«flow»

169

Geospatial Enablement (GE) - (Package diagram)

Figure: C2-4

170

GE_Data Flow Model_New - (Data Flow diagram)

Figure: C2-5

171

Project Development: Geospatial Enablement - (Data Flow diagram)

Figure: C2-6

dfd Project Dev elopment: Geospatial Enablement

GIS Warehouse

New roadway

ROW

Parcel_Cadastre

Layer

VideoLogRoadway ROW

layer

ROW Project

Parcels

Define

Parcel

Type of

Take :

Spatial

Analysis

Alignment

Selection :

Spatial

Analysis

ROW Mapping

and Engineering

Environmental/

Hazardous

Sites : Spatial

Analysis

Environmental

System/ Other

Spatial

Analysis :

Overlay &

Extraction

Identify

parcels for

right-of-way

Divide

Parcel(s) :

Spatial

Analysis

Thematic

/ Visual

Display

Thematic

/ Visual

Display

Imagery

Divide & Redefine

ROW Project

Parcels

ROW Project

Parcels

Identification

«trace»

Alignment

Selection

«trace»

«trace»«trace»

ROW

Plans

ROW

Plans

«trace»

Environmental &

Hazardous waste sites

Evaluation/Study Reports

172

APP: Geospatial Enablement - (Data Flow diagram)

Figure: C2-7

dfd APP: Geospatial Enablement

Appraisal SystemHistorical parcel

sales Records

GIS Warehouse

ROW Project

Parcels

New roadway

ROW

Parcel_Cadastre

Layer

Parcels with

special properties

VideoLog

Util ities

ROW Parcel

Util ities

APP :

Initial

Review

(Visual

Display)

Sales

Comparison

(Data

Analysis)

Data

Query/

Extraction/

Overlay

Spatial

Analysis :

3D Analyst

Thematic

/ Visual

Display

Thematic

/ Visual

Display

Appraisal

Technique

(Data

Analysis)

Data

Query/

Extraction

Roadway ROW

layer

Imagery

Identification

of Parcels

with util ities

Appraisal_Technique

«trace»

«trace»

«trace»

Special

Property

Identification

«trace»

«trace»

«trace»

«trace»

Effect of

Elevation

Changes

«trace»

173

REL: Geospatial Enablement - (Data Flow diagram)

Figure: C2-8

dfd REL: Geospatial Enablement

Demographic Data

Layer

Candidate Parcel

Inventory for

Displaced Persons

Lease/Sale

property

management

system

GIS Warehouse

ROW Project

Parcels

Parcel_Cadastre

Layer

Data Query

(Extraction)

Parcels for /

Requiring

Relocation

Spatial

Analysis /

Modeling

Util ities

Spatial

Analysis :

Overlay /

Spatial

Query

Candidate Parcel

Inventory for

Relocating or

Adjusting Util ities

Thematic /

Visual

Display

Thematic /

Visual

Display

Transportation

Roadway Network

Suitable

Parcels

«trace»

Parcel Land Use

or Primary

Relocation

Indicator

«trace»«trace»

Needs of the

Displaced

Socio-Economic

Factors

«trace»

Suitable

Parcel(s) /

Location(s)

«trace»

Parcel(s)

Identification

174

PM: Geospatial Enablement - (Data Flow diagram)

Figure: C2-9

dfd PM: Geospatial Enablement

PM :

Clearance

/Demolition

PM :

Grading

PM :

Requirement

Type

PM : ROW /

Excess

Disposal

JustificationExcess Property

Topography Layer

Soil Data Layer

GIS Warehouse

ROW Project

Parcels

New roadway

ROW

Spatial

Analysis :

Overlay

Data Query

(Extraction)

Surface

Analysis :

Cut/Fil l

(3D-Analyst)Spatial

Analysis :

Modeling

Visual

Analysis /

Data

Query

Parcel_Cadastre

Layer

Transportation

Roadway Network

Vegetation Layer

Thematic /

Visual

Display

Thematic /

Visual

Display

Roadway ROW

layer

Update:

Parcel_Requirement_Type

«trace»

«trace»

Excess Land

Identification

Area of Parcel in ROW

Boundary/Area

Cost of

earthwork

Type & Level

of Clearance

«trace»

«trace»

Thematic Maps/

Justification

Models

Highway

Safety/

Traffic

Demand

Status_of_Clearance

Status_of_Grading

«trace»

Soil Type

Vegetation

Classification

Improvement_Disposition_Type /

Personal_Property_Disposition_Type

LandUse/

Zoning

«trace»

Terrain /

Elevation

Soil

Type

Boundary/Area

«trace»

175

GE_Activity Model - (Activity diagram)

Figure: C2- 10

act GE_Activ ity Model

Acquisition

Property Management

Relocation

Project Closing

AppraisalProject Dev elopment

Initial Planning

Alignment Ev aluation


Parcel identification


Identification of

Env ironmental

impacts


Env ironmental study


Final Alignment

Selection


Hazardous waste site

ev aluation


ROW Mapping and

Engineering


Parcel Alignment

Inspection


Identification of Parcel

Type


Parcel Type


Update Excess to

Inv entory


Geospatial Data -

Parcels, Roads,

Right-of-Way


Geospatial Data - Parcels,

Right-of-Way

(from APP_Business Process Model Packag)

APP_Initial Rev iew


APP_Parcel for

Appraisal


APP_Determination of

Appraisal Technique


APP_Specialty

Appraisal


REL_Parcels for

Relocation

(from REL_Business Process Model Package)

REL_ Av ailable

Properties for Sale

and Lease, Community

Amenities


Candidate Parcel Inv entory for

Displaced Persons - Layer, 1st

DSS Inspection Report, 2nd DSS

Inspection Report, Assignment

Status


PM_Requirement Type

(from PM_Business Process Model Package)

PM_Clearance/

Demolition: PM_Clearance

- GEOSPATIAL

ENABLEMENT


PM_Grading


PM_ROW Disposal Justification -

GEOSPATIAL ENABLEMENT


PM_Excess


PM_Excess Disposal Justification -

GEOSPATIAL ENABLEMENT


No geospatially enabled

activities identified

within Acquisition

Geospatial data -

Parcels, Right-of-Way