|
|
If you are interested in purchasing this program, please contact us at 605-787-7871 or email us at agware@uaar.net.
Enterprises with multiple appraisers face some unique challenges in
ensuring they get the most value out of their sales data. The Enterprise
Edition of the UAAR DataLog addresses those issues. Our goal is to provide
our Enterprise customers with the centralized control and data storage they
need without slowing down the day to day appraisal process.
* Specific to Enterprise Edition only
At the heart of the UAAR Enterprise DataLog is Microsoft SQL server. SQL Server provides a secure central location to share and report on your sales data. It is possible with the current DataLog to use a common central Microsoft Access Database on a network share. However the program was not designed for multi-user access. Users must be careful to not add or modify records at the same time as other users. The new DataLog is designed specifically for multi-user access.
In a distributed environment multiple read only SQL Servers can be used to speed data access. A single common server must be accessible for writing data. However, read only data can be replicated closer to the user for faster searching and reporting.
Using Microsoft SQL Server for centrally storing sales is an important
feature of the program. Equally as important is the private offline storage
on each users' computer. Just because an appraiser is out of the office does
not mean that work needs to stop. Any editing of sales records is done
against the offline storage. This
means appraisers can add and modify sales even when they are not connected
to the network. Once a sale is ready to be shared it is "Posted" to the
Enterprise Database. This process will upload the sale into the database
where it can then be searched, downloaded, and used for reporting by other
users.
Each sale has a database status so the user can see if the sale needs to be posted to the Enterprise Database. There are five statuses:
Current (Posted): This sale is currently in the Enterprise Database.
New: This is a new sale that is not yet in the Enterprise Database. 
Modified: This sale is in the Enterprise Database, but has been modified
since it was posted or extracted from the database. 
Flagged Sales: The New and Modified statuses can also be marked as
private. In this case the user has marked the sale to indicate that it
should not be posted to the Enterprise Database. This can be useful when
dealing with a confidential sale or re-analyzing the sale in a way that
should not be shared with all users. Sales can be posted one at a time as they are completed. If many sales are entered while offline a Synchronize Sales feature can be used to post all sales that are currently new or modified and not marked as private.
As with the existing DataLog the new DataLog allows users to save common responses for each field. In addition, responses can be setup on the server and flagged as "Approved". These approved responses are automatically downloaded to the appraisers' computer when they connect to the database. This can help ensure data consistency by giving all users access to the same response list. Approved response lists can be setup for the following fields: Zone, Area, Region, Category, SCA Unit Type, Primary Land Use, Primary Commodity, Property Type, Attribute Type, Land Mix, Income, Expense, Improvement Type, Improvement Unit, Improvement Utility, and Improvement Condition.
To help with converted data and on going data cleanup, a merge function is available for each approved response list. This feature allows different or misspelled versions of the same item to be merged into the correct format. For example, if one appraiser entered "Grain Bins" and another used "Grain Bns" they can be merged so all the sales with the Bns spelling are updated to Bins.
Rule Sets are another way to ensure data consistency in the Enterprise Database. Any sale that is posted to the Central Database must be validated by a Rule Set. For each field on the sales sheet a rule can be created that requires data to be entered, requires a shared response to be used, or requires a specific value to be entered.
A typical Rule Set may contain the following rules: Require that Grantor, Grantee, Sale Date, Sale Price, and Acres be filled out; require field "C" to be "Tax ID" and field "D" to be "DOM"; and require that Primary Commodity and Primary Land Use be approved responses only.
A Rule Set only restricts what can be posted to the Enterprise Database. While editing a sale can be validated against the Rule Set, however anything can be entered and saved. This model allows appraisers to get their work done without being locked down, while still assuring shared data has the consistency needed to extract valuable information.
All posts to the Enterprise Database track the user that made the change and the date and time of the change. In addition, each previous version of the sale is stored. If a sale that was already updated is posted the most recent version is the one used for searching and reporting. All of the data for the previous versions is available in the database and can be retrieved and reviewed.
Another problem with trying to maintain a centralized database with the current system is preventing duplicate sales. The Enterprise version of the DataLog provides a unique matching system to help weed out duplicate sales. A potential match is determined by using a phonetic match for the Grantor and Grantee names plus a factor from the Sale Date, Acres, and Price. If these values combine cross a match threshold the sale will be flagged as a possible duplicate.
The image below is the main screen of the DataLog. The main screen is divided into four sections:
The image below is the 'Search for Sales' screen. The user has many options to use for searching through the sales. You can select either or all of the first three options – Date range, Price range, and Acre range. You can search by sales that were Resales, Improved Only, Unimproved Only, or All Sales. Then you can limit your search even more by selecting what you want to search by. You have several options to choose from, along with the ability to specify which value you want it to search for within that option.
The image below is the 'Server Responses' screen for 'Attributes'.
The image below is the 'Rule Sets' screen. The Rule Set example below is called "Ag" and it has several fields that have required values. If these fields are not filled at the time the user validates the sale, the program will not allow the sale to be posted until those fields are filled with the correct values.
Click here to return to the Products page.
| UAAR 2006 Products |
|---|
|
|
| Other Information |
|---|
|
|
