PC – Building Information

Property Control (PC) – Building Information

Version 6.x

Overview

The Building Information tab is used for creating and maintaining building records for the current property. Each record is assigned a Building ID by the user, or a new Building ID is generated. A Sequence Number is also generated for each unit within the building. For example, you can use sequence numbers for separate condominiums within a building.

 

NOTE: The Building ID (bldg_ID) is a unique system generated number that will stay with the building.

 

Read More...

What’s New

New developments related to the Property Control module will be listed here.

 

 

 

 

101-pc-frm-028

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.
Loading...

Legal Information

Legal Information

Version 6.x

Overview

The Legal Information form is used for setting up and maintaining legal information, including lot size, property classification, property type and land use. Unlimited space is provided for adding legal description notes and comments. As with all Property Control forms, the Legal Description form is linked to the GIS application. When you select a parcel on the map application, the legal information is available.

 

NOTE: Each property record can have only one legal description. This information is saved by year.

 

NOTE: The Lot Size, Total Size, Front Size and Unit fields are enabled only for clients who do not have the Mass Appraisal module. If you have the Mass Appraisal module, this information is entered through the Land Information function.

 

Two fields are provided for entering the lot size. Typically, this is for properties that have divided land use.

 

Read More...

What’s New

New developments related to the Property Control module will be listed here.

 

 

 

 

101-pc-frm-018

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.
Loading...

Parcel Information

Parcel Information

Version 6.0 and Version 6.1

Overview

Govern’s Property Control Profile creates and maintains data that may not be otherwise maintained by the integrated applications in the Govern suite. It also merges and extracts data from various sources to continuously improve and refine the quality of the available data.
Parcel Information OpenForms are used for recording and maintaining the basic reference information on each parcel. All data are saved to (Table: PC_PARCEL).
The new version of this custom control uses fluent validation to validate user input. In addition, error messages are displayed in a tool tip when the mouse pointer is hovered over the control that is in error. Controls containing errors are outlined in red. The Save button will not be enabled until the error in the custom control has been resolved.
The Parcel Information form uses the Property Information (Table: PC_PARCELINFORMATION) entity which requires the following:

  • Custom Duplicate Parcel Action
  • Custom Control for parcel duplication
  • Controller for Custom Save/Update/Delete

The Controller

As the controller is responsible for the actions of Saving Updating and Deleting, it follows specific rules for each action.

 

Read More...

Business Rules

in the instance of a custom save, the following actions are carried out by the system.

1. Custom Save

New Parcel

For a New Parcel…

  • Information about the new parcel is obtained from the form.
  • In the instance of an empty lot where a subdivision is specified, the Next Lot Number is obtained.
  • The system will verify if the Tax Map number exists in the database.
  • Subdivision and Lot number must be specified; if the system does not allow a duplicate Subdivision and Lot, the system performs a check to see if the the subdivision and lot exist in (Table: PC_PARCEL)
  • In the event that no Tax Map Number, Subdivision, Lot, and Alternate Parcel ID are provided
    • If the Non Parcel Flag is TRUE and the Non Parcel ID was not set, the system sets the Non Parcel ID to the Current Parcel ID.
    • If Non Parcel Flag is FALSE, and the Legal Index was not specified, the system will set the Legal Index and the Parcel Index to the Current Parcel ID.
  • If an Effective Year was not specified, the system will set the Current Year as the Effective Year.
  • If an Inactive Year was not specified, then the Inactive Year will be set to 9999.

 

Existing Parcel

When there is an Existing Parcel the system will perform the following…

  • Check the Tax Map Number and display an error message if the Tax Map already exists in the database.
  • If the system does not allow a duplicate on a Subdivision and Lot, the system performs a check to see if the Subdivision and Lot exist in (Table: PC_PARCEL)
  • When the Tax Map is inactive and there is an active Business Occupant, an error message will be displayed.
  • In the instance when there is NO Tax Map, Subdivision, Lot, and Alternate Parcel ID provided,
    • IF the Non Parcel Flag is set to TRUE and the Non Parcel ID is not set, the system sets the Non Parcel ID to the Current Parcel ID.
    • IF the Non Parcel flag is set to FALSE and the Legal Index was not specified, the system set the Legal Index and the Parcel Index to the Current Parcel ID.
  • If the parcel being updated contains a Split Merge record in (Table: PC_GENEALOGY), an error message is displayed.

 

Execute an OpenForm Save

A save process is carried out on the OpenForm.

Post Save Activities

After the Save process…

  • When the current parcel is New, and the Inactive Year is greater than the Current Year ID, the system sets all buildings linked to the parcel to Inactive.
  • Call MANTA process satellite systems batch for parcel change. In addition the system ensures that MANTA considers the parcel as new if the Non Parcel Flag is set to zero (0) and is of Type Proposed.

 

2. Custom Delete

Prior to Delete action

Before the Delete action, the system will perform the following…

  • Check if the parcel is linked to (Table: PC_GENEALOGY), AR or UB; if there is a link, deletion will NOT be allowed.
  • Verify all tables containing a P_ID; ask for user confirmation to continue the deletion even if the parcel is linked to these tables
  • Ask the user to confirm deletion

 

Execute the OpenForm Deletion

A save process is carried out on the OpenForm.

Action

The PC_DuplicateParcel_Action is used to open the Duplicate Parcel custom control.

Custom Control

Duplicate Parcel Custom Control

GOV60_PC PropInfo_ParcelCreatn_00.png
Duplicate Parcel Custom Control – Click on link to view in new window.

 

GOV60_PC PropInfo_ParcelCreatn_01.png
Parcel Creation – Click on link to view in new window.

 

Description

The new version of the custom control will use fluent validation to validate the inputs of the user. Also now the error message will be displayed in a tooltip and the control containing the error will be outlined in red. The save button will only be enabled when there is no error in the custom control.

On load

If the New Parcel is set to the default Non Parcel Type, then the NonParcelFlag is set to TRUE and the NonParcelType to the default value of 1.

Validation

During the validation process…

  1. The number of parcels to be created must be specified.
  2. Number of parcels to be created must be a number from 1 to 999 inclusive
  3. A Subdivision is required if the Lot is specified
  4. If the system does not allow duplicate on Subdivision and Lot, a validation is performed to check if the specified Subdivision and Lot are already present in (Table: PC_PARCEL).
  5. If the tax map number is specified then we check if it already exists in the table PC_PARCEL

 

The Save Process

Save Process

The following is a brief description of the Save process.

  1. Show a message asking the user to confirm the duplication of the parcel. (Optional – by default this is false)
  2. Generate Alternate Parcel ID’s by calling the GenerateAlternateParcel method.
    • The GenerateAlternateParcel method will check if there is data in the legal field in the PC_PARCEL table for the new alternate parcel
  3. If the lot was not provided while the subdivision was provided then generate one
  4. If the subdivision is provided create a list of lots using the BR_PC_General.GenerateNumber method.
    • If no lot was generated then exit save as there was an error.
  5. If the Tax Map Number is provided, create a list of tax map numbers using the BR_PC_General.GenerateNumber method.
    • If no tax map number was generated then exit save as this means there was an error.
  6. Copy general data from parcel to be duplicated.
  7. Create XXX new parcels where XXX is the number of parcels to create specified by the user.
  8. For the new parcels we also duplicate linked parcel data of the original parcel.
  9. If the entity is set to be audited, create an audit record in table usr_audit_trail
  10. Call to WPG Satellites to process new parcels
  11. Show a message indicating the number of parcels that were created
  12. Add new parcels in the treeview

Parcel Creation – Command buttons

Save Button

The Save button is only enabled if there are no errors in the validation of the screen.

Cancel Button

Click the Cancel button to close the Duplicate Parcel custom control.

Configuration

The following are the configuration parameters required in the following Govern applications:

  • Business Entity Designer (BED)
  • OpenForms Designer (OFD)
  • Govern New Administration (GNA)
  • Govern Security Manager (GSM)

 

Business Entity Designer (BED)

BED – Step 1

101-pc-frm-012-GOV60-(UI CfgPropInfo-BED00)-[v6.0].png
BED Step 1 – Click on link to view in new window.

 

BED – Step 2

101-pc-frm-012-GOV60-(UI CfgPropInfo-BED01)-[v6.0].png
BED Step 2 – Click on link to view in new window.

 

BED – Step 3

101-pc-frm-012-GOV60-(UI CfgPropInfo-BED02)-[v6.0].png
BED Step 3 – Click on the link to view the image in a new window.

 

BED – Step 4

101-pc-frm-012-GOV60-(UI CfgPropInfo-BED03)-[v6.0].png
BED Step 4 – Click on link to view in new window.

 

OpenForms Designer (OFD)

 

OFD – Step 1

101-pc-frm-012-GOV60-(UI CfgPropInfo-OFD00)-[v6.0].png
OFD Step 1 – Click image to view in a new window.

 

OFD – Step 2 – Add controller in Property Information

101-pc-frm-012-GOV60-(UI CfgPropInfo-OFD01)-[v6.0].png
OFD Step 2 – Click on link to view in new window.

 

OFD – Step 3 – Add duplicate parcel action in Property Information

101-pc-frm-012-GOV60-(UI CfgPropInfo-OFD02)-[v6.0].png
OFD Step 3 – Click on link to view in new window.

 

OFD – Step 4

101-pc-frm-012-GOV60-(UI CfgPropInfo-OFD03)-[v6.0].png
OFD Step 4 – Click on link to view in new window.

 

OFD – Step 5 – Add entity configuration

101-pc-frm-012-GOV60-(UI CfgPropInfo-OFD04)-[v6.0].png
OFD Step 5 – Click on link to view in new window.

 

Govern New Administration (GNA)

 

GNA – Step 1

 

101-pc-frm-012-GOV60-(UI CfgPropInfo-GNA00)-[v6.0].png
GNA Step 1 – Click on link to view in new window.

 

GNA – Step 2

101-pc-frm-012-GOV60-(UI CfgPropInfo-GNA01)-[v6.0].png
GNA Step 2 – Click on link to view in new window.

 

Govern Security Manager (GSM)

 

GSM – Step 1

 

101-pc-frm-012-GOV60-(UI CfgPropInfo-GSM00)-[v6.0].png
GSM Step 1- Click on link to view in new window.

End of Configuration

 

 

 

 

101-pc-frm-012

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.
Loading...

Govern Std. Navigation & User Interface

Standard Navigation & User Interface

Overview

The Govern user interface is designed to allow quick access to the required areas of the application. In the interface there is extensive use of tabbed forms, ribbons, and auto-hide windows. The main interface can be reconfigured through drag and drop actions. Once the interface has been configured, when the application is closed, the settings are saved. When the application is re-opened, the changes that were made become the new default until they are again changed by the user.

NOTE: As a result of the users ability to reconfigure the appearance of the interface, it should be noted that each users interface may differ in appearance. In addition, not all users will be able to see all aspects of the interface, nor will all features be present. This can be due to security restrictions; when a feature is not present, contact your administrator to verify that there are no restrictions in place.

Read More...

Mobile Users

Note: The current version of the mGovern is Release 6.0

mGovern – Your Mobile Solution provides a secure, user-friendly interface for: transferring property records from the office server to a mobile device; updating records in the field over a wireless connection or disconnected from the office server; and keeping records up-to-date and synchronized on both the mobile device and the office server. The mGovern UI provides the same user forms and features as Govern, such as the Govern Ribbon and Status Bar, Dataset tree view, forms, reports explorer, predefined searches. Plus, it has additional features to display connection status and information and error messages.

202-mGOV51_UI_ScrnCap001.png
mGovern 5.1 Ribbon Icons – Click image to open in new window.

For changes to the interface that are related to the Govern Mobile application, refer to the Govern Mobile release 6.0 user guide.

Interface Highlights

101-std-fea-001-GOV60-(UI Main-00)-[v6.0].png
Principal Areas of Govern 6.0 UI – Click image to open in new window.

As is standard for Govern applications, the version number and the name of the Connection Key that is used to access the database is located on the lower left hand side. On the lower right hand side is a status indicator for the Govern Global Message (E).

Principal Areas

The default interface consists of an application window that is divided into three (3) areas that are referred to as Panes (B,C,D), and a region called the Ribbon (A) that runs along the top.
Tabs indicating open Profiles (A) are found in the area below the Ribbon. Within Profile tabs are the workspace containing OpenForms (B), Tabbed Panes (D), and Auto-hide panes;
and Auto-hide panes (C); some auto-hide panes are referred to as Toolboxes.

101-std-fea-001-GOV60-(UI Main-PrinciplAreas01)-[v6.0].png
Principal Areas of Govern 6.0 UI – Click image to open in new window.

Tabbed Panes
In the interface, by default, a single pane can contain sub panes. The Forms Explorer, Reports Explorer, and the Dataset Treeview are panes, that by default, are accessed through tabs located at the bottom of the Explorer pane. The My Workload, and the Information and Predefined Queries panes, are by default accessed through tabs that are located below the ribbon. The Predefined Searches tab, is accessed through a tab that is located on the right hand side of the interface.
Auto-Hide Panes
Some tabbed panes are set to auto-hide, this means that they will appear when the mouse pointer is placed over them. If the pane is not selected and the mouse pointer is moved away from the vicinity of the pane, the window will recede back to the location of the tab.

NOTE: At times tabbed panes may not recede back to their original location when the mouse pointer is no longer in the vicinity of the tab. When this occurs, moving your mouse pointer over another tabbed pane will force the pane to recede.

The position of tabbed panes can be modified through a series of guides that are part of the interface. See The Explorer panes. The Ribbon can also be modified through floating menu options. See Pane Options Button for details on pane menus and buttons.
Registry Manager
The Registry Manager form contains User Registry parameters that are used to modify elements of the Govern user interface. Modifications include control of the maximum numbers of search records retrieved, and the behavior of Global Message notifications.

Common Features

Visual Notifications

In Govern there are visual cues that are presented to the user that indicate the status of their data. These cues appear in the form of colored dots or borders at various locations within the application. The grid below contains a list of the types of visual cues that are observed. Samples are observed after the table below.

Type Color Location Description
Dot Red On a form
tab
Error in a Validation or a Query on a
form. A modifications has occurred
Dot Blue End of form
field
The field is required.
Border Blue Form field This is an indication that this is the
current, active field.
Border Yellow Form field The field contains “Dirty” data; i.e. the
information has not been saved.”
Border Orange Form field Warning; unsaved change.
Border Red Form field Error in validation on query or form.

Modified Forms (Red Dots)
In the application, the red dots that appear on the tabs within a profile. An entity within the current form has been modified, but has not yet been saved. When changes to the form have been saved, the red dot indicators will disappear as confirmation.
Field Indicators
Modifications made to a field, e.g. a change to a value, cause the field in question to be highlighted with a yellow colored border. Note the fields that appear with a Red border. These fields are in an error state, either as a result of a validation or a query.
Date / Time Picker
In Govern, a Date /Time Picker is used to select a date and time. Click the Calendar icon that appears within a parameter to select a date from the drop-down menu (A). This displays the calendar; if the current date and time are required, click on the highlighted blue current date. To navigate to future or past dates, click the year at the top of the calendar (B). Alternatively, you may also use Forward and Backwards navigation arrows on the top of the calendar (C).

101-std-fea-001_GOV60-(UI DatePickr-01b)-[v6.0].png
Govern 6.0 Date / Time Picker – Click image to open in new window.

 

The Ribbon

The Govern Ribbon consists of menu tabs that allow you to configure the application through principal areas of the program.

  • Home – Access to applications settings, system clipboard, and system flags.
  • View – Display Govern panes and embedded applications.
  • Options – Control Query results and modify interface appearance.
  • Tools – Access MS Govern .NET applications and other configured external applications.
  • Batch Process – This menu tab will provide access to Govern batch processes.

Home tab

Global Information group

Fiscal Year – This is the Current Year (CurrentYear) or fiscal year that is used by the department. This is the Current Year as determined by a setting requested by the user; this value can be changed.
Each department within an organization may have to define and work in a different fiscal year. For example, Building Department profile users can work in the current calendar year when maintaining data on Permits and Licenses, Tax Collection department users work with data from the previous year, but Property Assessment department profile users may have to create appraisals for a future year.

NOTE: This field must be modified manually when the department changes to a new fiscal year. See Fiscal Year in the GNA guide.

The Fiscal Year parameter is found under the Home tab of the Ribbon; if not visible, the ribbon is probably minimized. Right click and select the Minimize Ribbon option. See Minimizing the Ribbon.

Change Fiscal Year (Current Year)

Unlike previous releases, the Fiscal Year can no longer be changed in the ribbon. The Fiscal Year can be changed in the History Panel.

Global Messages group

The Global Messages group allows the creation of Global or Department messages that will be displayed when a selected record is accessed. Previously the messaging system was based upon a PARCEL ID (P_ID). This current implementation of the messaging system is based upon both the USERID and the Parcel ID (P_ID) for greater flexibility. For example in the Self Reported Tax (ST) module, a notice of delinquency message can now be sent to the account holder by associating the message with the USERID.
This functionality replaces the Global or Department Flag.

Global Messages

Click Global Messages to create and attach a message to a current record or dataset. The message is created in the Global Message form. These messages can be assigned a priority and made private to a department or a primary key.

Explorer Panes

To work in Govern, you will need to open one or more profiles. The Explorer Pane is the area to view the contents, or OpenForms, of an open Profile. The Profile will contain OpenForms, Reports, and Datasets. For details about Profiles, see Profiles.

Govern Pane Buttons

Although the Forms Explorer is being used in the following examples, the procedures may also be applied to the Dataset Treeview and the Reports Explorer.
On the title bar of the Forms Explorer are buttons that allow you to change the appearance of the Govern Security Manager interface.

Pane Options Button

Click on the triangular icon of the Pane Options button, or right-click anywhere along the title bar of the pane to display menu options.
Some view options available in the Pane Options Menu can be achieved by dragging the pane title bar and dropping it on a Diamond Docking Guide.

Floating

Select this option to display the pane as a floating window.

Displays

Widescreen Displays and Dual Monitors

If your system is configured with a widescreen display or you are working with dual monitors. You can take advantage of your extended desktop setup by using the Floating option for some of your panes.
To restore a floating window to its last configuration, double-click on the title bar of the floating window.

Dockable:

This is the default option; select this option to keep the panes in a docked configuration.
Tabbed:
The tabbed option is not used in Govern and so cannot be selected.
Auto Hide:
Select the Auto Hide option to dock the pane to the left hand side of the interface. The pane can now be activated by hovering the mouse over the tab (A). To restore it to its previous view, when the pane is open, reselect the Auto Hide option.
Selecting Auto Hide is the same as selecting the “pin” button on the title bar of the pane. See The Pin Button.

  1. To restore the pane to the Dockable view when Auto Hide is selected…
  2. Hover your mouse pointer over the tab on the left hand side of the window to display the pane.
  3. Right-click on the title bar and select Auto Hide.

Hide:

This option will hide the Forms Explorer pane.

  1. To select the Hide option…
  2. Right-click on the Forms Explorer tab.
  3. On the floating menu, select Hide.

When the Forms Explorer is hidden, it can be restored with a click on Forms Explorer in the View section of the Ribbon (A).
The above procedure will also reopen the Object Explorer when it has been accidentally closed.
When the Auto Hide option is selected and the pane is open, you can make the pane recede back into the tab by performing the following action, click to activate the title bar of the open pane, then click anywhere within another open pane.

The Pin button

The pin button collapses a pane and attaches it to the bottom or the side of the interface. If selected, the pin icon will appear horizontal. When you click the pin button, the pane will take on the behavior of the Auto Hide option. See Auto-hide
for details. To restore the pane to its previous view, hover the mouse over the tab, when the pane opens, click the pin to turn off the option.

Dockable Windows

Reconfiguring Panes

Panes are re-configured by dragging their title bars from one location, and dropping to another. When you drag a title bar, you will observe a Pane Preview, i.e. a transparent representation of the window pane that is being dragged. In addition an overlay of icons appear, this overlay is referred to as a Diamond Docking Guide.
When dropping the Pane Preview on one of the icons of the Diamond Docking Guide, ensure that you position your pointer directly on top of the desired icon.

The Diamond Docking Guide

Dragging a Pane Preview to a location with a Diamond Docking Guide, the pane can be positioned in one of five (5) central icons, top, bottom, left, right, and center.
In addition, there are four (4) Periphery Icons within the application window that the pane preview can be dropped onto; they are located on the top, bottom, left, and right. When a pane preview is dropped on any one of these periphery icons, the dragged pane will be placed in a position that is relative to the entire application window.

Repositioning Panes

As you drag a pane to a new location, a Pane Preview and the Diamond Docking Guide can appear in various locations. When your application window has 2 or more panes, each time you move the pane preview over any one of the panes, a Diamond Docking Guide will appear. You will notice that the five (5) position central icon appears over the active pane, and the four (4) position periphery icons always appear relative to the application window.
Placing the Pane Preview over one of the five (5) central icons will reposition the window within the pane that the central icon is located in.

Repositioning a Pane within a Pane

To reposition the Reports Explorer pane within another pane…

  1. Drag the title bar of the Reports Explorer pane from its original location.
  2. While dragging the pane, the Diamond Docking Guide will appear (A) in the center of the interface.
  3. Place your pointer over the number “2” position, you will notice a dark preview that indicates where the new pane will be located; release the mouse button.

In some instances, should a pane preview be placed on the number “5” position of the central icons, then the repositioned pane will be tabbed with the existing pane.

The number 5 position has been disabled for Govern so a pane preview cannot be tabbed in the center pane. What will occur is the repositioned pane will become a floating window.
When a pane has been changed to a floating window, you can double-click on the new windows title bar to return it to its previous configuration.

Removing an Explorer Pane

As individual departments have specific tasks, they may not necessarily require the same configuration. Some departments may not require access to reports, and as a result they may simply want to remove the Reports Explorer to minimize clutter.
To remove the Reports Explorer pane in the View tab (A)…

  1. Click the tab that represents the Reports Explorer pane.
  2. When the pane appears, click the Close icon, the “X” in the upper right hand corner of the pane.

The Reports Explorer pane will remain closed until it is reopened, this includes closing and reopening the application.

Reopening Closed Explorer Panes

To reopen the Reports Explorer…

  1. On the Ribbon, click the Views tab.
  2. In the View group, click Reports Explorer.
  3. When reopened, the Reports Explorer will appear in the position it occupied before being closed.

The above steps may also be used to reopen the Forms Explorer and the Dataset Treeview panes.

Forms Explorer

To display the OpenForm in the Forms Explorer (A), double-click on the icon. The form will appear on the right hand side in the OpenForm area (B).
There may be a slight delay between the initial click on the icon and the appearance of the form. This delay is a function of your connection speed to your database, and/or network traffic.
To open an OpenForm…

  1. In an open profile, click to select the Forms Explorer tab along the bottom of the pane (A).
  2. In the Forms Explorer pane, you will see the OpenForms that are attached to this profile.
  3. Right-click on the OpenForm name or icon; select Open from the floating menu.

As with opening a Profile, there may be a slight delay between the initial click on the icon and the appearance of the OpenForm. This delay is a function of your connection speed to your database, and/or network traffic.

Tab Navigation Controls

When an OpenForm appears with multiple tabs and sub tabs, a new tab with navigational buttons will appear at the far right hand side of the active tab. See OpenForms Tab Navigation Control on page.

Reports Explorer

Depending on requirements, some Profiles may be configured with reports. For example, a Business Model designed for permitting could be configured with reports that can list owners, list expired permits, or generate renewal letters.
Reports that are available in the profile can be viewed in the Reports Explorer.

Viewing Available Reports

Reports are presented in a treeview format; most reports are seen at the top level. Occasionally you will see reports presented as report groups that can be expanded with a click on the [+] to expand and on the [-] to collapse.
To view the list of available Reports in an open Profile…

  1. Click to select the Reports Explorer tab.
  2. In the Reports Explorer pane, you will see the list of available reports.
    If the reports are in groups, click on the [+] to expand the group and view the report.

Profiles in Govern

The Profiles in Govern are the equivalent of a department in an office. Within this department are the tools for performing the job that is required of the department. The OpenForms and Reports that are displayed are the ones that have been assigned to the Profile in the Govern NetAdmin (GNA). For example a profile for the Building department might contain OpenForms for Building Permits, Complaints, General Permits, Grievances, Offences, Inspections, and Property Information. When this profile is being configured in GNA, the aforementioned OpenForms would be added. See Creating a New Profile in the Profile Editor section of the Govern Net Admin guide.

NOTE: Multiple profiles and multiple instance of a profile can be opened by a user, as long as they have been given access privileges to them.

Opening a Profile

To open a Profile or an instance of a Profile…

  1. Click the Govern Application Option button in the upper left hand corner of the application window.
  2. Select a Profile under the All Profiles list; for this example we will use a profile that is designed for maintaining parcel information – Parcel Maintenance.

When the profile is open, its name will appear on the tab preceded by a number; this is the Instance Number. When multiple instances of the same profile are open, each successive tab will bear a number that is incremented by one.

Closing a Profile

A Profile can be closed at two (2) locations, directly on the profile tab, or through the Govern Suite button.
To close a Profile…

  1. Locate the tab for the profile and click on the Close button “x”.
NOTE: When you have multiple instances of a Profile ensure that the profile that you are close is the correct instance

OR

  1. Click to select the Profile tab that you would like to close (B).
  2. Click on the Govern Suite button; select Close Profile.

 

Maximizing a Form

Users that have multiple profiles open, may periodically need to display one specific profile; ideally it is best to maximize this profile. This is accomplished by “undocking” the form. This option is available under the Options (tab).

To Maximize a form…
1. Click on tab of the profile that is to be maximized.
2. Select Options (tab) > Options group…
3. Click Maximize. (Alternatively click F11 on the keyboard).

To restore a Maximized form…
1. On the Upper Right Hand side of the window, click the triangular arrowhead to display the menu
2. Select the “Dock” option.
OR
1. Double click on the title bar of the Window.

To close a maximized OpenForm…
1. Click the X in the upper right hand corner of the window.

NOTE: Should you unintentionally close the profile form, you can re-open it from the Dataset Treeview pane. Expand the record with a click on the arrow beside the record. In the expanded list of forms, select the required form.

What’s New

Below is a list of new User Interface enhancements.

Enhancement to behavior of Maximize (F11)

Available in Release 6.0.1611.0141 / 6.0.1702.0191 / 6.1.1611.0124 / 6.1.1702.0332
In Govern, when a form is Maximized using the Maximize feature, Govern ribbon > Options (tab) > Maximize (F11), the active form is presented in full screen mode, all other forms are hidden, and the Toolbar and Ribbon are minimized. Users can encounter issues when the maximized form contains a link that will open another form. When the user clicks the link, the target form is not immediately accessible. The workaround has been to exit the Maximized screen, or minimize it in order to access the linked form. An enhancement has been implemented that will allow the user to quickly access screens that have been opened from a link with the F11 key.
Refer to the document below for details.
101-Techno_Access_Linked_Form_from_Maximized_Screen(Enhancement).pdf

 

 

101-std-fea-001

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.
Loading...

ST – Business Tax – Filings

Self Reported Business Tax – Filings

Overview

Under the Business Tax Filing tab, the Filing Information sub tab is used to enter collection information, to view totals, interest payments, and levies for each Business Tax record. The Filing Information tab may also be referred to as the Business Tax Data Entry form.

Display A/R Information by Period

By default the information that is displayed under the Self-Reported Tax Filing tab > A/R Information group, is obtained from (Table: ST_FILING_MASTER). When a filing is posted, by default, the A/R Information is displayed by AR_ID. In Govern for .NET, when required, the Display by Period option, when selected will display balance information by the ST_ID. Deselect the option to view the balance by the AR_ID. See Self-Reported Business Tax Display A/R by Period

Group Adjustment (All Years)

This enhancement was released in version 6.1.1706.
There is a functionality in the Govern A/R Inquiry form that allows the user to reverse for a parcel, multiple transactions for multiple years with a single process. See A/R Group Adjustment (All Years)

Allow Creation of Negative Levies

This enhancement was released in version 6.0.1702 / 6.1.1702.
Enabling this option will allow users to enter a negative amount in the Self Reported Tax Filing Information form, thereby creating a negative levy. When the return is posted to the A/R the levy will be created as a negative invoice which will credit the balance. See the user documentation below for details.
101-st-fea-009_Allow_Creation_of_Negative_Levies.pdf

SRT Transfer Filing

This enhancement was released in version 6.0.1605 / 6.0.1605 (June 2016).
When users erroneously file under the wrong period, there was no straightforward process available to transfer the filing. The Govern system now allows a transfer to any Unfiled Filing Period with the same Category. Refer to the document below for details.
101-st Allow Creation of Negative Levies.pdf

See also

 

 

101-st-frm-002

 

[rating]

MA – Compute Building Value

CAMA Building Value Computation

General Purpose

The purpose of the Building Computation is to provide values of all the Govern’s system columns for a given record of the table MA_BUILDINGS_XX. The ultimate goal of this compute is to provide a building value (the cost for a building structural elements) based on building’s physical characteristics (called structural elements). [VB6 class name: GvObjCostComp OF:MACostComp.cls]

Important Notes RE: the Computation

Auto Select Unique Code:

When only one code is available and the Auto Select Unique Code option is selected, that code is used for the compute. This applies regardless of what the user has previously selected.
It applies, for example, if the code is changed in GNA, after the user set the code on the form. The update is made when either the property record is opened and resaved or the Mass Appraisal Compute batch process is run.

Is Required:

If you select the Is Required option for a code after the user has created property records, you must verify that a code is selected for those records. Otherwise, an error is raised and the compute fails.

Parameters

General Parameters (SY REGISTRY by YEAR)

  • QP_ROUNDING = “Mass Appraisal”, “Quality Point Rounding” = (‘yes’ or ‘no’)
  • QP_DECIMAL = “Mass Appraisal”, “Quality Point Decimal”
  • USE_BASE_AREA_FOR_LOOKUP = “Mass Appraisal”, “Bldg Lookup By Base Area” = (‘yes’ or ‘no’)
  • ROUND_UP_AREA = “Mass Appraisal”, “Round Up Area” = (‘yes’ or ‘no’)
  • EFFECTIVE_LIVING = “Mass Appraisal”, “Effective = Living” = (‘yes’ or ‘no’)
  • “Mass Appraisal”, “Size Adjt Method”
  • CAMA_ADJ_DECIMAL = “Mass Appraisal”, “Cama Adjustment Decimal”
  • “Mass Appraisal”, “Size Adjt. Decimal”
  • SE_BY_MODELS = “Mass Appraisal”, “Associate SE to models” = (‘yes’ or ‘no’)
  • SE_BY_MODELS_YEAR = “Mass Appraisal”, “Associate SE to models Year Effective”
  • SQUARE_ROOT = “Mass Appraisal”, “Area In Square Root” = (‘yes’ or ‘no’)
  • “Mass Appraisal”, “Property Type From pc_legal_info” = (‘yes’ or ‘no’)
  • USE_METRIC = “General”, “use metric” = (‘yes’ or ‘no’)
  • SIZE_ADJ_METHOD = “Mass Appraisal”, “Size Adjt Method” = (‘1’ or ‘2’)
  • SIZE_ADJ_DECIMAL = “Mass Appraisal”, “Size Adjt. Decimal” default 3
  • PROPERTY_TYPE_FROM_PC_LEGAL = “Mass Appraisal”, “property type from pc_legal_info” = (‘yes’ or ‘no’)

Parameters discontinued in Govern OpenFroms 6.1.

  • “Mass Appraisal”, “Compatibility SE Compute”
  • “Mass Appraisal”, “Compatibility SE Compute Year Effective”
  • “Mass Appraisal”, “Optimize Computation Speed”
  • “Mass Appraisal”, “Round by Drawing Code”
  • “Mass Appraisal”, “Skip Rates Interpolation”

Changed Parameters

  • DEPR_BASE_YEAR=Year value (ex:2015), “Depreciation Year” should now be using the registry by year under “Mass Appraisal”

 

Tables and Fields

Tables

  • MA_BUILDINGS (includes old MA_BLDG_INFO)
  • MA_BLDG_AREA_YEAR (replaces old MA_BLDG_AREA)
  • PC_AREA.NBHD NOTE: At a minimum the PROPERTY_TYPE column has to be available to the building context, but ideally all columns of PC_LEGAL_INFO (to validate)
  • PC_LEGAL_INFO.PROPERTY_TYPE (same NOTE)
  • MA_BUILDINGS. BLDG_ID + BLDG_SEQ -> PC_LK_PARCEL_BLDG.P_ID
  • PC_LK_PARCEL_BLDG.P_ID -> PC_AREA.P_ID
  • PC_AREA.NBHD -> MA_PARM_NBHD.NBHD_CODE
  • MA_BUILDINGS.BLDG_USE_CODE -> MA_PARM_BLDGUSE.BUSE_CODE
  • MA_BUILDINGS.SUBMODEL_CODE -> MA_PARM_SUBMODEL.SUBMODEL_CODE
  • MA_BUILDINGS.BLDG_MODEL_CODE -> MA_PARM_DRAWING.BLDG_MODEL_CODE MA_BUILDINGS.SUBMODEL_CODE -> MA_PARM_DRAWING.SUBMODEL_CODE
  • MA_BUILDINGS.BLDG_MODEL_CODE -> MA_PARM_SE_MODELS.BLDG_MODEL_CODE
  • MA_BLDG_AREA_YEAR. AREA_CODE-> MA_PARM_DRAWING.BLDG_AREA_CODE
  • MA_BUILDINGS.YEAR_ID -> MA_MODIF_STAMP.YEAR_ID

Parameter Tables

  • MA_TABLES.TABLE_CATEGORY = “bldg”
  • MA_PARM_MAROUND.ROUNDING_CODE = “bldg” for the building value
  • MA_PARM_MAROUND.ROUNDING_CODE = “area” for the areas (building dimensions)
  • MA_PARM_MAROUND.ROUNDING_CODE = “look” for the areas used in lookups

Calculated Fields
The following system columns cannot be used in expressions stored in the MA_PARM tables nor should they be editable.

  • TOTAL_BASE
  • TOTAL_ACTUAL
  • TOTAL_EFFECTIVE
  • TOTAL_LIVING_AREA
  • TOTAL_HEATED
  • TOTAL_PERIMETER
  • TOTAL_RCN
  • TOTAL_RCNLD
  • TOTAL_VALUE
  • SITE_ADJ_TOTAL
  • NBHD_ADJ_TOTAL
  • FINAL_ADJ

Lookup Group
Many of the parameters used in the building computation depend on a lookup group. All the lookup groups are stored in the table MA_LOOKUP_GROUP and can be can be of the following types:

  • By neighborhood
  • By property type
  • By income neighborhood
  • By jurisdiction
  • By jurisdiction AND neighborhood
  • By jurisdiction AND income neighborhood
  • By jurisdiction AND property type

Look-up Group Example

We have a building record for the year 2015 with BLDG_USE_CODE = “45”. We want to get a BSE element which is defined in the table MA_PARM_SETAB where the table name is “EXTWALL” and the primary key contains the SE_CODE and LOOKUP_GROUP. We already have the YEAR_ID and the SE_CODE ( “45”) but now we need the lookup group.

Next, we go to the table MA_LOOKUP_GROUP and get all the records with TABLE_NAME=”EXTWALL”, YEAR_ID=2015 and CAMA_CODE=”45”. In our example, this lookup group is by jurisdiction and neighborhood so it will look like this:
LOOKUP_GROUP JURISDICTION NBHD
0 Null Null
1 31572 Null
2 31572 015
3 31572 016
4 31513 Null
5 31513 012

Here are some possible scenarios depending on the jurisdiction and neighborhood for the land record:
If Jurisdiction=31572 and Nbhd=015, then Lookup_Group=2
If Jurisdiction=31572 and Nbhd=020, then Lookup_Group=1
If Jurisdiction=45875 and Nbhd=015, then Lookup_Group=0

Properties required to get the lookup group
The following information is required to use the lookup group:

  • Jurisdiction:Use PC_PARCEL.JURISDICTION based on MA_LAND.P_ID = PC_PARCEL.P_ID.
  • Neighborhood and Income neighborhood: Use PC_AREA.NBHD and PC_AREA.INC_NBHD based MA_LAND.P_ID = PC_AREA.P_ID and _MA_LAND.FROZEN_ID = PC_AREA.FROZEN_ID.
  • Property type: Use MA_PARM_BLDGUSE.PROPERTY_TYPE based on MA_BUILDINGS.BLDG_USE_CODE = MA_PARM_BLDGUSE.BUSE_CODE and MA_BUILDINGS.YEAR_ID = MA_PARM_BLDGUSE.YEAR_ID. If no information is found in MA_PARM_BLDGUSE then we’ll use a blank property type (15 spaces). This is a table that depends itself on a lookup group. If the lookup group is by property type then for the purpose of the lookup we must use the PROPERTY_TYPE defined in PC_LEGAL_INFO.PROPERTY_TYPE.

 

Step 1 – Compute the areas

For each record in MA_BLDG_AREA_YEAR, based on the field BASE_AREA, using the percent values from MA_PARM_DRAWING (by searching with the AREA_CODE and lookup by MODEL/SUBMODEL if used):

a) Calculate the areas

Calculate the actual, effective, heated and perimeter area.

  • MA_BUILDINGS.TOTAL_BASE = the total of all MA_BLDG_AREA_YEAR.BASE_AREA

 

  • MA_BLDG_AREA_YEAR.EFFECTIVE_AREA = MA_BLDG_AREA_YEAR.BASE_AREA * Expression content [MA_PARM_DRAWING. EXPRESSION] * Expression content [MA_PARM_DRAWING.EFFECTIVE_EXPESSION] / 10000
    • If USE_METRIC we round to 1 decimal otherwise we round to 0 decimal

 

  • MA_BLDG_AREA_YEAR.ACTUAL_AREA = MA_BLDG_AREA_YEAR.BASE_AREA * Expression content [MA_PARM_DRAWING. EXPRESSION] / 100
    • If USE_METRIC we round to 1 decimal otherwise we round to 0 decimal. MA_BUILDINGS.TOTAL_ACTUAL = the total of all MA_BLDG_AREA_YEAR.ACTUAL_AREA

 

  • MA_BLDG_AREA_YEAR.LIVING_AREA = MA_BLDG_AREA_YEAR.ACTUAL_AREA
    • if MA_PARM_DRAWING.LIVING_AREA = -1 otherwise = 0
  • MA_BUILDINGS. TOTAL_LIVING _AREA = the total of all MA_BLDG_AREA_YEAR. LIVING _AREA
  • If EFFECTIVE_LIVING = “yes” then
    • MA_BUILDINGS.TOTAL_EFFECTIVE = the total of all MA_BLDG_AREA_YEAR. LIVING _AREA

 

  • MA_BLDG_AREA_YEAR.HEATED_AREA = MA_BLDG_AREA_YEAR.ACTUAL_AREA
    • if MA_PARM_DRAWING.HEATED = “yes” = MA_BLDG_AREA_YEAR.ACTUAL_AREA * MA_BLDG_AREA_YEAR.PERCENT_HEATED
    • if MA_PARM_DRAWING.HEATED = “partial” or = 0 if MA_PARM_DRAWING.HEATED = “no” MA_BUILDINGS. TOTAL_HEATED = the total of all MA_BLDG_AREA_YEAR. HEATED_AREA

 

  • MA_BUILDINGS. TOTAL_PERIMETER = the total of all MA_BLDG_AREA_YEAR. PERIMETER

 

b) Cumulate the building areas by type

This steps cumulates the areas by area type (i.e. Basement, Garage, Porch, 1st Floor … Attic, etc.). The Building Drawing Table Option By Area Type must be turned on where each drawing code can be associated to an area type. When none define, the Area Type ‘E’ Effective is used by default. When the Drawing Area Code Option Do not xxxx is turned on, the area is not added to the Effective or Area Type totals (i.e. for perimeter consideration only).

  • Cumulate the values in a collection by MA_PARM_DRAWING.AREA_TYPE (if NULL use the default ‘e’) if MA_PARM_DRAWING.EX_FROM_LOOKUP = 0 or NULL.
  • The collection is indexed by AREA_TYPE and contains the following variables:
    • TOTAL_EFFECTIVE = sum of all MA_BLDG_AREA_YEAR.EFFECTIVE_AREA per AREA_TYPE
    • TOTAL_FOR_LOOKUP = sum of all MA_BLDG_AREA_YEAR.EFFECTIVE_AREA per AREA_TYPE if USE_BASE_AREA_FOR_LOOKUP = “no” else sum of all MA_BLDG_AREA_YEAR.ACTUAL_AREA per AREA_TYPE if USE_BASE_AREA_FOR_LOOKUP = “yes”
    • TOTAL_RATE = 0 (will be use in the next steps)
    • TOTAL_VALUE = 0 (will be use in the next steps

c) Add the areas to TOTAL for Lookup
Cumulate the values of all TOTAL_FOR_LOOKUP into a variable GRAND_TOTAL_FOR_LOOKUP for use later in the compute.

Step 2 – Round and Update Areas

Round and update area fields in MA_BUILDING (see Rounding Table)

a) Rounding by Area type

  • Round each element of the collection created in step 1 for TOTAL_EFFECTIVE by using MA_PARM_MAROUND.ROUNDING_CODE = “area” and evaluating the Expression content [MA_PARM_ROUNDING.ROUND_TO_EXPESSION]. The rounding is performed by dividing TOTAL_EFFECTIVE by the ROUNDING_VALUE, by adding 0.4999999999999 if ROUND_UP_AREA = “yes”, by formatting the result to no decimal and then by multiplying back by the rounding value. If SQUARE_ROOT = “yes” then do a square root on TOTAL_EFFECTIVE.

b) Rounding by Total

  • Round each element of the collection created in step 1 for TOTAL_FOR_LOOKUP by using MA_PARM_MAROUND.ROUNDING_CODE = “look” and evaluating the Expression content [MA_PARM_ROUNDING.ROUND_TO_EXPESSION]. The rounding is performed by dividing TOTAL_FOR_LOOKUP by the ROUNDING_VALUE, by adding 0.4999999999999 if ROUND_UP_AREA = “yes”, by formatting the result to no decimal and then by multiplying back by the rounding value. If SQUARE_ROOT = “yes” then do a square root on TOTAL_FOR_LOOKUP.

c) Grand Total Rounding

  • Round GRAND_TOTAL_FOR_LOOKUP by using MA_PARM_MAROUND.ROUNDING_CODE = “look” and evaluating the Expression content [MA_PARM_ROUNDING.ROUND_TO_EXPESSION]. The rounding is performed by dividing TOTAL_EFFECTIVE by the ROUNDING_VALUE, by adding 0.4999999999999 if ROUND_UP_AREA = “yes”, by formatting the result to no decimal and then by multiplying back by the rounding value. If SQUARE_ROOT = “yes” then do a square root on GRAND_TOTAL_FOR_LOOKUP.

 

Step 3 – Get Initial Building Rate Information

Building Area Rate

Get Building Rate Setup
Check Rate Setup and get the initial rate from the building use code and the default property type. To do so, need to get one record from MA_TABLES for table_type = ‘bldguse’ to see if there is a lookup by:

  • bldg_model (field setab_use_model = -1)
  • submodel (field setab_submodel = -1)
  • units (field use_units = -1)

Get Property Type

  • PROPERTY_TYPE = MA_PARM_BLGUSE.PROPERTY_TYPE
  • If PROPERTY_TYPE is NULL then get the property type from PC_LEGAL_INFO.

Get Initial Rate
The rate is established by getting MA_PARM_BLGUSE or MA_PARM_BRATE if the units are used).
The rate will be associated with the TOTAL_RATE collection created in step 2 based on MA_PARM_SE_AREA.AREA_TYPE. If no records found, use ‘e’ (Effective area) as AREA_TYPE.
Fixed Rate

  • If MA_TABLES.USE_UNITS is False, then get the rate from MA_PARM_BLGUSE by searching with MA_BUILDINGS.BLDG_MODEL_CODE and with MA_BUILDINGS.SUBMODEL_CODE– depending on the lookup found above. The rate is evaluated from an expression and stored in TOTAL_RATE of every elements in the collection indexed by AREA_TYPE.

Rate by Unit

  • If the MA_TABLES. USE_UNITS is True, than get a pro-rated rate form MA_PARM_BRATE by searching with MA_BUILDINGS.BLDG_MODEL_CODE and with MA_BUILDINGS.SUBMODEL_CODE – depending on the lookup found above. The Up_to_units area information (TOTAL_FOR_LOOKUP) is prorated based on the collection indexed by AREA_TYPE (Up_to_units >= TOTAL_FOR_LOOKUP) AND the value of AREA_TYPE for each entry found in MA_PARM_SE_AREA . The rate is evaluated from an expression and stored in TOTAL_RATE for the selected elements in the collection indexed by AREA_TYPE.

 

Building Use Depreciation Table

We need to store the depreciation table and the maximum depreciation percentage into variables for use later in the depreciation step (step 18).

  • DEPR_TABLE = MA_PARM_BLGUSE.DEPR_TABLE.
  • MAX_ DEPR_PCT = MA_PARM_BLGUSE.MAX_ DEPR_PCT.

 

Building Rate by Area Units Example

When MA_TABLES. USE_UNITS is True
Collection contains:
AREA_TYPE TOTAL_FOR_LOOKUP TOTAL_RATE
b 1000 0
l 2000 0
MA_TABLES has:
TABLE_NAME COMPUTATION_SEQ SETAB_USE_MODEL SETAB_SUBMODEL SETAB_USE_UNITS
bldguse 0 0 0 -1
MA_PARM_SE_AREA has :
COMPUTATION_SEQ AREA_TYPE
0 b
0 l
MA_PARM_BRATE has:
BUSE_CODE UP_TO_UNITS RATE
ms0001a 1000 20.50
ms0001a 3000 18.50
ms0001a 9999999 10.00
The collection will contain:
AREA_TYPE TOTAL_FOR_LOOKUP TOTAL_RATE
b 1000 20.5
l 2000 19.5 (pro-rated)

Step 4 – Structural Elements Values Calculation

This step gets and calculates all building structural elements that apply.It computes or evaluates all the XXX_VA, XXX_V2 columns based on the corresponding value of XXX_CD.

Auto Select Unique Code:
When only one code is available and the Auto Select Unique Code option is selected, that code is used for the compute. This applies regardless of what the user has previously selected.

It applies, for example, if the code is changed in GNA, after the user set the code on the form. The update is made when either the property record is opened and resaved or the Mass Appraisal Compute batch process is run.

Is Required:

If you select the Is Required option for a code after the user has created property records, you must verify that a code is selected for those records. Otherwise, an error is raised and the compute fails.

Parameters

Structural elements can be associated to:

  • Property type
  • SE models (based on the registry SE_BY_MODELS and SE_BY_MODELS_YEAR which determines the effective year)

Structural Elements in MA TABLE
Get all the structural elements records from MA_TABLE for the year, having TABLE_TYPE = ‘setab’ AND MA_TABLES.setab_rd_code <> ‘h’.

  • If they are associated to the SE models then join with the table MA_PARM_SE_MODELS and filter on MA_BUILDINGS.BLDG_MODEL_CODE,
  • if not then use PROPERTY_TYPE (Step 3) that match MA_TABLES.PROPERTY_TYPE or MA_TABLES.PROPERTY_TYPE = NULL.

Computation Sequence
The records will be ordered by COMPUTATION_SEQ.

* Use this set of records within the steps below *

Query Sample if Associated to SE Models

  • SELECT ma_tables.* FROM ma_tables, ma_parm_se_models WHERE ma_tables.year_id = ma_parm_se_models.year_id AND ma_tables.column_name = ma_parm_se_models.column_name AND ma_tables.computation_seq = ma_parm_se_models.computation_seq AND table_type = ‘setab’ AND setab_rd_code <> ‘h’ AND ma_tables.year_id = 2015 AND bldg_model_code = ‘ms0009’ ORDER BY ma_tables.computation_seq

 

MA Building Records Calculation

Each of the records will be treated separately, in order to find the value to be updated in MA_BUILDINGS for the corresponding XXX_VA field of the MA_TABLE.COLUMN_NAME, using the XXX_CD field value set in MA_BUILDINGS.

a) No Table Name

If there is no MA_TABLES.TABLE_NAME and the value into the corresponding _CD field is numeric, it will be transferred into the _VA field, otherwise XXX_VA is set to NULL.

b) No Table Name and Setab Col 11 = -1

If there is no MA_TABLES.TABLE_NAME and MA_TABLES.SETAB_COL_11 = -1 then XXX_V2 is set to NULL.
The next sub steps are only performed when there is a MA_TABLES.TABLE_NAME

c) Get MA_PARM_SETAB

Based on:

  • bldg_model_code (if MA_TABLES.setab_use_model = -1 – lookup by model)
  • submodel_code (if MA_TABLES.setab_submodel = -1 – lookup by submodel)
  • matrix_code (if MA_TABLES.setab_use_matrix = -1 – then retrieve another MA_TABLES record that will provide the MA_TABLES.COLUMN_NAME based on MA_TABLES.COMPUTATION_SEQ = MA_TABLES.setab_seq_pointer.
    • The matrix code value is found in MA_BUILDINGS.XXX_CD based on the retrieved MA_TABLES.COLUMN_NAME or in MA_BUILDINGS.XXX_VA if MA_TABLES.lookup_on_value = -1.
  • matrix_code2 (if MA_TABLES.setab_use_matrix = -1 – then use MA_TABLES.COMPUTATION_SEQ = MA_TABLES.setab_seq_pointer2.
  • matrix_code3 (if MA_TABLES.setab_use_matrix = -1 – then use MA_TABLES.COMPUTATION_SEQ = MA_TABLES.setab_seq_pointer3.
  • with up_to_units (if MA_TABLES.setab_area_lookup is set – lookup using the area collection, there are 3 area lookup types: a, p, t
    • ‘t’ (Grand Total) : use GRAND_TOTAL_FOR_LOOKUP
    • ‘a’ or ‘p’ : use the collection TOTAL_FOR_LOOKUP using AREA_TYPE = entry with the greater TOTAL_FOR_LOOKUP value in MA_PARM_se_area
    • ‘p’ : apply the percentage entered into the XXX_PC corresponding column in MA_BUILDINGS in order to reduce area if MA_TABLES.setab_col_3 = -1.
      • NOTE: If XXX_PC contains 50 then TOTAL_FOR_LOOKUP is 2000 then we use 1000 (50% of 2000).
      • Rates are always pro-rated between the UP_TO_UNITS as per example in step 3.

 

d) Evaluate MA_PARM_SETAB Expression

Evaluate the expression of MA_PARM_SETAB and store it in XXX_VA.

e) Rate Adjustment / Depreciation

If the Element Category of the record is Rate Adjustment (MA_TABLES.setab_rd_code = “r”)
AND there is a Depreciation Table set (field MA_PARM_SETAB.depr_table) then depreciation will be applied on the value (XXX_VA) as per below:

  • a. We get the DEPR_PCT
    • i. We determine the Appraisal base year APPR_BASE (registry DEPR_BASE_YEAR) using the current MA_TABLE.YEAR_ID
    • ii. MA_PARM_DEPR.TABLE_NAME = MA_PARM_SETAB.DEPR_TABLE
    • iii. We evaluate the MA_PARM_DEPR.NUMBER_OF_YEARS = FORMAT (APPR_BASE – MA_BUILDINGS.EYB to ‘000’). If negative we use 0. If MA_BUILDINGS.EYB is NULL we use MA_BUILDINGS.YEAR_BUILT.
    • iv. We evaluate the expression MA_PARM_DEPR.EXPRESSION
    • v. If MA_PARM_DEPR.EXPRESSION > MA_PARM_SETAB.max_depr_pct then the DEPR_PCT is MA_PARM_SETAB.max_depr_pct
  • b. We set the XXX_VA Value XXX_VA = XXX_VA * (100 – DEPR_PCT) / 100

 

f) Apply % to the Value

If a percentage is entered into the _PC corresponding column in MA_BUILDINGS (when MA_TABLES.setab_col_3 = “-1”) then apply the % (XXX_PC) to the value (XXX_VA).

g) Set MA_BUILDINGS.xxx_V2

If MA_TABLES.setab_col_11 = -1, Then
MA_BUILDINGS.XXX_V2″ = MA_PARM_SETAB.base_value.

Step 5 – Round and Compute Average

This step computes the average for all structural elements having equal consecutive MA_TABLE.TABLE_NAME with different MA_TABLE.COLUMN_NAME.
We exclude from this step all MA_TABLE.setab_col_3 = -1 or MA_TABLE.no_average = -1

  • Simply divide XXX_VA by the entry count and round to:
    • Case MA_TABLE.setab_rd_code
    • Case ‘q’ – IF QP_ROUNDING = ‘yes’ then round to QP_DECIMAL
    • Case ‘a’, ‘t’ – Round to CAMA_ADJ_DECIMAL
    • Case else Round to 2 digits.

If MA_TABLES.setab_col_11 = -1 Then perform the same logic for XXX_V2.

Example
MA_BUILDINGS
A1_VA= 16.445 A2_VA=20.555 A3_VA=2
MA_TABLES
COMPUTATION_SEQ TABLE_NAME COLUMN_NAME SETAB_COL_3
23 WALL A1 0
24 WALL A2 0
25 WALL A3 0
Results
A1_VA=16.445/3=5.48
A2_VA=20.555/3=6.85
A3_VA=2/3=0.67

Step 6 – Round and Compute Link

This step computes the linked values for all structural elements having MA_TABLES.setab_lk_pointer not NULL)

a) Loop in reverse order, from the last record to the first.
b) Depending on the field MA_TABLES.MATHS of each element having a link, its _VA field will be added, subtracted or multiplied to the _VA field of the linked computation sequence. For multiplication, if the MA_TABLES.PCT_AMT field is ‘p’ than the result will also be divided by 100 (Percent)
c) Set the value of XXX_VA to null
d) Case MA_TABLE.setab_rd_code

  • Case ‘q’ – IF QP_ROUNDING = ‘yes’ then round to QP_DECIMAL
  • Case ‘a’, ‘t’ then Round to CAMA_ADJ_DECIMAL
  • Case else then Round to 2 digits.

If MA_TABLES.setab_col_11 = -1 Then perform the same logic for XXX_V2.

Example
MA_BUILDINGS
A1_VA= 8 A2_VA=4
MA_TABLES
COMPUTATION_SEQ TABLE_NAME COLUMN_NAME MATH setab_lk_pointer (verify)
26 QUAL A1 X NULL
27 QMOD A2 + 27

A1_VA = 12
A2_VA = NULL

Step 7 – Adjust Areas

Scan the records of MA_TABLE and adjust the areas in the area collection (EFFECTIVE_AREA) for all entries MA_TABLES.setab_rd_code = “m”

Use the same logic as in STEP4 to select the MA_TABLES records.
Update the area collection (EFFECTIVE_AREA) by AREA_TYPE for all entries found in MA_PARM_se_area compute the EFFECTIVE_AREA collection.
if MA_PARM_se_area has no record found then use ‘e’.

  • Depending on MATHS, cumulate or multiply the value from column_VA to the EFFECTIVE_AREA collection based on MA_PARM_se_area .area_type
  • If the _V2 column is used, cumulate also the value from column_V2

 

Step 8 – Override Areas

Scan the records of MA_TABLE and override the areas in the area collection (EFFECTIVE_AREA) for all entries MA_TABLES.setab_rd_code = “s”

Use the same logic as in STEP4 to select the MA_TABLES records.
If MA_PARM_se_area has no record found then use ‘e’.

  • For all entries found in MA_PARM_SE_AREA move the XXX_VA to the corresponding EFFECTIVE_AREAcollection.

 

Step 9 – Adjust Rates

Scan the records of MA_TABLE and adjust the rates in the rate collection (TOTAL_RATE) for all entries MA_TABLES.setab_rd_code = “r” (VB6 : pv_scan_ma_table, pv_set_rate_tab)

Use the same logic as in STEP4 to select the MA_TABLES records.
Update the rate collection (TOTAL_RATE) by AREA_TYPE for all entries found in MA_PARM_se_area compute the TOTAL_RATEcollection.

  • if MA_PARM_se_area .AREA_TYPE = “e” (Effective Area) or no record found, then, depending on MATHS, cumulate or multiply the value from column_VA to all the areas within the collection, otherwise apply it only to the area_type corresponding to the area set in MA_PARM_se_area.

 

  • If the _V2 column is used, cumulate the value from column_V2Into a variable (grand_total_amount_adj_add) used below for CAMA adjustments.

 

Step 10 – Compute Size Adjustment

Compute the size adjustment variable (Govern for Windows: pv_compute_size_adjt).
A size adjustment is an adjustment to the rate based on the value of the TOTAL_EFFECTIVE collection.

Notes

Auto Select Unique Code: When only one code is available and the Auto Select Unique Code option is selected, that code is used for the compute. This applies regardless of what the user has previously selected.
It applies, for example, if the code is changed in GNA, after the user set the code on the form. The update is made when either the property record is opened and resaved or the Mass Appraisal Compute batch process is run.
Is Required: If you select the Is Required option for a code after the user has created property records, you must verify that a code is selected for those records. Otherwise, an error is raised and the compute fails.

1. Get the MA_PARM_SIZEADJT entry for MA_BUILDINGS.BLDG_MODEL_CODE
2. If a record is not found then there is no size adjustment. Go to step 11.
3. If MA_PARM_SIZEADJT.SETAB_AREA_TYPE is NULL or = ‘e’ then we use MA_BUILDINGS.TOTAL_EFFECTIVE as the area value for the next sub steps, otherwise we use the TOTAL_EFFECTIVE collection item that match the area type. If the area value is 0 we go to step 11.
4. We evaluate the expression in MA_PARM_SIZEADJT.EXPRESSION and if the result is not zero then we set this value into MA_BUILDINGS.SIZE_ADJUSTMENTS and go to sub step 8.
5. if SIZE_ADJ_METHOD is Method 1 then the size adjustment is:

  • MA_BUILDINGS.SIZE_ADJUSTMENTS = ( MA_PARM_SIZEADJT.building_size * MA_PARM_SIZEADJT.land_bldg_ratio / area_value) + (1 – MA_PARM_SIZEADJT.land_bldg_ratio)
    • If MA_BUILDINGS.SIZE_ADJUSTMENTS < MA_PARM_SIZEADJT.MINIMUM_RATIO then we reset the size adjustment to the minimum.
    • If MA_BUILDINGS.SIZE_ADJUSTMENTS > MA_PARM_SIZEADJT.MAXIMUM_RATIO then we reset the size adjustment to the maximum.

6. if SIZE_ADJ_METHOD is Method 2 then the size adjustment is:

  • If the area value < MA_PARM_SIZEADJT.MINIMUM_RATIO then we reset the area value to the minimum.
  • If the area value > MA_PARM_SIZEADJT.MAXIMUM_RATIO then we reset the area value to the maximum.
  • MA_BUILDINGS.SIZE_ADJUSTMENTS = (area_value – MA_PARM_SIZEADJT.building_size) * MA_PARM_SIZEADJT.land_bldg_ratio

7. We round the size adjustments to the number of decimal positions as per the SIZE_ADJ_DECIMAL value.

8. If the size adjustment is for area type NULL or ‘e’ then we apply the following logic to ALL elements of the collection. If SIZE_ADJ_METHOD is Method 1 we multiply the rounded size adjustment by the rate found in the TOTAL_RATE collection for the current area_type. elseif SIZE_ADJ_METHOD is Method 2 we add the rounded size adjustment to the rate found in the TOTAL_RATE collection for the current area_type.

Step 11 – Compute Initial Value

In this step we compute an initial value for each items in the collection (VB6 : pv_compute_area_rate).

  • For each item in the area collection do TOTAL_VALUE = TOTAL_EFFECTIVE * TOTAL_RATE

 

Step 12 – Adjust the Total Value (CAMA Adjustment)

  • Scan the records of MA_TABLE and adjust the total value in the area collection (TOTAL_VALUE) for all entries MA_TABLES.setab_rd_code = “a”
  • Use the same logic as in STEP4 to select the MA_TABLES records.
  • If there are no records in MA_PARM_se_area or if MA_PARM_se_area.area_type = “e” then the adjustments are applied for all entries in the collection except for a Special Case (see below)
  • Depending on MATHS and PCT_AMT, cumulate or multiply the value from column_VA into the collection array TOTAL_VALUE.
  • If the _V2 column is used, cumulate also the value from column_V2into TOTAL_VALUE, independently of the MATHS.

Special Case:
If there are no records in MA_PARM_se_area OR if MA_PARM_se_area.area_type = “e”
AND also the MATHS is + or – and the PCT_AMT is ‘a’ (Amount), the adjustment will be applied only once, as following:

  • The value from column_VA will be cumulated into grand_total_amount_adj_add (and not into the collection array TOTAL_VALUE)
  • If the _V2 column is used, cumulate also the value from column_V2 into grand_total_amount_adj_add.

 

Step 13 – Compute the initial building value

The INITIAL_BLDG_VALUE is computed by adding all TOTAL_VALUE from the area collection.

  • Add grand_total_amount_adj_add (step 9) to INITIAL_BLDG_VALUE.

 

Step 14 – Compute the Quality Points

Quality points is a special type of adjustment that is a percentage that adjust the total value.
Scan the records of MA_TABLE for all entries MA_TABLES.setab_rd_code = “q”
Use the same logic as in STEP4 to select the MA_TABLES records.

  • Depending on MATHS (+ or – only), cumulate all the values of column_VA into MA_BUILDINGS.QUALITY_POINTS.
    • If MA_BUILDINGS.QUALITY_POINTS = 0 then set it to NULL and do not compute the adjustment below.

 

  • INITIAL_BLDG_VALUE = INITIAL_BLDG_VALUE * MA_BUILDINGS.QUALITY_POINTS / 100.

 

Step 15 – Compute Overall Adjustment

Overall adjustments are used to to modify the total value of a building according to user-defined criteria such as number of rooms or number

of fireplaces.

Scan the records of MA_TABLE and adjust the INITIAL_BLDG_VALUE for all entries MA_TABLES.setab_rd_code = “t”
Use the same logic as in STEP4 to select the MA_TABLES records.

  • Depending on MATHS and PCT_AMT, cumulate or multiply the value from column_VA into INITIAL_BLDG_VALUE.
  • If the _V2 column is used, cumulate also the value from column_V2into INITIAL_BLDG_VALUE, independently of the MATHS.

 

Step 16 – Compute the Effective Rate

The effective rate is calculated based on the building value divided by the area.

  • If SQUARE_ROOT = “yes” then
    • MA_BUILDINGS.effective_rate = INITIAL_BLDG_VALUE / Square root of (MA_BUILDINGS.total_effective)
  • Else
    • MA_BUILDINGS.effective_rate = INITIAL_BLDG_VALUE / MA_BUILDINGS.total_effective

Format the result to 2 decimal positions.

Step 17 – Compute RCN (Replacement Cost New)

The RCN value is the total value prior to depreciation.

  • If MA_BUILDINGS.nb_units > 1 then
    • MA_BUILDING.TOTAL_RCN = INITIAL_BLDG_VALUE * MA_BUILDINGS.nb_units
  • Else
    • MA_BUILDING.TOTAL_RCN = INITIAL_BLDG_VALUE.

Format the result to 0 decimal positions.

Step 18 – Get Depreciation

The goal of this step is to find the depreciation table to be used in step 19.

Scan the records of MA_TABLE for all depreciation types of structural elements.
Use the same logic as in STEP4 to select the MA_TABLES records.
The processing is specific to each Category MA_TABLES.setab_rd_code:

Depreciation (MA_TABLES.setab_rd_code = “d”)
Standard

  • DEPR_TABLE = MA_PARM_SETAB.DEPR_TABLE if not null and not set by type ‘e’.
  • MAX_ DEPR_PCT = MA_PARM_SETAB.MAX_ DEPR_PCT if not null.

Depreciation Override

  • If Depreciation Override (MA_TABLES.setab_rd_code = “o”), then:
    • MA_BUILDINGS.total_depr_pct = column_VA.
    • MA_BUILDINGS.total_RCNLD = MA_BUILDINGS.total_RCN * (100 -MA_BUILDINGS.total_depr_pct) / 100.
    • NOTE: There should be only one record with this Category, otherwise only the first value will used.

Format the result to 0 decimal positions.

    • Exit to step 21

Depreciation Table Override

  • If Depreciation Table Override (MA_TABLES.setab_rd_code = “e”), then
    • DEPR_TABLE = MA_PARM_SETAB.DEPR_TABLE if not null and not set by type ‘e’.

 

Step 19 – Compute Base Depreciation Percentage

The goal of this step is to compute the base depreciation percentage

We determine the Appraisal base year APPR_BASE (registry DEPR_BASE_YEAR) using the current MA_TABLE.YEAR_ID

  • MA_PARM_DEPR.TABLE_NAME = DEPR_TABLE
  • We evaluate the MA_PARM_DEPR.NUMBER_OF_YEARS = FORMAT (APPR_BASE – MA_BUILDINGS.EYB to ‘000’).
    • If negative we use 0. If MA_BUILDINGS.EYB is NULL we use MA_BUILDINGS.YEAR_BUILT.
  • We evaluate the expression MA_PARM_DEPR.EXPRESSION as DEPR_PCT

 

Step 20 – Adjust Depreciation

The goal of this step is to apply the depreciation adjustment,

Scan the records of MA_TABLE for the depreciation types ‘d’ of structural elements.
Use the same logic as in STEP4 to select the MA_TABLES records.
Depreciation (MA_TABLES.setab_rd_code = “d”)

  • If Non-Cumulative (MA_TABLES.no_cumulative = “-1”) keep the (column_VA) into an array called DEPR_ARRAY, to be applied later in this step.
    • NOTE: When the non-cumulative column is set, then PCT_AMT = ‘p’ and MATHS = ‘x’ (set by GNA), so we don’t need to check these values.
  • Otherwise
  • If MATHS = ‘x’ (Multiplier)
    • if the PCT_AMT = ‘a’ (Amount), multiply with the value: depr_pct = depr_pct * column_VA
    • if the PCT_AMT = ‘p’ (Percentage), multiply with the value and divide by 100: depr_pct = depr_pct * column_VA / 100
  • If MATHS = ‘+’ (Plus) OR ‘-’ (Minus). Add OR subtract the value from column_VA:
    • if the PCT_AMT = ‘a’ (Amount), add/subtract to the value:depr_pct = depr_pct +/- column_VA
    • if the PCT_AMT = ‘p’ (Percentage), add/subtract to the value and divide by 100: depr_pct = depr_pct +/- (DEPR_PCT * column_VA / 100)

Once all code processed compute the non-cumulative depreciations

NON_DEPR_AMOUNT = MA_BUILDINGS.total_RCN * (100 – depr_pct) / 100.

For each element of the DEPR_ARRAY

  • NON_DEPR_AMOUNT = NON_DEPR_AMOUNT – (NON_DEPR_AMOUNT * DEPR_ARRAY(x) / 100)

MA_BUILDINGS.total_depr_pct = 100 – (NON_DEPR_AMOUNT * 100 / MA_BUILDINGS.total_RCN) formatted to 2 decimal positions.
MA_BUILDINGS.total_RCNLD = NON_DEPR_AMOUNT formatted to 0 decimals.
MA_ BUILDINGS.TOTAL_VALUE = NON_DEPR_AMOUNT formatted to 0 decimals.

Step 21 – Compute Site Adjustment

Compute Site Adjustment MA_BUILDINGS.SITE_ADJ_TOTAL
See the site adjustment computation specs document. We will have to decide whether or not we call the site object before completing this step.

Site adjustment is based on the value of MA_BUILDINGS.SITE_NO and should be skipped if NULL (Should not occur as site is mandatory in 6.1)
The total site adjustment cannot produce a negative value if Allow_Negative_Value=False.

The adjustment (MA_BUILDINGS.SITE_ADJ_TOTAL) is calculated as (MA_BUILDINGS.total_RCNLD * MA_SITE.ADJ_BLDG_PERCENT / 100) + MA_SITE.ADJ_BLDG_AMOUNT.

The site adjustment is added to the MA_ BUILDINGS.TOTAL_VALUE.

Step 22 – Compute Neighborhood Adjustment

Compute Neighborhood Adjustment in MA_ BUILDINGS.NBHD_ADJ_TOTAL.
Property Type
The Neighborhood adjustment (MA_PARM_NBHD) is based on the property type (see the section on property type at the beginning of this document).
If NULL and PROPERTY_TYPE_FROM_PC_LEGAL = “yes” then we define the property type as PC_LEGAL_INFO.PROPERTY_TYPE.
IF no record found for a given property type then we search the MA_PARM_NBHD table with a blank property type (15 spaces).
Adjustment

  • The adjustment (MA_BUILDINGS.NBHD_ADJ_TOTAL) is calculated as (MA_BUILDINGS.TOTAL_VALUE * evaluated expression MA_PARM_NBHD.BLDG_EXPRESSION / 100)
  • The nbhd adjustment is added to the MA_ BUILDINGS.TOTAL_VALUE. This value cannot produce a negative value if Allow_Negative_Value=False.

 

Step 23 – Compute Global Adjustment

The goal of this step is to apply a global adjustment. This is an adjustment that is applied after the depreciation is calculated.

Scan the records of MA_TABLE for the global adjustments types ‘g’ of structural elements
Use the same logic as in STEP4 to select the MA_TABLES records.

Read all Global adjustments (MA_TABLES.setab_rd_code = “g”) and for each record:

  • Note: The type ‘g’ only support PCT_AMT = ‘p’ and MATHS = ‘x’ (set by GNA), so we don’t need to check these values.

If no records are found then continue to step 24.

Once all records ‘g’ are read:

  • MA_BUILDINGS.TOTAL_VALUE = MAF_VALUE

 

Step 24 – Compute Final Adjustment

The goal of this step is to calculate the final adjustment

The final adjustment is calculated only if MA_BUILDINGS.FINAL_ADJ_PERCENT is not NULL.

    • Note: A value of zero reset both the final_adj and final_adj_percent to NULL

 

  • MA_BUILDINGS.FINAL_ADJ = MA_BUILDINGS.TOTAL_VALUE * MA_BUILDINGS.FINAL_ADJ_PERCENT / 100

 

  • MA_BUILDINGS.TOTAL_VALUE = MA_BUILDINGS.TOTAL_VALUE + MA_BUILDINGS.FINAL_ADJ.

 

Step 25 – Compute the Final Rounded Value

The goal of this step is to compute the final rounded value.

  • MA_BUILDINGS.TOTAL_VALUE is rounded based on the MA_PARM_MAROUND information (code = ‘bldg’).

For example, if the rounding value is 1000, and the total value is 45678 then the value is 46000. If the rounding value was 100 then it would have been 45700.

Step 26 – Set the Modification Stamp

The goal of this step is to identify that the building value has been computed.

  • MA_BUILDINGS.MODIF_STAMP = MA_MODIF_STAMP.BLDG_STAMP if not null, otherwise we use the current date/time.

 

 

101-ma-compute-Bldg

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.
Loading...

 

Fort Collins (FTC) Upgrade Information

Fort Collins (FTC) Upgrade Information

Upgrade information

905-ftc Upgrade.docx

 

 

905-ftc-upgrade

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.
Loading...